Capturing time spent on a ticket
Start and stop the timer to capture the time spent on a ticket.
There are various GL account rules after you start the timer.
Displayed fields | GL Account (GLACCOUNT) GL Account (GLACCOUNT) |
---|
The following table describes which GL account rules apply when the GL Control Account field is not shown on the ticket.
If asset or location... | and the site and asset site are... | use the GL account... |
---|---|---|
not on the ticket | equal or not equal | from the Labor record of the user running the application as the LABTRANS (GL) default. If the GL account does not exist, the global ticket GL account is used as the LABTRANS (general ledger) default. |
on ticket | not equal | the asset or location generates the LABTRANS (general ledger) record. If asset or location do not have an associated GL account, the GL account from the labor record of the user running the application is used as the LABTRANS (general ledger) default. If the labor record does not have a valid GL account, the global ticket GL account is used as the LABTRANS (general ledger) default. |
both on ticket | equal | as determined by existing asset or location merging rules. If asset and location do not have associated GL accounts, the GL account from the labor record of the user running the application is used as the LABTRANS (general ledger) default. If the labor record does not have a valid GL account, the global ticket GL account is used as the LABTRANS (general ledger) default. |