Storing the date of Infotype 2010 Records in the Payroll Cluster and the Payslip form

[narayanv1]

Introduction

This post explains how to get the date of the Infotype 2010 (Employee Remuneration Info) record populated against the corresponding wage type entry on the payslip using standard SuccessFactors ECP / On-prem SAP Payroll configuration.

Background

Payroll customers often ask how an employee can reconcile multiple line items of time-based allowance payments with what they have been paid. Allowance payment data is usually entered via Infotype 2010 (from either SAP ESS or UKG Kronos or WFS). The onus is usually put on the humble payslip form to display a number, rate, amount and above all, the date for which that wage type was generated.

1. Keep it simple? In my experience navigating this requirement, customers are advised to keep the payslip simple and let the employee see the date instead on the incoming Infotype 2010 record on ESS or ECP IT2010 payroll mashup screen (if that’s where they claimed it from) or via UKG Kronos or WFS, the upstream rostering and timesheeting system.
2. Bite the bullet? If the requirement is a must-have however, the solution usually leans towards an ABAP development in two places, one at the payroll schema end with a custom operation to store the date against the wage type, and the other at the payslip form interface end to read this custom payroll cluster field.

In the interest of simplicity of the solution and long-term sustainability of supporting it, it makes sense to use standard payroll configuration and payslip HRFORMS configuration. The only challenge is an unavailability of any SAP community resources documenting how this should be done. So I set out to create something that will be useful.

Contents

This post talks about:

1. The payroll schema logic flow where we can plug in a custom PCR to catch the date of the wage type.
2. The corresponding configuration change required on the relevant country’s payslip form.

Disclaimer:

All screenshots taken are from SAP’s practice systems https://practice.learning.sap.com/ and employee data is entirely fictional. The sample configuration is based on German payroll as it has the best data available to work with. The payslip form is also only partially able to be tested in this demonstration because of environment constraints.

Payroll Configuration

Consider the following employee who has a few IT2010 records.

Figure 1 – Infotype 2010 Records

On running payroll, we can see that variable splits are assigned to individual IT2010 records.

Figure 2 – V0 Split on 2 of the records

Figure 3 – V0 split on the other 2 records

This split identifier is useful because this will help us correlate the RT entry with the IT2010 entry.

We dig deeper into the payroll log to find out where this is being assigned in standard SAP.

Running the payroll for this period using the standard schema shows that the function P2010 (International) is called in the Gross Remuneration: Time Data Processing part or subschema XT00 (International). My screenshot has the German payroll schema; hence it shows function D2010, rule D930 and subschema DT00.

Figure 4 – Rule that processes Infotype 2010

The next order of business would be to find out where is the IT2010 record being identified as a Variable split. The following screenshot depicts a flow of PCRs X930 -> X935 -> X931 -> X932 -> X933 -> X934 -> X936 which is the usual SAP flow of checking whether a custom rate exists, or whether a payscale is specified, etc.

Figure 5 – Where is the incremental split added?

In X936 (D936) is a statement as highlighted above where SETIN X=NX appears. This is our best place to plugin custom logic to spit out information such as the date of the IT2010 record into some internal table in the payroll cluster.

We customize this set of rules as shown below and then insert our logic to extract the date.

Figure 6 – Copied standard to custom

The statement TABLEP2010 prepares the current Infotype 2010 internal table entry for use, and the statement XV0B BEGDA adds the begin date of this record to the V0 table.

Figure 7 – Fetched and added BEGDA

Instead of having the splits as Variable Assignment type, we can have a custom alphanumeric character as below.

Figure 8 – Using a custom V0TYP

We neatly get the begin dates against the Variable assignment splits in the V0 table

Figure 9 – V0 internal table

This is now available in the cluster.

Figure 10 – V0 in PC_PAYRESULT

Figure 11 – Contents of V0 in the cluster

Payslip Form Configuration

Add Variable Assignment splits to the relevant section on the Form.

As shown below, drag the relevant fields from the MetaNet section into the InfoNet section.

Figure 12 - HRFORMS addition

Clicking on Layout will take you to the following screen where the same fields need to be added in the form context.

Drag and drop the Import STAR into the Context section as shown below.

Figure 13 - HRFORMS context editing

The newly added fields now appear in the context section.

Figure 14 - V0TYP and VINFO in form context

After saving and activating both the form context and form layout, you can do a Print Program (Test) to check if the newly added date in V0 actually does land up in the payslip form data containers.

Figure 15 - Print Program Test

Running the payslip for the same employee with a live payroll result displays data containers as below. You can see that the date is successfully populated.

Figure 16 - Date Appears in Container

Once this Payslip STAR has the requirement information, you can edit the existing payslip Adobe Form to display this element. Due to constraints of ADS connection in the SAP training system, I am not able to demonstrate this on a test payslip.

Conclusion

Thus, we have seen how Infotype 2010 entries from the HR system (upstream EC mashup or on-premise IT2010 Fiori app) can carry the date over to the payroll cluster and then be made available for the payslip form to display it.

 SAP SuccessFactors Employee Central Payroll 

HCM Payroll