Ansicht
Dokumentation
RPCRBMD0_INBOUND - Inbox: Pension Receipt Notifications
Addresses (Business Address Services) BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Purpose
This report imports the XML files sent by the German Central Pension Administration Office (<ZK>Zentrale Zulagenstelle für Altersvermögen</> (ZfA)) and stores the notifications contained in these files to the notification databases.
Selection
Inbound Platform
You can select the B2A inbox as the incoming item type assuming that the data transfer take places is B2A. The report then imports newly received data from B2A automatically.
Otherwise, you can specify an index of incoming item types on a local PC or on the application server.
File Selection
By making an entry in the Notification Reason field, you can restrict file selection to specific notification reasons.
Note:
A ZE99 file contains notifcations of the type MI01 or MZ01.
In this case, notification reason ZE99 is relevant for file selection.
General Program Options
The report shows a list of processed files and, in the detail view, the file in XML format.
If you select the Create Log checkbox, the extracted notifications are also shown.
If you start the report with the Database Update option, the notifications are stored in the notification database. In B2A, successfully processed files are given the status Transferred. If B2A is not active, the system moves the file from the specified index of incoming item types to the specified storage folder.
Standard Variants
Output
The report shows a list of processed files and, in the detail view, the file in XML format.
If you select the Create Log checkbox, the extracted notifications are also shown.
The statistic notifications are also output to the Total Statistics, separated into file statistics and notifications:
- Statistics:
- Files Read
- Notifications Read
- Assigned Notifications
- Unassigned Notifications
- Processed Files
- Files Not Processed
- File Statistics:
- Files Read
- Processed Files
- Files Not Processed
- Notification Statistics:
- Notifications Read
- Assigned Notifications
- Unassigned Notifications
Example:
A file with invalid XML structure produces an error message File <No> with errors: Day <...> not found in the log node General Messages and is counted in the statistics under Files Not Processed.
A file that contains a rejected MZ01 notification, but for which the outbound MZ01 notification cannot be found in the system, produces the error message File <No> Notification <No>: outbound notification not found in the log node General Messages and is counted in the statistics under Files Not Processed. The notification is counted under Unassigned Notifications.
Enhancements after First Delivery
Assignment of IM01 Notifications with Personnel Numbers
The processing of inbound notifications has been extended so that IM01 notifications for which there is no outbound notification are processed if the personnel number (notification obligation key), name, and date of birth match the master data. For more information, see SAP Note RBM: IM01 Inbound Notifications without MI01 Outbound Notifications (1533304).
Manual Postprocessing: Remove Unprocessed B2A Files
B2A files that cannot be processed automatically, can be set to the status "with errors" in a manual postprocessing step. This way they are removed from the B2A inbox. The "Manage Files with Errors" function key was added to the "Files Read" log node for this purpose. This function is available only in update mode and in dialog mode. For more information, see SAP Note RBM: Remove Unprocessed Files from the B2A Inbox (2190419).
Activities
Example
General Material Data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5407 Date: 20240601 Time: 134758 sap01-206 ( 138 ms )
