We’re looking to better understand the functionality behind approving timecards as it relates to updating raw registrations/job cards/production orders.
In short, our testing shows that using:
- the ‘missing clock out’ button on the approve timecard page, you enter the specific time of the missed clock out and it will create another job card on the production order with lines that net to zero, so no correction to the previous job card and this new job card is unposted.
- the ‘clock out workers’ on the approve timecard page, you select a group or individual worker and it looks to their time profile to create the missing clock out entry. Behind the scenes this creates the new job card that actually corrects the time on the production order.
- manually adding a line to the approve timecard page does not update anything else in the system, just the timecard - not ideal
We need to understand the intended use of both buttons - missing clock out and clock out workers.
We also want to understand why missing clock out would not update the registrations/job cards like the clock out workers. Where missing clock out allows you to enter a specific time, which could be different from the worker’s time profile, the corrections should flow through just like using the clock out workers.
We look forward to hearing about your experiences.
Thank you in advance!
Tracey
@Andrew_Lencsak
1 Like
Hi Tracey!
Can you confirm if the new job cards that are being created are not being created until AFTER the Transfer of registrations from Time and Attendance? Typically, whether we have workers clocking themselves out, are using “Missing clock out,” or “Clock out workers” the new job cards with offsets or corrections do not get created and linked back to the production orders until after the time is Calculated, Approved, and Transferred.
Time and attendance registration overview - Supply Chain Management | Dynamics 365 | Microsoft Learn
You should never manually add a line to an approved timecard as best practice. Manually editing timecards is usually only needed if someone’s timesheet became out of sequence, corrupt, or had missing entries that must be entered manually, not for clock outs. Ideally, any manual changes, you unapproved, and uncalculated, and then make changes, recalculate, and reapprove. Otherwise, the difference you stated matches what I have seen where “missing clock out” would produce an unposted journal after transfers, and “clock out” would produce a posted journal. However, whether the journals correct the production order should be based on if the clock out entry that was produced also stopped their time on the job. If the user had stopped or logged out of the job and just had not clocked out for the day, the entry should not correct any time on the production order.
1 Like
Hi All,
Apologies for the delay in responding.
@Andrew_Lencsak Thank you for your response and assisting in the troubleshooting of this issue!! To answer your question, the new job cards are created after registrations are transferred. We’ve found that many times users were forgetting to clock out for the day, which also meant they had not clocked out of the job they were logged into. So, when the timecard was updated to account for the clock out for the day, the ‘process’ line for the job would also get updated with the clock out. Then when the timecard was calculated, approved and transferred, the ‘correction’ job card would be created to the production order. It’s the ‘correction’ job card that was not updating correctly as mentioned in my initial post.
We had a support ticket open with Microsoft and after some challenges we finally made headway. The ticket was taken over by a very experienced and very knowledgeable senior support escalation engineer who was able to work through this with us. He found that there was in fact a bug and the fix is coming in v41. We do plan to test this after v41 is released and our UAT/DEV box is updated to v41. In the end, it was great working with this senior support escalation engineer and we look forward to v41.
Thanks!
1 Like
Hi Tracey, did y’all update to v41 yet? Curious to hear if this was resolved with the bug fix.
Thanks
Drew