Kontakt

Ansicht
Dokumentation

RPUD3AD0 - Identification and Deletion of DEUEV Notifications

RPUD3AD0 - Identification and Deletion of DEUEV Notifications

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Description

With the report RPUD3AD0 (marking and deleting the DCR notifications) you can change the status of the saved DCR notifications as well as delete the rejected DCR notifications.
You use the report to

  • Mark the notifications rejected by the health insurance fund with the status Rejected;
  • Mark the notifications you wish to transfer again with the status To transfer;
  • Delete the notifications with status Rejected;
  • Mark the notifications With errors, which you have transferred to to the funds via the form, with the status Notified manually;
  • Mark the notifications with the status Rejected as Notified manually if these notifications do not have to be created automatically any longer, but if they are transmitted to the funds via the form.

Features

Selection of notifications for each employee

In the group box Selection you can select the DCR notifications of specific employees (personnel number, payroll area).

Selection of notifications according to the year of origin/notification number

In the group box Selection via key fields you can search systematically for a notification number and/or for notifications across the whole year.

Selection of the notifications on a data medium

The notifications of a DCR data medium are determined uniquely by the specification of Sender (personnel area and subarea ), Recipient and File counter (file number).
In the group box Selection via data medium run you can select the notifications of a data medium run by indicating the personnel area/subarea (sender), the fund/branch office (recipient) and the file counter.

If the data medium was sent via a disk (or EDI) you have to specify the fund/branch office as recipient. If the data medium was sent by mail, you have to indicate the company number of the e-mail forwarding point.

The file counter is saved by the report RPCD3TD0 (create DCR data medium) for each sender and recipient, on the basis of the data exchange type, either in table DCR file counter (T5D4S) or in table File numbers for e-mail procedure (T5D4U).
During each run of the report RPCD3TD0 (create DCR data medium) with the same sender and recipient, the file counter increases by one unit.

Please note that the personnel subarea (if available) also has to be filled in for the sender. If several senders/recipients have to be marked, then the report has to be started separately for each sender/recipient pair.

Note:
A selection of the DCR notifications on a data medium is always sensible, if you have to repeat a specific data medium run for a sender and a recipient. In this case you mark the DCR notifications of this data medium run as To transfer.
In case of a data medium run with the current highest file counter, you delete this file counter for the sender and the recipient involved in the table T5D4S and/or T5D4U. The repetition run then receives the same file counter again. Subsequently you can transfer these notifications again with the report RPCD3TD0 (create DCR data medium).

Selection by creating period of notifications

If you have not entered anything neither in the group box Selection via key fields nor in the group box Selection via data medium run, the period entered in 'Payroll period' is used for selection. As a consequence, all the notifications created in this period with the report RPCD3VD0 are marked.

If you use this kind of selection, please note that the report RPCD3TD0 sets the creation period to the transfer month when the annual notification is transferred. I.e., an annual notification created in period 12 and transferred in period 03 can therefore only be selected in this manner with creation period 03.

Function Selection

In the group box 'Function selection' you determine what should happen with the selected notifications. The selected notifications can be

  • Marked with status 10 (Rejected).
    This status is used to mark the DCR notifications of single employees whose acceptance was rejected by the health insurance fund. Notifications with status Rejected are ignored by the report RPCD3VD0 (create DCR notifications) while importing the existing notifications and instead new ones are created.
  • Marked with status 03 (To transfer)
    This mark is significant only for DCR notifications of a data medium run that you wish to transfer again. Notifications with status 03 are selected again with the next execution of the report RPCD3TD0 (Create DCR data medium) and they will be written in the notification file.
  • Marked with status 13 (Notified manually)
    This mark should be put on notifications with errors that you have transmitted to the fund via the form ('Notification to social insurance').
    Furthermore it is possible to mark the rejected notifications as 'Notified manually' to avoid another automatic creation. This procedure is significant if the refusal of the notification was caused by a wrong data constellation which does not have to be corrected retroactively anymore. The status Transferred, Rejected (and if nec. Certified) are deleted here.
    DCR notifications with status 'Notified manually' cannot be corrected automatically by HR DCR anymore because it is not certain whether the notifications in the system match the data actually transmitted to the receiving offices. Therefore any corrections of these notifications are treated in a particular way: the cancellation to be done on the notification gets the status With errors and Locked, the correction notification to be submitted gets the status With errors and Notified manually. This type of marking ensures that notifications are not stored on the DCR data medium and that they are displayed when selecting notification with errors for a person resonsible list. The status 'Notified manually' shows that it must be a correction of a notification transferred via form. You can then decide case by case whether the correction is justified and if applicable transfer it via form to the insurance funds, if necessary.
  • Delete
    All the selected DCR notifications with status Rejected are deleted.

Test Options

Since the status changes carried out by the report RPUD3AD0 on the notifications can only be partially undone, we recommend starting the report at least once in test run before each update run (no database update, create log) and to check the short list created as well as the statistics. In this way you can avoid selecting wrong or too many notifications by entering incorrect or incomplete data on the selection screen.
In particular, marking notifications as 'Rejected' and/or 'Notified manually' cannot be undone.

  • No database update

If this parameter is activated, the report runs in test mode. No changes to the database are carried out.

  • Create log

A short list of all the selected notifications is created.

Requirements

Output

Example






RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 8787 Date: 20240520 Time: 131115     sap01-206 ( 163 ms )