[skip ci] Updates

api-reference/direct-connects/hotel-service-4/v4.single-pnr-solution.md

@@ -1,26 +1,29 @@
 # Single PNR Solution For CHS
 
-**Note: This feature is not yet generally available.**
+{% include prerelease.html %}
 
 ## Overview
-This document describes the design of "Single PNR Solution" for Hotel's direct connect offering of Custom Hotel Source (CHS) program.
 
-For bookings made using CHS today, if passives are enabled, we have two PNRs associated with each hotel booking. Concur creates and manages a PNR in the appropriate GDS for the trip and adds a passive segment to that PNR with details of the hotel booking made by the CHS supplier. The CHS supplier also creates a PNR in the GDS with the active segment. Duplication of PNRs not only causes sync and operational issues but also adds cost for each booking. Hence, in cooperation with CHS suppliers, we have come up with a solution where there is only one PNR created for the CHS hotel booking. This solution will be applicable to both GDS and non-GDS content booked through the CHS supplier.
+This document describes the design of the Single PNR (passenger name record) Solution for Hotel's direct connect offering of the Custom Hotel Source (CHS) program.
+
+For bookings made using CHS today, if passives are enabled, we have two PNRs associated with each hotel booking. The SAP Concur platform creates and manages a PNR in the appropriate GDS for the trip and adds a passive segment to that PNR with details of the hotel booking made by the CHS supplier. The CHS supplier also creates a PNR in the GDS with the active segment. Duplication of PNRs not only causes sync and operational issues but also adds cost for each booking. Hence, in cooperation with CHS suppliers, we have come up with a solution where there is only one PNR created for the CHS hotel booking. This solution will be applicable to both GDS and non-GDS content booked through the CHS supplier.
 
 ### Solution
 
-At a high-level, solution consists of:
-- Concur passes existing PNR locator or create a shell PNR (if hotel is first booking) to HSv4 endpoint for hotel booking
-- TMC/Supplier confirms the hotel booking with their source (GDS or direct-connect) and work on the PNR (segment, remarks etc.) and release it back to Concur. If source is GDS, supplier will create an active segment while if source is direct-connect, supplier will create a passive segment.
-- Concur takes the PNR back and perform finishing.
-- If GDS booking ("active" segment added by supplier) - all post-booking operations like `Retrieve` and `Cancel` will be managed as `GDS` booking within Concur. That is, HSv4 read and cancel endpoints will not be used and instead Concur will work directly with GDS to read/cancel booking.
-- If supplier supports `Modify` flow, Concur will use HSv4 endpoints to allow supplier to reshop and modify the booking.
-
-## Requirements from TMC/Supplier for this solution
-- TMC/Supplier will use standard active and passive segment format as required by Concur.
-- TMC/Supplier will have option to manage their own passive segment or use current Concur managed solution for passives. If they choose to manage their own passives, they will need to:
-  - Disable passive segment creation for CHS bookings to avoid duplicate passive creation for non-gds hotels.
-  - Create new passive segment in Concur created PNR along with booking with their direct connect source (as detailed in the design).
+At a high-level, the solution consists of:
+
+- We pass an existing PNR locator or create a shell PNR (if hotel is first booking) to the Hotel Service v4 endpoint for hotel booking.
+- TMC/Supplier confirms the hotel booking with their source (GDS or direct-connect) and works on the PNR (segment, remarks, etc.) and releases it back to us. If source is GDS, supplier will create an active segment. If source is direct-connect, supplier will create a passive segment.
+- We take the PNR back and perform finishing.
+- If GDS booking ("active" segment added by supplier) - all post-booking operations like `Retrieve` and `Cancel` will be managed as `GDS` booking within the SAP Concur platform. That is, Hotel Service v4 read and cancel endpoints will not be used and instead we will work directly with GDS to read/cancel booking.
+- If the supplier supports `Modify` flow, we will use Hotel Service v4 endpoints to allow supplier to reshop and modify the booking.
+
+## Requirements from TMC/Supplier for this Solution
+
+- TMC/Supplier will use standard active and passive segment format as required by the SAP Concur platform.
+- TMC/Supplier will have option to manage their own passive segment or use our managed solution for passives. If they choose to manage their own passives, they will need to:
+  - Disable passive segment creation for CHS bookings to avoid duplicate passive creation for non-GDS hotels.
+  - Create new passive segment in the SAP Concur platform created PNR along with booking with their direct connect source (as detailed in the design).
   - Cancel passive segment as part of their `cancel` flow along with canceling the booking with their direct connect source.
 
 ## Design
@@ -29,29 +32,32 @@ At a high-level, solution consists of:
 
 ![](images/diagrams/singlepnr/hotel_book.png)
 
-Above sequence diagram shows the flow for booking a hotel using CHS supplier that supports single PNR solution. Highlights of the flow are:
-- CHS supplier will never create a GDS PNR with this solution. During booking request, Concur looks up already existing PNR associated with the Trip and travel config used or creates a new shell PNR and associates with the trip.
-- Concur obtains an internal lock on the PNR (for 60 secs) and sends the hotel booking request to supplier with the PNR locator.
-- If supplier is booking with GDS, they will use this PNR locator to add the active segment to the PNR. If rate to book belongs to direct connect (e.g. Booking.com/Expedia), supplier will book with that direct connect and add a passive segment to PNR referenced by this record locator.
-- Once booking is done, Concur will release the PNR lock making PNR available for further changes e.g. adding Air/Car bookings, finishing etc.
-- If supplier takes longer than 55 secs, booking transaction will time out.
-- If PNR lock times out, lock will be released automatically to allow further actions on this PNR. In order to prevent "Simultaneous access" errors for user, it is necessary for supplier to honor this timeout and stop working on PNR after this. 
-- Booking response from supplier is expected to have `ActiveSegmentInConcurPNR` flag to indicate if the active segment was added to Concur PNR or not. This flag will be used to decide if Concur should treat this booking as GDS booking or direct-connect booking for post-booking functions.
+The above sequence diagram shows the flow for booking a hotel using a CHS supplier that supports single PNR solution. Highlights of the flow are:
 
-### Cancel flow
+- A CHS supplier will never create a GDS PNR with this solution. During a booking request, we look up the existing PNR associated with the Trip and travel config used or create a new shell PNR and associate it with the trip.
+- We obtain an internal lock on the PNR (for 60 secs) and send the hotel booking request to supplier with the PNR locator.
+- If the supplier is booking with GDS, they will use this PNR locator to add the active segment to the PNR. If rate to book belongs to direct connect (e.g. Booking.com/Expedia), supplier will book with that direct connect and add a passive segment to PNR referenced by this record locator.
+- Once booking is done, we will release the PNR lock making PNR available for further changes for example, adding Air/Car bookings, finishing, etc.
+- If the supplier takes longer than 55 secs, booking transaction will time out.
+- If the PNR lock times out, lock will be released automatically to allow further actions on this PNR. In order to prevent "Simultaneous access" errors for the user, it is necessary for supplier to honor this timeout and stop working on PNR after this. 
+- Booking response from the supplier is expected to have `ActiveSegmentInConcurPNR` flag to indicate if the active segment was added to the SAP Concur platform PNR or not. This flag will be used to decide if we should treat this booking as GDS booking or direct-connect booking for post-booking functions.
 
-As mentioned earlier, if `ActiveSegmentInConcurPNR` is set true booking is treated as GDS booking and Concur will manage cancel flow directly with GDS. Though, CHS supplier will still be notified using HSv4's [cancel endpoint](./v4.endpoints.html#cancel-). Note that invocation of `cancel endpoint` is only for notification to allow CHS supplier to perform any cancel related processing in their system and hotel booking with GDS should be already canceled at that time.
+### Cancel Flow
+
+As mentioned earlier, if `ActiveSegmentInConcurPNR` is set to true, booking is treated as a GDS booking and we will manage cancel flow directly with GDS. Though, the CHS supplier will still be notified using the Hotel Service v4 [cancel endpoint](./v4.endpoints.html#cancel-). Note that invocation of `cancel endpoint` is only for notification to allow CHS supplier to perform any cancel related processing in their system and hotel booking with GDS should be already canceled at that time.
 
 ![](images/diagrams/singlepnr/hotel_cancel.png)
 
 #### GDS Booking
-- User initiates cancel request and Concur cancels the active segment/trip in GDS and updates storage with `Canceled` status with cancellation no.
-- Concur sends `cancel` request to CHS supplier with cancel number. Note here that this request is just acting as a notification to CHS supplier as booking is already canceled in GDS.
-- Above `cancel` request can trigger any post-booking processing in CHS supplier system.
+
+- User initiates a cancel request and we cancel the active segment/trip in GDS and update storage with `Canceled` status with cancellation number.
+- We send the `cancel` request to CHS supplier with cancel number. Note that this request is just acting as a notification to the CHS supplier as booking is already canceled in GDS.
+- The `cancel` request can trigger any post-booking processing in CHS supplier system.
 
 
 #### Direct Connect Booking
-- User initiates cancel request and Concur forwards this cancel request to CHS supplier.
-- Supplier sends cancel request to their direct connect source and also deletes any related passive segment if they created one for the booking. 
-- Cancel response with cancellation no. is returned to Concur which is then stored and displayed to user.
+
+- User initiates a cancel request and we forward this cancel request to the CHS supplier.
+- Supplier sends the cancel request to their direct connect source and also deletes any related passive segment if they created one for the booking. 
+- Cancel response with cancellation number is returned to us which is then stored and displayed to user.
 

feed.xml

@@ -5,8 +5,8 @@
     <description>Concur docs provides comprehensive information on working with the Concur platform</description>
     <link>https://preview.developer.concur.com/</link>
     <atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
-    <pubDate>Mon, 16 Sep 2024 17:54:36 +0000</pubDate>
-    <lastBuildDate>Mon, 16 Sep 2024 17:54:36 +0000</lastBuildDate>
+    <pubDate>Mon, 16 Sep 2024 20:33:47 +0000</pubDate>
+    <lastBuildDate>Mon, 16 Sep 2024 20:33:47 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>