Synchronization with Sabre
You can use the IDoc interface to synchronize SAP Travel Planning with new and changed data from the Sabre
database.
IDocs are containers for exchanging data between SAP systems and third-party systems. SAP Travel Planning uses new and changed data from the Sabre
database to create new travel plans or update existing travel plans.
Prerequisites
In addition to an active connection to Sabre
, you need to have created in Sabre
the identity of the sales office of your enterprise and the associated queue number. Sabre
uses this information for sending Passenger Name Records (PNRs) to SAP Travel Planning.
Activities
Importing PNR Changes and Creating IDocs
You use the GET_SABRE_PNR program to import PNR data from the connected reservation system (Sabre
). This program saves the data in a temporary buffer in IDoc format.
To identify itself, this program sends the identity of the sales office and the related queue number to Sabre
. If changed PNR data exists in the Sabre
database, the SAP system imports this data and creates an IDoc for each PNR. The imported data is then removed from the synchronization queue in the Sabre
database.
Configuring IDoc Control Parameters
You make the following settings to configure the control parameters for the IDocs:
|
Process Step |
Transaction Code |
Activities |
|---|---|---|
|
Define IDoc type and segment types |
WE30 |
Make sure that the IDoc type TRPL_PNR_IDOC exists and that it contains all segment types whose technical names begin with E1FTPS_PNR_*. |
|
Define inbound process codes |
WE42 |
Create a new entry for the process code TRPL_PNR_IN. |
|
Define properties of inbound function modules for processing the IDocs |
BD51 |
Create a new entry for the inbound function module IDOC_INPUT_FITP_PNR with input type 1. Activate the |
|
EDI: Define logical message types |
WE81 |
Create a new entry for message type TRPL_PNR_MSG and enter a short description, for example, "Inbound PNR". |
|
Assign message types to the IDoc types |
WE82 |
Create a new entry with the following values:
|
|
Assign the inbound function modules to the message types and IDoc types |
WE57 |
Create a new entry with the following values:
|
|
Define function modules for ALE EDI inbound |
BD67 |
Create a new entry with the following values:
|
|
Define ports in IDoc processing |
WE21 |
Define a port for the type |
|
Define partner profiles |
WE20 |
You have to define the inbound and outbound parameters because the SAP system creates and processes the IDocs. Create a logical system (Partner type Outbound parameters:
Inbound parameters:
|
Processing IDocs
When processing the generated IDocs, the SAP system updates existing travel plans or creates new travel plans. You can process the IDocs manually or automatically.
Automatic processing
In live environments, we recommend that you process the IDocs automatically. To do this, you can create a background job, which the system processes regularly. Then, in the WE20 transaction, you need to choose the option Trigger Immediately
for the inbound parameters and the option Pass IDocs Immediately
for the outbound parameters.
Manual processing
In manual processing you can perform tests.
If you choose the option Collect IDocs
in the WE20 transaction for the outbound parameters, you have to manually trigger the processing of IDocs. To do this, run the program RBDAPP1. The program sends the IDocs to SAP Travel Planning, which updates the PNR data in the SAP database.
Error Control
With the WE05 transaction, you can display the status of the IDocs. Here you can select and edit IDocs that have errors.
If you change an IDoc, save your changes and send them to Travel Planning using the program RBDAGAIE.