2 Step Stock Transfer in EWM Kanban
It is always true that, when observed, the overall solution and the concepts used in all Warehouses will be the same. But there are always variations in which the process executed on the Warehouse floor. It is one such variation that I would like to share in this blog.
Through this blog, one will be able to understand the below:
- 2 Steps Stock Transfer in EWM Kanban– Configuration Steps and Execution
- The need for a New Document Type and New WPT
- Partial Pick during Kanban
This blog is with the assumption that you have setup the Warehouse to function already. Steps below will be concentrated only towards Kanban process related setup.
Note – In my process, both the Source and Destination Slocs are EWM managed.
Process Flow that will be explained in this blog:
Step – 1: I have configured the 2 step Kanban Process using the “Delivery Option”. There is a new method that SAP has introduced, not long back, using Warehouse Task. The use of this method, technically called as the Control Type, is defined in the below configuration node.
As noticed in the screenshot above, the Control Type – 7 is used. Type – 8 can be used for Warehouse Task Option (I haven’t tried that option though, yet). Movement Type is 313, which is triggered during the Step – 1 of the 2-Step Kanban Cycle. Now comes the question on the 2nd Step and defining that in our configuration.
Step – 2: The system is now informed of the Movement Types and the ERP Document Type to be used for Outbound and Inbound Deliveries.
Step – 3: This is where the little deviation that I had to do in specific for my client. I had to auto create the WT at both Inbound and Outbound automatically including the auto post of GR and GI. This is in conflict to the other configuration in place for the regular Vendor GR and Customer GI, which will use the same Document Type in ERP and EWM.
This made it difficult for me to play around with PPF to automate WT/ GR and GI creations only for Kanban and to leave out other GR and GI processes for manual execution by the Warehouse Operator.
This left me with no option but to use a different Document Type in both ERP and in EWM. I had an unused Document Type that I havent used in any of my processes – HID and HOD.
Also, in the EWM side, I had 2 Standard Document Types that I haven’t used for any of my other processes, which is IPS and OUTS.
Respective configurations for HID/ HOD and its link with EWM Document Types are as below:
SCM Extended Warehouse Management –> Interfaces –> ERP Integration –> Delivery Processing –> Map Document Types from ERP System to EWM
SCM EWM –> Interfaces –> ERP Integration –> Delivery Processing –> Map Item Types from ERP System to EWM
Standard EWM Document Types used are shown below. I havent changed anything other than its description and hence I don’t see a need to show the details inside the Document Types.
SCM Extended Warehouse Management –> Goods Receipt Process –> Inbound Delivery –> Define Document Types for Inbound Delivery Process
SCM Extended Warehouse Management –> Goods Issue Process –> Outbound Delivery –> Define Document Types for Outbound Delivery Process
Step – 4: All the configuration that is done till now will manage the IBD and OBD creation separately but the trigger of IBD once the GI is done is for OBD is not managed yet. For this we will have to activate a Workflow in the system. Below are the details.
Above are the configurations needed to be in place for Kanban to work. When the Kanban Control Cycle is setup, one will have to maintain the Container Qty that needs refilling by the WH Operator.
When the Container is marked as Empty, WT is generated for the Container Qty as in the Control Cycle.
In an ideal world, it will work when the stock is present in the source bin, but this is not always the case in the real world. If the stock is less than the Container Qty in the source Storage Bin, the WT will be created for the Qty that is available. When this is the case, GI cannot be posted as the pick Qty is less than the OBD Qty.
Hence, we will have to use the concept called “Pick Denial”. When the WT creation Qty is less than the Available Qty, the Pick Denial which was set during WT creation is triggered. This will reduce the OBD Qty in EWM and in ERP to the WT Qty. This will now allow auto GI in hence the 2nd Step of Kanban is continued.
When the above is configured, it will allow the WH Operator to continue with his pick Qty and the Production will not have to stop their process due to stock non availability.
Step – 5: Below are the steps to configure Pick Denial
SCM Extended Warehouse Management –> Goods Issue Process –> Pick Denial –> Activate Pick Denial at Warehouse Number Level
SCM Extended Warehouse Management –> Goods Issue Process –> Pick Denial –> Specify Pick Denial at Warehouse Process Type Level
Activate this for the WPT that you are planning to use for Kanban Goods Issue.
SCM Extended Warehouse Management –> Goods Issue Process –> Pick Denial à Assign Internal Exception Codes to Exception Codes
Cross verify the configurations of Exception Code PD01 assignment to your Warehouse along with the below values (though should be present by default).
Now, in the WF above, SAP has provided it to work as a Dialog Step. So once the WT is created with less Qty, this WF will be triggered in the backend but will NOT get completed unless there is some manual intervention, which will NOT happen. Hence the WF needs to be updated as below.
Once all the above configurations are done, you will be able to complete the 2 Step Kanban Pick Cycle with Pick Denial.
As mentioned above on the assumption that the Warehouse is already setup to work, I will NOT be showing the Master Data used other than that is in specific for Kanban.
Kanban Control Cycle:
Once the Control Cycle is setup and the Kanban Board is updated with status as WAIT for the Container. Based on Status configuration, the status sequence may vary. Am going with the standard flow here, where the status will change from WAIT –> EMPTY –> IN TRANSIT –> FULL. If it’s a 1 step Kanban, IN TRANSIT status will be skipped.
Let’s work with Container 32.
Step – 1:
Mark the Bin as Empty either using the App – Set Kanban Container Status (Can be used in any supported HHD) or using the Transaction PK13N, if executed using desktop or tab. As an alternative, if your Warehouse uses RFUI application, you can try mapping the standard program provided by SAP for Container Status Change – TCODE: PKRFBC.
The behaviour is however the same way whichever way you choose to perform the action.
The Kanban Container once marked Empty, an OBD is generated automatically to pick the items. Since I have used a different OBD Doc Type along with a WPT that is specifically configured for this, I have maintained PPF condition to generate WT at once it gets distributed.
As noticed above, OBD is now created for the 2 Qty as mentioned in the Control Cycle. However, I currently hold only 1 Qty as stock in the Warehouse. Since I have also configured Pick Denial, WT would have been created for 1 Qty and the OBD in EWM and ERP is should also be reduced to 1 Qty. Can be noticed in the screenshots below:
Once the Pick is confirmed and the GI posted (via PPF trigger as the WH Operator cannot come to the PC to do a PGI for this OBD, all should happen either on the WH Floor or automatically), the Container status will now turn to IN TRANSIT and an IBD is created automatically to place the item in the PSA.
Once the above WT is confirmed, the stock is placed in the PSA and the status of the Container is changed to FULL automatically.
Appreciate feedback and happy to correct.