The FBO One database stores a broad set of data. For example aircraft details, customer details, orders, service requests, and so on. Each of these entities contain data elements in the form of fields, for example, a customer record contains a name, a short name and a contact number.
The exact use and purpose for each of these fields in defined in the pages below:
Administration (Fields) — An administration in FBO One is defined for each back office in the FBO network that issues its own invoices. Each Administration in FBO One can have it's own entry export format to an external accounting system.
Aircraft Registration (Fields) — The aircraft registration screen in FBO One contains the following fields that can be edited within the edit registration screen.
Aircraft type (Fields) — An aircraft type in FBO One has the following fields that can be edited in the edit aircraft type screen.
Auto-add Product (Fields) — The Auto-add Product feature has the following fields to allow setting conditions for products to auto-add to Orders, conditions can be combined to allow specific auto-add rules.
Flight leg (Fields) — A Flight leg or a 'movement' represents a flight sector inbound or output n arrival or departing flight sector. in FBO One has the following fields that can be edited in the edit flights screen, or directly in the create order screen.
Parking position (Fields) — A p https://amsterdam.jira.com/wiki/spaces/MAN/pages/9080351arking position has the following fields that can be edited in the Parking areas & positions (Administration) page.
Peak Categories / Peak Lists (Fields) — A peak category and peak list has the following fields that can be edited in the Peak categories (Administration) & Peak lists (Administration) screens.
Price agreement (Fields) — A price agreement has the following fields that can be edited in the Admin Price Agreements (Administration) screen and the price agreements tab of the Product details screen, Organization contact details screen.