UNDO PAYROLL G/L#

Processing Information#


Report Parameters & Filters#

Report Parameters
G/L CompanyMandatory, LOV Available
This field allows you to select the G/L company associated with this report.
EntityMandatory, LOV Available
This field allows you to select the entity associated with this report.
Undo OptionOptional, Undo Option lexicon available
This field allows you to select an G/L Undo option.
From/To PeriodMandatory, Date, LOV Available
Only information that falls within these period dates will be processed.
From/To Fiscal PeriodMandatory, Date, LOV Available
Only information that falls within these fiscal period dates will be processed.
From/To Pay NumberOptional, Text
Only records between these two pay numbers will be included in the report.
Remove Labor G/LOptional, Yes or No lexicon available
If <Yes>, labor G/L will be removed.
Retain Original G/LOptional, Yes or No lexicon available
If <Yes>, original G/L will be retained.
Remove Prev RetainOptional, Yes or No lexicon available
If <Yes>, previous G/L will be removed.
TrialOptional, Yes or No lexicon available
You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>.
Exception LevelOptional, Exception Level lexicon available
This field defines the exception level (report messages) required.
User Comments Optional, Text
This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other.

Report Filters
PersonOptional, Multiple selection and LOV available
This field limits the report to the persons specified.
PayrollOptional, Multiple selection and LOV available
This field limits the report to the payrolls specified.
Pay RunOptional, Multiple selection and LOV available
This field limits the report to the pay runs specified.
Undo Execution IDOptional, Multiple selection and LOV available
This field limits the report to the undo execution ID's specified.

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 Periodoptional, specify a beginning Pay Period to qualify the Pay Headers
To Pay Periodoptional, 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:

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

- 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

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

|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


Notes#

Click to create a new discussion page

}]