Ansicht
Dokumentation

RPCWVSD1 - Start Creation of Interface Data Using Processing Type

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Title

Create Dataset for Actuarial Interface

Purpose

With report RPCWVSD1, you create a dataset for each personnel number. This dataset describes the status of the pension entitlement on a balance sheet key date. This dataset can be used as the basis for the creation of the actuarial interface.

Prerequisites

For a balance sheet key date, report RPCWVSD1 writes personal data to table P01CVH, entitlement data to table P01CVD, and pension data to table P01CVR. With the transfer report RPCAVTD0, you can extract all data that is relevant for the actuarial interface from the dataset and write it to a sequential data file. The data structure for your interface must be declared in the Data Dictionary and assigned to the benefits provider using view V_5DC3_A.

Before you create the dataset with report RPCWVSD1, all fields for the interface must be included in the standard dataset for tables P01CVH, P01CVD and P01CVR. If this is not the case, you must insert a field in a customer include structure CI_P01CVH, CI_P01CVD or CI_P01CVR for the corresponding table. You can then use the customer exit EXIT_RPCWEXIT_310 for enhancement P01ABAV7 to fill the field according to your requirements.

Compensated entitlements

You can use feature DWVMT to manage the entitlements that have been compensated. The last personnel action from the inventory key date is used to determine whether or not an entitlement must be determined.

Individual day for balance sheet key date

Feature DWCBS enables you to assign the balance sheet key date to a benefits provider. If the 'Individual balance sheet key date' is not flagged in table T5DC5, the dataset is only created for benefits providers if the balance sheet key date matches the key date from feature DWCBS.

Inventory key date

This key date defines the time limit to which the CPS-relevant data can be evaluated. Data for which the validity start date is after the inventory key date is not taken into account.

Valuation key date

The status of the current entitlements is calculated on the valuation key date.

Data model

The current status of the entitlements and pensions is stored in three transparent tables by report RPCWVSD1.

Table P01CVH contains employee date, for example, personal data

Table P01CVD contains entitlement date. Current entitlements and vested entitlements are stored.

Table P01CVR contains pension data. The system differentiates between individual pensions and surviving dependants' pensions.

The key fields for all three tables are as follows:

1. 'Reason for Creation of Interface Data'. This field enables you to differentiate, for example, between the creation of an annual dataset as the basis for reserve calculations and the creation of a data basis for valuation of a company if it is devolved.
2. The balance sheet key date is given on the selection screen of the report. This is the date for which a financial statement is created for an enterprise. Report RPCWVSD1 uses the balance sheet key date to fill the 'Notification status for actuarial interface' field in the new dataset. The system differentiates between 'new notifications', 'change notifications', and 'non-relevant notifications'. New notifications are in the dataset for the first time, change notifications were already in the dataset on the last balance sheet key date, and non-relevant notifications were in the last dataset but they were no longer included on the balance sheet key date of the current dataset. The entitlement is, however, carried over in a different record (for example, the conversion of a current entitlement to an individual pension). Non-relevant notifications for the previous balance sheet key date are no longer included in the dataset.
3. All data is created for each benefits provider.
4. As well as the personnel number, the 'Identification key for person' is necessary to group together persons for an original entitlement. For example, surviving dependants' pensions for a testator can be grouped together using this key criterion. The 'Identification key for person' is filled with the personnel number by report ROCWVSD1. To fill this field according to your requirements, use customer exit EXIT_RPCWEXIT_300 for enhancement P01ABAV7.
5. The 'Benefit type' shows whether entitlements, vested entitlements, individual pensions or surviving dependants' pensions exist.
6. The dataset in tables P01CVD and P01CVR is also stored for each entitlement.

Status administration

The permissibility of individual records in the dataset for subsequent transfer is controlled using the 'Processing status for interface data'.The standard system contains the following statuses:

1. NEW:

Report RPCWVSD1 generally creates data records with the processing status 'New'. Records with the status 'New' can be set up directly in the interface by the transfer report RPCAVTD0. Records with the status 'New' can be cancelled, in other words, when RPCWVSD1 is started again, the old data record is overwritten by the new data record.

1. TRANSFERRED:

If data records have already been transferred in a TemSe file by report RPCAVTd0, their status is set to 'Transferred'. Transferred records can be transferred again by report RPCAVTD0. However, the dataset cannot be cancelled with report RPCWVSD1 for notifications that have already been transferred. If you want to create a new dataset for transferred notifications because the dataset was subsequently found to have errors, you must use report RPUAVDD0 to delete the transferred dataset so that you can then create a new dataset.

1. INCORRECT:

If the status of the interface data is set to 'Incorrect', this data is not used in the transfer report. This records is overwritten by a new data record when the notification creation report is run again. The status 'Incorrect' is not set in the standard system. However, in customer exit EXIT_RPCWEXIT_310, you can include a consistency check and set the status to 'Incorrect' yourself. All incorrect data records can be displayed with report RPUAVAD0.

1. REJECTED:

You can assign the status 'Rejected' to notifications that have been rejected by the recipient. You do this in report RPUAVAD0. The notification and transfer report treats rejected notifications in the same way as incorrect notifications.

1. TRANSFERRED MANUALLY:

You can set the status of incorrect or rejected notifications to 'Transferred manually' using report RPUAVAD0 if you have sent the data to the recipient without using the transfer report in the system.

1. NEW WITH WARNING:

If notifications have been created without errors but the corresponding data record for the previous balance sheet key date has a status that is not 'Transferred', the status is set to 'New with warning'. If you check the data and find that this dataset can be set up in the interface without any problems, you can use report RPUAVAD0 to set the status from 'New with warning' to 'New'. If this is not the case, the notifications are not transferred.

1. Reaction of data creation report to processing status

Notifications with the status 'Transferred' or 'Transferred manually' are not overwritten if the report is restarted on the same balance sheet key date (reversal). A warning is displayed. Notifications with all other statuses are overwritten.

If the status of the notification for the previous balance sheet key date is 'Transferred', the current notification is set to 'New'. For all other statuses, the new notification is assigned the 'New with warning' status. For all these cases, you must check whether you can set to notifications to 'New'.

The transfer report only selects notifications with the status 'New' and 'Transferred'.

Activities

Example

ROGBILLS - Synchronize billing plans   General Material Data  
This documentation is copyright by SAP AG.

Length: 8444 Date: 20240601 Time: 061919     sap01-206 ( 182 ms )