Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS (Application Component) Public Sector⤷
P01O (Package) HR Germany: Public Sector
IMG Activity
| ID | PAY_DE_B2A_ZFA_110 | Set Up Connections |
| Transaction Code | S_L7D_24001296 | (empty) |
| Created on | 20070926 | |
| Customizing Attributes | PAY_DE_B2A_ZFA_000 | Data exchange with ZfA |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PAY_DE_B2A_ZFA_110 |
Use
Setting up the Business Connector
Prerequisite: To enable data exchange with the German central pension administration office (ZfA), you must be able to establish a VPN connection simultaneously to the ZfA and the R/3 system from the server on which the BC is installed. This is only possible using the network-network link provided by the ZfA. The system currently does not support the use of the VPN client, since the VPN client does not permit a network connection between the SAP R/3 system and the BC once it has been started.
The Business Connector (BC) is freely available server for SAP customers for the realization of various data exchange scenarios between SAP systems and/or external systems belonging to service providers and authorities.
Install the BC (Version 4.7 or above) in your system landscape to enable the exchange of data between the SAP system, the BC, and the ZfA using Websphere MQ.
More information on the installation and administration of the BC is provided in the documentation, which is available on the SAP Service Marketplace under the Quick Link "Connectors".
ZfA-specific steps for setting up data transfer:
Import the ZFA package on the Business Connector
- The package for the BC is available on the SAP Service Marketplace under the Quick Link HRDE. (www.service.sap.com/HRDE)
Click on the Media Center menu option on the right-hand side. The list contains the most recent package under the entry Package ZFA Version X.Y (BusinessConnector 4.7/Websphere MQ) - Copy the file to the following Business Connector directory: .../replicate/inbound .
- Log on to the BC. In the menu, choose Packages -> Management -> Install Inbound Releases and select the file. Install the package (install release).
- In the overview of packages under the menu option Packages -> Management, check that the ZFA package is enabled and loaded.
Setting up the SAP system
- To enable communication between the SAP system and the BC, the SAP system must be created on the BC.
To make this definition, choose SAP -> SAP Servers -> Add SAP Server in the menu.
Maintain the blocks System, Login Defaults and Server Logon. An RFC user (type C) is sufficient as a user for defining the server. - Choose Test Connection to check the connection. You must be able to log on to the defined SAP system.
Setting up the listener for the created SAP system
To establish the connection between the RFC connection created in the SAP system (HR_DE_ZFA_BC) and the previously defined SAP system on the BC, you need to create a "listener".
- The overview in the BC menu under SAP -> SAP Servers contains a list of the defined systems. In the row for the relevant system, click on the number in the "Listeners" column to display the defined listeners. To create a new listener, choose "Add Listeners".
- For the program ID, enter the name ZFA_BC_<System name>_<Client> as used in the RFC definition.
Example: ZFA_BC_PRO_010
Select Autostart Yes. This ensures that the listener is reactivated automatically when the BC is started.
Note for Unicode: If you create the listener for a Unicode SAP system, you have to set the Unicode option for the listener and the RFC connection. (After creation, click "Started" to start the listener manually) - In the listener overview, check that the listener has started. If it has started, the menu option Started? is displayed in green.
- The check the connection between the SAP system and the BC. To do this, test the previously created RFC connection in the SAP system. You may have to re-register the connection in the SAP system. (To do this, call transaction SM59 in the SAP system and select "Registered Server Program" again).
Setting up maps for the listener you have created
Before you perform this step, the RFC connection in the SAP system must be created and tested. The SAP system must be defined on the BC and a listener must be set up for the RFC connection.
In addition to the listener, you have to create maps as a connection between the function modules in the SAP system and the executed services on the BC.
- In the menu, choose SAP -> Lookup and enter the server name of the SAP system under RFC Lookup. Under the function "Search", enter HR_DE_B2A_OED* in the Function Name field, and choose Search.
The system then displays all function modules in the SAP system with the name HR_DE_B2A_OED*.
Create a map for each of the following function modules:
HR_DE_B2A_OED_ZFAO_BC
To do this, click on the name of the function module. The direction of the connection is SAP -> SAP BC. Choose Define New Map.
On the next screen, assign the R/3 function module to the service in the ZFA package.
Enter the following data for each of the function modules listed:
Field Contents
Generate for Listener ZFA_BC_<System name>_<Client>
Package Default
ACL <None>
Remote Server Alias (local)
Folder MQ
Service MQPUT
Scope Session
HR_DE_B2A_OED_ZFAI_BC
To do this, click on the name of the function module. The direction of the connection is SAP BC -> SAP. Choose Define New Map.
Enter the following data for each of the function modules listed:
Field Contents
Folder MQ
Service ZFAI
Package Default
ACL <None>
HR_DE_B2A_OED_ZFAI_GETCUST_BC
To do this, click on the name of the function module. The direction of the connection is SAP BC -> SAP. Choose Define New Map.
Enter the following data for each of the function modules listed:
Field Contents
Folder MQ
Service ZFAI_GETCUST
Package ZFA
ACL <None>
HR_DE_B2A_OED_ZFAI_REP_BC
To do this, click on the name of the function module. The direction of the connection is SAP -> SAP BC. Choose Define New Map.
On the next screen, assign the R/3 function module to the service in the ZFA package.
Enter the following data for each of the function modules listed:
Field Contents
Generate for Listener ZFA_BC_<System name>_<Client>
Package Default
ACL <None>
Remote Server Alias (local)
Folder MQ
Service MQGET
Scope Session
- Check the maps.
To do this, choose SAP -> SAP Servers -> RFC Function Maps for <Name of SAP system>.
To reach this point, choose the blue M in the overview of SAP servers.
The Function Map List should now contain the following maps:
Function Module Type Folder Service
HR_DE_B2A_OED_ZFAO_BC SAP->SAP BC MQ MQPUT
HR_DE_B2A_OED_ZFAI_BC SAP BC->SAP MQ ZFAI
HR_DE_B2A_OED_ZFAI_GETCUST_BC SAP BC->SAP MQ ZFAI_GETCUST
HR_DE_B2A_OED_ZFAI_REP_BC SAP->SAP BC MQ MQGET
Scheduling the service for periodically querying the inbound queue
Because you not only send data to the ZfA, but the ZfA also prepares notifications for customers, the customer must periodically check their inbound queue at the ZFA for notifications relevant for them.
There are two options for checking the queue:
(1) Query using periodic scheduling of report RPUZFAD0_MQIN
(2) Query using a periodic service on the BC
Option 2, using the service on the BC, has the disadvantage that only a single inbound queue can be queried. If you have to connect multiple SAP systems or clients with different customer numbers (and hence different inbound queues), option 2 is not possible.
Set-up:
Option 1 - Query using periodic scheduling of report RPUZFAD0_MQIN
For test purposes, you can start report RPUZFAD0_MQIN online. If the inbound connection is working, schedule the report
periodically, for example once a day.
For more information, refer to the report documentation.
Option 2 - Query using a periodic service on the BC
To do this, you schedule a service on the BC. You periodically start this service and check whether the ZFA has provided any data. If the service finds messages in the inbound queue, it transfers these to the R/3 system, where they are available for further processing.
In the menu, choose Server -> Scheduler and choose Create a scheduled task.
Make the following entries:
Service Information
folder.subfolder:service MQ:MQGETMAIN
Schedule Type and Details
Here you determine the patt
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 |
History
| Last changed by/on | SAP | 20070926 |
| SAP Release Created in | 600 |
