Load Plan

From UG

Contents 1 Intro 2 Schema 3 Message structure 4 Use Case 1 One Load One CT No Pooling 5 Misc 5.1 Case of AddressTypeDesc is Pool Point 5.2 StopTypeCode

Intro

Load Plan is a message transmitted by TMS to CT2 about finalized loads in the form of XML.

CT2 script is to extract some information and update its database. Initially only the following data will be extracted (for every CT#CT Num):

• CT#Pick Up Trucker // from Inbound.DocLoadPlan.CarrierCode or Inbound.DocLoadPlan.CarrierName

• CT#Delivery Trucker // ???
• CT#Estimated_Pick_Up_Date
• CT#Estimated Delivery Date

Schema

See http://mantis.jaguarfreight.com/mantis/file_download.php?file_id=1707&type=bug

Message structure

 <S:Envelope> 
   <S:Header>
    ...
   </S:Header>

   <S:Body>
     <Inbound>
       <DocLoadPlan ... >
         <BillToInformation ... />
         <CtyLoadAccessorial ... />
         <DocLoadRate> ... </DocLoadRate> 
         <BOLInformation ... >
            <ShipFromInformation ... />
            <ShipToInformation ... />
            <DocShipment ... />
               <DocShpLineItem ... />
               <DSGReferenceNumbers .../>
            </DocShipment>
         </BOLInformation>
         <DocLoadStop ... />
           ....
         <DocLoadStop ... />
       </DocLoadPlan>
     </Inbound>
   </S:Body>

 <S:Envelope>

Use Case 1 One Load One CT No Pooling

Misc

Case of AddressTypeDesc is Pool Point

Drop off or pick up are not origin or destination for CT. But this helps to distinguish between CT#Pick Up Trucker (before Pool point) and CT#Delivery Trucker (after)

StopTypeCode

<xs:attribute name="StopTypeCode">
−
<xs:simpleType>
−
<xs:restriction base="xs:int">
−
<xs:enumeration value="1">
−
<xs:annotation>
<xs:documentation>Pickup</xs:documentation>
</xs:annotation>
</xs:enumeration>
−
<xs:enumeration value="2">
−
<xs:annotation>
<xs:documentation>Dropoff</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:attribute>