In this blog post you will get to know how to add field as mandatory in sales document - Incompletion Log. 

 

Usually in sales process most of the customers uses In-completion log for their business requirement to ensure that all the mandatory fields are updated in sales document or Customer, it is observed that below are the common issues faced by many customers

 

Ø  How to add the field that are not available in standard Incompletion procedure

Ø  Field is added than too it is not updating in Incompletion log

Ø  Warning and Information message not working for BADI SD_SLS_CHECK_BEFORE_SAVE

 

 

Blog Applicability

 

SAP S/4HANA Cloud Release

2005

 

Target Audience

Business Users, Key Users, Consultants

Target Industry

Any

Business benefit

 

·       Ease of checking all the mandatory fields in sales document

·       Faster execution sales process as all required information is available

·       Business critical checks can be applied by making these fields as mandatory

·       Reports can be extracted as all required fields are already updated in document

What is Incompletion Procedure?

Process to check the sales documents is regarded as complete and how system to respond when you create a document

We can check the incompletion in following level, configuration ID - 101189

 

Note

Note that different procedures can be assigned to the partners in the documents if they have different partner functions. However, the required data for a partner function is relevant for all procedures.

Pricing can be checked via PRSOK field in the incompletion procedure for sales items.

Text can be checked via Text Procedure

Special features in the incompletion log for shipping processing

Dynamically determined document characteristics, For example, the log may indicate that the batches of an item have not been assigned completely, so you may have to change the main item quantities or the split quantities.

Follow-up activities that you can control, such as picking, goods movement (posting goods issue), and packing (deliveries only).

If incompletion field is not updated, when processing a sales document, you will receive a warning and order can be saved but block for subsequent function, based on status group

The relevant specifications for warnings and blocks are defined in the incompletion procedure.

Issue details

How to add the field that are not available in already defined incompletion procedure

Solution

Go to Fiori App Manage your Solution , find In Configuration ID – 101189

 

Click Configure

Example Storage location needs to be added as Item incompletion field check , select Group as - Sales – Item and Click on procedure

Copy standard Item and create Z1, with all entry copied or modify as required and add Storage location

Assign the same to Item cat – 101198

Now create sales order and check, system will respond as below , if sales order is created without Storage location

Save the sales document.

 

In the same way Custom field added to sales document header or item table can also be added in the incompletion procedure, to be checked in sales document incompletion log

 

Issue details

 

Field is added than too it is not updating in Incompletion log

Solution

 

Common reason for the same is Incompletion procedure is not assigned with correct GROUP

 Example: Group “B” sales - item and the same is assigned with table VBAK (example vbak-bstdk) to be check as shown below

 

Group should be relevant to check the incompletion check.

 

Issue details

Warning and Information message not working for BADI SD_SLS_CHECK_BEFORE_SAVE

Check is applied to at sales document save via BADI SD_SLS_CHECK_BEFORE_SAVE, with Warning “W” and Information “I” message is not working

 

Solution

 

Usually to cater certain business requirement, check/coding is done with W or I message in BADI SD_SLS_CHECK_BEFORE_SAVE, and is not raised during processing.

As cloud BADI is used to abort the transaction and as alternatively option 'Sales Item Check' can be used.

Note:  2820950 - Message type W and I does not work for BADI SD_SLS_CHECK_BEFORE_SAVE

 

Related SAP Note / Links

 

2820950 - Message type W and I does not work for BADI SD_SLS_CHECK_BEFORE_SAVE

 

https://help.sap.com/viewer/a376cd9ea00d476b96f18dea1247e6a5/2005.500/en-US/66a2f4107e754be68a458408eb332d91.html