This page (revision-4) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 3 KB kparrott to previous
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
UPLG
UPLG

Version management

Difference between version and

At line 2 added one line
Labor costs may be sent to the G/L system on a regular (daily, weekly, bi weekly etc.) or ‘on demand’ basis prior to the pay being calculated. Labor G/L processing (UPLG) takes place after the payroll batch has been entered into [{$applicationname}] system.
At line 3 removed 3 lines
!!Processing Information
Labor costs may be sent to the G/L system on a regular (daily, weekly, bi weekly etc.) or ‘on demand’ basis prior to the pay being calculated. Labor G/L processing (UPLG) takes place after the payroll batch has been entered into Personality system.
At line 10 changed one line
Labor G/L may take place prior to auditing a batch (set the Include Unaudited Transactions lexicon to ‘Yes’) and Labor G/L may be run in update or trial mode (set the Trial lexicon to ‘Yes’).
For testing the G/L set up and balancing, it is recommended that Labor G/L be processed for one batch at a time. Labor G/L may take place prior to auditing a batch (set the Include Unaudited Transactions lexicon to ‘Yes’) and Labor G/L may be run in update or trial mode (set the Trial lexicon to ‘Yes’).
At line 28 removed 3 lines
----
!!Report Parameters & Filters
At line 32 changed 7 lines
|GL Company Code|Mandatory, LOV Available \\General Ledger Company that the pays must be journalized for. As set up in the \\[IDGC] form. Only one G/L company may be processed at a time.
|Batch Eligible|Optional, LOV Available, <Both>\\Transactions may be processed for batches that are marked eligible, not eligible or \\both.
|Person Code|Optional, LOV Available \\You may specify one or more employees for processing.
|As Of|Mandatory, Date, LOV Available \\The date up to which the transactions are to be journalized. This date is used to pick \\up all pay headers with a pay period end date up to and including this date. Then \\the pay lines are picked up if the pay line date is up to and including this date.
|Include Unaudited \\Transactions|Optional, Toggle\\If ‘On’, all pay lines including audited and un-audited transactions will be processed.\\This should be used if you have a large volume for UPLG and time does not permit\\[UPAUDT] to run prior to UPLG.\\If ‘Off’, only audited pay line will be processed.
|Trial|Optional, Toggle\\If ‘On’, the journal entries will be created with Journal Source = ‘Trial Labor G/L’.\\This allows [RPGL] report to print for verification and UPLG may be run again.\\If ‘Off’, the journal entries will be created with Journal Source = ‘Labor G/L’ and it \\cannot be removed unless the [UPLGUNDO] process is run.
|Exception Level|Mandatory, LOV Available\\You may increase the level of exception to user or utility levels for testing purposes\\only.
|__GL Company Code__|__Mandatory, LOV Available__ \\General Ledger Company that the pays must be journalized for. As set up in the \\IDGC form. Only one G/L company may be processed at a time.
|__Batch Eligible__|__Optional, LOV Available, <Both>__ \\Transactions may be processed for batches that are marked eligible, not eligible or \\both.
|__Person Code__|__Optional, LOV Available__ \\You may specify one or more employees for processing.
|__As Of__|__Mandatory, Date, LOV Available__ \\The date up to which the transactions are to be journalized. This date is used to pick \\up all pay headers with a pay period end date up to and including this date. Then \\the pay lines are picked up if the pay line date is up to and including this date.
|__Include Unaudited \\Transactions__|__Optional, Toggle__\\If ‘On’, all pay lines including audited and un-audited transactions will be processed.\\This should be used if you have a large volume for UPLG and time does not permit\\UPAUDT to run prior to UPLG.\\If ‘Off’, only audited pay line will be processed.
|__Trial__|__Optional, Toggle__\\If ‘On’, the journal entries will be created with Journal Source = ‘Trial Labor G/L’.\\This allows RPGL report to print for verification and UPLG may be run again.\\If ‘Off’, the journal entries will be created with Journal Source = ‘Labor G/L’ and it \\cannot be removed unless the UPLGUNDO process is run.
|__Exception Level__|__Mandatory, LOV Available__\\You may increase the level of exception to user or utility levels for testing purposes\\only.
At line 41 changed 9 lines
|Entity|Optional and LOV Available \\Limits the process to the entity specified. You should select only one entity.
|Payroll|Optional and LOV Available \\The payroll code of the pays to be journalized. You should select only one payroll \\code.
|Batch Number|Optional, Multiple, and LOV Available\\Batch numbers for the specified entity and payroll are displayed on this list. You \\may select multiple batches.
|Person Code|Optional, LOV Available \\You may specify one or more employees for processing.
----
![Notes|Edit:Internal.UPLG]
[{InsertPage page='Internal.UPLG' default='Click to create a new notes page'}]
|__Entity__|__Optional and LOV Available__ \\Limits the process to the entity specified. You should select only one entity.
|__Payroll__|__Optional and LOV Available__ \\The payroll code of the pays to be journalized. You should select only one payroll \\code.
|__Batch Number__|__Optional, Multiple, and LOV Available__\\Batch numbers for the specified entity and payroll are displayed on this list. You \\may select multiple batches.
|__Person Code__|__Optional, LOV Available__ \\You may specify one or more employees for processing.
This page (revision-4) was last changed on 26-Nov-2021 10:22 by kparrottTop