Load Plan

From UG

Revision as of 17:45, 7 October 2010

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

Misc

??? MApping for <xs:attribute name="MasterShipmentNumber" type="xs:string" use="required"/> TBD

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>

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

S:Envelope

S:Header

wsa:From

wsa:To

wsa:Action

ebi:Sequence

S:Body

Inbound

DocLoadPlan

Example:

<DocLoadPlan BilledAsUOM="200" BilledAsUnitCost="0" BilledAsValue="0" BillingOptionDescription="0" CarContract="JWEL Contract 1" 
 FixedRate="0" Service="1" TotalCharge="172.63" TotalDeclaredValue="0" MasterShipmentNumber="LD000022469" TotalWeight="7" 
 BillingOption="0" Distance="2624.84" WeightUOM="200" DistanceUOM="100" CurrencyCode="USD" TotalStops="2" TransitTime="3" 
 TotalVolume="0" DimensionUOM="400" VolUOM="300" BaseRate="125" OtherCharges="47.63" EquipmentName="VN" CarrierCode="JWEL" 
 CarrierName="Jewels Transportation" Reason="0" TransportMode="TL" ContractModeDesc="TL" TotalLadingQty="1">

Child elements:

<xs:sequence>
<xs:element ref="BillToInformation" minOccurs="0"/>
<xs:element minOccurs="0" maxOccurs="1" ref="DocLoadRate"/>
<xs:element ref="BOLInformation" maxOccurs="unbounded"/>
<xs:element ref="DocLoadStop" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>

Required and important attributes and mapping:

• <xs:attribute name="MasterShipmentNumber" type="xs:string" use="required"/> // map to: ???
• ....

BillToInformation

DocLoadRate

BOLInformation

DocLoadStop

DocLoadStop