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

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

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
12 26-Nov-2021 10:22 4 KB tchau to previous
11 26-Nov-2021 10:22 4 KB jmyers to previous | to last
10 26-Nov-2021 10:22 5 KB jmyers to previous | to last
9 26-Nov-2021 10:22 4 KB jmyers to previous | to last
8 26-Nov-2021 10:22 4 KB jmyers to previous | to last
7 26-Nov-2021 10:22 6 KB jmyers to previous | to last
6 26-Nov-2021 10:22 6 KB jmyers to previous | to last
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB JMyers to previous | to last
2 26-Nov-2021 10:22 238 bytes RForbes to previous | to last
1 26-Nov-2021 10:22 46 bytes UnknownAuthor to last

Page References

Incoming links Outgoing links
UPGLUNDO
UPGLUNDO

Version management

Difference between version and

At line 1 removed 2 lines
[{TableOfContents }]
At line 12 changed 7 lines
|Undo Option|Mandatory, [Undo Option|X_GL_UNDO_OPTION] lexicon available\\This field allows you to select an G/L Undo option.
|From/To Period|Mandatory, Date, LOV Available\\Only pay headers that fall within these period dates will be processed.
|From/To Fiscal Period|Mandatory, Date, LOV Available\\Only pay headers that fall within these fiscal period dates will be processed.
|From/To Pay Number|Optional, Text\\Only pay headers that fall between these two pay numbers will be included in the report.
|Remove Labor G/L|Optional, [Yes or No|X_YES_NO] lexicon available\\If <Yes>, Labor GL journal entries are removed.\\If <No>, Labor GL journal entries are not removed.\\ \\If Labor GL journal entries exist for a pay header after the UPLG run, the user should not remove these entries for UPGL run.
|Retain Original G/L|Optional, [Yes or No|X_YES_NO] lexicon available\\You may need to retain the original GL to reverse out from the General Ledger system when re-sending the re-journalized journal entries\\ \\If <No>, original GL journal entries will not be retained, just removed\\If <Yes>, original GL journal entries will be retained\\ \\If the field is set to <Yes> when a journal entry is removed, the original journal entry will be copied and negated. The journal source is changed as follows\\01 – Labor G/L changed to: 71 - Orig Labor G/L\\02 – Payroll G/L changed to: 72 - Orig Payroll G/L\\03 – Accrual G/L changed to: 73 - Orig Accrual G/L\\06 – Accrual Rev G/L changed to: 76 - Orig Accrual Rev G/L\\ \\The above original journal entries are for auditing purpose only and will not be re-sent in UPGLF.\\ \\The amount will then be negated and will be re-send in UPGLF\\01 – Labor G/L changed to: 81 - Negate Labor G/L\\02 – Payroll G/L changed to: 82 - Negate Payroll G/L\\03 – Accrual G/L changed to: 83 - Negate Accrual G/L\\06 – Accrual Rev G/L changed to: 86 - Negate Accrual Rev G/L
|Remove Prev Retain|Optional, [Yes or No|X_YES_NO] lexicon available\\If <No>, Prev Retain GL journal entries are not removed.\\If <Yes>, Prev Retain GL journal entries are removed\\ \\After one UPGLUNDO is run, the original GL entries may be retained in P2K system. At that point UPGL is run again and errors are discovered. Next, the UPGLUNDO will be run gain and at that point you may select to remove the previously retain original GL in subsequent UPGLUNDO run.\\ \\Usually you will not remove original retain GL entries because these retain entries may already be recorded in the General Ledger system that need to be reverse out from the negated entries.
|Undo Option|Optional, [Undo Option|X_GL_UNDO_OPTION] lexicon available\\This field allows you to select an G/L Undo option.
|From/To Period|Mandatory, Date, LOV Available\\Only information that falls within these period dates will be processed.
|From/To Fiscal Period|Mandatory, Date, LOV Available\\Only information that falls within these fiscal period dates will be processed.
|From/To Pay Number|Optional, Text\\Only records between these two pay numbers will be included in the report.
|Remove Labor G/L|Optional, [Yes or No|X_YES_NO] lexicon available\\If <Yes>, labor G/L will be removed.
|Retain Original G/L|Optional, [Yes or No|X_YES_NO] lexicon available\\If <Yes>, original G/L will be retained.
|Remove Prev Retain|Optional, [Yes or No|X_YES_NO] lexicon available\\If <Yes>, previous G/L will be removed.
At line 20 changed one line
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.\\ \\Typically ‘Exception only’ should be run, except for debugging\\ \\If Level ‘1 - User Trace’, UPGLUNDO displays each Employee header\\If Level ‘9 - Utility Trace’, UPGLUNDO displays all trace messages
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.
At line 25 changed one line
|Payroll|Optional, Multiple selection and LOV available\\This field limits the report to the payrolls specified.\\Payroll is required if Pay Run Number is specified
|Payroll|Optional, Multiple selection and LOV available\\This field limits the report to the payrolls specified.
At line 29 removed one line
!!UPGLUNDO – Processing
At line 31 removed one line
*When UPGLUNDO is run, the ‘Undo Option’ indicates how to change the Payrun and Pay Headers Stage, the Pay Headers Journalized and Journalized Fund Toggle will be turn OFF
At line 33 changed one line
*After UPGLUNDO, user may view the Payrun on IPVP screen, the Payrun Stage and Pay Header Stage are updated
|Entity|- optional, if used, the user may enter one Entity code only\\Entity is required if Pay Run Number is specified
|Payroll|- optional, if used, the user may enter one Payroll code\\- Payroll is required if Pay Run Number is specified
|Pay Run Number|- optional, select list of Pay Run Numbers for the Entity/Payroll specified
|Person Code|- optional, multiple Person codes are allowed
|Pay Number|- optional, multiple Pay Numbers of Pay Headers are allowed
|Undo Execution ID|- optional, multiple Execution ID of UPGL or UPGLUNDO are allowed\\- the user may undo by UPGL run or undo the run from previous UPGLUNDO
|GL Company Code|- mandatory, the user must enter one ‘GL Company Code’
|Undo Option|- mandatory, must enter an undo option from lexicon X_GL_UNDO_OPTION:\\
01 - Undo for UPGL Re-run\\- this option resets the Pay Run Stage and Pay Header Stage to the stage prior to UPGL\\- use for undoing and re-doing the GL until all GLs are correct\\
02 - Undo for Re-journalize\\- this option changes the Pay Run Stage and Pay Header Stage to ‘To be re-journalize’ for user to send only the re-journalize entries to correct the General Ledger system\\
03 - Undo for UPGLF only\\- if user satisfies with the UPGL and RPGL results, however the UPGLF has been run in Update mode and need to re-run UPGLF again to generate the interface file only, then this option removes the IPPH screen Journalized tab ‘Interface mex id’ and the ‘Costed by mex id’ if exists\\- after UPGLUNDO with this option, the user can re-run UPGLF
|From Pay Period|optional, specify a beginning Pay Period to qualify the Pay Headers
|To Pay Period|optional, specify an up to Pay Period to qualify the Pay Headers
|From Fiscal Period|- optional, specify a beginning Fiscal Period to qualify the Pay Headers
|To Fiscal Period|- optional, specify an up to Fiscal Period to qualify the Pay Headers
|From Pay Number|- optional, specify a beginning Pay Number to qualify the Pay Headers
|To Pay Number To|- optional, specify an up to Pay Number to qualify the Pay Headers\\- can be used with Person code selection to undo certain pay number ranges
|Remove Labor GL|- optional, if Labor GL journal entries exist for a Pay Header after the UPLG run, the user should not remove these entries for UPGL run\\
- if toggle is OFF, Labor GL journal entries are not removed\\
- if toggle is ON, Labor GL journal entries are removed
|Retain Original GL|- optional, the user may need to retain the original GL to reverse out from the General Ledger system when re-sending the re-journalized journal entries\\
- if toggle is OFF, original GL journal entries will not be retained, just removed\\
- if toggle is ON, original GL journal entries will be retained\\
- if toggle is ON when a journal entry is removed, the original Journal entry will be copied and negated, Journal source is changed as follows:
At line 35 changed one line
*On IPPH screen Journalized tab, the ‘Original’ and ‘Negated’ journal entries are displayed:
01 – Labor G/L changed to: 71 - Orig Labor G/L
02 – Payroll G/L changed to: 72 - Orig Payroll G/L
03 – Accrual G/L changed to: 73 - Orig Accrual G/L
06 – Accrual Rev G/L changed to: 76 - Orig Accrual Rev G/L
- the above Original Journal entries are for auditing purpose only and will not be re-send in UPGLF
At line 37 changed one line
*After UPGLUNDO, UPGL will re-journalize Payrun and Pay Headers with Stage = ‘85-To be re-journalized’; UPGF (Journalize Fund Actual) will process Payrun and Pay Headers with Journalized Fund Toggle that are set to OFF
- then the amount will be negated and will be re-send in UPGLF:
01 – Labor G/L changed to: 81 - Negate Labor G/L
02 – Payroll G/L changed to: 82 - Negate Payroll G/L
03 – Accrual G/L changed to: 83 - Negate Accrual G/L
06 – Accrual Rev G/L changed to: 86 - Negate Accrual Rev G/L
At line 66 added 4 lines
Remove Prev Retain GL:- optional, after one UPGLUNDO is run, the original GL entries may be retained in P2K system, then user runs UPGL again and errors are discovered, then user will run UPGLUNDO again, the user may select to remove the previously retain original GL in subsequent UPGLUNDO run
- usually the user will not remove original retain GL entries because these retain entries may already be recorded in the General Ledger system that need to be reverse out from the negated entries
- if toggle is OFF, Prev Retain GL journal entries are not removed
- if toggle is ON, Prev Retain GL journal entries are removed
At line 71 added 4 lines
|Trial: | - in Trial run, database activities will not be updated, this is used for testing
|Exception Level:| - user should run with ‘Exception only’ except for debugging
- if Level ‘1 - User Trace’, UPGLUNDO displays each Employee header
- if Level ‘9 - Utility Trace’, UPGLUNDO displays all trace messages
At line 79 added 11 lines
At line 46 changed one line
[{InsertPage page='Internal.UPGLUNDO' default='Click to create a new notes page'}]
[{InsertPage page='Internal.UPGLUNDO' default='Click to create a new discussion page'}]
}]
This page (revision-12) was last changed on 26-Nov-2021 10:22 by tchauTop