SAP Knowledge Base Article - Preview

3815334 - New Concur Travel - Why are finishing remarks built on SegNum not written to the PNR for Sabre NDC bookings?

Symptom

Travel Management Companies (TMCs) that use PNR finishing templates with conditions referencing the `SegNum` data point (the GDS-assigned segment line number) may find that those conditions never evaluate to true for Sabre NDC bookings. As a result, any remarks, reason codes, or other finishing actions that depend on `SegNum` being present are silently skipped.

The affected finishing template path is: 

PNRFinishData/CliqbookItineraryDisplay/Segments/FlightSeg/SegNum

This affects all Sabre NDC air bookings (product type `AIR_NDC`). Traditional Sabre GDS bookings are not affected.
2026-07-08_14-47-00.png
 


Read more...

Environment

Travel > Core Travel

Product

Concur Travel all versions

Keywords

When a Sabre NDC booking is made through New Concur Travel and violates a travel policy rule, the finishing template condition that checks for the flight segment number (`SegNum`) is not met, so the expected PNR remarks are not written. , KBA , CON-SRV-TRV-ADM-FIN , Finishing Template Editor , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.