SAP Logistics

 At times, there is a a situation where the business requires a release strategy to be triggered if there are any changes to the purchase order document value either increase or decrease of document value. In general, standard SAP does trigger a release strategy if there is an increase in document value but however, if there is any decrease in the document value system doesn't trigger release strategy. This post covers the technical changes that we have to make to trigger release strategy if there is any decrease in the document value to that of the released amount. Release strategy at purchase order level is triggered based on the function module - 'ME_REL_STRATEGIE_EKKO' so we are required to make changes in this FM to accomplish this requirement. Perform reset is used to reset the release strategy post-release of the document. IF  cekko -gnetw  GT f1 .            PERFORM reset      ...

  At times, we will have a table and requires to find a transaction for it.  In this situation, use the table - 'TSTCP' and pass the table name *XXXX* in the parameter field. Then click on execute to display the transaction for the table.

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          ...

Characteristics values for an object cannot be extracted from the database table directly. Hence we are required to follow the below steps to fetch the data : First, pass the material into table KSSK and fetch object number Pass the object number into the KLAH table to fetch the class Pass the class into a functional module: 'CLAF_CLASSIFICATION_OF_OBJECTS' to fetch the characteristics and characteristics values.