Skip to main content

Posts

Showing posts with the label BADI

[SAP EWM] EWM-> ERP: GI Date, GR Date and Posting Date

Below BADI need to be leveraged to influence the dates received from EWM to ERP : If you would like to influence the dates sent from EWM to ERP side, For PDO related GI, you can use the BADI /SCWM/EX_ERP_MAPOUT_OD_CONFDEC method  /SCWM/IF_EX_MAPOUT_OD_CONFDEC~MAPOUT. The dates are passed in the CT_BAPI_HEADER_DEADLINES parameter table, where you can modify the GI date. the relevant date is WSHDRWADTI which is the actual goods issue date   (constant /SCWM/IF_MAPPING_CONSTANTS=>SC_TT_OBDLV_GI_ACT). For PDI related GR, use BAdI /SCWM/EX_ERP_MAPOUT_ID_CONFDEC. The time type of IDRECDOCK(constant /SCWM/IF_MAPPING_CONSTANTS=>SC_TT_IBDLV_REC_ON_DOCK) will be taken over by ERP as the posting date.

Shipment document BADI

 At times, there will be situations where we are required to trigger a specific set of data during the creation/saving of shipment documents. In this situation, we are required to leverage the BADI 'BADI_LE_SHIPMENT' to accomplish the requirement 

[SAP] Easy way to identify customer EXIT or BADI

 At times, We find difficult to identify exits for a program.  This post will explain you an easy way to find list of  Customer Exits and BADI's available for a program. Below are the process steps to be followed : Step 1 : Goto T.Code : SE16N, Enter transaction code  Step 2 : Fetch program name Step 3 : Collect Program Name and pass it to TADIR table to fetch development class Step 4 : Pass Development class again into TADIR table by passing OBJECT as SMOD to fetch all customer exit's and OBJECT as SXSD to fetch BADI's related to the program. In this case, I have passed SMOD to fetch customer exits. Step 5 : All Customer exits related to the program are displayed Step 6 : Once EXIT is identified. To get description related to it, Pass Exits into table MODSAPT and SXS_ATTRT to get descriptions corresponding to them. Thank you.