SAP ABAP IMG Activity PAY_DE_B2A_FIN_130 (Set Up RFC Connection)
Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
   PY-DE (Application Component) Germany
     PC01 (Package) HR Payroll: Germany
IMG Activity
ID PAY_DE_B2A_FIN_130 Set Up RFC Connection  
Transaction Code S_PL0_86000094   (empty) 
Created on 20040301    
Customizing Attributes PAY_DE_B2A_FIN_000   Data Exchange with Financial Administration 
Customizing Activity PAY_DE_B2A_FIN_130   Set Up RFC Connection 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PAY_DE_B2A_FIN_130    

Use

This activity provides information about setting up the RFC connection between an SAP system and the XI platform or Business Connector (BC).

Using XI Platform

Data is exchanged between the SAP system and the XI by means of an RFC connection. You can create RFC connections in transaction SM59 (RFC Destinations (Display/Maintain)):

Enter the RFC destination HR_DE_ELSTER. The RFC destination is used to call the function modules. (You can use constant RFCDE in table T50BK, view V_T50BK to choose a name other than HR_DE_ELSTER for the RFC destination).

Choose the connection type T (start external program via TCP/IP).

Choose the activation type Registration. Enter the program ID <Object>ELSTER_XML_<system name>. The program ID must match the program ID used on the XI when creating the RFC adapter.

Example of a program ID: ELSTER_XML_H01

You can only test the connection once the RFC adapter is configured in XI.

Unicode note:

For a Unicode system, set the Unicode flag under "Special Options". The Unicode flag must also be set for the RFC adapter in XI.

You only need to create the following RFC connections if you want to use the HTTP connections from the SAP system. If the http connection is established via the XI system, the necessary settings (communication channels) are made there. You use constant USEXI in table T50BK, view V_T50BK to select one of the two variants.

For the HTTP communication with the clearing house, you need to create a corresponding RFC connection for each of the four IP addresses of the clearing house.

Enter the RFC destination HR_DE_ELSTER_C1. The RFC destination is used to call the HTTP and is fixed.

Choose the connection type G (HTTP connection to ext. server).

Enter the following values under Technical Settings:

Destination machine 193.109.238.58 service no. 0080

Path prefix /Elster2/EMS

HTTP proxy options:

Enter the appropriate values for your network environment.

Repeat this step for the remaining three RFC destinations with the following values:

HR_DE_ELSTER_C2 destination machine 80.146.179.2

HR_DE_ELSTER_C3 destination machine 193.109.238.59

HR_DE_ELSTER_C4 destination machine 80.146.179.3

Using the Business Connector

Data is exchanged between the SAP system and the Business Connector by means of an RFC connection. You can create the connection in the SM59 transaction (RFC Destinations (Display/Maintain)).

Enter the RFC destination HR_DE_ELSTER. The RFC destination is used to call the function modules and is fixed.

Choose the connection type T (start external program via TCP/IP).

Choose the activation type Registration. Enter the program ID ELSTER_XML_<system name>. The program ID is used again later to define the listener (program ID) on the Business Connector.

Example of a program ID: ELSTER_XML_H01

The connection cannot be tested until the listener has been set up and activated on the Business Connector.
Unicode note:
For a Unicode system, set the Unicode flag under "Special Options". The listener must also be selected as a Unicode listener on the BC.

If you use more than one server for your system, you can define one of them as a gateway, meaning that you only have to maintain this one connection in the BC. (To do so in releases before 4.6C, choose Destination -> Gateway Options.)
Enter the server as the gateway host and, under Gateway Service, enter the system number in the form "sapgw<system number>".

Example:

Gateway host: LS0096

Gateway service: sapgw05

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object SM59  
History
Last changed by/on SAP  20040906 
SAP Release Created in 500