Ansicht
Dokumentation

PAY_DE_RVBEA_000 - rvBEA - Overview -

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This chapter explains how to set up the rvBEA (Request and Accept Statements Electronically) notification procedure.

rvBEA describes a new communication standard of the German Statutory Pension Insurance data office (DSRV) based on XML schemas. The new communication standard should be used to replace the paper-based communication between pension insurance funds and employers with electronic data transfer. This ensures that pension insurance meets the legal requirements of Section 108, paragraph 2, clause 3 SGB IV.

The first rvBEA subprocedure - electronic request for a GML57 notification - is based on Section 194, paragraph 1, clause 3 SGB VI.

The second rvBEA subprocedure is FORMS.

You can find the reports on creating notifications and notification files for the registration and the GML57 and FORMS subprocedures in the SAP menu:

• Registration

Human Resources -> Payroll -> Europe -> Germany -> Subsequent Activities -> Period-independent -> Payroll-related area -> rvBEA Registration

• GML57 Subprocedure

Human Resources -> Payroll -> Europe -> Germany -> Subsequent Activities -> By Payroll Period -> Payroll-related area -> rvBEA GML57

• FORMS Subprocedure

Human Resources -> Payroll -> Europe -> Germany -> Subsequent Activities -> Period-Independent -> Payroll-Related Area -> rvBEA Forms

Information on GML57 Subprocedure

If you receive an electronic request for a GML57 notification, a record of infotype Electronic Data Exchange (IT0700) with subtype DXAR is created during the processing of the notification for the personnel number affected. This is a key date infotype that is created on the last day of the month of the payroll period of the GML notification requested. The GML57 notification is created with the next DEUEV run if the payroll results for the payroll period requested are available.

You can manually maintain the IT0700 record. To manually enter the date for submission of the GML57 notification, you can continue to use infotype Date Entries (IT0041).

When processing the GML57 notification request, if you discover that the DEUEV notification GD57 cannot be created, infotype Electronic Data Exchange (IT0700) with subtype DXAR is created and the relevant prevention reason is entered.

The following prevention reasons may occur:

• 11,,No Employee Exists for this Insurance Number

• 12,,Error in Dataset

• 13,,GML57 Notification Already Transferred

• 14,,Employment Relationship No Longer Exists

• 15,,Employee Does Not Receive Remuneration

• 16,,All Periods Were Already Reported For

• 17,,Request Contains Formal Errors

• 18,,Requested Period Can Not Be Transferred

• 50,,GML57 Notification Rejected due to Errors

• 51,,Confirmation Record with Prevention Reason Was Rejected

• 52,,Company number (BBNRVU)is not on record

• 99,,Other error

The prevention reason is confirmed with XML data record DXEB in the rvBEA procedure.

For more information about the procedure, see the report documentation. You can find information about the technical set-up of the communication standard in Customizing under Payroll: Germany -> Communication with Authorities (B2A) -> Data Exchange with Health Insurance Providers -> Technical Basis for Communication with PKCS#7 -> Communication Server/Web Service-> Communication Server/Web Service of Pension Insurance (rvBEA).

Information on GML57 FORMS Subprocedure

For more information on the FORMS subprocedure, see the documentation Process for the rvBEA FORMS Notification Procedure.

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

Length: 4839 Date: 20240523 Time: 194105     sap01-206 ( 75 ms )