Delivery Split and Status in EWM

[former_member602629]

Dear Experts,

We have the below scenario in one of our projects.

1) We are using the warehouse monitor to display deliveries open for goods issue.

2) Consider an example where the delivery item is for 10 PC. 5 PC is picked, packed into a HU and is ready for GI.

3) GI is done at HU level. Split items get created.

4) Though there is an open quantity of 5 PC, the overall GI status of the delivery turns to "Completed".

5) At item level the higher level items have GI status "Not Relevant".

6) How to interpret the right delivery status. There is a possibility of missing some delivery items during GI due to this issue.

Please share your thoughts.

Thanks,

Mageshwaran Sivasamy

[former_member230160 · Accepted solution]

Hello Mageshwaran Sivasamy,

the normal GI header status (status type DGI) only aggregates the item status. It does not consider e.g. incomplete splits.

For this you could use the status "goods issue and distribution" (status type DGD). This also takes into consideration if incomplete splits (=distribution) exists. As this is an optional (transient) status it may be that it is not active for your delivery type. In this case you could activate it in the corresponding status profile.

This status is available in the /SCWM/PRDO as well as the monitor node.

Does this answer your question?

Best regards

Markus

[former_member230160]

Hello,

if you plan to read/query in own applications, you may have a look at note https://launchpad.support.sap.com/#/notes/1414179

This contains a document DelivServiceProviderCallExamples.pdf

In this chapter 8 described method /SCWM/CL_DLV_MANAGEMENT_PRD->QUERY which can also calculate some transient status. Further information can be found in this method documentation

Best regards

Markus

[former_member602629]

Hello Markus,

Thanks a lot for the quick response.

I got similar answer from the wiki -

https://wiki.scn.sap.com/wiki/display/SCM/EWM+delivery+status+handling. The only problem is the transient nature of the status and inability to persist the data in a table.

We will have to identify how the status is determined and apply the same logic in our monitor program.

Thanks,

Mageshwaran Sivasamy