You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »


TermTransactionUsageCode
Business termTransaction Usage Code
Description

Code describing how a transaction was used in a system. For instance, if an AODB receives a transaction there are a number of typical usages:

  • A new flight leg can be created
  • An existing flight leg can be updated
  • The transaction can be ignored due to prioritization
  • It can be ignored if it doesn't match an existing flight leg, and isn't the type of transaction that are used to create a flight leg

Legal values

The following list of codes are defined:

  • "01" - A Flight or FlightLeg was created based on the transaction
  • "02" - A Flight or FlightLeg was updated based on the transaction
  • "03" - The transaction was not used due to prioritization
  • "04" - The transaction was not used as it could not be matched to an existing Flight or FlightLeg, and could not be used to create a flight leg.
  • "05" to "29" are reserved for future use
  • "30" to "99" are reserved for airport specific codes
Comments


StatusApproved 2021-05-28
XML typestring(2)
Ref from


Labels
  • No labels