cancel
Showing results for 
Search instead for 
Did you mean: 

Designing EDI Interfaces for Advance Shipment Notification and POD

Former Member
0 Kudos

Our client does not engage in manufacturing and distribution of its products and components. They have developed partnerships with companies who provide distribution, manufacturing, shipping and movement services. They have authorized Forwarding Agents to transport the shipment. However, our client monitors and controls the business operations and remains the final authority in decision making.

The distribution company does the actual delivery and sends our client shipment confirmation (EDI-856). A single IDOC (SHPCON) comes in and performs the following functions

Update the delivery document (set picking value based on what shipped)

Generate a shipment document (with Handling Unit Information)

Post Goods Issue

We are facing performance issue with this kind of setup and the remedy suggested is to have multiple IDOC types to come in and create the shipment document and do the PGI separately.

I would like to hear experiences from practitioners on how they designed this requirement with other clients

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Prabhahar,

Try in this transaction NACE.

Select V2 for Shipping. And click output types.

Select LALE (Shipping Notification to Sold-to-party) or LAVA (Outgoing Shipping Notification) and use the Program RSNASTED for EDI processing and customize with the help of ABAPer.

Hope this helps.

Thanks

Augustine Ponraj

Former Member
0 Kudos

This is the normal process followed. If there is performance issues it could be due to the coding in the processing program. You may need the ABAPer to look into the processing program rather than creating seperate IDOCs which would not be the right buisness process.

reward points if it helps

regards

Biju