An order in FBO One has the following fields that can be edited in the edit order screen. On creating an order, more fields seem to be available; but those are actually flight leg fields.
the aircraft this order is for.
the debtor thats going to pay for this order. The default debtor is taken from the registration. The debtor is a mandatory field. Every order has a debtor. The debtor automatically receives a movement notification email on arrival and departure.
Debtor order number
the ordernumber from the debtor. This field is printed on the handling order, and some debtors want to see it. It is commonly used for Netjets flights (and used by the Netjets link) to enter the request number for the arrival and departure in this field. It shows up on the handling order like this:
Free text remark that will be printed on the handling order report. This can be used for example to specify the name of the person that requested this order. It shows up on the handling order like this:
the operator for this order. This field is used to check the AOC (Glossary) for VAT (Glossary) calculation. The default operator is taken from the registration. The operator automatically receives a movement notification email on arrival and departure.
Trip support provider
the trip support provider for this order, this organization will get movement messages. The default trip support provider is taken from the registration. In case the flight has been requested by a trip support provider such as Universal, you can specify the handling team here. The trip support provider automatically receives a movement notification email on arrival and departure.
This is a reference number for the trip support provider. This field can be set by EnterTripNumber transition workflow transition action.
Form of payment
theform of payment for this order. It can be set by the PayOrder transition and SetFormOfPayment workflow transition actions.
The receipt number for electronic payments. It can be set to be mandatory for certain forms of payment, and a special workflow transition action (PayOrderWIthReceiptNumberCheck) can check for it.
Pre-assigned parking position
With the pre-assigned parking position you can specify on which parking position the aircraft must be parked. This makes it possible to schedule the parking. On arrival, the pre-assigned parking position is used as the default parking position. When the parking module is disbled, the pre-assigned position is used as the actual position for price calculations by the parking calculator.
this field will not be printed on any report intended for external use.
this field will be printed on the handling order.
The exact amount actually paid, set by the PayOrder transition workflow transition action. In combination with the Form of payment field, this field is used by FBO One to determine if there is a price difference or not.
Order details screen
Edit order screen