Skip to main content

[SD] sales orders not getting displayed in delivery due list

Once a sales order is created and pending for delivery then the system will update in delivery due list table VEPVG, which the system uses to fetch and process pending deliveries.

 There will be some situations where the delivery due list table is not updated even though the sales order is not blocked and pending for delivery this will result in missing the sales orders for delivery creation. This issue will occur due to the incorrect way of handling user exits when X* and Y* tables are manipulated before save of the sales documents.

 In this situation, program 'RVV05IVB' is used to reorganize delivery due list entries and fix the inconsistency 

SNOTE: 128947 - Correction of SD document indexes with RVV05IVB

 Report RVV05IVB is available in your system for reorganizing or correcting incorrect SD document indexes. The report can correct the following index tables:


Table    Contents                      Usage

VEPVG    Delivery Due Index                Delivery Due List (VL04)
VKDFS    Billing Initiator                    Billing Due List (VF04, VF24)
VTRDI    Shipment Planning Index          Shipment processing (VT01/VT04)
VRSLI Receipt of Material from Deliveries  SC Stock Monitoring (ME2O)
VAKGU    Sales Index: Quotation Validity List of Quotations (VA25)
VAKPA    Orders by Partner Function     List of Sales Orders (VA05)
VAPMA    Order Items by Material            List of Sales Orders (VA05)
VLPKM     Sched. Agrmnts by Cust Mat. List of Scheduling Agreements (VA25)
VLKPA    Delivery by Partner Function     List of Deliveries (VL05/VL06)
VLPMA    Delivery Items by Material       List of Deliveries (VL05/VL06)
VRKPA    Bills by Partner Functions       List of Billing Docs (VF05)
VRPMA    Billing Items per Material           List of Billing Docs (VF05)

Comments

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).
4 comments
Read more

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.
Post a Comment
Read more

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...
1 comment
Read more