NDC FAQs: Reporting and MBOS

NDC bookings made through 1P/1V will automatically create a passive (ZK) segment with all the NDC flight data, fare, taxes, etc. captured in the DI lines (Travelport+), Ticketing Remark lines (1V), or Remark lines (1P), and these will flow through to the MIR (Travelport+ and 1V) and TAIR (1P) to flow through to mid- and back-office systems. This similar process is used today for booking low cost carriers via the LCC’s API.

MIR and TAIR data is transmitted in the same way as any type of booking, and NDC data will be stored in the DI lines (Travelport+), Ticketing Remark lines (1V), or Remark lines (1P). It is not automatically transmitted.

Important: Have early discussions with the agency and/or MBOS providers to review any work required on their side to capture this data from the MIR and TAIR files because it is different to an ordinary air booking.

Agencies will need to use non-faring options in the transmission. This is because we are not storing fares/prices.

In 1V it will be DJD modifier

J = NON-FARING MIR (DJD command used). The DJD command transmits a MIR only to the MIR device targeted in the command. This MIR does not enter the fraud package and does NOT contain ANY fare information (APO only). The DJD command will also transmit a non-faring MIR for non-participant carriers with or without a MIR device targeted in the command (APO only).

In 1P it will be EZI|@B0.00 (@B is the fare override)

Show 1V example

TPCQCA/WS DENOU J0B/GWS AG 14537482 10FEB

1.1SATHISHH/SARAVANAN

1 AA7562O 15MAY SFOLAS ZK1   700A  832A           MO

OPERATED BY ALASKA AIRLINES

FONE-ORDR/1--212456121-/1.1

FOP:-S

TKTG-T/

>HBDJD

NON - FARED   MIR ISSUED - TTL FARE      0.00

TAB AND ENTER TO REDISPLAY PNR >*TPCQCAí

Show 1P example

1P- NECVH7 ¬

1.1BEST/TEST.MR*ADT¬

1 AA1832Y 25SEP MO DENDFW ZK1  1638  1950 /O A E @¬

2 AA2749Y 28SEP TH DFWATL ZK1  2030  2342 /O A E @¬

P- 1.T4S----30333333-H/1.1¬

T- 1.T/11FEB1355  1P/T4S/CE*5230421412820 *I¬

TKG FAX-NOT PRICED  FARE TYPE EX ¬

FOP- 1.CA ¬

**** ITEMS SUPPRESSED ****/DH/DR¬

>

>EZI|@B0.00

TRANSACTION COMPLETE PNR >*NECVH7(¬

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 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.

No, the MIR or TAIR is not automatically updated with these modifications. A DI. line (1G and 1V) or remark line (1P) will be added to the PNR with these actions. Keep in mind that a PNR with no segments will go into a past date status and a MIR or TAIR cannot be generated. A workaround is to ensure you input retention lines in the PNR before doing these actions to keep the PNR alive so you can re-send the MIR.

HMPR and DDL will not be updated, as these are the GDS record of ticket numbers, which we create. As the airline is doing the ticketing, they are in control of the ticket number and ticket number reports. Some airlines are looking at order history, but this is not implemented yet through IATA standards.

No, these entries will not work. However, in 1P using the *M entry, the ticket number will be displayed separately.

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.

For more format options for Travelport+, refer to Formats for List Display.

For Worldspan, there is not a host entry that would display all ZK bookings. An option would be to do a PNR Search which could be used to put all PNRs on a specific queue that contained a segment with a ZK segment status. A QLD entry would provide a list of all the PNRs on queue.

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.