Product Information
Splitting of full & partial pallet pick WTs into separate warehouse orders in SAP EWM
Introduction:
In this blog post you will learn about the splitting of full and partial pallet pick WTs into separate warehouse orders where in one warehouse order is devoted for full pallet and the other one for half pallet.
For instance, there are business cases in which, a dedicated person is assigned to pick up only full pallets using forklift and it is not required for the warehouse employee to carry any pick HU. However, the other person earmarked for partial pick should carry pick HU. In such scenarios, we need to group all the full pallets warehouse tasks into one warehouse order and all the partial pallet warehouse tasks into another warehouse order.
It is to be noted that the stock received from suppliers is always as full pallet (example each pallet contains 30 Quantity) and it will be placed in a single storage. Also, there are no separate storage types for full and partial pallets.
Solution Approach:
The below mentioned configuration steps can be employed to achieve this functionality:
- There are some specific indicators that should be enabled in the storage type to achieve this scenario.
- Level of quantity: Highest-level HU.
- HU Picking Control: Propose source HU as Destination HU.
With the above setting, the system will propose the source HU as the destination HU during the warehouse task creation (Full pallet pick).
Configure/enable storage type settings using the below mentioned node:
IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Master Data -> Define Storage Types.
- Define filters for the warehouse order creation rules using the below mentioned node:
IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Warehouse Order-> Define filters for the warehouse order creation rules.
Filter for full pallet pick:
If the warehouse task contains the same source and destination HU, then system will consider this is as a full pallet pick and it will successfully pass through the item filter: FULL.
Filter for partial pick:
If the warehouse task contains only the source HU, then system will consider this is as a partial pick from a pallet and it will successfully pass through the item filter: PART.
- Define creation rules for warehouse orders using the below mentioned node:
IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Warehouse Order-> Define creation rules for warehouse orders.
Define and update the sort rules, limit, and packaging profile as per your requirement in the warehouse order creation rules.
Creation rule for full pallet pick:
Creation rule for partial pick:
- Define search sequence of creation rules for activity areas using the below mentioned node:
IMG Path – SPRO -> IMG -> SCM Extended Warehouse Management -> Extended Warehouse Management -> Cross-Process Settings -> Warehouse Order-> Define search sequence of creation rules for activity areas.
Testing:
- Parts:1108 & 1109 are used to perform this testing.
Ensure the stocks are available for these 2 parts using a warehouse monitor before execution of this test. The put away rules for this storage type: N023 is an empty bin, such that each bin will contain only one pallet.
Stock for the part 1108:
Stock for the part:1109:
- Outbound delivery: 80004011 is created.
- In the delivery screen, create warehouse task manually by clicking on CREATE button and then SAVE.
Outbound delivery screen can be reached using the t-code:/SCWM/PRDO.
- Warehouse task can be viewed in the monitor screen using the transaction code:/SCWM/MON.
In this scenario 4 warehouse tasks are created, that is 2 warehouse tasks for full pallet pick and 2 warehouse tasks for partial pick. As per the configuration setup, 2 full pallet warehouse tasks are grouped to one warehouse order and other 2 partial pick warehouse tasks are grouped to another warehouse order.
Conclusion:
This blog post explains the configuration steps involved in the grouping of full pallet WTs in a one warehouse order and partial pallet WTs in a other warehouse order for a delivery with the test results.
Hello
Nice article and share of knowledge.
Keep it up.
I have one query to you regarding storage type setting of HU picking control. Is this necessary to have this set as '1'. I checked destination HU is alos proposed as source HU when we have this as 'space'. Did you notice any strange behavior when using 'space' instead of '1'?
Thanks in advance for your clarification.
Rest the blog post looks very nice and you have provided almost all the information relevant to the topic.
Regards- ASLAM
One thing to note Aslam, Irrespective of this indicator, we can change data in confirmation screen
Thanks Ekta for additional information.
With space it should be as well proposed, but if you have pick HU you should get source Hu moved into it (you should get nested HU at the end)
+ it is similar control in warehouse process type
Thanks Daniil for your comment.
Hi Aslam , Daniil, Ekta,
Thank you 🙂 for your comments.
Regards,
Krishnakumar
Nice Work Krishna
Hi Krishna,
Very nice share with problem statement , along with detail business process and complete config steps, this is a very practical scenario in Warehouse where the forklift driver would not be carrying a pick HU and while scanning the source HU, the same HU should be a destination HU. we could further differentiate the Queue's for Forklift drivers and pickers, so that there will be efficient picking in the WH, Thanks for sharing the blog, keep sharing all the blogs.
Thanks and Regards
Sadiq...
Hi Sir
Thanks your response 🙂
Regards,
Krishnakumar
Nicely addressed a common scenario of a complex warehouse.
Hi Harsh,
Thanks for you comment 🙂
Regards,
Krishnakumar
Good effort Krishna, another option to divide wt to manage full and partial pallet that you can utilize from quantity classifier.
M.Ozgur Unal
Hi M.Ozgur,
Thank you
. Yes if we use 2 different storage types to store partial and full pallets then we can utilize quantity classifier.
Regards,
Krishnakumar
Excellent article on splitting of full & partial pallet pick WTs into separate warehouse orders. Look forward to more such articles on complex functionalities!!!
Hi Sir,
Thank you 🙂
Regards,
Krishnakumar
As usual great blog Krishna!
Hi Aravind,
Thanks for you response 🙂
Regards,
Krishnakumar
Nice Blog !
Hi Selvaganesh,
Thanks for your comment 🙂
Regards,
Krishnakumar
Hi Krishnakumar,
Nice blog, very good information.
Regards,
Rajesh
Hi Krishnakumar,
Very Nice Blog! Really appreciate your strategy used.
I was looking, that how you maintained the HU content as 30 qty to be determined as full HU by the WOCRs.
Thanks!
Regards
Abhishek
Nice explanations
Hi Krishnakumar Chokkar,
I have a storage type that contains products managed in meters, such as rolls or belts. I need the system to check if an exact 10m belt is available when an order for 10m is placed. If not, the system should suggest cutting the required meters from a larger belt. Additionally, the system should prioritize suggesting a complete 10m length rather than two separate pieces of belts (e.g. 5m and 5m). Is it possible to meet this requirement using the standard SAP setup?
Hi,
If my HU contains multiple Batches of same product, done the configuration as mentioned above, but source hu is not withdrawal in destination HU, May I know any other additional settings required pls
Hi Krishna,
If my HU contains multiple Batches of same product, done the configuration as mentioned above, but source hu is not withdrawal in destination HU, May I know any other additional settings required pls
Hi Krishna,
If my HU contains multiple Batches of same product, done the configuration as mentioned above, but source hu is not withdrawal in destination HU, need your help
Hi Krishna,
HU contains multiple Batches of same product but source hu is not withdrawal in destination HU, need your help
Hi Krishna,
HU contains multiple Batches of same product, need any additional configuration to work, pls let me know