xFWB Mapping: Connect TransportMovement (Flight) to Waybill through Booking instead of Loading

[NiclasScheiber]

An xFWB refers to a flight a shipment is booked on.

The currently proposed way to connect the booked TransportMovement to a Waybill is as follow:

Waybill -> Shipment -> Piece -> Loading -> TransportMovement

This approach has some problems:

• If a Piece is connected to multiple Loadings (and TransportMovements), such as on- and pre-carriage trucking, you will not be able to easily fetch the TransportMovement that describes the flight without resolving all connections
• Loading (and LogisticsActions in general) describe a physical relationship, which is not yet clear when a flight is only booked

Hence, I propose to change to the following:
Waybill -> Booking -> ActivitySequence -> TransportMovement

With the advantages:

• Follows the way ONE Record's Service-Activity-Model was designed
• Clearly indicates the relationship of a Flight to the Waybill (at this stage, it is booked)
• This allows to keep operational discrepancies in the 1R data: The Flight in the original AWB (contract) would stay, even if (parts of) the shipment takes another one for operational reasons

You should only use and create Loading actions when you know when and where the actual Pieces will be loaded on an aircraft; as in the physical action of doing so is planned.

[lambertciata]

This issue can be directly linked to #249

[lambertciata]

Your proposal makes sense and goes along the remarks from #249 . Data in the Waybill are most likely inherited from the Booking than the actual load plan.

It seems to simplify as well the mapping between 1R and XFWB.

[lambertciata]

To illustrate the proposal see the 2 images below:

[lambertciata]

Update the mapping accordingly with the proposal