Customer — Custom Fields
The extension adds 14 fields to the standard Customer table. These fields control how the system handles bookings, invoices, and credit card settlements for each customer.
Field Reference
| Field ID | Field Name | Data Type | Description |
|---|---|---|---|
| 51309 | Require Department | Boolean | When enabled, the system warns if Department is empty on sales order lines created from AIR bookings |
| 51310 | Require Project Number | Boolean | When enabled, the system warns if Customer Project is empty on sales order lines |
| 51311 | Require Cost Place | Boolean | When enabled, the system warns if Cost Center is empty on sales order lines |
| 51312 | Require Employee Number | Boolean | When enabled, the system warns if Employee ID is empty on sales order lines |
| 51322 | Require Requisition No | Boolean | When enabled, the system warns if Requisition No is empty on sales order lines |
| 51323 | Require Requester | Boolean | When enabled, the system warns if Requester Name is empty on sales order lines |
| 51313 | Credit Card Provider | Enum | Which credit card provider handles this customer's payments. Values: None (default — invoice payment), FirstCard, Diners |
| 51314 | Credit Card No. | Text[16] | The customer's corporate credit card number. Required when Credit Card Provider is not None |
| 51316 | Specify Service Fees | Boolean | When enabled, service fees are itemized separately on the invoice report instead of being grouped |
| 51317 | Hotel Voucher Option | Enum | Controls how hotel vouchers are handled. Values: Manual (user decides per booking), Yes (always create voucher), No (never create voucher) |
| 51318 | Car Rental Voucher Option | Enum | Controls how car rental vouchers are handled. Same values as Hotel Voucher Option |
| 51319 | Hotel Voucher Dismissed | Boolean | Internal flag — suppresses the voucher decision prompt after user has dismissed it. Not for manual configuration |
| 51320 | Car Rental Voucher Dismissed | Boolean | Internal flag — same as above for car rentals. Not for manual configuration |
| 51321 | Excl. Currency Rate Markup | Boolean | When enabled, the currency rate markup percentage (from AIR Setup) is not applied to this customer's bookings |
Config Package Mapping
When building a config package, include these fields from the Customer table (table ID 18):
| Include in Package | Field ID | Typical Source |
|---|---|---|
| Yes | 51309–51312, 51322–51323 | Customer requirements document — which reference fields are mandatory per customer |
| Yes | 51313 | Contract with Diners/FirstCard — which provider, if any |
| Yes | 51314 | Customer's corporate card number |
| Yes | 51316 | Customer preference — itemized service fees or not |
| Yes | 51317–51318 | Customer preference — voucher behavior |
| No | 51319–51320 | Internal flags, leave as default (false) |
| Yes | 51321 | Customer agreement — currency markup exclusion |
Behavior Details
Required Field Warnings
The "Require" flags (Department, Project Number, Cost Place, Employee Number, Requisition No, Requester) do not block order creation. Instead, they generate warnings (visible in the Order Reference Warning table) when the corresponding field is empty on a sales line. This allows the booking to be processed while flagging missing information for follow-up.
The data for these fields comes from RM remarks in the AIR booking file:
- Department → from
RM*ADremark - Customer Project → from
RM*PRremark - Cost Center → from
RM*COremark - Employee ID → from
RM*EMremark - Requisition No → from
RM*REremark - Requester Name → from
RM*YRremark
Credit Card Provider
When a Credit Card Provider is set on a customer:
- Sales orders created for this customer are automatically tagged with the provider
- The credit card status tracking is enabled on the order
- Settlement files can be generated for the provider
- The Credit Card Provider field on the sales order is locked (cannot be changed manually) for AIR-created orders
Voucher Options
The voucher option controls what happens when a hotel or car rental booking is processed:
- Manual: The user is prompted to decide whether to create a voucher or confirmation for each booking
- Yes: A voucher is always created automatically
- No: No voucher is created; a regular sales line is created instead