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 subsequent document processing.
So as to remind 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 is not maintained in the system, then system is told how to respond i.e., does / does not give warning message & 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 & 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.
SD Material
163
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.
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 – Standard 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
SD Material
164
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 line 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
VBAP = Item data
VBEP = Schedule line data VBKA = Sales activities VEDA = Contract data
VBPA = Partner
LIKP = Delivery header data LIPS = Delivery item data
SD Material
165