incompleteness procedure

SPRO: Sales and Distribution > Basic Functions > Log of Incomplete Items > Assign
Incompletion Procedures.
In SAP Sales and Distribution (SD), the incompletion log is a tool used to identify
and manage incomplete or missing data in sales documents. It helps users ensure
that all necessary information is entered before proceeding with further
processing, such as saving, printing, or releasing the document

in status groups you can define which function may be carried out for an incomplete
SD document or for the items where a field entry is missing.

can be used for block a document for delivery , billing or pricing and can be
checked on header level whether the general data is complete.

OVA2
VUA2
================================================================================

for pricing
Final = base price- discount+ frieght + taxes
* access sequence img = Basic function > pricing > pricing control > define access
sequences.

pricing img path = IMG - Sales and distributions > Basic function > pricing >
Pricing control > define and assign pricing procedures> Maintain pricing procedure.

Access Customizing: Enter transaction code SPRO in the SAP Easy Access screen or
the command field to access the SAP IMG (Implementation Guide).

Navigate to Pricing Procedure Configuration: Follow the menu path:

SAP Customizing Implementation Guide -> Sales and Distribution -> Billing ->
Pricing -> Define Procedures -> Pricing Procedures.

what are the basic conditons of pricing ?

Base price , discount , tax , freight charges

what are condition techniques?

condition technique is the procedure where each pricing procedure has a condition
type.condition tech has four elements namely condition types, condition tables ,
access sequence and pricing procedure.

route determiantion

Go to: SPRO → IMG → Logistics Execution → Transportation → Basic Transportation

Function → Routes → Define Routes → Define modes of transport → Execute.
Route determination in SAP SD can be configured to determine the transportation
route automatically based on various criteria such as shipping point, loading
group, transportation group, and transportation zone. In this transaction, you
define the route determination criteria and rules.

tcode OVTC to define route , OVRF to define route determination

Plant determination
PLANT DETERMINATION IN SALES ORDER (SAP SD)
7 September 2020|Customer Master, Material Master, Plant Determination, SAP Basic
Concepts
Plant determination takes place in the sales order at 3 different levels based on
priority:

1. Plant from Customer-material information record

2. Plant from Customer master

3. Plant from Material master

Logic for Plant Determination:

Step 1: Plant from Customer-material information record (VD51/VD52/VD53):

If it is maintained, it will take the plant and pass it in the sales order line and
system will not
go to the next step of the determination

Else, System will proceed with step 2.

Step 2: Plant from Customer master (VD01/VD02/VD03):

If it is maintained, it will take the plant and pass it in the sales order line and
system will not go to the next step of the determination.

Else, System will proceed with step 3.

Step 3: Plant from Material master (MM01/MM02/MM03):

If it is maintained, it will take the plant and pass it in the sales order line

Else, order will be incomplete and plant need to be passed manually.

1)RAD - Revenue account determination

revenue account tcode = VKOA
* it is an interface between SD and FI modules

Sales Order: A customer places an order for electronic gadgets through Sales
Organization SO1 and Distribution Channel DC1. The ordered items belong to Material
Group MG1.
Revenue Account Determination:
The system checks the condition records based on the key fields (sales
organization, distribution channel, material group).
It finds a condition record that matches SO1, DC1, and MG1.
The condition type associated with this record specifies that revenue should be
posted to Account1.
Therefore, when the sales order is invoiced and revenue is recognized, the system
automatically updates Account1 in the General Ledger.
tables

1) sales document types

VBAK: Sales Document: Header Data
VBAP: Sales Document: Item Data
VBEP: Sales Document: Schedule Line Data

LIKP: SD Document: Delivery Header Data

LIPS: SD document: Delivery: Item data

VBRK: Billing Document: Header Data

VBRP: Billing Document: Item Data

2)COPYING CONTROL
In SAP Sales and Distribution (SD), various copying control tables (VTLA, VTAA,
VTFL, VTFA, VTFF, VTAF) define how data is transferred between different documents
during the sales and distribution process. Let's explore each one with real-life
examples:

1.VTLA - Delivery: Order Item > Delivery Item**:

- Real-life example: ABC Electronics receives a sales order for 100 laptops from
a customer. When creating the delivery for this sales order, the system needs to
copy information such as the product code, quantity, pricing conditions, and
delivery dates from the sales order item to the corresponding delivery item. This
ensures that the delivery reflects the details specified in the sales order
accurately.

2.VTAA - Delivery: Order Header > Delivery Header**:

- Real-life example: Continuing with the previous example, in addition to
copying item-level details from the sales order to the delivery, the system may
also need to copy header-level information such as the customer's address, shipping
instructions, and payment terms from the sales order header to the delivery header.
This ensures consistency between the sales order and delivery documents.

3.VTFL - Billing: Delivery Item > Billing Item**:

- Real-life example: After the goods are delivered, ABC Electronics needs to
generate a billing document to invoice the customer. The system should copy
relevant information such as the delivered quantities, pricing conditions, and tax
details from the delivery item to the corresponding billing item. This ensures that
the billing document accurately reflects the goods delivered to the customer.

4.VTFA - Order: Order Item > Order Item**:

- Real-life example: Sometimes, a customer may request changes to an existing
sales order, such as adding or removing items, updating quantities, or changing
delivery dates. In such cases, the system copies relevant information from the
original sales order item to the revised sales order item, ensuring that the
updated order reflects the customer's requirements accurately.

5.VTFF - Delivery: Delivery Item > Delivery Item**:

- Real-life example: If a delivery needs to be split into multiple shipments due
to logistical reasons, the system may need to copy information from the original
delivery item to the new delivery items created. This ensures that each delivery
item contains the necessary details for the shipment, such as product codes,
quantities, and shipping instructions.

6. VTAF - Delivery: Order Header > Billing Header**:

 - Real-life example: When creating a billing document based on delivery, the
system may need to copy header-level information such as the customer's address,
shipping instructions, and payment terms from the sales order header to the billing
header. This ensures consistency between the sales order, delivery, and billing
documents.

3) DS = Scheduling agreement
IN , QT , OR

4)Delivery document type

LF = Delivery with order reference
LO = without order reference
BV = del cash sales
LP = delivery for project
LR = Delivery for returns

5) business partner = BUT000

SE16N = to check any tables in SAP

BOM

logistics > master data > products > bills

BOMs are exploded in sales document , several materials can be sold as set of
packages
each seperate material can be configured individually
CS01

ERLA for main item

LUMF for sub item

======================================================================

Output determination

step 1 = Maintain output types ( trans= V/30 or Sales & Dist> Basic function >
Output > output determination > output proposal using the condition technique >
maintain output determination for sales doc > maintain output types

select and copy BA00 t0 ZA00

step 2 = access sequence 003( sales org/customer)

to change the transmission medium = 6(EDI) , partner fucntion = SP , Time= 4

step 3 check assign output determination procedures > allocate sales document
header for output procedure

======================================================
text determination : VOTXN

SAP Customizing implementation guide → Sales and Distribution → Basic function →

Text Control → Define and assign text determination procedure.
Business partners involved in a sales transaction often exchanhe various
instruction and information
like shipping , packing , delivery
we can maintain customer master records and also sales document at the header and
item

steps 1: defining the text type for sales document header

step 2 : text procudure
step 3:assign text proc to sales doc type
step 4 :defining text type for delv.header

step 5: setting up an access sequence to link both documents order and delivery

final step = assign text determination procedure to delivery doc type.

===================================================================================
============================================
Cash sales : pays imediately
sales from plant
sales Doc type : BV
Immediate Delivery : switch checked
standard item category : BVN
Delivery type : BV
Delivery item category: BVN
Billing type : BV( order related billing)

in case of free goods for cash sales item category is BVNN with higher item
category BVN

Rush order:
sales from plant
sales Doc type : RO
Immediate Delivery : switch checked
standard item category : TAN
Delivery type :LF
Delivery item category: BVN
Billing type : F2( delivery related billing) It allows companies to bill customers
only after the goods have been physically delivered.

===================================================
Material determination : VB11 substituting of material that is available