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

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.

Ideally Storage Location is determined through standard SAP functionality maintained at delivery type level based on the below criteria : Shipping point + Plant + Storage Condition (MALA) Plant + Situation + Storage Condition (RETA) but however, if business requires to deviate from standard SAP criteria then we have to leverage the below exit to accomplish the requirement : V02V0002  EXIT_SAPLV02V_002

 RKANBU01 - Transfer Purchase Requisition and Purchase Order Commitments RKACOR04 - Adjustment Betw. Line Items and Totals Records (Act.Cost + Commitment) CJEN - Reconstruct Project info database CJBN -  Re-construct availability check for projects S_ALR_87013558 - Budget - Actual - Commitment report

Automatic POD Concept For customer proof-of-delivery (POD) confirmations for an outbound delivery, you can define a time window in which the confirmation from the customer must occur. This time window is specified in units of days and stored in the field 'POD timeframe' of the customer master data for the sales area (KNVV-PODTG). If the current date and time in the local time zone (!) of the user running the transaction lies before the end of the time window, the transaction / program does NOT process the delivery, because the confirmation of the customer could still happen.   Logic for POD date calculation The end of the time window in which the POD is expected from the customer is calculated as the delivery date (LIKP-LFDAT) plus the POD timeframe as a net duration. Net duration means that only the working hours according to the factory calendar of the delivery (LIKP-KNFAK) are used for this scheduling. The factory calendar of the delivery is usually determined from the calen

  Proforma invoice Goods issue is not required to create delivery related proforma invoice. Order related billing document If business requires to raise invoice before goods are delivered to customer or Service items then order related billing document is used Delivery related billing document If business requires to deliver goods to customer before raising commercial invoice then delivery related billing document is used