Kontakt

Ansicht
Dokumentation

RPCBOVD0 - Create PPO Notifications for Collection of Contributions

RPCBOVD0 - Create PPO Notifications for Collection of Contributions

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

Purpose

For members of a professionals pension scheme, the compulsory contribution from a job with obligatory insurance or from a part-time job is the same as the pension insurance contribution. For payroll periods as of January 2009, the employer must transfer the data required by the professionals pension schemes about the collection of contributions to this body on a monthly basis and in electronic form. This applies for both the self-payer and the company payer, for whom the employer handles the payment transaction for the compulsory contribution (section 28a paragraph 11).

Integration

Prerequisites

The notifications about the collection of contributions are created based on the data for a payroll result. This means that you must first execute the payroll run for the member of the professionals pension scheme in the payroll period being evaluated.

The system also evaluates records from the Supplementary Pension infotype (0126) to determine the member number. If you have to create a notification again due to retroactive accounting but do not yet know the complete member number (only dummy member number), the system searches the infotype records for the complete member number and uses this instead.

Required Customizing

  • Import the PPO File
You must start the report RPUBVDD0. For more information, see Prerequisites in the documentation for the report RPUBVDD0.
  • Determine the employment company using the Reporting personnel area
Use the subapplication Reporting for PPO Collection of Contributions (SVEB) for the following settings.
In Customizing for Payroll: Germany, under Personnel Area Reporting, you use Define Reporting Personnel Area and Assign Reporting Personnel Area Directly to specify the employment company. This represents the employer as opposed to the professionals pension scheme. The Company Number of Notifying Employer field in the notification record DSBE contains the company number of this employer. In the company payer procedure, the system also prints the company number of this employer in the note to the payee of bank transfers.
  • Determine the sender using the Reporting personnel area
Use the subapplication Reporting for Professionals Pension Schemes (SVMB) for the following settings.
In Customizing for Payroll: Germany, under Personnel Area Reporting, you use Define Reporting Personnel Area and Assign Reporting Personnel Area Directly to specify the sender. This is the personnel (sub)area for which you have received the certificate for encryption.
In the Customizing activity Configure Addresses, you need to enter addresses for the address type Company Address (CA) to be used in the B2A Manager and addresses for the address type Administrator (CL) to be used in the Communication data record.
In the Customizing activity Enter Data on Reporting Personnel Area, you need to enter the address of the administrator in the Determination of Administrator group box in the From Address Admin. field. Do not make any entries in the Address of Recipient group box.
  • Communication with Authorities
To process notifications in the B2A Manager, you need to perform the following Customizing steps:
  • To set up the communication server, make the settings under Payroll: Germany -> Communication with Authorities (B2A) -> Data Exchange with Social Insurance Agencies -> Technical Basis for Communication with PKCS#7 -> Communication Server -> Communication Server GKV.

  • Under Payroll: Germany -> Communication with Authorities -> Data Exchange with Social Insurance Agencies -> Technical Basis for Communication with PKCS#7 -> Maintain Constants for PKCS#7, make the required settings for the SI area and the document types OBVB (dispatch) and IBVB (receipt).

Features

If you select the Database Update parameter in the Program Control group box, the system stores the notifications that are created. The report creates notifications with the following statuses:

  • New
The notification was created without errors and can be transferred and sent to the DASBV using the report RPCBOHD0.
  • Incorrect
The notification was created with errors and cannot be transferred. The error messages are displayed in the report log. You can also use the report RPCBOLD0 to display the incorrect notifications since the error messages are saved with each notification.

Selection

You specify the notification period for creating the notifications in the Payroll Period group box. The periods that were recalculated in this payroll period are added to the notification period. If the Recalculation From Date parameter is used in the Program Control group box, the system may increase the notification period again. If a notification is rejected for a specific personnel number, the system increases the notification period in such a way that it includes the date entered in the rejected notification. If the payroll period lies in the first quarter it is possible to apply the March clause. For this reason, the notification period is increased to at least the start of the previous year or otherwise to the start of the current year.

Standard Variants

Output

The report log is divided into the following sections:

  • Parameter
This section displays the run ID, which consists of the date and time. The system assigns this ID to all the notifications that were created in this run. You use report RPCBVLD0 to display all of the notifications that were created in this run by using this run ID to select the notifications.
  • Details of notification creation
If you select the Create Log checkbox in the Program Control group box, the system displays a detailed log for each professionals member. Do not select this parameter for the entire run.
This section displays the following subpoints for each personnel number selected:
  • Parameter

The system displays the data that led to the specification of the notification period.
  • Notification-Relevant Issues

The system displays the relevant variables in chronological sequence; these are then used to create the Notifications According to Latest Status.
  • Notifications According to Latest Status

These are the notifications that according to the current data are to be notified to the professionals pension scheme.
  • Notifications According to Old Status

These are the notifications that were created in previous runs.
  • Notifications to Be Transferred

The system compares the notifications according to the latest status and those according to the oldest status and lists those notifications that have to be transferred to the professionals pension scheme.
  • Person-Specific Messages
This section displays the error messages that indicate why a message was set to the status With Errors.
  • General Messages
This section displays, among other things, the error messages that indicate why personnel numbers were rejected.
Statistics This section displays information about the processing of personnel numbers.

Compare Notifications

The system compares the notifications according to the latest status and those according to the old status based on the following schema.

Starting with a notification according to the old status, the system searches for a matching notification according to the latest status.

  • If the system cannot find a matching a notification, it considers the status of the notification according to the old status. You must distinguish between the following cases:
  • Status New or With Errors

The notification is deleted because it has not yet been transferred to the professionals pension scheme.
  • Status Transferred

A "zero notification" is created because you cannot cancel notifications.
  • Status Reported Manually

Because the original notification was notified manually, the new notification also has to be notified manually. Therefore, a notification is created with the status With Errors to remind the administrator about this task.
  • If the system finds a matching notification, it compares the contents of the notification and the status of the notification according to the old status:
  • The contents are identical

If the status was Incorrect, the notification is deleted according to the oldest status and replaced by the notification according to the latest status. Otherwise, the notification is kept according to the old status.
  • The contents are different and the status is New or With Errors.

The notification according to the oldest status is deleted because it has not been transferred to the professionals pension scheme; it is replaced by the notification according to the latest status.
  • The contents are different and the status is Transferred.

The notification according to the latest status must be transferred to the professionals pension scheme.
  • The contents are different and the status is Reported Manually.

The notification according to the latest status must be notified to the professionals pension scheme. Because the original notification was notified manually, the new notification also has to be notified manually. Therefore, a notification is created with the status With Errors to remind the administrator about this task.
  • Notifications according to the latest status, for which the system has not found any matching notifications according to the oldest status, must be transferred to the professionals pension scheme.

Activities

If the report log does not list any rejected personnel numbers and any personnel numbers with incorrect notifications under Statistics, you can use the report RPCBOHD0 to transfer the notifications.

Example






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 13645 Date: 20240520 Time: 113920     sap01-206 ( 200 ms )