You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li>04 - In ONE Record we try to avoid duplicate data as much as possible, especially <strong>totals</strong> are usually not in ONE Record data model if all detailed data are already available. This applies for instance for the total or summary values of charges.</li>
<p>XFWB data fields are mostly a mix of <code>Waybill</code>, <code>WaybillLineItem</code>, <code>Shipment</code>, <code>Pieces</code> and <code>TransportMovement</code> data in ONE Record realm.</p>
3868
-
<h4id="usage-of-waybilllineitem-object">Usage of WaybillLineItem object<aclass="headerlink" href="#usage-of-waybilllineitem-object" title="Permanent link">¶</a></h4>
3869
-
<p>The <code>WaybillLineItem</code> object was introduced to properly share rate data as required in the Air Waybill. The <code>WaybillLineItem</code> has a n-to-1 relationship with a <code>Waybill</code> object and represents the different line items on the paper waybill with all their specifities based on the type of rating used. In order to stick to reality as much as possible, some data at line item level are taken from <code>Pieces</code> and <code>LoadingUnits</code> directly (dimensions, volume, ...). The <code>WaybillLineItem</code> object itself shall only contain <strong>rate</strong> specific data.</p>
3870
-
<p>It is important to note that the <code>WaybillLineItem</code> has been added <strong>only in the context of sharing Air Waybill data</strong>. When looking at Operations, digital twins shall be used (<code>Piece</code>, <code>Item</code>, <code>Product</code>, etc.)</p>
<p>XFWB movement and routing details are mapped to <code>TransportMovement</code> objects. The proper linkage, starting from the <code>Waybill</code> is to to go through the <code>Booking</code> object which refers to the contractual engagements between a carrier and the freight forwarder. The various <code>TransportMovement</code>(s) planned for the transportation of the goods need to be linked to the <code>Booking</code> as an <code>ActivitySequence</code>. </p>
3873
-
<h4id="usage-of-othercharge-object">Usage of OtherCharge object<aclass="headerlink" href="#usage-of-othercharge-object" title="Permanent link">¶</a></h4>
3874
-
<p>The <code>OtherCharge</code> object is used to record all charges, it refers to <code><ram:ApplicableLogisticsAllowanceCharge></code> grouping in XFWB message. Code List 1.2 "Other Charge Code" is used to properly identify the charges associated with the Prepaid/Collect indicator.</p>
3875
-
<p>Totals are not directly recorded in ONE Record as they can be directly calculated based on the existing data (e.g. filtering by type of charge and prepaid/collect indicator).</p>
3876
-
<h4id="other-specific-mapping-guidelines">Other specific mapping guidelines<aclass="headerlink" href="#other-specific-mapping-guidelines" title="Permanent link">¶</a></h4>
3877
-
<ul>
3878
-
<li>
3879
-
<p><code>DensityGroupCode</code> field will be linked to Distribution phase as the feedback received from the industry shows that it's not an operational data but used for the Sales & Booking process part. It is then found on the <code>BookingShipment</code> object if required.</p>
3880
-
</li>
3881
-
<li>
3882
-
<p><code>Special Service Request</code> and <code>Other Shipping Instructions</code> code fields are not in ONE Record as there is no evidence of an actual referential and standard used for those. Moreover it seems stakeholders use SSR or OSI for the same purposes. Thus we have merged into <code>textualHandlingInstructions</code> property in ONE Record.</p>
3883
-
</li>
3884
-
<li>
3885
-
<p>In the <code>ApplicableRating</code> grouping, the <code>TypeCode</code> field is set to F (Facial) by default as it is the only value used with CXML.</p>
3886
-
</li>
3887
-
<li>
3888
-
<p>In the <code>ApplicalbeFreightRateServiceCharge</code> grouping, the <code>AppliedAmount</code> is not directly mapped as it is a total that needs to be derived from either the <strong>Rate</strong> or the multiplication of <strong>Rate</strong> and <strong>Chargeable weight</strong> depending on the type of charge. Refer to CSC Resolution 600a for further explanations.</p>
<p>In its essence, XFZB is very similar to XFWB. <code>Waybill</code> object is the main focus and many details are from the <code>Shipment</code>(s) linked to it as well as the <code>TransportMovement</code>.</p>
3893
3767
<p>The major distinction in the <code>Waybill</code> object for XFZB is the usage of <code>Waybill#waybillType = House</code>.</p>
3894
3768
<p>Another major distinction with XFWB is that for the time being we recommend a mapping of the <code>TransportMovement</code> through the <code>Loading</code> action with a Planned or Scheduled state. Since the <code>Booking</code> object has been mainly designed for the Carrier to Freight Forwarder contractual agreement, there is no specific <code>LogisticsService</code> reflecting the House Waybill contractual agreement yet.</p>
<p>XFHL message is used to communicate the list of House Waybills associated to a Master Waybill. This message is not focused on details at House level, only high level information is shared.</p>
<p>The starting point is a Master <code>Waybill</code> and we are interested in all the House <code>Waybill</code>(s) linked to the Master via the <code>Waybill#houseWaybills</code> object property. </p>
<p>XSDG specifications, aligned with the Dangerous Goods Declaration (DGD) requirements have been integrated into ONE Record, the details can be found on the Data Model section, under "Dangerous Goods".</p>
3902
3776
<p>The need for a proper XDSG mapping still needs to be assessed.</p>
<p>XFSU message is used to provide a Shipment Status update, discrepancy details or sometimes to provide complementary Customs information.
3906
3780
In most cases, the Status updates is based on the usage of <code>LogisticsEvents</code> on the Shipment and/or the Pieces. The XFSU data fields are then a mix of Waybill, Shipment, Pieces and LogisticsEvent data in ONE Record realm.</p>
3907
3781
<p>In case of <strong>full shipment</strong> status update, the <code>LogisticsEvents</code> can be added on the Shipment or on all the Pieces. Both scenarios are valid.</p>
<p>The Flight Manifest represents an essential set of data that is today either a Paper document or a message (FFM or XFFM). It contains the details of cargo that is transported.</p>
3918
3792
<p>ONE Record by essence contains all the required data, Flight details, Piece and ULD details and so on.</p>
3919
3793
<p>Multi-destination usecases will require the aggregation of data starting form multiple <code>TransportMovement</code> objects if required for the generation of an XFFM equivalent.</p>
<p>The <code>starting point</code> of the manifest is the flight, or the <code>TransportMovement</code> in ONE Record. The Manifest requires information from <code>Piece</code>, <code>ULD</code>, <code>Shipment</code> and <code>Waybill</code> objects mainly.</p>
3922
3796
<p><code>Piece</code> details are central and from the <code>TransportMovement</code> there are two possiblities:</p>
<h4id="definition-from-cxml-toolkit">Definition from CXML toolkit<aclass="headerlink" href="#definition-from-cxml-toolkit" title="Permanent link">¶</a></h4>
3931
3805
<p>To supply a complete list of consignments for which space has been reserved in a particular flight, including details of the agent/airline from which the consignments will be received and, if known, inward flight details as well.</p>
3932
3806
<p>When a carrier is controlling his own flight but the physical handling of consignments is carried out by a handling party (agent/airline), the former will issue an XFBL message to the latter to provide him with a complete list of consignments for which space has been booked and any other relevant information</p>
<p>The XFBL data requirements are similar to XFFM however the mapping changes as XFBL refers to freight <strong>booked</strong> on a flight while XFFM refers to freight <strong>loaded</strong> on a flight.</p>
3935
3809
<p>There are two possible mapping depending on the usage of ONE Record by the Airline/GHA.</p>
<p>The XTMV message is intended to dispatch departure and arrival notification in XML immediately after departure or arrival of a surface transportation. Delay, cancellation and diversion of an aircraft will also be dispatched using XTMV as soon as it is known. (cf. Cargo-XML Toolkit definition).</p>
3942
3816
<p>The need to do a full mapping of XTMV message with ONE Record needs to be properly assessed based on the necessity and the actual usage of the message currently.</p>
<li>Transport Movement Header contains information about Origin and Destination, Type of Transport, Transport Means and Operator details. These details are available with usage of <code>TransportMovement</code>, <code>TransportMeans</code> and <code>TransportMovement#operatingParties</code> objects.</li>
0 commit comments