Skip to main content
Question

GI - Employees Clocked into jobs


rcreasy
Varsity I
Forum|alt.badge.img

I am trying to create a GI that shows all Employees who have clocked into jobs, but have not yet clocked out. 

I have 2 GIs set up that combined seems to get what I want. I am getting all entries where StartTime is NOT empty and where EndTime IS empty. I am doing this on the AMClockTran and AMClock Item tables.

Is there a way to get all employees that are currently clocked in on one report?

What is the difference in these 2 tables?

6 replies

Laura02
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3135 replies
  • August 23, 2024

Hello,

It’s possible to create a single GI that shows employees that have clocked in but not clocked out. This example uses two tables, AMProdOper and AMClockItem in a manufacturing tenant.

  • Group by AmClockItem.EmployeeID.
  • Sort by AMClockItem.Starttime.
  • Use the following Relations & Conditions:

Laura


hkabiri
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Support Team
  • 195 replies
  • August 23, 2024

@rcreasy These two tables are storing data which you see on Clock Entry Screen.

AMClockItem holds the Header information which basically the key is the EmployeeID for this table and Lower table stores in AMClockTran Table as you can see below:

 


rcreasy
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • 60 replies
  • August 23, 2024

@hkabiri Thank You! But, I still don’t understand why my 2 GIs give different results? It seems the AMClockTran table would have all employees that have a start time and no end time.

 


rcreasy
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • 60 replies
  • August 23, 2024

@Laura02 I don’t need the grouping, we have situations where an employee can be clocked into multiple jobs. We need to see all jobs that have employees currently logged in.

That said, your conditions is exactly what I have. My GI misses some employees for some reason. using AMClockTran gets the missing employees. But, it does not include the employees displayed by the GI that uses AMClockItem


Forum|alt.badge.img+1
  • Jr Varsity II
  • 37 replies
  • August 23, 2024

@rcreasy The GI’s are likely giving different results because I believe when you clock out, the AMClockItem (Header) clears both Start and End Date fields, but the AMClockTran (Detail) should always have a start date populated because it’s created when you clock in, but it really depends on how you have the 2 GI’s setup. I’d need a bit more information on both and what results you get vs. expected to help more.

 

There’s also a field on the AMClockItem DAC named “IsClockedIn” which you can use to filter by currently clocked in users. That flag is true only when the start time is populated and the end time is blank, otherwise it’s false, so it’s essentially doing the same thing as checking start/end times. It’s not a persisted field, so you may not be able to do as much as persisted fields in the GI.


rcreasy
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • 60 replies
  • August 23, 2024

@mbridges00 The conditional logic is pretty much like the example above from @Laura02 
The PDnum below is just an optional search criteria on the PD Number

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings