Ansicht
Dokumentation

OFTP_RFC000 - Set Up RFC Destinations for Interfaces to External Systems

OFTP_RFC000 - Set Up RFC Destinations for Interfaces to External Systems

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

The definition of an RFC destination is the technical prerequisite for a connection to the central system of the external reservation system. The RFC call (Remote Function Call) is thus the basis for using the functions in Travel Planning that access the external reservation system (primarily availability queries for travel services and booking of selected services).

The server landscape is as follows:

SAP System
<->
SAP Gateway
(in-house or centrally
as application hosting)
  <->
  Gateway of reservation system
  <->
  API Server / application server
    <->
    Central system of
    reservation system

The RFC destination represents the logical connection between the SAP system and the SAP Gateway. The SAP Gateway provides the necessary bridge between the SAP system and the external application, the global reservation system. With the SAP Gateway, communication takes place through the Gateway of the reservation system, which identifies the API Server or the application server. The API servers/ application servers control access to the respective central system of the global reservation system.

 
  • You have set up an SAP Gateway and a reservation system gateway. It is best for both gateways to be installed in the same computer.

The requirements in the documentation Technical and Organizational Prerequisites in the IMG for Travel Planning have been fulfilled.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
For general information on setting up an SAP Gateway, see Help ->
SAP Library -> Basis Components-> Basis Services/Communication Interfaces ->
SAP Communication: Configuration -> SAP Gateway.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Current information on installation of the Gateways of the global reservation systems can be found in SAPNet for Customers and Partners:
http://sapnet.sap.com/TM -> Downloads
or under the following path:
Solutions: mySAP.com Business Applications → Financials: Travel Management → Downloads
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 

The RFC destinations for Travel Planning are notpreset in the standard system.

 

To set up the RFC destination for Travel Planning, proceed as follows:

  1. Call the IMG activity Set up RFC destination for Travel Planning.
  2. Place your cursor on the connection type TCP/IP connection.
  3. Choose Edit -> Create.
  4. In the RFC Destination screen enter the following:
  • RFC Destination:The (user-definable) name of the RFC destination should correspond with the name of the respective logical system.

  • Connection type: T (= Start of an external program via TCP/IP)

  • Description: Short documentation on the RFC connection

  1. Confirm your entries with Enter.
  2. Choose the activation type Registration.
  3. Enter the Program ID. Caution: Be sure to use upper and lower case appropriately.

    The program ID is the identification under which an RFC Server program (in this case the gateway of the reservation system) can register with an SAP Gateway and then await RFC calls from different SAP Systems.
    The program ID must correspond with the parameters for registration (via RfcAccept). For the RFC destination of Travel Planning this means (during installation) that: The program ID of the RFC destination must correspond with the PROGID in the configuration file SAPRFC.INI (during installation of the Amadeus Gateway).
    For more information, read the installation instructions for the Amadeus Gateway in SAPNet (see above).
  4. Choose Destination -> Gateway Options and enter the following:
  • Gateway Host:IP Address of SAP Gateway PC where the gateway of the registration system is registered

  • Gateway Service: Port number of the SAP Gateway, where the Amadeus Gateway is registered

    The values used here (without the router string) for Gateway host and Gateway service also must correspond with the values of the parameters GWHOST and GWSERV in the configuration file SAPRFC.INI mentioned above (during installation of the Amadeus Gateway).

Gateway Parameters

  • In more complex system landscapes the SAProuter string from the SAP system to the SAP Gateway must be specified. In cooperation with the responsible network administrator, determine the IP addresses and port numbers of the communication elements involved.

RFC Destinations

  • RFC destinations are client independent.
  • Maintenance of the RFC destination is not connected with automatic transport and correction systems. Therefore you have to carry out the setting on all systems manually.

More information on creation and maintenance of RFC destinations in the SAP System can be found in the implementation guide (IMG) under Define RFC Destinations or under Help → SAP Library → Basis Components → Basis Services / Communication Interface → RFC Programming in ABAP → Maintain Removed Destinations.






BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 7866 Date: 20240523 Time: 204150     sap01-206 ( 97 ms )