SAP Logistics

At times, there will be a situation where batch number need to be generated based on custom naming convention rather than through regular number series for example, having financial year as a prefix to the batch number like that. This is most common requirement in Pharma & FMCG industries. The solution for this cannot be achieved through standard functionality. So in order to accomplish this requirement, we need to write a custom logic in the exit ' EXIT_SAPLV01Z_002 ' to accomplish this requirement.

 At times, there will be a situation where sample warehouse task is not created.  The first step, we will check the configuration of the QM note of EWM  Define and Activate warehouse IOT settings. If the sample size config is maintained there. Then check if the inbound delivery document flow is determined with doc category 'Q01', this will give you the sample size. System still unable to determine warehouse tasks then in that situation, from technical standpoint during debugging, keep a breakpoint at the below class and Methods to troubleshoot the issue. This is the place where inspection rules will be called.  CLASS -  /SCWM/CL_QGR_CONTROL METHOD - /SCWM/CL_QGR_CONTROL~SAMPLE_SPLIT_CHECK CLASS - /SCWM/CL_GOODS_MOVEMENT METHOD - /SCWM/CL_GOODS_MOVEMENT~CHECK_QGR_CONTROL METHOD - PREPARE_DLV_DATA~CHECK_QGR_CONTROL BADI : GGR_CONTROL ~ SET_GGR_CNTRL_BY_IRULE can be leveraged in case of if business have a requirement that deviates from the standard functionality...

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

 Error Message Creating a return to vendor delivery on VL60 raises error: 'Unknown error has occurred in target system (Message No. /SCWM/DELIVERY_UI056)'. Root Cause RFC user is not configured as a dialog user. When creating a return delivery from EWM, the system attempts to call the RFC function /SPE/INB_CALL_TRX_VL60 using an RFC destination. This process involves executing the dialog transaction VL60, and the RFC destination relies on the RFC user for the call. Solution Approach Solution 1: Master data. Ensure that the RFC User master data is adapted to 'dialog'. Solution 2: BAdI implementation. Maintain a separate RFC destination for Return to Vendor scenario. Maintain a separate dialog user with restricted authorizations (e.g. only VL60). Assign the dialog user to the RFC destination. Change the RFC destination for calling the VL60 transaction from EWM, with BAdI '/SCWM/EX_DLV_ERP_CALL_CTRL->CALL_CTRL'. BAdI documentation extract: "Sample coding an...

The customizing flag for storage type "No GI" blocks only the posting goods issue for delivery documents, but in ad-hoc goods movement scrapping process (/SCWM/RGI_SCRAP), it is not evaluated.  On the selection screen of /SCWM/ADGI, if flag "Select Scrap Stock only" is set, the system will filter for stock with stock type S5 Scrapping from Putaway and/or S6 Scrapping from Warehouse.  In case it is needed additional checks on ADGI, customer-specific checks during unplanned goods issue can be implemented via BAdI /SCWM/EX_CORE_GM_STOCK.

If there is a requirement where system has to determine warehouse process type based on the storage location then in that situation we have to leverage exit /SCWM/EX_DLV_DET_PROCTYPE~CHANGE_PROCTYPE to accomplish the requirement. Logic should be written such that /SCWM/WHR_QUERY is used to fetch the delivery document details from EWM. REFDOC field in the IT_HEADER-REFDOC will contain the S4 delivery number.  This is passed into LIPS and fetch storage location and determine process type based on TVARVC or custom table