NVB & NVA

As there is no industry standard processing logic or ATPCO Data Application for NVB/NVA Travelport process as follows.

When a rule contains Category 16 data indicating that voluntary changes are either not permitted, or permitted for a charge, the NVB/NVA fields are populated with the actual dates of the booked flight of each sector of the itinerary. The actual dates of the confirmed sector derived from Category 16 validation take precedence over minimum and maximum stay and last travel dates derived from categories 6, 7, 14 and footnotes. Many/most rules have minimum and/or maximum stay and/or last travel dates in addition to Category 16 penalties. In all cases, the presence of Category 16 data restricting voluntary changes requires the dates of booked sectors to be populated in the NVB/NVA fields.

When Cat 16 Bytes 8, and/or 14, and/or 16 are populated with value X, and bytes 24-27, and/or 32-35, and/or 40-43 contain values greater than zero, NVB/NVA fields must contain the actual segment dates.

The dates that are used to populate the NVB/NVA fields of the ticket are a product of rules validation. The categories validated for NVB/NVA data are 6, 7, 14, 16, and footnotes which contain last travel dates. If no data is found in the relevant categories or footnotes, the NVB/NVA fields are blank.

Not Valid Before

When a minimum stay date is determined from data coded in category 6, that date is populated in the NVB field of the coupon at the point of validation and in all subsequent coupons of the pricing unit. The point of validation, or measurement is usually determined by a TSI. Once the point of validation is determined, the NVB dates must be populated on that coupon and all subsequent coupons in the pricing unit.

Not Valid After

When a maximum stay or last travel date is determined from data contained in category 7 or 14 or footnote, that date is populated in the NVA field of all coupons of the pricing unit. When the data is processed, a given itinerary may have a maximum stay and a last travel date. In this case, the more restrictive date is validated and populated in the NVA field(s).

However as mentioned above data contained in category 14 or footnotes applicable to outbound travel is not populated in the NVB/NVA fields.

The fare has a Max Stay of 3 Months where Departure is 08Nov and a Category 14 restriction as follows

Standard Processing : The example below shows the NVA field populated with the Max Stay (Category 7)

Exception Processing: Below example for the same fare as above with the exception processing activated populates from Category 14 data

If you wish to have the outbound Travel Restriction (Category 14) data shown in the relevant NVA Box as above please contact your Account Manager.

Combinations

When two or more fares with different minimum stay, maximum stay, or last travel dates are combined to create a single pricing unit, the NVB/NVA fields are populated with the dates of the rule which is most restrictive.

When a pricing solution is a combination of multiple pricing units, the NVB/NVA dates should be applied separately within each pricing unit.