Ansicht
Dokumentation

RPCBMTD0 - Create DEUEV Data Medium for Professionals Pension

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.

This report is out-of-date and was replaced by the report Create DEUEV Reporting Files for Professionals Pension (RPCBMTD1).

Use

The report creates a file for each sender containing DEUEV notifications for the professionals pension organizations.

The sender of the report file is the reporting personnel area assigned under the subapplication SVMB (reporting for professionals pension schemes). For more information, see the SAP Customizing Implementation Guide for Payroll: Germany.

The receiver of the report file is the e-mail forwarding office of DASBV GmbH.

The file is stored as a TemSe object and forwarded to the B2A Manager. You can use the transaction PB2A (selection by area SV (social insurance) and document category OBVM (pay notifications for professionals pension) ) to e-mail the report file to the forwarding office.

Prerequisites

• Using the report RPCBMVD0 (Create Notifications for Professionals Pension), you have created DEUEV notifications and corrected all incorrect notifications.

• Notifications have been stored with the status New (or To Transfer).

• You have made the Customizing settings for sending e-mails (see Prerequisites in the documentation for the report Create Notifications for Professionals Pension).

Features

Selection of Notifications

You determine the payroll period to be evaluated and the employees to be selected in the Payroll Period and Selection group boxes. If you select an employee, the system writes all the existing DEUEV notifications with the status New to the corresponding TemSe file. The status of the selected notifications changes from New to Transferred.

The payroll period is only relevant for annual notifications. It determines whether existing annual notifications with the status New are to be transferred in the current run (see below).

You start the report RPCBMTD0 (Create DEUEV Data Medium for Professionals Pension) for the same payroll period (usually the current period) and the same employee for which you created the DEUEV notifications using the report RPCBMVD0 (Create Notifications for Professionals Pension). This ensures that the annual notifications are transferred in the required month and that all the employees with new notifications are selected.

Creation of TemSe Objects

TemSe objects are temporary, sequential files that are stored in the system.

All the DEUEV notifications for a sending personnel (sub)area are stored as TemSe object HR_CSVBM0_(consecutive number).

This TemSe object contains the complete report file and is evaluated by the B2A Manager.

Annual Notifications

Annual notifications are created automatically from the month of December by the report RPCBMVD0 (Create Notifications for Professionals Pension). Annual notifications are stored in the system with deduction reason 50. The report RPCBMTD0 (Create DEUEV Data Medium for Professionals Pension) transfers the annual notifications, but not with the other notifications in the DEUEV run in December. Instead, the report RPCBMTD0 contains the Transfer Month parameter in the Annual Notifications group box. Using this parameter, you can determine the month (January, February, March, or April), in which the annual notifications that have not yet been transferred are transferred.

File Counter/File Number and Repetitive Runs

The file counter numbers the DEUEV report files for each sender and receiver in an ascending and continuous sequence.

A file counter is stored for each sender (personnel area, subarea) and forwarding office (company number of the DASBV) ) in the table File Numbers for E-Mail Procedure (T5D4U).

Each time the report RPCBMTD0 creates a TemSe object for a sender and receiver, the file counter for this sender/receiver pair is increased by one in the corresponding table.

Repeating a Data Medium Run

You need to re-create individual TemSe objects if the corresponding file has not arrived at the receiving office or if it has not been sent by mistake and the TemSe object has been deleted.

In this case, you do not have to create new notifications; it is enough to set the status of the affected notification to To Transfer. To do this, you use the report RPCBMLD0_OUT (Person Responsible List for DEUEV Notifications (Professionals Pension)).

First, you determine the date and time of creation of the report file from the T5D4U table. You enter this data on the selection screen for the report RPCBMLD0_OUT under Run Identification and select the Display All Notifications radio button under Func. Selection. The report selects all the notifications that were transferred at the specified time. If you want to transfer only one single data medium again, you set a filter in the Company Number of Logical Sender field in the overview list.

Select all the displayed notifications and choose the Transfer Again pushbutton. Save your status changes. The selected notifications now have the status To Transfer and are written to a new TemSe object when you restart the report RPCBMTD0.

Before you start the report RPCBMTD0, you should delete the file counter in the T5D4U table that belongs to the report files that have not been transferred.

Sending of DEUEV Notifications

The DEUEV data mediums created are stored in the B2A Manager. You can use the B2A Manager to e-mail notifications. On the SAP Easy Access screen, choose Human Resources -> Payroll -> Europe -> Germany -> Subsequent Activities -> Period-Independent -> Authorities Communication (B2A). Alternatively, call the transaction PB2A.

You find the data mediums under the area SV and document category OBVM.

Split Reporting

Using the supporting program RPUD3MD0, the report RPCBMTD0 can group the notifications from several clients/systems in a single report file for each sender and receiver.

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7405 Date: 20240601 Time: 195247     sap01-206 ( 137 ms )