Ansicht
Dokumentation
RFTP_SET_ITEM_RES_SYSTEM - Assignment of Reservation Systems to Travel Services (Items)
rdisp/max_wprun_time - Maximum work process run time rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
Purpose
From release ERP2005, the code of the reservation system at which a traveler searches for or reserves travel services is assigned to the travel services (database table FTPT_ITEM) when they are generated. The code is stored in the RES_SYSTEM field.
Without this information, it would not be possible for example to determine the reservation system for a hotel service in cases where access parameters for multiple hotel reservation systems are defined (such as both GDS and HRS plus a system connected with XI) for the sales office determination grouping of the service (USERG field, based on feature TRVOF).
Furthermore, travel plans may contain travel services of the same category and sales office determination grouping but different reservation systems (such as one hotel reserved with GDS and another reserved with HRS).
Since the field FTPT_ITEM-RES_SYSTEM did not exist in releases before ERP2005, the information on the reservation system is missing for travel services transferred during an upgrade from a pre-ERP2005 system to an ERP2005 system. This can cause problems when displaying travel plans if information is specific to a certain reservation system.
To prevent this problem, this report can assign the code of the reservation system to travel services with an empty RES_SYSTEM field. However, this is only necessary if your old system was using both global reservation systems (GDS) and direct reservation systems (HRS or BIBE).
Integration
Prerequisites
The program can only function reliably if your travel planning customizing meets the following requirements:
- All reservation systems on which travel services can be based are correctly defined in the maintenance view V_TA21P_R (Define Reservation Systems). In ERP2005 the standard system supplies entries for Amadeus, Galileo, Sabre, HRS, and BIBE.
- In the new system, you have specified the same groupings for sales office determination as in your old system (maintenance view V_TA20O_FIND, Define Groupings for Access to External Reservation Systems). Otherwise it is not possible to determine the access parameters for reservation systems.
- In the new system, you have defined the access parameters for reservation systems (global reservation systems and others) for each grouping for sales office determination in the same way as in the old system. Otherwise the system cannot associate the access parameters with the reservation systems.
Features
Selection
You can assign the reservation systems for the travel services of all groupings for sales office determination or a single grouping:
- All Groupings TRVOF
All travel services are processed.
- Specific Grouping TRVOF
This option processes only the travel services of grouping TRVOF that you have specified under Parameters - Sales Office Determination.
Parameters:
- Sales Office Determination
Specify the grouping for sales office determination (TRVOF) if you want the assignment to apply only to the travel services of one grouping (option Specific Grouping TRVOF).
- Simulation (No DB Mod)
The program is run as a simulation. No changes are made to the database.
- Process All Items
All travel services are processed (not just those to which no reservation system has been assigned). This may overwrite information.
Standard Variants
Output
A list is output showing the number of travel services that were assigned to a GDS, HRS, or BIBE system. Also shown are the total number of processed items and the number for which no assignment was possible (because the parameter Process All Items was not set or due to incorrect customizing settings).
Activities
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 4174 Date: 20240520 Time: 102105 sap01-206 ( 82 ms )
