Controlling internal movement of an expired Batch and blocked stock type- BAdI /SCWM/EX_WHO_DSTGRP

[shailesh_mishra5]

Requirement: During internal transfer posting of a Full HU (/SCWM/ADHU) or a Product transfer( /SCWM/ADPROD) using Fiori or RF transaction, there shall be a capability of stopping HU/Product movement based on certain condition.

 Business Conditions:

• Don't allow internal movement of HU/Product if Batch is expired
• Don't allow internal movement of HU/Product if stock type is Blocked.

Problem Addressed/ Standard Scenario: There is no standard functionality available in SAP which allows to control the movement of HU/Product based on above condition.

Solution: SAP EWM offers a BAdI /SCWM/EX_WHO_DSTGRP which can be used to put a validation on lot of business conditions. This blog will showcase a solution how to this BADI. There could be many usage of this BAdI, and primarily this is used for changing the consolidation group of WT during WO creation.( This BAdI gets triggered every time when each WT is assigned to WO).However, this is extremely critical BAdI in EWM and its usage is at lot of places before WO generation. In this blog, the business conditions of stopping internal movement of Expired & Blocked stock would be controlled using the BAdI  /SCWM/EX_WHO_DSTGRP.

Replication Steps: During Bin to Bin transfer from Component warehouse to Production supply( Adhoc), system should forbid the movement of HU reading the condition from BAdI.

Using RF: Create & Conf ADHOC HU

Using /SCWM/ADHU:

Using RF: Create & Conf ADHOC Product

Using /SCWM/ADPROD:

BAdI details: The BAdI uses interface /SCWM/IF_EX_WHO_DSTGRP using importing parameter IT_TO which allows to read HU WT( FLGHUTO), Warehouse Process Type( PROCTY=3), Stock Type( CAT=BB), Batch( CHARG), Shelf Life Expiration Date( VFDAT< current date), Product(MATID) & Warehouse Task(TANUM). Reading the above attribute before WT creation( HU or Product), a validation is put inside the BAdI.

Other BAdIs: Customer can also use /SCWM/EX_CORE_CR_INT_CR. This BAdI is specifically designed for Internal Process and customer can put validation. This BAdI is called during every WT creation.
In this BAdI, you can read the Batch ID, HU,VFDAT, Stock type and abort WT creation using parameter setting to ET_BAPIRET. This would work both HU WT and Adhoc Product WT.

Thanks for reading. All test is performed in S/4HANA 2022 Embedded EWM.

The blog is co-authored by @prem_swaroop