Versions Compared

Old Version 4

changes.mady.by.user Ole Nymoen

Saved on

compared with

New Version Current

changes.mady.by.user Ole Nymoen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


...

scrollbar

...


Page properties


TermTransactionUsageCode
Business termTransaction Usage Code
Description


Excerpt

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
was created based on this transaction
  • can be created
  • An existing flight leg
was updated from this transaction.
  • can be updated
  • The transaction
was
  • can be ignored due to prioritization
The transaction was ignored since it didn
  • 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


Status
Proposal
Approved 2021-05-28
XML typestring(2)
Ref from


Incoming Links
modeflat
spaces@all
stylenone



Labels
Page info
labels
labels
typeflat