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_000 | Data Exchange with ZfA - Overview |
| Transaction Code | S_L7D_24001295 | (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_000 |
Use
Communication with the German central pension administration office (ZfA) is enabled by the Websphere MQ software from IBM (MQ Series). The software enables you to exchange XML data containing the notifications with the ZfA using "queues". As a prerequisite for data exchange, you must have a network connection to the ZfA.
Before the customer can exchange data with the ZfA, the customer must also register with the ZfA. On registration, inbound and outbound queues are created for the customer. Notifications from the customer for the ZfA, or notifications from the ZfA for the customer are placed in these queues.
The ZfA provides two possible variants for communication using Websphere MQ:
- Server-server communication
In server-server communication, the customer requires a server version of the Websphere MQ software (for a charge). In this variant, establishing the connection and the message exchange are initiated by both the customer and the ZfA. - Client-server communication
In client-server communication, the customer only requires a part of the Websphere MQ software (free-of-charge libraries). These are integrated by the application software (SAP XI or SAP BC) and are used for exchanging messages with the ZfA. In this variant, establishing the connection and the message exchange are only initiated by the customer.
For a brief overview of the permitted variants for data exchange, refer to the ZfA document "Rundbrief zur Abfrage über den Einsatz von MQSeries und VPN" from 18.04.2006.
For detailed information on data exchange with the ZfA, refer to the communication manual - General Principles, which is available on the ZfA website at: https://www.zfa.deutsche-rentenversicherung-bund.de
Process overview:
For notifications to the ZfA, from a communication perspective you have to differentiate between two different notification types. These are outgoing notifications (notifications from the customer to the ZfA), and inbound notifications (notifications from the ZfA to the customer).
Outgoing notifications are created by an application report in the SAP R/3 system and are provided for transfer in the B2A Manager (area OED, document type OZFA). From here, the notifications can be sent to the ZfA by starting the transfer.
Inbound notifications that the ZfA prepares for the customer are automatically retrieved from the inbound queue for the customer at the ZfA (periodic process), and are sent to the B2A Manager (area OED, document type IZFA). From here, they are further processed in the SAP R/3 system using an application report.
For more details on this process, refer to the section Status Management (B2A connection).
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 |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| PAY_DE_B2A_ZFA_000 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | PAY_DE_B2A_ZFA_000 | 0 | PL00000001 | B2A: Business to Administration |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20070926 |
| SAP Release Created in | 600 |
