Understanding Relationship PT and PY

I. Relationship

Every employee who’s in an enterprise, has to come offices/ companies and work days by days. Normally 5/6 working days per week is mandatory. He uses his time, his efforts, create benefits for company and then get monthly salary. In SAP HCM, system will calculate how many times he works in company (It’s Time Management – PT in SAP HCM), and then bring time results calculated by Time Schema to Payroll. After receiving result, system will give his salary in this month by running Payroll Schema (It’s Payroll – PT in SAP HCM).

How can system link between Time Schema and Payroll Schema? The answer is the TIME WAGE TYPE. Time Schema calculates and gives this value into Time Wage Type. The NUMBER field of wage type is inputted. Whenever running Payroll Schema, system will use the existed value in this wage type, multiply with RATE , and then give a part of salary into AMOUNT field of Wage Type. It’s the relationship of Time Management and Payroll.

II. Exercise

Now let’s look at carefully a typical example in PT and PY. It’s my client’s expectation. In this enterprise if employee attends or has check-in and check-out, he will get 27 INR per day and it’s accumulated into his month salary. If in a month he has ten days in company, his salary will be added more 27*10 = 270. But only available from Oct-2012, as in the past HR user calculated manually monthly. Now how to do?

1. Time Schema

First, you have to calculate number of date that employee attend or check-in check-out fully. Time schema will help you accomplish this function. Before creating new PCR (Personal Calculation Rule), a Time Type must be registered in system. In my case it’s 9M99 – Worked Days 4 FurnaceAll. You can configure in V_T555A with T-Code SM30 / SM31

As you can see, Cumulate in period balance, Transfer prev. period & Transfer prev. year I chosen 1, because in my system cut-off date is 25th every month. Next coming to with PCR

ZE05 Full Time Event/Attendance for Wage Type 1065

It’s quite easy.

OUTTPORIGS Origin status

–       E: data in infotype 2011.

–       P: data in Infotype 2002.

OUTTPEXTIM Times exist?: check Time Event full check-in and check-out or not.

Inserting the PCR into Time Schema as same as picture below: after calling Functions P2011, P2002, etc

You see, the value’s still stored in Time Type 9M99, next you have to move it into Wage Type – 1065 (field NUMBER).

NOTE: as of putting Operation ADDMB in middle of month (every 25th), so must correct with following guidance in document Understanding operation ADDMB. Period X to Y with X = 26th and Y = 25th.

Check if 26th, generate more time type (assuming 9H99, same configuration with 9M99) by HRS=M9M99 HRS-M9H99 ADDDB9H99.

in pcr ZTFR on 25th, HRS=M9M99 HRS+D9M99 HRS-M9H99 ADDZL 1065.

Checking Year, Month and then bring value stored in 9M99 into Wage Type 1065. After that 9M99 is immediately cleared. However where should PCR ZTFR be inserted into Time Schema:

  • Create 1 pcr checking cut-off date: ZI22, in my example ZPY03 in constant in V_T511K and equals 25.

  • And then insert ZTFR inside: so ZTFR only run on the cut-off date:

Time Schema is done here.

2. Payroll Schema

Secondly, you have to modify Payroll schema.

ZKFUR is a constant in V_T511P with value 27.

Next Creating PCR – ZPFR Furnance All – to multiply (NRA):

NUMBER value in Wage Type 1065 is calculated by Time Schema above.

RATE: constant in T511P ZKFUR

Where do you should put your schema? Yes copying ZT00 from XT00 and you can put your schema as below:

Note: input PCR into sub-schema XT00 after Functions ZLIT, because Function ZLIT is used to import wage types from internal table ZL to internal table IT.

That’s all in configuration and modification in Time Schema as well as Payroll schema.

3. Testing

In my testing, the employee works 6 days per week. In Oct-2012, 07th 14th 21st and 28th are working-off dates.

In Infotype 2011, in Oct, he only has 22nd-Oct fully check-in and check out. 19th-Oct has been missed check-out.

In Infotype 2002, he has attended from 23rd to 27th Oct.

Note 25th every month is cut-off date. So with that case, in Oct-2012, he has 4 days to calculate FurnaceAll: 22nd, 23rd, 24th and 25th. And in Nov-2012 he only has 2 days on 26th and 27th for FurnaceAll. Look at my payroll testing below, you can see all is correct for both 2 months Oct-2012 and Nov-2012.

III. Conclusion

Time Wage Type is a bridge for PT and PY. In order to understand deeply PT and PY, you have to control Time Schema, Payroll Schema especially understanding how Time Wage Type is generated. Hope you will be able clear 2 most important parts in SAP HCM.



Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.