Quote:
Originally Posted by ianlo  Hi,
First of all kudos to Chris for organising this site! Excellent resource site!
I am using Shipment Status XMLs in my OTM implementation and noticed the following:
1) Any outbound Shipment Status XMLs from OTM are always a pass through. Meaning that if I were to recieve a Shipment Status XML from a carrier, the SAME XML previously recieved is sent when I need to generate a Shipment Status XML to another system.
2) If the user were to manually enter the shipment status via the UI, a Shipment XML is generated as an inbound transmission. And when I need to generate a Shipment Status XML to another system, that OTM generated XML is sent. 
This causes problems for me because the data in these 2 different XML formats are incompatiable - for example the Carrier sends me a POD status against a EquipmentNumber, but if the user enters the POD status against an equipment via the UI, the SEquipment GID is populated instead of the EquipmentNumber.
I need to send the EquipmentNumber to an external system regardless where the shipment status is recieved.
Anyone has any ideas?
Ian |
Ian
You may want to look into the capabilities of using a Out Xml Profile. This can be assigned to the outbound external system and parse out some of the data that you do not need. If the outbound xml displays the equipment number at more then one level you can parse out the SEquipment information which may resolve the issue.