Answer Posted / vaibhav

Incompletion procedure: As sales, delivery, billing data is recorded into the system through the data
entered in the sales, delivery and billing documents. It is important that specific controls are maintained. The data
that has been maintained in the sales document passed through delivery document and finally billing document.
Billing document also need some important data to be maintained. So that if we forget to maintain the data and
saved the document we may have to face problems during sub – sequent document processing.
So as to remain us about missing of this valuable data SAP provided this “incompletion log” facility. Its
main function is to highlight the missing data
Configuration settings
Define status group: Transaction code: OVA0
Path:
 IMG
 Sales and distribution
 Basic functions
 Log of incomplete items
 Define status groups
 Choose existed status group [01]
 Select it and click on copy as icon
 Rename
 Save and Exit
Incompletion process inspects the objects such as line item and also inspects specific fields that have been
maintained or not. If data did not maintained in the system, then system told how to respond. That is does/does not
give warning message and what extent does it allow further processing of the document.
The incompletion log cannot register what data is maintained in the specific field and compare it to the data that
should be in the specific field.
Ex: VBKD – BSTKD (purchase order number) – KBES 
We can create incompletion log for the following objects like: Sales document header, Sales document
item, Sales document schedule lines, etc.
First we have to define “status group” by using OVA0 transaction code. Status groups are assigned to
specific fields in the incompletion log. So it is possible to specify in a sales document like:
 A: It may be incomplete but not prevent the document processing further while.
 B: It may be incomplete and the case of sales documents being blocked for further processing.
Status group settings:
 General: If you set it to the status group to a field in the incompletion procedure that will cause sales
document is incomplete. But it will allow the document to be processed further.
 Delivery: It will cause the sales document to be incomplete for further processing. That means creation of
the delivery document will not prevent the processing of the billing document. But it affects when saving the
billing document.
 Billing document: It will cause the sales document and delivery document to be incomplete for further
processing. That is the creation of the billing document should the associated field not be filled.
 Price: It will cause the sales document to be incomplete for further processing should pricing not have been
carried out.
 Goods movement: It will cause the delivery document to be incomplete for further processing. That for
goods movement should a field not be filled such as quantity picked.
 Picking: It will cause the delivery document to be incomplete for further processing. That is picking should a
field not be filled such as serial number.
164
 Packing: It will cause the delivery document to be incomplete for further processing that is packing, should a
field not be filled such as quantity picked.
Define incompletion procedure: Transaction code: OVA2
Path:
 IMG
 Sales and distribution
 Basic functions
 Log of incompletion items
 Define incompletion procedures
 Select group “A” – [sales document header]
 Click on procedures control button under dialog structure
 Go to change icon
 Select incompletion procedure [11 – sales orders]
 Click on copy icon (or) go to new entries
 Define your incompletion procedure
 Select your incompletion procedure
 Click on fields control button
 Go to new entries and maintain the data like below:
Table Field name Warning option Screen
VBAK AUGRU  KKAU [This is for order reasons]
 Save and Exit
We can see the order reason is relevant as incomplete.
The assigned screen KKAU is the screen that the system takes the user through in order to complete the missing
data.
Status group number is [10] (our number which we defined previous step) which we defined as a deliver and
delivery will render the document incomplete for further processing.
So that we have to create incompletion procedures for order reasons and assign it to the sales document header.
Table Field name Warning option Screen
VBKD VSTKD  KBES [This is for purchase order number]
Assign incompletion procedure: Transaction code: VUA2
Path:
 IMG
 Sales and distribution
 Basic functions
 Log of incomplete items
 Assign incompleteness procedures
 Assign procedures to the sales document types
 Choose sales document type OR from position button
 Assign our incompletion procedure
With or without IC – dialog OR  You can leave the blank
If you mark this field and then try to save a sales document in which information is missing, the system advises you
that the document is incomplete.
 Save and Exit
 Go to VOV8
Check incompletion procedure field in transaction flow section
 Save and Exit
NOTE: Item category and schedule lines are also same.
Important notes: We can create incompletion logs for the following:
1. Sales document header data [Incompletion group = A].
2. Sales document item data [B].
3. Sales document schedule line data [C].
4. Sales activity data [F].
5. Partner data in sales documents, deliveries and sales activities [D].
6. Delivery header data [G].
7. Delivery item data [H].
NOTE: The tables that can be used in the maintenance of the incompletion procedure are as follows:
VBKD = Business data
VBAK = Header data
VEDA = Contract data
VBAP = Item data
VBKA = Sales activities
VBEP = Schedule line data
VBPA = Partner
LIKP = Delivery header data
LIPS = Delivery item data

what are the sales document types in sap? What is the configuration step to define sales document type in sap sd?

1121

---

What is availability check? When and at what level is availability check carried out?

1099

---

which screen support consultant uses in support project?

2272

---

pl tell me 3/4 gaps peculiar to any one industry with there solution plz its very urgent

2149

---

In case of third party sales what would trigger for the automatic creation of pr or po?

1247

---

How do you integrate sd with mm, fico?

1222

---

What are the sap erp release, enhancement pack and support pack requirements for integrating with sap tm? : transportation management

1269

---

Do you have any link for customer master and credit management?

1132

---

I have advance payment scenario where customer want advance payment cannot be used against another sales order and against any credit limit. Let me put one example. Customer X is having credit limit of 1000 USD, if my client is received customized product order then he will take advance for this special order but customer X is already enjoying credit limit of 1000 USD. In this scenario my client wants advance payment received cannot use against any sales order and against any credit limit. If I will post advance payment in F-29 then customer credit exposure will decrease against credit limit in FD32 which will affect normal sales order credit limit. Here customer does not want to utilize advance payment against credit limit of customer which is use for normal sales order. Please suggest

2061

---

What is the difference between make-to-order production with and without assembly processing?

1185

---

I have a shopping mall. If a customer comes to my mall and if he purchase or not anything I give him pen free. How we map it in sap?

2153

---

What are the different types of partial agreements available in sap sd ?

1157

---

Change of sales document a sales document type of a sales order can be changed after getting saved. How do you do this?

1024

---

Explain the 'sales organization.' How it is assigned to a 'plant'?

1134

---

Can anyone have any experience with the fashion version of it?

918

---