The purpose of writing this blog is to describe how the replenishment of Kanban materials are carried out in a business process where there is one Storage location which is EWM managed. This process is called One Step Stock transfer where source and destination storage location is EWM managed. The warehouse and production storage location is in same premise, so we can carry out One step stock transfer.
Kanban is a procedure for controlling production and material flow based on the physical material stock in production. Material that is required on a regular basis is continually kept available in small quantities in production. With Kanban, the replenishment or production of a material is triggered only when a certain quantity of the material has been consumed. This replenishment is triggered directly by production .
An attempt is made to replicate the scenarios given in help.SAP how the staging process is conducted in EWM managed warehouse.
- Define delivery type Determination
|Logistics Execution–>SAP EWM Integration–>Production Planning and Control–>Define Delivery Type Determination|
2) Define stock Transfer Strategies:
|Production–>Replenishment Strategies—>Define Stock Transfer Strategies|
3) Define Interface to Inventory Management and Delivery relevant data
|Logistics Execution–>Decentralized WMS Integration –>Central Processing–>Application–> Define Interface to Inventory Management and Delivery-Relevant Data|
Here, we need to map the IM movement type to WM reference movement type and assign the plant which is created as Customer and Vendor. Since in EWM we dont have material documents so, it is required to create Plant as customer and vendor to communicate with Outbound delivery(Customer) and Inbound delivery(Vendor). When customer and vendor is CIFed in EWM, they become Business partners which unique CRM identification number CRM004 and CRM002.
It is mandatory to assign ERP warehouse to ship to part and vendor and with other sales data to create outbound delivery when Kanban container becomes ”Empty”
4) Map storage locations from ERP system to EWM
|Extended Warehouse Management—> Interfaces–>ERP Integration–> Goods Movements–> Map Storage Locations from ERP System to EWM|
Here, it is mandatory to mention the ERP plant, ERP storage location with Logical system. EWM doesnt work with storage location as stock in EWM is available in LIME(Logistics Inventory Management Engine, so there is something called as Availability group which technically is a storage location in EWM. And party entitled to dispose is technically Plant in EWM which is created in EWM after CIFing of Plant from ERP.
5) Determine Stock type in EWM
With the stock type, you determine the status and therefore the availability of a stock within LIME.
|SCM Basis –>Logistics Inventory Management Engine (LIME)–> Basic Settings –>Application-Specific Settings–>Determine Stock Type|
6) Assign EWM stock type to Availability Group 002. Since we have just one storage location in ERP, so it will also be only 1 Availability group in EWM. N:N ratio
7) Define storage types.
I have created 3 storage type 1001 Production, 5001 and 5500. 1001 will be the destination storage type and 5001 and 5500 are the stock removal storage types hence it is mandatory to have stock available in these 2 storage types.
8) Define staging areas
|Extended Warehouse Management–>Master Data–>Staging Areas–> Define Staging Areas|
9) Warehouse Process types
|Extended Warehouse Management–> Cross-Process Settings–>Warehouse Task–> Define Warehouse Process Type|
4100 is the warehouse process type to stage the Kanban materials from source to destination Bin. It is mandatory to keep the Posting change Bin value as 2, because there is only 1 storage location which is EWM managed, so for transfer posting is withing the same sloc, a posting change document is created which will be replicated as Posting change delivery in EWM. The value as 2 will create a Warehouse task with reference to posting change delivery in EWM system
11) Determine Warehouse types.
|Extended Warehouse Management -> Cross-Process Settings -> Warehouse Task -> Determine Warehouse Process Type|
WPT 4100 will be determined to trigger PICK with FIFO rule.
Master data required.
- Create a Production supply Area in ERP, PK05.
2) Create a Control cycle for Kanban, PKMC,
Mention the supply area, Warehouse number ERP, no of kanban and containers.
Assign the storage location and supply area in control cycle.
Assign stock transfer Strategy
3) CIF the material into EWM system CFM1/CFM2
Product is replicated to EWM system now.
4) Replicate PSA in EWM
5) Create storage Bins in EWM: /SCWM/LS01
6) Define PSA in EWM: /SCWM/PSA
- Display Kan ban board by PK13N and check the status of Containers.
There containers with Wait and Full status.
2) Pick 003 Container and click on Empty. Once it is emptied, the color changes to Red as below
3) Click on 003 Kanban Card, and outbound delivery is generated.
4) Check the delivery, delivery is created with Movement type 411 and it is distributed to EWM system
Delivery is created with item category DOGN and delivery type DOG with status as ”B” meaning it is replicated to EWM system for picking.
5) Check the Posting change delivery in EWM:
/SCWM/IM_PC – Delivery Processing -> Posting Change -> Maintain Posting Change
6) Create Warehouse Task by follow on function. Click on create+save button.
Warehouse order will be generated
7) Check the Warehouse order in Monitor screen. /SCWM/MON
WO is confirmed, menaing material is staged to Production supply Area.
8) Check the Status of Delivery in ERP.
411 transfer posting is successfully executed in ERP through PPF action from EWM
9 Check the status of Kanban card in ERP, it will be in Full state now in Green
Material document is also created in ERP which means Materials is replenished in PSA
Hence the replenishment of Kaban with one step stock transfer is successfully done. There are more scenarios like 2 step Stock transfer when Warehouse and Production locations are practically separated and are not in same premise or far away. In this case, stock in transit is necessary to show in Kanban board.
Here the topic end. I would wait for any correction or improvement required for this blog.
In the upcoming blogs I will write on Batch management in EWM with Inbound and Outbound process, Advance Production Integration and Classic delivery based Production scenarios.