Symptom
Investigation determined that for EDIFACT bookings in New Concur Travel, the credit card form of payment (FOP) is not included in the Sabre pricing request used to create the stored PQ. As a result, Sabre cannot resolve a card-specific OB fee and instead returns a list of conditional OB fees with messaging indicating that the final fee depends on the form of payment used.
The review found that:
- The booking flow has access to the FOP information (card type, token, expiry).
- The
setAirPriceRequest()function in the Sabre adapter creates the pricing request stored in the PNR but does not populate theFOP_Qualifiersnode. - Without the credit card BIN/FOP details, Sabre cannot calculate and document a specific OB fee within the stored PQ.
- Agents who subsequently update or reprice the PQ can generate a PQ that includes the applicable OB fee based on the form of payment used.
- This behavior applies to EDIFACT bookings. NDC bookings currently support passing payment information during pricing.
Read more...
Environment
Product
Keywords
This article explains why OB fees are not included in the stored PQ total for New Concur Travel EDIFACT bookings and why differences may exist between the original Concur PQ and an agent-updated PQ. , KBA , CON-SRV-TRV-SBR , TwsSabre Test , 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.
SAP Knowledge Base Article - Preview