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_000 | Data Exchange with the ZfA (Pension Receipt Notifications) - Overview |
| Transaction Code | S_L7D_24001843 | (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_000 |
Use
IBM's WebSphere MQ software (MQ Series) is used for communication with the ZfA (German Central Pension Administration Office). XML data with the notifications are exchanged with the ZfA using queues. For the data to be exchanged, there must be a network connection to the ZfA.
For the customer to be able to exchange data with the ZfA, the customer must register with the ZfA. When the customer registers, inbound and outbound queues are created for the customer. In these queues, customer notifications are set up for the ZfA, or the ZfA provides notifications for the customer in the queues.
The ZfA has two variants for communication via WebSphere MQ:
Server-Server Communication
For server-server communication, the customer requires a server version of the WebSphere MQ software (subject to charge). For this variant, both the customer and the ZfA initiate the connection setup and exchange of messages.
- Client-Server Communication
For client-server communication, the customer requires only part of the WebSphere MQ software (libraries free of charge). These are integrated by the application software (SAP XI or SAP BC) and are used for the exchange of messages with the ZfA. For this variant, only the customer initiates the connection setup and exchange of messages.
For detailed information about data exchange with the ZfA, see the Communication Handbook # General Basics on the ZfA#s website at https://www.zfa.deutsche-rentenversicherung-bund.de.
Overview Process:
For the notifications to the ZfA, two types of notification must be differentiated from the point of view of communication. Outbound notifications (notifications from the customer to the ZfA) and inbound notifications (notifications from the ZfA to the customer).
Outbound notifications are created by an application report in the SAP system and placed in the B2A Manager for transfer (area CPS, document category ORBM). From there, the notifications can be sent to the ZfA by starting the transfer.
Inbound notifications that the ZfA provides for the customer are automatically taken from the customer#s inbound queue for the ZfA (periodic process) and placed in the B2A Manager (area CPS, document category IRBM). From there, they are further processed in the SAP system using an application report.
Requirements
Standard settings
Activities
Example
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 |
