Status Message

From UG

Contents 1 Intro 2 Schema 3 Message structure 4 Use Case 1 is Picked Up Event 5 Use Case 2 is Delivered Event 5.1 History 5.1.1 0002391: [EDI to TMS] (Status Message) Use Case 1 is Picked Up Event; Use Case 2 is Delivered Event 5.1.2 0003152: [EDI to TMS] Check both Load Plan & Status Message for Pro Bill # & update CT Pro Number Field on Gen Tab

[edit] Intro

Status Message is a message transmitted by TMS to CT2 with info about updates for some fields.

CT2 script is to extract some information and update CT record.

Initially only the following data will be extracted (for every CT#CT Num):

• CT#Actual Export Pick Up Date
• CT#Actual Delivery Date

[edit] Schema

[edit] Message structure

[edit] Use Case 1 is Picked Up Event

CT was picked up.

See XML below or here: http://mantis.jaguarfreight.com/mantis/file_download.php?file_id=1709&type=bug

<S:Envelope>
<S:Header>
  <wsa:From>
  <wsa:Address>urn:zz:JAFR_TM</wsa:Address>
  </wsa:From>
  <wsa:To>urn:duns:657589457</wsa:To>
  <wsa:Action>urn:myvan:214</wsa:Action>
  <ebi:Sequence>
    <ebi:MessageNumber>BAT2010-10-0620-34-26Z375</ebi:MessageNumber>
  </ebi:Sequence>
</S:Header>


<S:Body>
<Inbound>
  <DocTracking BOLNo="BOL000000039" MasterShipmentNumber="LD000000038" 
     TrackDate="2010-10-06T00:00:00"City="jamaica"   
     State="ny" Country="US" Comment="alex posted test comment" Event="2028" Reason="3042"   
     ModifyDate="2010-10-06T20:33:41" EventDescription="Picked Up" ReasonDescription="Normal" SCAC="DSCG">
     <DocShipment ShipmentNo="300755">
       <DSGReferenceNumbers RefNoType="GL Account 2" Value="Yes"/>
     </DocShipment>
  </DocTracking>
</Inbound>
</S:Body>
</S:Envelope>

Above means that CT#300755 was picked up and:

• field CT#Actual Export Pick Up Date should be set to 2010-10-06
• post event to CT Update log

[edit] Use Case 2 is Delivered Event

CT was delivered.

See XML below

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:Num="Num-namespace-URI" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:ebi="http://www.myvan.descartes.com/ebi/2004/r1" xmlns:dcf="DCF-namespace-URI" xmlns:D2P="D2P-namespace-URI">
- <S:Header>
- <wsa:From>
  <wsa:Address>urn:zz:JAFR_TM</wsa:Address> 
  </wsa:From>
  <wsa:To>urn:duns:657589457</wsa:To> 
  <wsa:Action>urn:myvan:214</wsa:Action> 
- <ebi:Sequence>
  <ebi:MessageNumber>BAT2010-10-0820-51-44Z358</ebi:MessageNumber> 
  </ebi:Sequence>
  </S:Header>
- <S:Body>
- <Inbound>
- <DocTracking BOLNo="BOL000000035" MasterShipmentNumber="LD000000034" TrackDate="2010-10-08T00:00:00" City="Holmdel" State="NJ" Country="US" Event="2013" ModifyDate="2010-10-08T20:50:54" EventDescription="Delivered" SCAC="DSCG">
  <DocShipment ShipmentNo="SHP000000013" /> 
  </DocTracking>
  </Inbound>
  </S:Body>
  </S:Envelope>

Above means that CT#SHP000000013 was delivered and:

• field CT#Actual Delivery Date should be set to 2010-10-08
• post event to CT Update log

[edit] History

[edit] 0002391: [EDI to TMS] (Status Message) Use Case 1 is Picked Up Event; Use Case 2 is Delivered Event

[edit] 0003152: [EDI to TMS] Check both Load Plan & Status Message for Pro Bill # & update CT Pro Number Field on Gen Tab

• Mapping changes were needed by Descartes as their load plan did not contain the Pro Bill # as it should have. Therefore Descartes have implemented the following work around: put the ProbillNo in the TrackInfo attribute

WU? Y