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

Comments

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...

SAP Logistics

Search This Blog