[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

[samuellevin_mavenwire]

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.

[ianlo]

Hi samuellevin,

thanks for the reply. So far I am actually using OutXML profiles only to reduce my XML output sizes - and to great success I might add.

Do you mean that the default OutXML profile applied to the ShipmentStatus XML is actually filtering out the SEquipmentNumber information? Do you know where the OutXML profile is actually being applied on the ShipmentStatus XML?

Thanks!

[JoeMac]

In using the OutXML you should be able to select the XML object that you want to prevent from transmitting. I've used it with great success when sending Tenders. Never used it for Status transmissions but it sounds like a possible way forward for you.

[ianlo]

Originally Posted by JoeMac

In using the OutXML you should be able to select the XML object that you want to prevent from transmitting. I've used it with great success when sending Tenders. Never used it for Status transmissions but it sounds like a possible way forward for you.

Hi I solved my problem. It turns out that PlannedShipment XML also has ShipmentStatus element and the PlannedShipment XML is not based on a 'pass through' model as described in the OTM user guides when recieving ShipmentStatus from carriers. The PlannedShipment XML is actually created when the DataQuery is executed. This allows me to modify and add my carrier connote number to the event remarks field AFTER receieving the connote number in the ShipmentStatus XML from the carrier.We were able to recieve the ShipmentStatus and then get the Send Integration to output the PlannedShipment XML with the desired information.Subsequently, we applied OutXML profile and XSLT transformation to only get the latest ShipmentStatus from the PlannedShipment XML and send it out.Looks like PlannedShipment XML is the way to go!Thanks for all your replies nonetheless!