Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PA-PF-DE (Application Component) Company Pension Scheme Germany⤷
P01A (Package) HR Germany: Retirement Pension Plan
IMG Activity
| ID | PAY_DE_B2A_RBM_110 | Set Up Connections |
| Transaction Code | S_L7D_24001844 | (empty) |
| Created on | 20081103 | |
| 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_RBM_110 |
Use
Setting Up the Business Connector
Prerequisite:
For the exchange with the ZfA, a VPN connection from the server on which the Business Connector (BC) is installed to the ZfA as well as to the SAP system must be possible. This is only possible with the network-network coupling provided by the ZfA. The use of the VPN client is not currently supported since, once it is started, the VPN client does not permit network connections between the SAP system and BC.
The Business Connector (BC) is a server that is freely available to SAP customers to realize various data exchange scenarios between SAP systems and/or external systems of service providers and authorities.
Install the BC (version 4.7 or higher) in your system landscape so that data can be exchanged via WebSphere MQ between the SAP system, the BC, and the ZfA.
For information about installation and administration, see the documentation available on SAP Service Marketplace, under the quick link Connectors.
ZfA-Specific Steps for Setting Up the Transfer for the Pension Receipt Notification
Applying the ZFA_RBM Package to the Business Connector
- For the package for the BC, see SAP Service Marketplace and quick link HRDE (www.service.sap.com/HRDE).
Right-click on the menu item Media Center. The list contains the current package under the entry Package ZFA_RBM Version X.Y (BusinessConnector 4.7/Websphere MQ). - Copy the file to the .../replicate/inbound directory of the BC.
- Log on to the Business Connector. Choose Packages -> Management -> Install Inbound Releases and select the file. Install the package by choosing Install Releases.
- Choose Packages -> Management and check in the overview of packages that the ZFA_RBM package is enabled and loaded.
Setting Up the SAP System
- The SAP system has to be created on the Business Connector for communication between the SAP system and the BC.
To define the system, choose SAP -> SAP Servers -> Add SAP Server.
Maintain the System, Login Defaults, and Server Logon blocks. An RFC user (category C) is sufficient as the user for the server definition. - Choose Test Connection. It must be possible 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_RBM_BC) and the SAP system defined previously on the BC, you create a Listener.
- The defined systems are listed in the overview in the BC, under SAP -> SAP Server. In the row of the relevant system, click the number in the Listeners column to display the defined listeners. To create a new listener, choose Add Listeners.
- As the Program ID, enter the label used in the RFC definition, RBM_BC_<system name>_<client>.
Example: RBM_BC_PRO_010
Under Autostart, select the Yes radio button. You thus ensure that the Listener is automatically reactivated after the BC is restarted.
Unicode Note:
If you create the listener for a Unicode SAP system, set the Unicode option for the listener and the RFC connection (manually start the listener after the creation by clicking Started). - Check in the overview that the listener is started. If so, the Started? field is displayed in green.
- Check the connection between the SAP system and the BC by testing the RFC connection created previously in the SAP system. You may have to reregister the connection in the SAP system. (In the system, in transaction SM59, select Registered Server Program again).
Setting the Maps to the Created Listener
Before you can set maps, the RFC connection must be created and tested in the SAP system. 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 services executed on the BC.
- From the menu, choose SAP -> Lookup and under RFC Lookup enter the server name of the SAP system. Under Function Search, enter HR_DE_B2A_BAV* in the Function Name field, and choose Search.
All function modules with names HR_DE_B2A_BAV* in the SAP system are then displayed. - Create a map for each of the following function modules:
HR_DE_B2A_BAV_ORBM_BC
To do so, click the name of the function module. The direction of the connection is SAP -> SAP BC. Choose Define New Map.
On the subsequent screen, assign the R/3 function module to the service in the ZFA_RBM package.Enter the following data for each of the above-mentioned function modules:
Field Content
Generate for Listener RBM_BC_<system name>_<client>
Package Default
ACL <None>
Remote Server Alias (local)
Folder MQ_RBM
Service MQPUT
Scope Session
HR_DE_B2A_BAV_IRBM_BC
To do so, click 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 above-mentioned function modules:
Field Content
Folder MQ_RBM
Service ZFAI
Package Default
ACL <None>
HR_DE_B2A_BAV_IRBM_GETCUST_BC
To do so, click 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 above-mentioned function modules:
Field Content
Folder MQ_RBM
Service ZFAI_GETCUST
Package Default
ACL <None>
HR_DE_B2A_BAV_IRBM_REP_BC
To do so, click the name of the function module. The direction of the connection is SAP -> SAP BC. Choose Define New Map.
On the subsequent screen, assign the R/3 function module to the service in the ZFA_RBM package.
Enter the following data for each of the above-mentioned function modules:
Field Content
Generate for Listener RBM_BC_<system name>_<client>
Package Default
ACL <None>
Remote Server Alias (local)
Folder MQ_RBM
Service MQGET
Scope Session
- Check the maps.
To do so, choose SAP -> SAP Servers -> RFC Function Maps for <name of SAP system>.
You access the function by choosing the blue M in the overview of SAP servers.
The function map list now contains the following maps:
Function Module Type Folder Service
HR_DE_B2A_BAV_ORBM_BC SAP->SAP BC MQ_RBM MQPUT
HR_DE_B2A_BAV_IRBM_BC SAP BC->SAP MQ_RBM ZFAI
HR_DE_B2A_BAV_IRBM_GETCUST_BC SAP BC->SAP MQ_RBM ZFAI_GETCUST
HR_DE_B2A_BAV_IRBM_REP_BC SAP->SAP BC MQ_RBM MQGET
Scheduling of the Service for the Periodic Query of the Inbound Queue
Since RBM data is not only sent to the ZfA, but rather the ZfA also provides notifications for the customer, the customer must periodically query his or her inbound queue at the ZfA for notifications for him or her.
Two alternatives exist for querying the queue.
(1) Query via the periodic scheduling of report RPURBMD0_MQIN
(2) Query via a periodic service on the BC
Alternative 2 (with the service on the BC) has the disadvantage that only a single inbound queue can be queried. If multiple SAP systems or clients with different customer numbers (meaning different inbound queues) need to be connected, alternative 2 must be excluded.
Setup:
Alternative 1 # query via the periodic scheduling of report RPURBMD0_MQIN
For test purposes, you can start report RPURBMD0_MQIN online. If the entry works, schedule the report
periodically, for example, once a day.
For more information, see the report documentation.
Alternative 2 # query via a periodic service on the BC
A service is scheduled on the BC. This service is launched periodically. It checks to see whether the ZfA has provided data. If the service finds notifications in the inbox, it transfers them to R/3 where they are available for further processing.
Choose Server -> Scheduler and then choose Create a scheduled task.
Enter the following:
Service information
folder.subfolder:service &#
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 | 20081103 |
| SAP Release Created in |
