Kontakt

Ansicht
Dokumentation

RPCEDGV0 - Electronic Dialogue with Employer - Collect Employee Data

RPCEDGV0 - Electronic Dialogue with Employer - Collect Employee Data

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

Purpose

This report reads data from payroll result (RT payroll result table), master data and Customizing that is necessary for Electronic Dialogue with Employer (EDAG) reporting. The report prepares a separate XML entry in the EDAG reporting database for each selected employee.

This report creates XML files in the IRED (Income Recipient Data) schema format that are stored into the database.

You can run this report multiple times for the same reporting period. The system uses the latest XML entry to prepare the A-melding.

Integration

Prerequisites

Features

XML files in the (IRED) format are used by the RPCEDGV0_CORR report as input and XML files in the same format are also stored into the database.

Other reports for example, RPCEDGV0_SBMS, RPCEDGV0_DISP, and RPCEDGV0_ANST also read the XML files in this (IRED) format from the database.

The structure of this XML file is very similar to the XML schema for an A-Message submission. But, the XML file can only contain data for one each of the following:

  • Database Storage ID (STGID)
  • Personnel Number (PERNR)
  • Reporting Period (PERIOD)
  • Enterprise Number (ENTNR)
  • Business Number (BUSNR)

Note: if you have data for one STGID, one PERNR, one ENTNR, and one BUSNR but for more than one PERIOD, then they must be stored in several XML files (in this case, each PERIOD must have it's own XML file).

The following list of IRED changes is from the official XML schema for A-Message submission:

  • XML namespace is defined as "http://sap.com/HRNO/EDAG_v2_1"
  • The root element in the XML file is inntektsmottaker
  • Type Inntektsmottaker is extended with the following attributes:
  • stgid - Database Storage ID

  • pernr - Personnel Number

  • period - Reporting Period

  • entnr - Enterprise Number

  • busnr - Business Number

  • build_info - information about version of RPCEDGV0 report which was used for creation of this XML file

  • elements
  • arbeidsgiveravgift: compared to A-Message, this element is moved from the virksomhet node to the inntektsmottaker node. In general, it contains the same information but only part which is related to the area specified by keys (STGID, PERNR, PERIOD, ENTNR, BUSNR).

  • betalingsinformasjon: compared to A-Message, this element is moved from oppgave node to inntektsmottaker node. In general, it contains the same information but only part which is related to area specified by keys (STGID, PERNR, PERIOD, ENTNR, BUSNR).

  • betalingsinformasjonForForenkletOrdning: compared to A-Message, this element is moved from oppgave node to inntektsmottaker node. In general, it contains the same information but only part of which is related to area specified by keys (STGID, PERNR, PERIOD, ENTNR, BUSNR).

  • Type Arbeidsgiveravgiftsgrunnlag is extended with the prosentsatsForAvgiftsberegningBunnfradragLav element. This value is used in the RPCEDGV0_SBMS report instead of prosentsatsForAvgiftsberegningwhen any Bunnfradrag is available.
  • Type FradragIGrunnlaget is extended with the prosentsatsForAvgiftsberegningBunnfradragLav element. This value is used in the RPCEDGV0_SBMS report instead of prosentsatsForAvgiftsberegning when any Bunnfradrag is available.
  • Type Betalingsinformasjon is extended with the sumArbeidsgiveravgiftBunnfradragDelta element. This value is used in the RPCEDGV0_SBMS report when any Bunnfradrag is available.
  • Type BetalingsinformasjonForForenkletOrdning is extended with the sumArbeidsgiveravgiftBunnfradragDeltaelement. This value is used in the RPCEDGV0_SBMS report when any Bunnfradrag is available.

Code lists that are used in IRED XML files are the same as code lists for A-Message submission. Code lists used in the XML file are validated when the XML file is upload by the RPCEDGV0_CORR report.

If used codes are not correct then the XML file will be rejected by the RPCEDGV0_CORR report with an error message in log. These code lists are not part of the XML schema but they are published and updated by authority in external file.

For the actual file with latest code list, you must contact authority.

Selection

The Data Selection Period field is not relevant for this report.

Standard Variants

Output

Activities

Running this report is a prerequisite to submitting an A-melding message to Altinn. After performing this step, you still need to make the following steps to send your A-message to Altinn:

  1. Consolidate employee data that this report prepares into a single XML message for your whole enterprise. For more information, see the Submission Message (RPCEDGV0_SBMS) report.
  2. Send the consolidated XML message to Altinn in one of the following ways:

Note

  • XML files downloaded from this report are not indented. To indent them, you can use various XML editors like XML Copy Editor (an open source XML editor) and select the "Pretty-print" functionality from the menu.
  • If the XML file from this report is used as a template, remove the arbeidsforhold node. Only one UNIQUE arbeidsforhold node in submissions can be reported. If it's found in the correction file, then this file won't be included in the submission (there'll be an error message in the log).

Example






PERFORM Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 8303 Date: 20240601 Time: 115056     sap01-206 ( 109 ms )