johndanter
Legendary Poster
Hi guys,
An EDI customer sends us an 850, we create SO and SO lines
The customer may then send us an 860. We respond with back with an 865.
The customer may only be changing us changes to their order lines 2 3 7, but we will create a new EDOC and 3 new EDLNs 1 2 3
Can I ask how you guys map and link an inbound 860 (F47131 header & F47132 detail lines) to E1 SO header and detail lines for the 865 return.
There must be a spare field to store their original order line????
I can see that we use VR01 and AN8 in the F47131 to link to F4201, but I'm becoming unstuck in linking the detail F47132 lines to specific F4211 lines.
How do you guys do this?
Do you use EDLN or is there something else you use to map them.
As their line 2 may not be our line 2. I think this is why we are having issues as their customer order line reference may not be a simple 1 to 1
so they may send us their lines 2 3 7 which will be lnid 1 2 3 our end. When we talk back to them we need tell them lines 2 3 7 etc
Thanks
John
An EDI customer sends us an 850, we create SO and SO lines
The customer may then send us an 860. We respond with back with an 865.
The customer may only be changing us changes to their order lines 2 3 7, but we will create a new EDOC and 3 new EDLNs 1 2 3
Can I ask how you guys map and link an inbound 860 (F47131 header & F47132 detail lines) to E1 SO header and detail lines for the 865 return.
There must be a spare field to store their original order line????
I can see that we use VR01 and AN8 in the F47131 to link to F4201, but I'm becoming unstuck in linking the detail F47132 lines to specific F4211 lines.
How do you guys do this?
Do you use EDLN or is there something else you use to map them.
As their line 2 may not be our line 2. I think this is why we are having issues as their customer order line reference may not be a simple 1 to 1
so they may send us their lines 2 3 7 which will be lnid 1 2 3 our end. When we talk back to them we need tell them lines 2 3 7 etc
Thanks
John
Last edited: