SAP Logistics

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