on 2023 Jul 12 9:43 AM
Hello experts,
we try to create hierarchical planned shipping HUs based on OBDs. Therefore we are using the package builder engine. If I use the test transaction /SCMB/TEST_PB all works fine (product in carton ==> carton on palette). If I use transaction /SCWM/CAPDLV in order to create the PSHU in EWM I get an error message like "For PSHU header number 12 a PSHU tree or item entry is missing" (/SCWM/POHU028). It seems that the system recognizes the hierachy but cannot create them.
Has anyone some information about this? Is it not possible to create hierarchical PSHU in EWM by the package builder engine?
Unfortunately I am not able to upload some screenshots.
Thanks!
Regards
Ralf
Request clarification before answering.
Hello @ralf_b
To my knowledge EWM cartonization planning (PSHU creation) supports single level PSHUs only. I know that nested PSHUs can be created with TM package planning and sent over to EWM with the LDAP interface.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes the standard algorithm SAP1 will only plan for single level.
But SAP has also the SAP2 and for what i understood is to use the UPB at EWM.
Found this note but still don´t know if it´s the solution:
3329303 - UPB with Package Builder (EWM) : Package Level Aggregation Parameter - Handling Unit structure is missing quantities
Hi, you was able to find the solution? It´s realy a bug i have the same scenario.
Regards,
Carlos Ozorio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have no experience with using the package builder for cartonization planning, only with using packaging specifications. With PackSpecs cartonization planning uses the algorithm SAP1, which can only create a one-level proposal. With the package builder it uses the algorithm SAP2 - which I don't know if it can create a multi-level proposal (the documentation does not really say much about it).
So maybe you need to build your own implementation, the same as if you would use PackSpecs?
Brgds
Juergen
---
All the above is no official SAP statement.
Want to learn EWM?
Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA
Get a SAP Learning Hub Subscription: https://training.sap.com/learninghub
And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jürgen,
thanks for your reply. I know that it is possible to create nested PVHUs in EWM by an individual implementation (BAdI). In our process were are using the ASR-scenario and TM use the same engine (Package builder) in order to create the packages in TM. That of course is one goal of the package builder engine that different moduls use the same engine in order to receive the same results 😉
Therefore: Is this a bug or intended that EWM can not create nested PVHUs based on the package builder?
Maybe some of the other guys here have an idea ...
Regards
Ralf
"I know that it is possible to create nested PVHUs in EWM by an individual implementation (BAdI)."
But did you create you own implementation? Or are you using the SAP implementation?
"Is this a bug or intended that EWM can not create nested PVHUs based on the package builder?"
Again, I don't know what the algorithm SAP2 can do. But we algorithms SAP has delivered are simple, more complex requirements you have to build by yourself.
Brgds
Juergen
User | Count |
---|---|
6 | |
4 | |
3 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.