on ‎2019 Jan 14 11:29 AM
Hi EWM experts,
I am working on the process of goods issue for account assignment (e.g., cost center).
It is stated from SAP that we can use pickup delivery for this process. Link:
I have activated the BC Set /SCWM/DLV_OUTBOUND_DIRODO_1, and /SCWM/DLV_OUTBOUND_DIRODO_1A_PRD, /SCWM/DLV_OUTBOUND_DIRODO_1A_REQ
The EWM delivery type is OPIG.
I am using the default delivery type in ERP, which is DOG (triggered when post 201 MvT with MIGO).
The mapping for ERP and EWM delivery is as below
ERP Del. Type / Code Ini. Com. Chain / EWM Del. Type
DOG / PIG / OPIG
However, when delivery is created and distributed to EWM, the system cannot find the EWM delivery document.
Do I miss something with the configuration?
Request clarification before answering.
Tri/Juergen,
I have an issue which is related to this question.
I created the consumption delivery in EWM using /scwm/sgi, created wo, picked it & did PGI.
But got the delivery stuck in queue with below error

the BP got extended to the required sales org, but not sure which setting is SAP referring to pick the best practice sales are 1710 10 00
I have checked under Decentralized WMS Integration -> Central Processing->Application->Inventory Management Interface and Delivery-Relevant Data->Define Default Values for Deliveries
custom sales org is maintained here

But i am not sure, why the delivery creation in Core is looking for Plant BP maintenance in 1710 10 00 sales area.
What is the setting i am missing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
"However, it clearly states that the process can be from ERP or EWM."
What process? What constitutes an "planned pickup" and an "unplanned pickup"?
"PIG can be found at BOTH places, in ERP configuration and EWM configuration like below."
Yeah, but that doesn't mean that it really exist. You can also find DSH on the EWM side and it does not really exist there. And on the ERP side you can find PSP as code and it does not exist there either.
"This code Ini. Com. PIG should operate just like any other codes (such as PCD, PSD, etc.). By that I mean if it is a pickup delivery from ERP, the system should use an entry with code PIG in the above table."
What is "PIG"? How does the system know that the process is "pickup of goods"? It knows it because the EWM delivery type has a process profile in which the "Pickup" setting is "Mandatory". That's it. So it can never come from ERP.
Brgds
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Juergen Pitz,
Having re-read the documentation, I do see that SAP doesn't say anything about settings regarding the use of code ini. com.
I changed the configuration in the current system by creating a Z delivery type in ERP and just mapping it to OPIG delivery type in EWM. The process runs smoothly.
So while I agree that this code ini. com. PIG doesn't do anything when it comes to creating ODO in EWM, the pickup process can start from ERP just by configuring another delivery type.
Pickup delivery basically just means that customers come to the warehouse and pick the goods. SAP just plainly separates planned from unplanned by the origin of the document. If it is from ERP, then it is planned, and vice versa.
It may be a term created by SAP but the process does exist and I have seen one in one of my previous implementations.
Hi Juergen Pitz,
Thanks for your comment.
I do agree that the documentation from SAP doesn't provide enough information. However, it clearly states that the process can be from ERP or EWM.
DOG can be triggered from MIGO without any problem. It's the standard pre-configuration.

PIG can be found at BOTH places, in ERP configuration and EWM configuration like below.

This code Ini. Com. PIG should operate just like any other codes (such as PCD, PSD, etc.). By that I mean if it is a pickup delivery from ERP, the system should use an entry with code PIG in the above table.
In the above settings (with code PIG in EWM settings), when the ERP delivery was distributed to EWM, it wasnt identified as a pickup delivery. So, EWM wasn't able to find the EWM delivery type, in my opinion.

However, when I added an entry of ERP delivery DOG mapped to EWM delivery OUTB without any code Ini. Com., the delivery type OUTB was used to generate an outbound delivery order in EWM. The account assignment was also distributed as well.
My guess is that I need to create a Z delivery type in ERP, and map it to OPIG in EWM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
"Do I miss something with the configuration?"
You miss something about the overall process. It is difficult to understand in the documentation your refer to, but the process starts in EWM. So you do not map the ERP delivery to the EWM delivery (and you do not trigger DOG with MIGO in ERP), but you map the EWM delivery to the ERP delivery in ERP. PIG is a code with is only sent from EWM to ERP, not from ERP to EWM.
Brgds
Juergen
---
Want to influence SAP software development decisions for EWM?
https://influence.sap.com/ewm2019
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/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.
| User | Count |
|---|---|
| 17 | |
| 16 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 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.