Time Period 1 month behind Payroll Period

[Former Member]

Dear All,

We are working on +ve time management but time evaluation period is different from payroll period.

The time period is 1 month behind payroll period. So in month of August, the time results of July should be taken into consideration.

The issue is that according to business requirement, the customer wants to run time evaluation on a daily basis.

When this happens, the payroll reads the result of the current month along with the previous month.

Currently, the time period is assigned to period parameter 01 and the payroll period is assigned to a different period parameter.

Is there a way to restrict the payroll schema to only import previous month's time result without reading current time result (in the above example, July only without August)?

Best Regards,

Rana Amr.

[antoine_foucault · Accepted solution]

Hi Rana:

¿what about processing ZL only during retro?

A simple

IF      R

ZLIT

ENDIF

Regards,

Antoine

[Former Member · Accepted solution]

Sounds like a good solution, Rana I think you should try this.

[Sanky · Accepted solution]

Hi,

This will work when retro will happen.

Regards, Sankarsan

[Former Member · Accepted solution]

If as mentioned by Rana, time evaluation relevant data of previous month is updated in the infotypes in the current month, in my opinion retro will be processed every month.

E.g. If It 2011 data for July is updated in August, the payroll program will automatically go retro till July.

Rana you can check and confirm this behavior.

[Former Member · Accepted solution]

Hi All,

Thank you very much for your replies.

I have added the condition for the retroactive and I ran time evaluation for an employee for January and payroll for February, however the retroactive is not triggered. So the ZL table is not processed at all.

Regards,

Rana.

[Former Member · Accepted solution]

Hi Rana,

I have seen the retro getting triggered in my system. Scenario:

Jul payroll is complete, user then makes an entry in It 2011 for 1st July.

1) If you look at Earl MD change in IT 3, it is currently blank assuming no change in payroll relevant infotypes.

2) If you check the PDC recalculation date in It 3, it will be set to the date in Jul for which your new record of It 2011 was created, in our case 01/07.

3) When time evaluation runs next, the time evaluation driver will be executed from 1st Jul since it checks the PDC recalculation date.

4) After live run of PT60, you will see the Earl. Md change which was blank earlier, is now set to 1st Jul.

5) Hence when Aug payroll is run, it will automatically go retro till 1st July.

Try the steps above, paying attention to the dates in IT 3. Please note that the Earl. Md change will be updated after PT60 live run.

[antoine_foucault · Accepted solution]

Hello:

Alternatively, you can just force retro to happen in your payroll program.

Since you want to handle previous month ZL in current month for everyone force retro to happen.

In my opinion P2011 is not processed further in the current month since it only contain personal entry and exit time that actually occurred in the previous month so no retro is generated. Also 2011 changes does not lead to payroll retro.

Time eval happens on a daily basis, but payroll should only consider up-to-previous month data so ZLIT only in retro plus force at least one period retro. System would take care of going further back if IT0003 say so.

Regards,

Antoine

[Sanky · Accepted solution]

Hi Rana,

You can do one thing.

Create a custom function which will same behaviour like IMPRT function but log would period-1 from data transfer from time management to payroll.

Instead of IMPRT function in the XT00 subschema you will use this custom function which will read the B2 cluster for the Payroll Period-1 that is time management period.

Try and let me know.

Regards,

Sankarsan

[Former Member · Accepted solution]

Dear Antoine,

Thank you very much for all your help.

When forcing retroactive calculation, the ZL table is imported only for the previous month and not for the current. So it is processed correctly.

Appreciate all your help.

[jagan_gunja]

There is no standard configuration for such requirement.  In payroll sub schema XT00, function DAYPR

executes the time schema based on employee's PDC recalc date.

However you can do as below:

1)Using a time period end date

1.1)Maintain time eval period start/end dates ZTBEG & ZTEND in TVARV table.

1.2)Create a user program to update these dates, based on the pay period start date - 1

(i.e., T549Q-BEGDA - 1)

1.3)Create a batch job to be run with this program, for every pay period after exiting a pay period or after releasing the payroll for a period.

1.4)Create a variant for RPTIME00 to use the start date / end date using the above dates ZTBEG & ZTEND.

1.5)In RPTIME00, with a user exit or similar code change facility, ensure the above run variant from step 1.4 is used.

1.6) In Payroll sub schema XT00, insert a PCR before function DAYPR - to check if the employee's IT 3 PDC recalc date is before the time eval end date ZTEND in TVARV and if so, allow DAYPR to execute.

Above should satisfy your requirements.

[Sanky]

Hi Rana,

Then how you will control the retro for the same.

Regards,

Sankarsan