It might be hard to get an overview on how the module works, so I made this chart that I feel pretty well illustrates the process and flow of the module in general.
When doing training I feel that this is a great point to start.
An alternative view is this top down approach with a little more detail.
Time and attendance uses jobs to that is registered in raw registrations at the time of input from the user. It creates multiple jobs for each production operation depending on the settings, a job for each project and project activity, a job for each indirect activity and absence code and absence group.
Calculating work times:
When the person doing the calculation/approval opens the profile day for control of the hours the system creates the time journal header and time journal transactions based on the raw registrations. The journal can be changed. It can also be reverted back to it’s original transactions by importing the raw registration transactions again. The system require absence to be identified at calculation.
Calculating parameters and Pay agreements:
The pay agreements are used to set the base for what pay types that will be generated.
After the work times are calculated and approved it runs through the calculation parameters where the profile types corresponding with the raw registrations generate pay agreement types based on the calculation parameter settings and pay agreements.
After calculating and approving the user will transfer the journals. This results in the lines being removed from the view of the user and pay types being locked in. These can later be exported to an external payroll system and the pay type transactions will be flagged as exported.
At the time of transfer the production orders and projects will get hours amended in the time journals posted as discrepancies in new route cards/Job Cards and Hour journals.
That should cover the basics!