NDC FAQs: Reporting and MBOS

These frequently asked questions provide information about reporting and mid- and back-office systems (MBOS).

Refer to the other FAQ topics for information about getting started, shopping and booking, seats, and servicing for NDC content.

Question

Answer

Customers want to issue an invoice for NDC PNRs, including the Service Fees, with totals, terminal, seat information, etc. Are we going to have an outlined process for this?

The DI. lines and remarks fields can be used for MBOS data; the agent will then have to use their own methods to extract this to create a customer invoice.

In NDC when doing an exchange ticket for the booking, how will this flow through to MBOS?

In NDC all passengers in the booking are exchanged together and the amount per ticket is reported together for all passengers in the DI lines and not per passenger. We are aware MBOS providers logic is to capture data for one passenger at a time. So MBOS providers will need to have new logic in place to capture this information for all passengers. In NDC if you are only exchanging the ticket for one passenger, then that passenger needs to be split out on his/her own PNR.

How can I see a list of all the PNRs I’ve created for NDC?

A list of all NDC PNRs created is available using the current GDS formats and the passive ZK PNR is returned in the PNR list. For example:

LD/SC-ZK/C24OCT*02NOV/01JAN*20OCT-D

returns a display of all PNRs with a status code of ZK between the dates input. Please note that this returns ALL segments with a status code of ZK, which could include low cost carrier segments as well as NDC. This displays on the Smartpoint cryptic screen.

To restrict results to a particular carrier within a date range, use entry: 

LD/SC-ZK/QF/1NOV*30DEC-D

Where QF is the carrier code.

Can NDC create GDS booking file with passive segment for mid-back-office integration purposes?

While agents are not able to create passives manually within the GDS environment for NDC bookings, any NDC bookings done through Travelport will have a special type of passive (a ZK passive segment) automatically created in our system to flow into mid-back-office integration.  This is the same system we use today for low cost carrier segments obtained through the LCC’s API so is not new.

If ARC, what would identify an NDC ticket from other ARC tickets?

The Airline Ticket stock form code on your ARC report would be different to your agency ticket stock as in NDC the airline is issuing the ticket and the ticket number would be from AA’s ticket stock, not your agency stock. This could be different than your existing direct carrier fulfilment processes.

Below is an example of the IAR report:

  • #TT will show ET.

  • If NDC booking qualifies for commission based on your agreement with AA, you would add your commission in the IAR box.

  • Service Carrier ID will show 9413 FareLogic as the Service Carrier.