I'm looking for anyone with real life experience that can share lessons learned with the Inbound Delivery Tracking functions in the ISAUTO_BOR Package.
I can see how an Inbound Delivery with a route can be manually updated with status events on the Delivery Tracking tab.
Looks like this automatically creates a TRXSTA Logical message (basic message type TRXSTA01) via the 'TRACKING" port .
This seems to imply that mapping inbound 214 Carrier Status EDI messages to Idocs which update the delivery status should be pretty straight forward. Is it process code TRXS.
Did you create a custom monitor transaction for the Material Planners? Or is there something in VL60 where the statuses can be monitored?
What are the upfront set up considerations for routes? Fairly simple?
OR
If there is an alternative way to handle inbound 214 messages from the Carriers related to Inbound deliveries that would be great too.
There is already the MM/LE process in place which posts inbound DESADV Idocs from either EDI or SNC to create the inbound delivery against scheduling agreements. The business need is to report to the Material Planners using SAP, the latest Carrier status, for example, at a border crossing. Workflow is not an acceptable solution.
Edited by: Motown on Nov 9, 2011 8:59 PM