Incompletion Log in SD

In general

Incompletion Log ensures that all required fields in a document are populated. Incompletion
procedures can be configured to (1) raise no messages, (2) raise a warning message, or (3) raise
an error message.

If configured with no warning message, the system will indicate the sales document is
incomplete and offer an option to complete missing data upon save. The incompletion procedure
determines to what extent further processing of the document is allowed and if subsequent
documents can be created. If a document is incomplete, it cannot be referenced.

Incompletion procedure

An incompletion procedure groups the fields together that must be checked for completion. If
any of the fields are blank, the document is incomplete. Incompletion procedures can be assigned
and maintained at various levels and for various document types:

Sales header (different procedures can be assigned to different document types)

Sales item (item categories can contain different procedures)

Schedule line (each can contain different procedures)

Partners (can maintain different procedures for each partner function)

Sales activity

Delivery header

Delivery item

To display the procedures run transaction OVA2 or use the IMG path > Sales & Distribution >
Basic Functions > Log of Incomplete Items > Define Incompletion Procedures.
Incompletion procedures are assigned to each document type via transaction VUA2 or use IMG
path > Sales & Distribution > Basic Functions > Log of Incomplete Items > Assign Incompletion
Procedures > Assign Procedures to Sales Document Type. The incompletion procedure can be
viewed in document configuration (VOV8) but can only be changed here. To prevent the
document from being saved if any fields are incomplete, check the box IC-dialog. In example
below document type CR (Credit Memo Request) cannot be saved if any fields in incompletion
procedure 14 are not populated.

Sales - Header Group (A) uses incompletion procedure 14 which contains the following fields:
The Table, Field Name and Description fields above are self explanatory. Screen field is the
function code (Fcode) the system uses to navigate from incompletion log to the screen where
field is missing. If no entry is made here, you cannot branch to correct screen to complete
missing data. See Note 422132.

The available Fcodes for sales header screens are:

<BLANK> No automatic screen selection available

KBES Sales: Header - PO data

KBUC Sales: Header - Financial accounting
KDE2 Sales: Header - Shipping
KDE3 Sales: Header - Billing document
KGRU Sales: Header - Additional data A
KKAS Sales - Item proposal: Header - Business data
KKAU Sales: Header - Sales
KKNT Sales: Header - Product allocation
KKON Sales: Header - Conditions
Sales - Independent Requirements: Header -
KKPB
Business data
KPAR Sales - Header - Partner
KPAR_SUB Sales: Header - Partner (Subscreen)
KSTA Sales: Header - Status
KTEX Sales: Header - Texts
KTPR Sales: Account determination analysis
KVER Sales: Header - Extras - Sales data
KZKU Sales: Header - Additional data B
WPA1 Sales: Header - Partner - Detail
WUMA Sales - Delivery order: Header data

Status group indicates whether system will record a status message in item or header status
screens in sales document. Path: transaction OVA0 or IMG > Sales & Distribution > Basic
Functions > Log of Incomplete Items > Define Status Groups.

Warning indicates if a warning message is received if no entry is made. Can only be used for
fields in sales order. If this box is not checked but fields are incomplete, upon saving the
document you will be brought to incompletion screen where you can branch to each missing
field.

Sequence refers to the order the missing fields will be processed in the incompletion log. The
first field to be procesed is given the lowest value but fields with no value are processed last.

Status groups

Status Groups are assigned to specific fields in the incompletion log and control further
processing of the document. It is possible to specify that if field X is missing, further processing
is allowed, but if field Y is missing, no further processing is permitted. Further activities of the
document can be blocked, for example, the sales document can be saved but a subsequent
document for delivery, billing, or pricing can be blocked. Status groups can be defined in
transaction OVA0.

Standard Status Groups include:

General: Checks status of general fields assigned to this status group in the incompletion
procedure. General fields can include PO Number, document date, etc.

Delivery: Setting this status in the status group and assigning the status group to a field in the
incompletion procedure causes the sales document to be incomplete and may prevent creation of
delivery document, e.g. if the plant or shipping point is missing.

Billing: Setting this status causes the sales document to be incomplete for further processing and
may prevent the creation of a billing document, e.g. if the terms of payment is blank in the sales
order.

Pricing: If pricing is not carried out, the sales document is incomplete and may prevent
subsequent billing documents from being created.

Goods Movement: System determines the status of the goods movement data by checking the
fields that comprise this status group in the incompletion procedure. For example, you can
specify that the item data of a delivery is incomplete for goods issue if the quantity picked is
missing. If the quantity
picked is not specified during delivery processing, the system issues corresponding status
message. This is only valid for shipping documents.

Picking: You can specify that the item data of a delivery is incomplete for picking if the serial
numbers have not been assigned, and the system issues corresponding status message. This is
only valid for shipping documents.

Packing: You can specify that the item data of a delivery is incomplete for packing if the
external delivery identification is missing. If the external delivery identification has not been
specified during delivery processing, the system issues status message. This is only valid for
shipping documents.

This table indicates whether the system records a status message in the header and item status
screens of sales documents. If you mark this status for a particular status group, the system
determines the status by checking the fields assigned to the status group in the relevant
incompletion procedure. If some or all of the fields are missing information, the status message
says that the function is partially incomplete or incomplete. If all the fields are filled, the status
message will say complete.

Configuration

1. Set up Status Groups (OVA0).

 2. Define procedure (OVA2).

3. Assign status group to fields (OVA2).

4. Assign procedure to various document types as follows:

A. Orders (VUA2)

B. Deliveries (VUA4)

C. Items (VUP2)

D. Schedule Lines (VUE2)

E. Partners (VUPA)

F. Sales Activities (VUC2)

5. Set Error or warning message (VUA2).

6. Test expected results.

Important transactions

OVA2 Define incompletion procedure

VUA4 Assign incompletion procedure to delivery type
Assign incompletion procedure to Sales document
VUA2
Header
Assing incompletion procedure to Sales item
VUP2
category
Assign incompletion procedure to Schedule line
VUE2
category
VUPA Assign incompletion procedure to Partner functions
VUC2 Assign incompletion procedure to Sales Activities
OVA0 Define Status groups
V.02 List incomplete sales orders
VUA2 Set warning or error message on document save

Important tables

VBUV Incompletion log - Sales documents

VBUK Header incompletion
VBUP Item incompletion
TVUVG Groups
TVUV Procedures
TVUVF Fields
TVUVS Status groups
TVUVFC Fcodes
V50UC Incompletion log - Deliveries
V50UC_USER Incompletion log - Deliveries - Enhancements
FMII1 Funds Management Account Assignment Data

Steps for Incompletion Procedure

In an incompletion procedure, you can group together the fields that are to be checked for
completion. If you have not entered data in one of the fields in the document, the document is
incomplete. Depending on the status group you can block certain subsequent activities for the
document.

Regarding Incompletion Procedure

( Incompletion Procedure is exclusively for SAP-SD )

Places where we can maintain the Incompletion Procedure;

1. Sales Document Header.

2. Sales Document Item Category.
3. Schedule Line Category.
4. Delivery Document Header.
5. Delivery Document Item Category.
6. Sales Activity.
7. Partner Function

The steps are as follows;

1). Create Status Group

( Status Group is nothing but the area you want to get effected if end user missed some
entries ).
The T.Code to create Status Grp is OVA0.
2). Define Incompletion Procedure by selecting fields as per your Client's specification.
Like for example in delivery Document we can say that Ship to party is must so in Sales Order
we have to make the Incompletion Log that include Ship to party than only we can create
Delivery Documents.
T.code is OVA2. Here you can define the massage type if you miss some entries like warning
msg., error msg etc....as per the importance of the fields.

3). Assign Incomp.

Procedure to required field like for Sales Doc., the T.code is VUA2 etc..
e.g. Incom. pro. 11 is for Sales Order so you have to assign that 11 via VUA2 to Sales Order.

How to identify the screen name in Incompletion Procedure?

First you have to identify in which particular tab that incompletion log should work for you in
sale order.

For example, if you want a control at header level in sale order for the field Pricing date, you
have to check which table and field the value will be stored. In this case, it would be VBKD
table and PRSDT field. As I said above, this will come in tab "Sales".

So now in OVA2, after selecting "Standard Order" double click on "Fields". There maintain the
above table and field and in the Screen tab, just press F4 so that you can see "Sales: Header -
Sales". This would be the appropriate screen for the control you want. Like this, you have to
assign accordingly.

Procedure To Do Incompletion Log

What are the steps to do incompletion log?

For sales related functions:

SPRO --> Sales & Distribution --> Basic Functions --> Log Of Incomplete Items -->

1. Define Incomp. Proc.

2. Assign Incomp. Proc.
3. Define Status Group

For shipping/ delivery functions following path:

SPRO --> Logistic Execution ---> Shipping ---> Basic Shipping Functions ---> Incompletion
Control For Deliveries ---->

1. Define Incomp. Proc.

2. Assign Incomp. Proc.
3. Define Status Group

Please find the example to put "Pricing date" as mandatory in sales order.

1. Spro --> sd --> basic functions ---> Log of Incomplete Items --> Define Status Groups

Here create your status group as per requirement and

2. Spro --> sd --> basic functions ---> Log of Incomplete Items --> Define Incompleteness
Procedures

In this step select the entry "A" and double click on procedures and select procedure "11" and
double click on fields and select new fields and then give the table as" vbak" and field name as
"prsdt" and assign screen and status group and put warning and save.

2. Spro --> sd --> basic functions ---> Log of Incomplete Items --> Assign Incompleteness
Procedures --> Assign procedures to the sales document types

In this step assign the incompletion procedure(11) to your sales document type and save.

and now create a sales order and save the sales order without the pricing date then system will
give the warning message.

In this way, you can configure the incompletion log.