Skip to main content

Incompletion Log functionality

This is used to instruct system, On how to respond in case of any sales document, delivery document or Billing document should be regarded as incomplete.

Below are the areas in which we can maintain incompleteness procedure.

  • Sales document header data
  • Sales document item data
  • Sales document schedule line data
  • Sales activity data
  • Partner data in sales documents, deliveries and sales activities
  • Delivery header data
  • Delivery item data

Configuration settings :
  • Define Status Group
  • Define Incompleteness procedure
  • Assign incompleteness procedure to document type
Status Group:

This states the function at which we can block a document like delivery, pricing, billing, picking, and packing.

if we enable delivery field in the status group then in case of an incomplete document then the system will restrict business from the creation of delivery document until the sales document is complete.

Likewise, we can maintain block at different levels as mentioned above.


Define Incompleteness procedure

In sales document, incompleteness check can be maintained at header, item and schedule line level.

Below is the elucidation of incompletion fields listed :

Table and Field Name  - Enter the technical name of the field which we are looking forward to maintaining as a part of incompletion log.

Screen 

Select the screen to which the mentioned field belongs to.



Status :

Assign the status group created against each field

Warning :

If we select this field system will give you warning when user doesn't make an entry in the required field

Sequence :

This gives the sequence need to be followed during display of the incompletion log in the document level.



Assign Incompleteness procedure

In this assignment of incompleteness procedure to document type will be done.

IC - Dialog :

If the business requires having a provision to save the document for the time being even if the document is incomplete then we need to enable this field.

Once enabled, System will display a pop up with a provision to either save or complete the document.




Comments

  1. Thank you for providing useful post about incompletion log functionality and its giving best info for the students about how to respond in case of any sales document, delivery document or Billing document should be regarded as incomplete.Attend now SAP SD Online Training in Hyderabad to learn SAP SD skills.

    ReplyDelete

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...