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

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...