hi,
SALES INCOMPLETION LOG / INCOMPLETION LOG:
An incompletion proc inspects the object, such as a sales doc line item & inspects specific fields in order to see if data has been maintained in these fields. Should data not be maintained in these specific fields, the system is told how to respond, i.e., does it or does it not give a warning message & to what extent does it allow further processing of the doc?
The incompletion log cannot register what data is maintained in the specific field & compare it to the data that should be in the specific field.
One can create incompletion logs for the following:
Sales Doc Header Data: VBAK
Sales Doc Item Data: VBAP
Sales Doc Schedule Line Data: VBEP
Business Data: VBKD
Customer Data: KNA1 (general data: CMD)
Sales Area Data: KNVV
Delivery Header Data: LIKP
Delivery Item Data: LIPS
SPRO- IMG- SD- Basic Functions- Log of Incomplete Items:
• Define Status Group: OVA0
• Define Incompletion Procedures: OVA2
• Assign Incompletion Procedures: VUA2
Define Status Groups:
First, one needs to define the status groups. This status groups are eventually assigned to the specific field in the incompletion log. Thus, it is possible to specify in a sales doc that field A may be incomplete, but not hinder the doc from being processed further, while field B may be incomplete and be the cause of the same doc being blocked for further processing. The status groups will be assigned to field ‘status’ in ‘define incompletion proc.
The statuses group settings are:
Status Group General Delivery Billing Doc Price Goods Movement Picking Packing
Define Incompletion Procedure: OVA2
By selecting Group A: Sales Header, Select Procedures, (& then click on display button), you can see incompletion procedures. Then select incompletion group line item & go to fields
Procedures
Fields
Incompletion Group
Group Description
A Sales header
B Sales item
C Sales schedule line
D Partner
F Sales activity
G Delivery header
H Delivery item.
Error Group A
In Proc Description
10 Inquiry / quotation
11 Sales header
12 Outline agreements
Note that incompletion proc are assigned to various sales doc types & sales doc item categories
It is not possible to create your own error group such as a copy of Group A: sales header
You can create a copy of the assigned procedures to the error, such as a copy of the standard procedure: 11- sales order.
To create your own incompletion proc, select the change display button. Then go to new entries.
One can see the table names with assigned field name & description of that field.
Table Name Field Name Descp Screen Status Warning
VBKD BSTKD P.O. No KDES 02 Flag on the Box
The assigned screen “KBES” is the screen that the system takes the user through in order to complete the missing data. Assigned to the P.O. No is an indicator saying the system must display a warning message in the sales order at the time that the system checks to see if the data is maintained for the purpose of incompletion log. Should no warning indicator, be assigned the system will merely indicate the sales doc is incomplete & offer an option.
Assign Incompletion Procedure to Sales Doc Types: VUA2
One can assign the procedure to each object that resembles an incompletion error group, such as Group A: sales header. You can assign the proc for e.g. IL to OR (sales doc type)
Sales Doc Type Procedure Incompletion Message
OR IL Flag It on
Should one not require the pop up box, but merely allow the doc to be automatically saved, even though it will still be blocked for further processing, if incomplete. One can select the indicator “incompletion message”. If you mark this field & then try to save a sales doc in which info is missing, the system advises you that the doc is incomplete.
• For certain types of documents like rush orders, complaints, you can leave this field blank.
regards
sadhu kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.