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              USING e_frgst e_frggr                   e_frgzu e_frgkz e_frgrl .           e_

  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                      Usage VEPVG    Delivery Due Index                Delivery Due List (V

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.

FM: WS_LM_QUANTITY_ADD is used for checking the weight and volume of an outbound delivery to calculate the delivery weight, we have to keep the FM in the loop. FM: BAPI_OUTB_DELIVERY_CREATE_STO is used to create outbound delivery for a purchase document in the stock transfer process ensure to use COMMIT FM post calling the BAPI to create an entry in the database Table VBSS - to get group number based on the sales document    FM: WS_PICK_WAV_UPDATE_PREPARE' is used for the wave picking  FM:  RV_SHIPMENT_VIEW is used for viewing shipment FM: 'SD_DELIVERY_ASSIGN_TO_SHIPMENT' is used for the assignment of delivery to shipment FM:  SD_SHIPMENTS_SAVE is used for creating the shipment FM: BAPI_SHIPMENT_CHANGE is used for changing the shipment FM:  CS_BOM_EXPL_KND_V1 is used to fetch sales order BOM items

Output condition records are crucial for business in the case of interfaces. Any changes to it will have an impact on the receiver system not receiving the data. Standard SAP hasn't given any feature to capture records directly but however, SAP has given a provision to do so. Below is the process to be recommended by SAP through SNOTE: 2967998 - No changelog available for OUTPUT condition records Check the indicator for "Log Data Changes" for table NACH in SE11. (-> click button for Technical settings) This can be set. You can develop your own query or Abap to read out the changes made in an output condition record. Use this information as a source: If you create/change an output condition in MN04/MN05, an entry is written into the table B02* (e.g. B026) and into table NACH. The two tables are linked with B026-KNUMH=NACH-KNUMH. Read table CDHDR where OBJECTCLAS = COND_OC and OBJECTID = NACH-KNUMH = B026-KNUMH OBJECTID is stored in this format: 0000000001BEF026NEU where

Standard SAP provides routine to maintain at output procedure level to trigger output type when post goods issue is completed.  But however, SAP hasn't given any routine to trigger output when packing status is incomplete. To enable this functionality, we have to create a new custom routine in the 9* series with the below logic and assign it to the respective output type in the output determination procedure. IF  KOMKBV2-PKSTK = 'C' AND ( KOMKBV2-KOSTK EQ 'C' ).     SY-SUBRC = 0.   ELSE.     SY-SUBRC = 4.   ENDIF.