I need materail for Time Evaluation (positive time managment) to fix many problems in PT60?

[former_member223911]

Dear Experts,

i have many problems in the time evalution run from PT60 and i couldn't understant the reason also i have problems that related to the retroactive records from previous months in the attaendance and this affect the payroll for the employees with additions or deducations (However it comes from old months with no reason)

i couldn't find any valuable and easy material over the internet, and the academy material doesn't match my requiremnt i need to know the behioviour of the time schema and the pcr also the lateness and overtime calculations over this schema

Appreciate if you support me

[BGibbons · Accepted solution]

Hi,

Just some thoughts

It may or may not be the right approach but I always try to minimize the number of schemas in use.

For instance if you have a business unit that has a number of different locations with different rules, you could have a separate sub schema for each location. You would have a main schema which would include a 'COPY' statement for your sub schemas with each one controlled by an "IF" and "ENDIF" and associated PCR.

Then you would only ever need to run the main schema and depending on the location of the employee the correct sub schema would be processed.

However my advice is that when writing a PCR that contains rules that may not apply to all employees you should always try ensure that the logic will only fire for the appropriate employees.

For instance if you have a PCR that has logic for Flex employees the PCR should be constructed such that it can fire for all employees but non flex employees get ignored.

One way this can be done is to have a separate personnel sub area for flex and non flex employees. Then in your PCR you limit the logic by personnel sub area (utilizing operator OUTWPPLTSC ). Depending on your situation there are a number of different ways of achieving this.

Also if you have a set of PCRs that only apply to a specific subset of your employees and they are not scattered throughout your schema you could book end them with an IF ENDIF so they only get processed for the correct set of employees.

bg

[BGibbons]

Hi,

I think you need to be more specific in query and elaborate on one specific problem.

However

If your PT60 is retroing and you do not know why then you can check the following.

Usually you can stop a retro by setting your dates on IT0003, but sometimes this does not work.

If IT0003 dates are having no effect then you can check

Cluster B2 (transaction PT_CLSTB2) Check dates onTable BEZUG

Cluster B1 (transaction PT_CLSTB1) Check table NT2. Historic Time Events if there are data inconsistencies will cause retroing.

If all else fails you can delete results from the clusters and recreate with PT60 if required.

bg

[former_member193210]

As implied by Brendan, executing an Ad-Hoc Query on IT0003 before executing Time Evaluation can be very helpful to identify the employees for whom Time Evaluation will be done retroactively.

Note that all Time Evaluation Results that existed previously will be overwritten as a Day is being re-evaluated, so there is no easy way to compare the "New TE Results" with the "Old TE Results". If you anticipate problems with retroactive attendances/absences for an employee, you could look at the results that exist "now", then run TE for that employee, and then re-examine the new results for that Day.

[former_member223911]

Dear rmi.corriveau and brendan.gibbons2,

Thank you sou much for your answers,

what i mean is i have many issues in the time evulation schema so i need to understand it carefully to fix any issues in general

for example we have 2 different Time schema ( 1 for all the WS, and 1 for only Flexaible WS) so the users run the employees seperatly once for all the employees expt those, and another run for who assigned on Flex WS with the second schema
and i'm not sure if i can merge 2 shemas in one schema or not and how if it's poosible, however they are same behaiviour and calculations except some differemt PCRs in the second one (Flex) not maintained in the first scehma

[former_member193210]

We have 11 different School Boards, and each one has it's own TE Schema. Yet, they share some of their Sub-schemas and PCRs. Note that sometimes, even those "shared" PCRs include decisions that make processing different based on WPBP or some other element.

Your first step should be to find the source of the problems, and to fix it.

Then, you could compare your TE Schemas, identify what Operation would enable you to identify if the employee being processed has a "Normal" WS or a "Flex" WS, and see if you could merge 2 PCRs that have the same purpose into a single PCR. I've never worked with employees on a flexible schedule, but it should be possible to integrate the 2 schemas into one and yet, some sub-shemas could remain distinct (Function IF associated to a PCR to identify the employees on Flex schedule, and if the return statement is TRUE, sub-schema ZXXX is called, ELSE sub-schema ZYYY is called).

If you proceed with the idea of merging the 2 schemas into 1, go at it slowly, with a lot of testing (including retroactive TE processing).