Time registration workers are grouped to calculation groups. These should (in my opinion) be grouped as low as forman or team leder level. Offcause every user has to have this (also formen and team leaders), so I normally illustrate this as a hierarchy even though it is a flat table.
The calculation action is:
- Define the work profile
- Approve switch codes (for instance Overtime)
- Define missing or redefine absence reasons
You can configure the group with a password which the user is prompted at opening the form with a specific group if you need to restrict access.
Start the Calculation form by going to Time and Attendance > Review and approve > Calculate.
You can do this week by week for a single user or day by day for the entire calculation group. Select the week or the day when you open. I like doing this on a day by day for entire group. Probably since this is the way it has been done before and old habits die hard. Click the day field to go into the day mode or keep the week setting to go to week mode.
Once the form is opened AX looks through all the the raw registrations and create these time journals.
You can look through the lines and do amendments to them if you want. You can go back to the original raw registrations data. If all fails. Delete the journal header. Go to the next day and go back.
You can run calculation for everyone in the list by clicking “Calculate” from the menu. The menu item changes to “Undo Calculation” when the line is calculated.
If you run the calculation for everyone (by clicking “Update > Calculate all”) you can click the “Display errors” in the main menu to only display the records that didn’t go through.
If the line goes in to an error you can view the error message by clicking the error pane in the header.
If absence is missing you can go to the absence tab and define the absence. You have to go there. You can not to this direcly on the line below.
Another common error I’ve run in to is if you’ve edited the lines you might have chronological issues. Especially if you have transactions going on till the next day. Profile day has to be the same day as you calculate and not the next day even if the job starts the next day. Check the times and dates on the lines to get the right. You can not be on different types of jobs (Indirect, Project, Production) at the same time.
When the calculation is completed you can go and check the times that are calculated.
You can change the profile for any worker before you calculate and you can even override the profile for a unique day if there is a “once-in-a-blue-moon” event.
By clicking Override and Profile you can change the profile for that particular user for that day.
You can load the existing profile as a template by clicking “Retrieve profile” and start changing that one or create each line from scratch. You create this the same way you would a standard profile.
After the override is done the line will have the “Override profile” flag activated.
Remove the ovverride by clicking Delete override in the Profile override window.
You can allocate the overtime for each of the jobs that has been worked on durring the day. Select the percentage of overtime hours to each job. This can be automatically allocated by the overtime allocations principle that is done in the general parameter settings under costing.
This is great, because it might not be the final job of the day that rightfully should carry the overtime cost. It might be that you had issues with the first job of the day and required to complete your work load for that day. Then the unfortunate last job had to be done on overtime, but the first job was the one that really should carry the cost.
Switch codes can be reviewed, changed and/or approved by the person doing the calculation.
You can also do clock out workers from the calculation form. You can do a selection of the users that are not yet clocked out and do a clock out for each user.
The clock out time that the user get is the one sat in the profile, even if the clock out happen at a earlier time.
As you can do amendments on the lines you might do errors or for some other reason want to go back to what was generated based on the terminal registrations. Trigging this will delete amendments to the lines and pull the terminal registrations again.
On the action pane menu on the lines of production jobs you can now also quickly access the quantity feedbacks given by the operator and even change these. Be aware of the consequences of changing them though… Well at least they are available.