on 03-30-2007 12:51 PM
My client makes use of a logistics service provider. Based on the delivery a dispatch order is sent (SHPORD) Idoc type DELVRY03. The logistics service provider receives the dispatch order, picks the materials and confirms the actual picked quantities to my client (SHPCON, Idoc type DELVRY03).
The problem is this, for some reason the delivery is not being updated with the actual picked quantity. As a result, the system doesn't post GI because it thinks the delivery is not yet picked completely.
In E1EDL20 (header) I added the sub segment E1EDL18 (qualifier-header) with the value 'PGI'. In E1EDL24 (item) I added the sub segment E1EDL19 (qualifier-item) with the value 'QUA'.
Can anybody tell me what I did wrong??
Thanks very much for your reply!!!
Kind regards,
Wander Jansen Venneboer
I think you'll need 2 separate IDocs. First create an IDoc to update pick quantities (enter all quantities and E1EDL18 qualifier PIC). Then create second IDoc for PGI (no quantities are needed here) like you did. Quantities can also be updated in the PGI IDoc, but I think it only works if something was not picked and you need to change the delivery quantity to 0 (or actual pick quantity) to do PGI. We use this second option on the site that has WM but PGI data is being triggered from the third-party software. I was unable to use it to pick the deliveries for the site that doesn't have WM.
You might need to post the PIC IDocs first and then go about the PGI IDocs. Also even if you don't use parallel processing, the next IDoc actually starts processing before the previous one is completely done. We ran into a big issue with locking errors when 2 consequent deliveries had the same material number. I complained to SAP but was told that this is standard. If this becomes an issue for you, try late locking feature and also you can schedule the error processing program RBDMANIN after the IDoc posting to take care of the remaining locking errors.
Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jelena,
thanx very much for your reply. I was thinking of an alternative: maybe the system can Goods Issue the delivery after updating the delivery quantity by the Idoc. The update itself is the trigger, instead of the qualfier in the Idoc (PGI). In that case I only need to send one Idoc.
What do you think?
Kind regards,
Wander
Hmm... I know that it is possible to pick and PGI delivery automatically without any custom ABAP coding. We do this for the return deliveries for one site but I'm not sure how it's working exactly (I'm just an ABAPer). There should be some configuration for this or maybe there is a program that could run in the background to PGI all the eligible deliveries after the PIC IDocs have been processed?
Hi All,
I have the similar requirement. Steps are below,
1. Subcontract PO will be created in S/4 HANA
2. Outbound delivery will be created and sent to 3PL via IDOC (IDOC Basic Type: DELVRY03, Message Type DESADV)
3. Assume an IDOC will be receive from 3PL, expecting to automatic Pick and Post Goods Issue (PGI) should happen in S/4 HANA.
Note: No HU, No WH managed materials.
I have tried to create an idoc via we19, One E1EDL18 has QUALF = PIC, and the other one has QUALF = PGI. The item level segments have correct materials by number and the quantity picked maintained. However idoc throwing an error stating that EXDIV is mandatory field even though no HU.
Kindly help me to get the solution as soon as possible, if anyone come across and resolved the issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jelena,
It's possible to do both the quantity change on item level and the goods issue post on header level in the same SHPCON IDoc.
Best regards,
Jochen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.