Skip to content

Commit 3fa8f3f

Browse files
[skip ci] Updates
1 parent 2ea043c commit 3fa8f3f

3 files changed

Lines changed: 28 additions & 9 deletions

File tree

feed.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
<description>Concur docs provides comprehensive information on working with the Concur platform</description>
66
<link>https://preview.developer.concur.com/</link>
77
<atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
8-
<pubDate>Thu, 10 Apr 2025 12:00:15 +0000</pubDate>
9-
<lastBuildDate>Thu, 10 Apr 2025 12:00:15 +0000</lastBuildDate>
8+
<pubDate>Thu, 10 Apr 2025 20:00:14 +0000</pubDate>
9+
<lastBuildDate>Thu, 10 Apr 2025 20:00:14 +0000</lastBuildDate>
1010
<generator>Jekyll v4.1.1</generator>
1111

1212
</channel>

tools-support/release-notes/api/2025-03-06.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -494,13 +494,13 @@ <h3 id="preview-single-pnr-solution-for-the-hotel-connector-booking">Preview: Si
494494

495495
<p><strong>Overview</strong></p>
496496

497-
<p>For bookings made through hotel connectors today, we create a new PNR in the appropriate GDS and adds a passive segment to that PNR with details of the hotel booking made by the Hotel Connector. The Hotel Connector also creates a PNR in the GDS with the active segment. This causes issues for the TMC and the Hotel Connector as SAP Concur platform PNR is in the SAP Concur standard format and any changes have to be made manually as no PNR synch is available.</p>
497+
<p>For bookings made through hotel connectors today, the SAP Concur platform creates a new PNR in the appropriate GDS and adds a passive segment to that PNR with details of the hotel booking made by the Hotel Connector. The Hotel Connector also creates a PNR in the GDS with the active segment. This causes issues for the TMC and the Hotel Connector as SAP Concur platform PNR is in the SAP Concur standard format and any changes have to be made manually as no PNR synch is available.</p>
498498

499499
<p>This Single PNR solution will result in only one PNR created for the Hotel Connector booking. The solution will allow us and the Hotel Connector to work in the PNR at the same time using lock/release. For GDS content, the Hotel Connector will add an active segment. For non-GDS content, the Hotel Connector will add a passive segment.</p>
500500

501501
<p><strong>API Details</strong></p>
502502

503-
<p>The reservation/modify request will be sent with the SAP Concur platform PNR locator (<code class="language-plaintext highlighter-rouge">ConfirmationCodeType: CONCUR_GDS_REFERENCE</code>) to the Hotel Connector supplier. If the connector supports the single PNR solution the <code class="language-plaintext highlighter-rouge">ActiveSegmentInConcurPNR</code> flag will be added to the <code class="language-plaintext highlighter-rouge">HSV4 ReservationDetails</code> and will be handled in the reservation/modify response. If the booking is cancelled, we will forward the cancellation number in the cancel request to the Hotel Connector.</p>
503+
<p>The <code class="language-plaintext highlighter-rouge">reservation/modify</code> request will be sent with the SAP Concur platform PNR locator (<code class="language-plaintext highlighter-rouge">ConfirmationCodeType: CONCUR_GDS_REFERENCE</code>) to the Hotel Connector supplier. If the connector supports the single PNR solution the <code class="language-plaintext highlighter-rouge">ActiveSegmentInConcurPNR</code> flag will be added to the <code class="language-plaintext highlighter-rouge">HSV4 ReservationDetails</code> and will be handled in the <code class="language-plaintext highlighter-rouge">reservation/modify</code> response. If the booking is cancelled, we will forward the cancellation number in the <code class="language-plaintext highlighter-rouge">cancel</code> request to the Hotel Connector.</p>
504504

505505
<h2 id="ongoing">Ongoing</h2>
506506

tools-support/release-notes/api/2025-04-03.html

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -426,6 +426,30 @@ <h1 id="api-release-notes-april-2025">API Release Notes, April 2025</h1>
426426

427427
<h2 id="new-this-month">New This Month</h2>
428428

429+
<h3 id="now-available-single-pnr-solution-for-the-hotel-connector-booking">Now Available: Single PNR solution for the Hotel Connector Booking</h3>
430+
431+
<p><strong>Overview</strong></p>
432+
433+
<p>For bookings made through hotel connectors today, the SAP Concur platform creates a new PNR in the appropriate GDS and adds a passive segment to that PNR with details of the hotel booking made by the Hotel Connector. The Hotel Connector also creates a PNR in the GDS with the active segment. This causes issues for the TMC and the Hotel Connector as SAP Concur platform PNR is in the SAP Concur standard format and any changes have to be made manually as no PNR synch is available.</p>
434+
435+
<p>This Single PNR solution results in only one PNR created for the Hotel Connector booking. The solution allows us and the Hotel Connector to work in the PNR at the same time using <code class="language-plaintext highlighter-rouge">lock/release</code>. For GDS content, the Hotel Connector adds an active segment. For non-GDS content, the Hotel Connector adds a passive segment.</p>
436+
437+
<p><strong>API Details</strong></p>
438+
439+
<p>The <code class="language-plaintext highlighter-rouge">reservation/modify</code> request is sent with the SAP Concur platform PNR locator (<code class="language-plaintext highlighter-rouge">ConfirmationCodeType: CONCUR_GDS_REFERENCE</code>) to the Hotel Connector supplier. If the connector supports the single PNR solution the <code class="language-plaintext highlighter-rouge">ActiveSegmentInConcurPNR</code> flag is added to the <code class="language-plaintext highlighter-rouge">HSV4 ReservationDetails</code> and is handled in the <code class="language-plaintext highlighter-rouge">reservation/modify</code> response. If the booking is cancelled, we will forward the cancellation number in the <code class="language-plaintext highlighter-rouge">cancel</code> request to the Hotel Connector.</p>
440+
441+
<h3 id="preview--travel-allowance-service-from-third-party-solutions">Preview: Travel Allowance Service from Third-Party Solutions</h3>
442+
443+
<p>The Travel Allowance v4 APIs will also support writing travel allowance itinerary data into SAP Concur platform from a third-party solution. Customers and Partners will be able to use the APIs to build custom solutions to enhance their business processes wherever travel allowance itineraries need to be created and updated from a third-party solution. This could be solutions for time recording, service management, staffing solutions in CRM systems, booking tools, and many more. The new feature will be automatically available, so no additional configuration or activation steps will be required.</p>
444+
445+
<h3 id="preview-new-report-events-for-concur-expense">Preview: New Report Events for Concur Expense</h3>
446+
447+
<p>Concur Expense Events will be amended to include two new events: <code class="language-plaintext highlighter-rouge">reportUpdated</code> and <code class="language-plaintext highlighter-rouge">reportDeleted</code>. They will be on the same <code class="language-plaintext highlighter-rouge">public.concur.expense.report</code> topic associated with this event group. These events will be published upon any report <code class="language-plaintext highlighter-rouge">update</code> or <code class="language-plaintext highlighter-rouge">delete</code> action whether through the product UI, an API such as the Update Unsubmitted Report, or other automated sources such as the Expense Assistant.</p>
448+
449+
<h3 id="preview-new-languages-supported">Preview: New Languages Supported</h3>
450+
451+
<p>The Malay and Slovenian languages will be added to the supported locales.</p>
452+
429453
<h3 id="preview-new-fields-added-to-financial-integration-services-fis-v4-api">Preview: New Fields Added to Financial Integration Services (FIS) v4 API</h3>
430454

431455
<p>For customers using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. This change will provide enhanced features to customers using Concur Expense Professional Edition.</p>
@@ -517,11 +541,6 @@ <h2 id="previews">Previews</h2>
517541
<td>Support of Hotel Date Modification for Hotel Connectors</td>
518542
<td>Hotel connectors will support the modification of check-in and check-out dates using the Hotel Service v4 Modify endpoint. This will allow users to change their dates of stay without having to cancel and rebook.</td>
519543
</tr>
520-
<tr>
521-
<td><a href="/tools-support/release-notes/api/2025-03-06.html">03/2025</a></td>
522-
<td>Single PNR solution for the Hotel Connector Booking</td>
523-
<td>This Single PNR solution will result in only one PNR created for the Hotel Connector booking. The solution will allow us and the Hotel Connector to work in the PNR at the same time using lock/release.</td>
524-
</tr>
525544
<tr>
526545
<td><a href="/tools-support/release-notes/api/2024-05-09.html">05/2024</a></td>
527546
<td>Retention Period for Credit Card Data Files</td>

0 commit comments

Comments
 (0)