Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When two or more elements are present, which indicate two distinct events, i.e. BagEventCode, the event is decided by the first matching rule in the table below:

BIM ElementBIM DescriptionBagEventCodeBagEventErrorCodeBagEventDescription

DEL

DeletedBagInfoReceived
Deleted
.B/<status>

Baggage irregularity

<status>:
NAL: Loaded, but not authorised for loading
OFF: Offloaded
OND: On-hand, not loaded, not authorised for loading
ONA: On-hand, not loaded, authorised for loading

BagInfoReceived

If <status> is NAL, OFF, OND, ONA then
→ Not Loaded (<status>)


.U
BagInfoReceived

If BUM → Unloaded (<status>)
else → Loaded (<status>)

.X/... /<status>

Screening Cleared
<status>:
REJ: Screening Rejected
CLR: Screening Cleared
UCL: Screening Unclear

BagInfoReceived

If <status> REJ → Screening Rejected
If <status> CLR → Screening Cleared
If <status> UCL→ Screening Unclear

.G/<earliest datetime>/<latest datetime>/<address>
BagInfoReceived

Always → <address>

.J/<code>Processing information
<code>:
R: Reconciliation
S: Sortation
G: Ground Tracking
H: Hand scanned
BagInfoReceived

If <status> R → Reconciled
If <status> S → Sorted
If <status> G → Ground Tracked
If <status> H → Hand Scanned


.R/<data>Internal Airline DataBagInfoReceived

Always → <data>