Skip to main content

Posts

Showing posts from November, 2025

[SAP EWM] Troubleshooting storage bin inconsistencies

 In some cases, the capacity related data of the bin, stock or HU are calculated incorrectly. Or the master data is changed. The data must be corrected on database level. Common issues like Storage Bin cannot be deleted in transaction code /SCWM/LS02; Warehouse task cannot be confirmed due to storage bin inconsistency; Inconsistencies in the storage bins - number of HUs. Empty flag (field KZLER) is not set even if: No stocks (physical neither available) exist & no open/on hold WTs exist. Storage bin inconsistency is the root cause for all the above issues. To resolve this, please follow the below steps :  1. Go to transaction /SCWM/CHM_LOG --->  click on Ad-Hoc button; 2. Go to node Stock and Bin, click on 'Selection' button and insert a Warehouse number and storage bins: 3. Open the Capacity check node, 'Choose' Recalculate capacity, click on 'Selection' button and check either 'Update bin only' or 'HU counters + Empty bin flag' and execu...

[SAP MM] Error VLA317 or VLA318 given while posting Goods Receipt via MIGO transaction

Below is the solution approach for the following error messages : Batch Error VLA317 during Goods Receipt using Inbound Delivery  Error VLA317 'Inbound delivery batch cannot be changed to &1 here' is reported  Error VLA318 'Inbound delivery valuation type cannot be changed to &1 here' is reported  Error VLA319 Return delivery qty greater than previously GR-posted qty: &1/&2 when reversing a delivery GR is not happening with reference to Inbound Delivery Solution Approach Options for Resolution:  Approach 1 : Update the Inbound Delivery with the Batch Number (LIPS-CHARG)/Valuation Type (LIPS-BWTAR) prior to posting the Goods Receipt via MIGO transaction.  Approach 2 : Implement Note 2991640 and then the error VLA317/VLA318 can be customized as a warning. Please be aware that this may cause inconsistencies so review all the information provided in this note. Run transaction SPRO (or OVM1) and follow the path: Logistics Execution -> Shipping -...

Fields missing in BP post upgrade of S4 HANA system

 At times, we can see that post system upgrade some fields in the business partner will go missing, to fix this we need to re-generate the screens. Ensure to keep this is included in the post migration activity. Below is the approach need to be followed  Run T-code BUSP. Enter application object as BUPA. Select "All screens" in session "generate all screens or just selected screens". Then press "execute" button.

[SAP MM] Custom batch number generation during receipt or production process

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.

[SAP EWM] Sample size WT determination technical analysis

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

[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