Pair Formation Issue in Positive Time Management with Time Events

[vianshu]

Hi All,

We are facing an issue with pair formation in positive time management with time events. Let me explain the issue in detail.

The planned working times are from 7 am to 3 pm on working days (Mon - Fri).

On 02-Jan-14, the employee clocks in at 7 am. He forgets to clock out while leaving office on 02-Jan-14. The time evaluation runs at 2 am on 03-Jan-14 and gives an error that the clock out on 02-Jan-14 is missing.

On 03-Jan-14, the employee comes to office but forgets to clock in on 03-Jan-14. At the time of leaving the office, he clocks out at 3 pm on 03-Jan-14.

The time evaluation runs at 2 am on 04-Jan-14.

The system is currently assigning the clock out 3 pm on 03-Jan-14 to 02-Jan-14. Hence, it creates a time pair for 02-Jan-14 with total no. of hours as 32 hours and start time as 7.0000 and to time as 39.0000 . It also points out that the employee is not at work on 03-Jan-14. This is not correct processing in SAP.

I checked in help.sap.com and I found that this is not the standard behavior. Please refer the below link:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/8a/9852b546c411d189470000e829fbbd/content.htm?frame...

The above standard behavior says that the time evaluation should point out that there is a missing clock out on 02-Jan-14 and there is a missing clock in on 03-Jan-14.

I raised an oss message with SAP and the first level support consultant said that my configuration in Table V_T705B for A07 is incorrect. I had maintained 400 for A07.

I cleared the configuration of A07 to blank and the issue still existed. The SAP consultant then came back after few days and said that the documentation in help.sap.com is incorrect and she would get it changed. I found this rather strange.

I haven't accepted her solution and have escalated it to SAP.

If the clock out of 03-Jan-14 is assigned to 02-Jan-14 and the total no. of hours appear as 32 in Table TIP for 02-Jan-14, then it also means that the DWS of 02-Jan-14 is not being taken into account at all.

Also, I am surprised why the consultant advised that the documentation in help.sap.com is incorrect. If that documentation is incorrect, it means that SAP is giving preference in pair formation to a scenario whose possibility in real time is less than 1%. And the scenario for which the possibility is around 99% is being ignored.

Does anyone have any idea about the solution to this issue?

Thanks and regards,

Vivek Barnwal

[former_member1006256]

Hi Vivek,

this is the same issue, I am facing right now. Please suggest the solution to the problem

[vianshu · Accepted solution]

For the benefit of everyone, SAP Development Support, Germany has advised that the information available in help.sap.com Previous Day Assignment in Pair Formation - Time Evaluation - SAP Library is incorrect.

The time event 15:00 on 03-Jan will get assigned to 02-Jan if the clock out on 02-Jan is missing. And it will not take the DWS into consideration.

I was really surprised and unhappy with this response. Because on how many occasions will an employee work continuously for more than 24 hours. I believe it will be less than 1% possibility. And SAP is giving preference to less than 1% scenario over a scenario which can occur in 99% times.

Regards,

Vivek

[Former Member · Accepted solution]

Thanks for the info.

Are they going to correct the documentation at least?

[vianshu · Accepted solution]

They said that they have initiated the process to correct the documentation.

[Former Member · Accepted solution]

Hi Vivek,

We are facing the same issue.

Were you able to solve it by any workaround?

Regards,

Shai

[vianshu · Accepted solution]

Hi,

Actually, my client requirement didn't need this anymore. However, if you wish to implement a solution, you will have to build a custom solution.

Thanks and regards,
Vivek Barnwal

[Former Member · Accepted solution]

Any tip?

Can you somehow influence the pair formation (even in code) or must you ignore it in time evaluation?

Regards,

Shai

[vianshu · Accepted solution]

You can influence pair formation at the code level. You will have to introduce your custom code. Initially, I was also thinking of doing the same thing. But my customer's requirements changed and hence, it isn't required anymore.

Regards,

Vivek

[Former Member · Accepted solution]

Last question:

Is there any user-exit/BAdI or only modification option?

Many thanks,

Shai

[vianshu · Accepted solution]

My ABAPer told me that there are places in RPTIME00 where you can do implicit enhancements.

Thanks and regards,

Vivek

[Former Member · Accepted solution]

This manual execution, may be treated differently?

I checked for that pairing, if I change to the + symbol, function correctly.

Thanks and regards,

[vianshu · Accepted solution]

If you use manual assignment, it will always override the automatic assignment done by system.

Hence, you can control manually whether to assign the time event to current day or prev day.

Thanks and regards,

Vivek Barnwal

[Former Member · Accepted solution]

Yes....

I thought so .... but I thought I could "tune" the system!

But....

thanks for all! 😃

[vianshu · Accepted solution]

Hi Paula,

Since you are working in time management, please refer the below link which has other time management documents.

I hope these documents will be helpful for you.

Thanks and regards,

Vivek Barnwal

[former_member1006256]

Hi Vivek,

I am facing the same issue.

Whenever there are only punch-in and no punch-out, then system is assigning next day punch-in and punch -out to previous day, and showing absence on that day.

please help me in solving the issue.

[Former Member]

Thanks for sharing this info.

[Former Member]

how is the time event recorded on IT2011 for Jan 3rd? What is the day assignment for this time event? Is the clock in and clock out in this case identical to EEs WSR start/end time. Please try function P2011 with parameter "ALL".

[vianshu]

The time events will flow in from time recording system.

The day assignment is initially blank and the time evaluation program then assigns the day assignment after time evaluation run. Yes, the clock in and clock out are idential with EEs WSR start/end time but that should have no bearing on why the system is behaving like this. If we change the timings to make them non-identical to EEs WSR start/end time, the issue still exists.

Function P2011 with parameter ALL is not going to work.  As per SAP, ALL is used for below:

"If there are pairs on the day with an identical clock-in and clock-out time, they are only entered in table TIP if Par1 has the value "ALL"."

This is not my scenario. I don't have identical clock in and clock out time.

Regards,

Vivek