Kontakt

Ansicht
Dokumentation

PAY_DE_B2A_RBM_110 - Set Up Connections

PAY_DE_B2A_RBM_110 - Set Up Connections

General Data in Customer Master   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

The SAP Business Connector (BC) or SAP Process Integration (PI) can be used for transferring notifications.

Setting Up the Business Connector (BC):

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

In ZfA package ZFA_Version_2_3.zip, there are no longer two separate packages for the ZfA public sector (ZFA) and ZfA pension receipt notification (ZFA_RBM). In both cases, the communication is done using the new ZFA package.

Importing package ZFA to the Business Connector

  • You can find the package for the BC in SAP Note 3149765 - B2A-ZfA: Download area with current package for transferring data using the Business Connector.
  • Copy the file to the .../replicate/inbound directory to 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 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
Service MQPUT
Scope Session



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
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 MQPUT
HR_DE_B2A_BAV_IRBM_REP_BC SAP->SAP BC MQ 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. You can achieve this using the periodic scheduling of report RPURBMD0_MQIN. The scheduler on the BC is no longer supported with new ZfA package ZFA_Version_2_3.zip.

Setting Up SAP Process Integration (PI)

Prerequisite:

  • In your system landscape, there is a PI for connecting to the SAP Hr system.
  • VPN: From the server on which the PI is installed for the exchange with the ZfA, it must be possible to connect to the ZfA using a VPN. This is only possible with the network-network coupling provided by the ZfA. The use of the VPN client is not supported as the VPN client does not permit any network connection to other systems including the SAP R3 systems after it has been started. You can find further technical information about the VPN in the communication handbook provided by the ZfA.

Steps to Set Up the PI:

  • Import the latest version of the XI content SAP HR to the PI system.
    Example: Release SAP HR 604: XI CONTENT HR 604 SAPHR6042166063 Patch #1

    You can find the relevant files on the SMP. (Description in English)
    SAP Service Marketplace (SMP)

    The XI content software component versions are part of the product version (Support Package Stack). The software component versions are also linked in a central area under "SAP Content" on the SAP Service Marketplace. Therefore, in addition to the search function, you have two further options for navigating to the XI content package:
  • Using the product version to which the packages belong: http://service.sap.com/swdc -> Support Packages and Patches -> Browse our Download Catalog -> for example, SAP Application Components

  • Using the central "SAP Content" area: http://service.sap.com/swdc -> Support Packages and Patches -> Browse our Download Catalog -> SAP Content -> ESR Content (XI Content)

  • You also have to import the corresponding mappings (PI content) to the PI system and adjust them to match the parameters for the MQ connection defined by the ZfA. For these steps, we recommend that you contact SAP Consulting.

Checking the Settings Carried Out

You can use the reports BAV RBM:Test Report for WebSphere MQ for Communication ZfA (RPURBMD0_MQ) and ZfA: Test Report for WebSphere MQ for Communication ZfA (RPURBMD0_MQCUST) to check the Customizing performed. For more information, see the report documentation.

MQ

MQ

MQ

MQ






General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 14082 Date: 20240523 Time: 191157     sap01-206 ( 171 ms )