Sabre
You can use IDoc Technology to synchronize SAP Travel Planning with changes and new data in the Sabre databank. IDocs are containers for data exchanges between R/3 and third party systems. This new data is then used to update existing travel plans or when creating new ones.
Prerequisites
In addition to an active connection to Sabre, the sales office of the company and the corresponding queue number must be created with Sabre. Sabre uses this information to send the correct PNRs for the company back to SAP Travel Planning.
Importing PNR Changes and Creating IDocs
To import PNR Data from the connected reservation system (Sabre) you use the program GET_SABRE_PNR. This saves the data as a IDoc in a temporary buffer. The program GET_SABRE_PNR sends the virtual sales office and the queue number to Sabre for identification purposes. If changed PNRs exist in the Sabre System, they are imported into the SAP system and a IDoc is created for each PNR. The data is then deleted from the synchronization queue in the Sabre databank.
Procedure for Setting up the IDoc Control Parameters
To set up the control parameters for IDocs, you need to make the following settings:
Process step |
Transaction code |
Activities: |
Define IDoc type and Segment Types |
WE30 |
Check that the entry TRPL_PNR_IDOC exists and that it contains all segment types where the technical names begins with E1FTPS_PNR_*. |
Define inbound process codes |
WE42 |
Create process code TRPL_PNR_IN using the button New entries |
Define characteristics of inbound function modules for processing the IDocs. |
BD51 |
Use the button New entries to create inbound function module IDOC_INPUT_FITP_PNR, with input type 1. Activate the field Dialog allowed |
Define EDI Logical Message types |
WE81 |
Create message type TRPL_PNR_MSG using New entries, enter a short text, for example "Inbound PNR". |
Assign message types to IDoc types |
WE82 |
Click New entries and make the following entries: Message type: TRPL_PNR_MSG Basic type: TRPL_PNR_IDOC Release: 46C |
Assign Inbound function modules, to message types and IDoc types |
WE57 |
Click New entries and make the following entries: Function module: IDOC_INPUT_FITP_PNR Type: F Basic type: TRPL_PNR_IDOC Message type: TRPL_PNR_MSG Direction: '2' (inbound) |
Define function modules for inbound ALE-EDI |
BD67 |
Click New entries and make the following entries: Process Code: TRPL_PNR_IN Function module: IDOC_INPUT_FITP_PNR |
Define port for IDoc processing |
WE21 |
Define a port for the type Transactional RFC |
Define partner profiles |
WE20 |
As the IDocs are created and processed by the R/3 System, you must define inbound and outbound parameters. Create a logical system (Partner type LS) with the following parameters: Outbound Parameters: Message type: TRPL_PNR_MSG Receiver port: As defined in WE21 Inbound Parameters: Message type: TRPL_PNR_MSG Process Code: TRPL_PNR_IN |
Processing the IDocs
When processing the generated IDocs, the SAP system either updates existing or creates new travel plans. The IDocs can be processed manually or automatically.
Automatic Processing
This type of processing is recommended for productive (live) operation. You can create a batch job for the processing which then runs on a regular basis. To do this you must activate the option Transfer IDoc Immediately for both the inbound and outbound parameters when setting up the control parameters using transaction Partner Profiles (WE20).
Manual Processing
Manual processing allows you to complete specific tests.
If the parameter Collect IDocs is set for the outbound parameters, you must start IDoc processing manually. Manual Processing uses program RBDAPP1 to send the IDocs to SAP Travel Planning, and therefore to update the PNR data in the R/3 databank.
Error Control
You can display the status of the IDocs. To do this choose Tools à Business Communication à IDoc Basis à IDoc à IDoc Lists (WE05). You can select any IDoc segments with errors and process them here.
If you change any IDocs, save your changes and send them to SAP Travel Planning using program RBDAGAIE.
See also:
Further information on IDoc Technology can be found under
IDoc Interface/Electronic Data Interchange (BC-SRV-EDI)