AIR Order Item Mapping (Table 51339)
The AIR Order Item Mapping table determines which Item is used on sales order lines when processing an AIR booking. Each row maps a combination of product type, region, service type, web origin, and voucher flag to a booking item and a service fee item.
Page
Accessible via AIR Item Mapping page (search for "AIR Item Mapping" in Business Central). You can also enter mappings directly in this page instead of importing via config package.
Primary Key Structure
| Field ID | Field Name | Data Type | Values |
|---|---|---|---|
| 1 | Product Type | Enum | Other, Flight, GroundTransport, Train, Hotel, CarRental |
| 2 | Region | Enum | Domestic, Nordic, NordicNonEU, Europe, EuropeNonEU, International |
| 3 | Service Type | Enum | Booking, Void, Exchange, Refund |
| 4 | Is From Web | Boolean | True if booked via online tool, False if booked by agent |
| 5 | Plus Voucher | Boolean | True if the line includes a voucher component |
Item Fields
| Field ID | Field Name | Data Type | Description |
|---|---|---|---|
| 6 | Booking Item No | Code[20] | Item used for the main booking line (flight, hotel, car rental, etc.). Must reference a valid Item |
| 7 | Service Fee Item No | Code[20] | Item used for the service fee line associated with this booking. Must reference a valid Item |
| 8 | Booking Item Description | Text | Read-only — auto-populated from the Item table |
| 9 | Service Fee Item Description | Text | Read-only — auto-populated from the Item table |
How It Works
When the system processes an AIR booking and creates a sales order line:
- It determines the Product Type from the booking segment (Flight, Hotel, CarRental, etc.)
- It determines the Region from the flight route or destination country (using the AIR Region on Country/Region)
- It knows the Service Type from the AIR file type (Booking, Void, Exchange, Refund)
- It checks Is From Web based on the booking source
- It checks Plus Voucher based on whether a voucher is being created
- It looks up the matching row and uses the Booking Item and Service Fee Item for the sales lines
Example Configuration
| Product Type | Region | Service Type | Is From Web | Plus Voucher | Booking Item | Service Fee Item |
|---|---|---|---|---|---|---|
| Flight | Domestic | Booking | No | No | FLIGHT-DOM | SVC-FEE-DOM |
| Flight | Domestic | Booking | Yes | No | FLIGHT-DOM-WEB | SVC-FEE-DOM |
| Flight | Nordic | Booking | No | No | FLIGHT-NOR | SVC-FEE-NOR |
| Flight | Europe | Booking | No | No | FLIGHT-EUR | SVC-FEE-EUR |
| Flight | International | Booking | No | No | FLIGHT-INT | SVC-FEE-INT |
| Flight | Domestic | Refund | No | No | FLIGHT-DOM-REF | SVC-FEE-DOM |
| Hotel | Domestic | Booking | No | No | HOTEL-DOM | SVC-FEE-DOM |
| Hotel | Domestic | Booking | No | Yes | HOTEL-DOM-V | SVC-FEE-DOM |
| Hotel | Europe | Booking | No | No | HOTEL-EUR | SVC-FEE-EUR |
| CarRental | Domestic | Booking | No | No | CAR-DOM | SVC-FEE-DOM |
| GroundTransport | Domestic | Booking | No | No | GROUND-DOM | SVC-FEE-DOM |
Config Package Notes
- This is a multi-row table — create rows for all combinations that the customer uses
- The number of rows depends on:
- Which product types the customer handles (flights only? flights + hotels? all types?)
- How many regions they need to distinguish
- Whether they differentiate web vs. agent bookings
- Whether they use vouchers
- All referenced Items must exist before importing this table
Planning the Mapping
To determine which rows are needed, answer these questions:
- Which product types does the customer sell? (Flight, Hotel, Car Rental, Ground Transport, Train)
- Does the customer need different items per region? (e.g., domestic vs. international flights)
- Does the customer differentiate web bookings? (different items for online vs. agent-booked)
- Does the customer use vouchers? (if yes, do voucher bookings use different items?)
- Does the customer handle refunds/exchanges/voids? (these may need different items)
caution
If a booking is processed and no matching Item Mapping row is found, the system will raise an error. Make sure all expected combinations are covered before go-live.