3824548 - New Concur Travel - Why is the air violation code selected during booking not appearing in the finishing template Trip/Violation_Code_Air datapoint?

During the air booking process, travelers may be required to enter a reason code when selecting an out-of-policy flight. The selected violation code is visible in the itinerary data, but when the finishing template runs, the Trip/Violation_Code_Air datapoint is empty or falls back to a default value. As a result, finishing templates that use this datapoint — for example, to write a fare savings code remark into the GDS PNR — emit the wrong or missing value.

This issue affects New Concur Travel bookings where the finishing template is configured to read the Trip/Violation_Code_Air XPath. The problem is specific to new-experience bookings and does not affect classic Concur Travel bookings.

When travelers select a policy violation code during an air booking in New Concur Travel, the code may not appear in the `Trip/Violation_Code_Air` XPath datapoint used by finishing templates. This affects companies whose finishing templates rely on that datapoint for GDS queue writes, approvals, or TMC processing. , KBA , CON-SRV-TRV-ADM-FIN , Finishing Template Editor , Problem