Skip to Content

Issue with multiple P01 entries in TEVEN table

Feb 02 at 12:57 PM


avatar image

Dear experts,

I have browsed many SCN blogs however was not able to find solution for my requirement hence raising this query.

Positive Time management has been implemented at my current client by earlier consultant who has integrated SAP with 3rd party system through a custom program. In this program if there is a Clock In it is getting recorded as "P01 - Clock in/Clock out" and if there is a Clock out entry it is recorded as "P01- Clock in/Clock out" that means everyday if any Employee has Punched In and Punched out once this program is working fine.

However, now we are getting as issue if there are multiple Punch in/Punch out by employee, so in that case if there are 3 entries of "P01- Clock in/Clock out" for a day then I get an error in PCR "TE30"that Punch In/Punch out missing.

I have already refer the blog in which Mr. Vivek has designed an excellent method however that becomes applicable only if my program passes P10 & P20.

So want to check below points:

a) Shall I inform Abaper to change the code in program and accept 1st entry as P10 and Last entry as P20, then in this case what will be the implications as Positive Time management went live on 1st November 2017.

b) Is there a possibility to achieve this scenario through PCR/Schema.

c) Any other solution that an suffice this requirement.

Appreciate your quick guidance on the same.


Ritesh Shetty

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Brendan Gibbons Feb 02 at 05:54 PM


In terms of dealing with missing swipes.

My response would be, that this is 'Exceptional' behavior and needs to be handled as such.

If an employee 'forgets' to clock in, or forgets to clock out, or clock out for a break and forget to clock back in etc etc then these are all scenarios that need to raise an exception. These exceptions need to be reviewed by a time supervisor and the appropriate action taken to rectify.

You can thru configuration manage to a limited degree how the system deals with swipes, for example get the system to ignore swipes within a time window to cater for the scenario where an employee not sure if they have swiped correctly re swipe in or out multiple times.

I would be very cautious about trying to programmatically (either via ABAP or PCR) determine which are the correct ins and outs and eliminate the spurious ones. An approach that would be very likely to end in tears!

In summary I would see this as a process issue and not a technical one.

Employees need to understand when they are expected to swipe in and out and work schedules (with breaks if necessary) need to reflect the reality.



Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Brendan,

Thank you for the response! I will find it difficult to streamline the process because, Employees have started using SAP ESS Clock In Clock Out corrections which means as per the HR policy if work timings are 9.30 AM to 5.30 PM and if any Employee comes late and punch in at 10 AM then he is allowed to create a new entry in SAP ESS Clock In Clock Out Corrections as 9.20 AM and can take his/her manager's approval.

Thus, if an EMployee creates a new entry in SAP ESS then again there are 3 entries in TEVEN Table (2 Clock In and 1 Clock out). My challenge is I cant even play with SAP ESS CLock In/Out corrections so that Employees can only edit the recorded entries. If I put such a restriction then if there is a missing punch then Employee will not be able to create the same:(

I am stuck and cant find out a solution.


Ritesh Shetty