on ‎2021 Jan 07 8:45 PM
Hi everyone,
I am currently implementing the new synchr. GR for a greenfield implementation of an embedded EWM in S/4 2020.
It is working pretty good in MIGO - the system creates a warehouse document directly and creates an HU immediately. Getting rid of delivery processing really is a relief!
To cover customer requirements I want to use CO11n for posting the good receipt. This works as well, only the HU is not being created. Same test data, same customizing - it seems the new methods for triggering the HU creation are not being called.
Then I tried out to use BAPI_GOODSMVT_CREATE to post GR and create the HU. Same story: GR is being posted directly, but HUs are still missing.
Do I miss something or is this functionality not yet implemented?
Thanks a lot!
Dominik
Request clarification before answering.
Hi Dominic , Did you find solution for your issue?
Regards,
Ambrishh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Balint,
thank you for your answer!
What I actually want to do is to consume components and post GR in one step - like you can do in CO11n. This works, but it does not create an HU. And that is my problem.
In the meantime I digged deeper into the new code... Seems like the packing determination is being called when starting MIGO (and when the user updates quantities, ...). This action (done in class /SCWM/CL_MIGO_S4) already creates the HU internally in internal structures, which are being used when saving the posting.
Since this class seems to be used in MIGO only, EWM cant create HUs by using CO11n....
Maybe some SAP guy can shed some light?
Thanks!
Dominik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you need to use a seperate app for posting goods receipt with HUs. This is from the What's New document for the 2020 S/4:
Typically, HUs containing the products produced in production are planned, physically created and packed on the Production side. Goods receipt can be posted in the GR HU for Production Order app for discrete and process manufacturing, and the order confirmation including goods receipt and goods issue posting can be performed with the Confirm Repetitive Manufacturing for Handling Units app for repetitive manufacturing. Up until now, using these apps required the system to create deliveries and warehouse request documents in EWM. Now the system can post the goods movements in EWM without the delivery and warehouse request documents. When you confirm HUs in production for an EWM managed storage location using synchronous goods receipt, the system creates EWM HUs from the HUs in production and, if the HUs were created with reference to a sales order, it stores the sales document reference in the EWM HUs as an alternative identification under identification type B (Sales Document Reference). You can use a BAdI to make it possible to use the sales document reference in the EWM HU at warehouse task creation to determine another destination bin, for example, the goods issue area.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 13 | |
| 7 | |
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 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.