Ansicht
Dokumentation

RPCAOPD0 - Data Access Tax Audit: Export of a Year

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Purpose

The export program for the interface format (transaction code PU12) is called for all the periods of a year to generate the files for the "data transfer for tax audit". The data from the export program is used to generate files for the data transfer and a *.xml data description in the file system.

If you start the report for a large set of personnel numbers, you must start it in the background. If this is the case, deactivate the Export Logs checkbox, otherwise the large quantities of data can cause a runtime error.

For test purposes, you can run the report in dialog mode. Since processing can be extremely time-intensive, execution is only possible for small sets of personnel numbers.

If the Export Logs checkbox is set, the export program for the selected interface program outputs the export log for each personnel number and period. The log is very detailed and only suitable for testing with small sets of personnel numbers. Deactivate this switch for update runs, as the program might terminate otherwise.

The generic text reader is used to read text tables (see IF_TEXT_IDENTIFIER). The corresponding text tables are generated and are part of the data transfer. The .XML data description references the corresponding text table (if any) for each field in the data tables.

General information about data access for tax audits

Integration

Prerequisites

Payroll results must exist for the selected personnel numbers.

The interface format DAO0 is delivered as a template for data transfer in the standard delivery. In transaction PU12, copy DAO0 to a transportable customer package in the customer namespace and make the required adjustments to your copy. In PU12, generate the source text of the related export program in your development system. You have to repeat this generation after every change to the structure of the transferred data (for example, infotype structures). Transport your interface format including the export program to your system landscape. Create a variant in your export program. In the Export Options block, select the fields Original Periods Only and Update.

Employment tax notification, external data: Starting in 2005, it is possible to create "external data" for the employment tax notification (see the documentation for the Elster employment tax notification). The data is saved in database table P01T_A_EXT. All fields for the selected year that are contained in structure P01T_A_EXT_AO are transferred. You can modify this structure as necessary.

Wage type classification: A classification for each transferred wage type is determined in class CL_HRPAYDE_LGART_CLASSIFIC (click the link for more information) and is available to the tax auditor in the wage type table. Key C147 is used for the data transfer.

Logical file name or logical path:see HR_DE_TX_DATENUEBERLASSUNG_DATEINAME

Duration of the created TemSe objects:In the case of errors, the TemSe objects created by the export program are not automatically deleted and are available for error analysis. Set the duration of the HR TemSe object ID "PINFTS" using the TEMSE feature. In this way, the standard TemSe tools (such as a regularly scheduled job for report RSTS0043) can delete it in an appropriate period of time.

Transaction authorization PC00_M01_RPCAOQD0 is required to execute report RPCAOPD0 as report RPCAOQD0 is called after the TemSe objects have been created.

Features

Selection

Standard Variants

Output

When RPCAOPD0 is started in the background, background jobs are scheduled for the file export. When job management starts them, they run in the background. The constant V_T511K-AOPNR restricts the number of personnel numbers that can be processed per period in one job. Once they are scheduled, RPCAOPD0 waits for their successful completion. The job status is queried every 60 seconds. If you want to override this wait time, you can define the constant V_T511K-ZAODT.

The report creates extremely large tables at runtime. To avoid filling the main memory, they are periodically buffered and deleted. You can configure constant V_T511K-AOGAP to define the size for buffering. Check this constant if any runtime errors with type system_Imode_too_large occur.

Activities

After you have copied the necessary files for the auditor from the application server to a suitable data medium, or after you have decided that they are not required, you can use report RPCAORD0 to delete the TemSe files created in the last run and the files on the application server.

In the case of errors, you can also process individual TemSe files for analysis using report RPCAOQD0. Do not use the files created on the application server for a productive data transfer.

Example

Fill RESBD Structure from EBP Component Structure   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5707 Date: 20240601 Time: 183934     sap01-206 ( 142 ms )