Process Flow: Import Payroll Results from a Third-Party System (SAP Library

Process Flow: Import Payroll Results from a Third-Party System

Purpose

If you run payroll in an external system, y ou use the data import method shown here in the R/3 System.

Prerequisites

You have set up the ALE distribution model in Customizing.

Process Flow

Importing Data to the R/3 Payroll System

This graphic is explained in the accompanying text

An IDoc is created for each employee from the input file containing the wage types from the external payroll system. The InsertOutsource BAPI is called for each IDoc. Due to the amount of data, we recommend that you call the BAPI asynchronously. This also applies if you use your own file interface.

For documentation on the BAPI and its interfaces, see the BAPI Explorer.

The BAPI creates entries in the following interface tables:

Payroll Account Transfer: Payroll Periods (T558B)
Transfer Wage Types with Split Indicator (T558B)

Transfer External Payroll-Arrears Results – International (T558E)

For performance reasons, these tables are only updated once per input file.

Before the data is transferred to the tables, the system deletes the existing entries for the respective personnel numbers. The Start date (BEGDA) and End date (ENDDA) fields are filled with the end date of the current payroll period.

The payroll driver must be started with a special import schema which writes the data from the interface tables to the payroll results in PCL2. SAP provides schema XINF as an example.

Note

To create an example for an input file, you can use report RPUOUTIDOC. This report creates IDocs from the entries in tables T558B, T558D, and T558I. You can write to a file interface using the IDoc exit.

SAP recommends this method. Other methods for data import:

You write a report that calls the BAPI InsertOutsourcer asynchronously. The BAPI is called for each personnel number and reads the data in the interface tables. In this case, you should regularly execute the command COMMIT WORK by calling the BAPIService.TransactionCommit BAPI. The data in the interface tables is then updated with the data from the working memory.
A separate report is used to fill tables T558B, T558D, and T558E.