Hello - For those who run the LP199 in Production, how often do you do it?
What would be a sample date range?
Thank you,
Cindy Minter
I would like to know myself. This is the first time I even heard of this report. I have some records dated back to 2009.
We looked into it but it would erase data we want to keep, so it is not done.
We run the LP199 every month. It is the last job of our payroll process. Our date range for May EOM was 4/1/2020 - 4/30/2020.
When we went live on V10 this February, we noticed that our LP140 job was taking a much longer time to run for one of our companies. We opened a ticket with support and they suggested we run the LP199. First we ran it in report mode only with the date range wide open so that we could see how many unprocessed records we had. Ours went back to 2009. We then ran it in update mode, first with a date range of 1/1/2009 - 12/31/2014 and then with a date range of 1/1/2015 - 12/31/2019 because we weren't sure how long it would take to run. It actually ran pretty quickly for the company in question which had over 700 pages of unprocessed records. Once we ran it in update mode through 12/31/2019, we only had 14 pages. Our LP140 runs very quickly now. We plan on running it once a year with our year end process just to keep things cleaned up. It really depends on how many records you have how often you might need to run it. We have about 1200 employees so if you have a much larger group, you may want to run it more often.
What does it impact?
Thank you all for your answers. So some do it monthly, some yearly, and some not at all! I will take this information to our payroll manager to see how they want to proceed.
Thank you!
Cindy
Carmen -
The following is KB article #1206045 which should answer your question:
How is the new Absence Management program, Close Unprocessed Service Records (LP199), intended to be used?
This new program has been provided for scenarios where unprocessed (open) service records are accumulating in the Absence Management (LP) screen for Employee Service Entry (LP53.1).
Background:
If an employee is not enrolled in any LP plans, then the standard cycle processing programs Employee Absence Plan Calculation (LP140) and Absence Plan Close (LP197) will not process and close out service records. The records remain in entry status in Employee Service Entry (LP53.1) instead of being moved to history in Employee Event History Update (LP54.1). There are also batch update and reporting performance impacts when a large volume of unprocessed records are accumulated.
The intent of this program is to process these records. This program will be run by the user outside of the LP processing cycle. The frequency will be determined by the user; either every processing cycle or on a less frequent basis such as monthly or annually. How often it is run will depend on how these records are interfering with user interactions and/or reporting needs.
Note: having unprocessed records in LP53.1 does NOT interfere with the functionality of the LP cycle programs or reports, so this is an optional program.
Field Help Text for LP199
Company
Select the Company to process.
Processing Group
Select the Processing Group if you want to process by this option. Cannot select Process Level or Employee Group if Processing Group is selected.
Process Level
Select the Process Level if you want to process by this option. Cannot select Processing Group or Employee Group if Process Level is selected
Employee Group
Select the Employee Group if you want to process by this option. Cannot select Processing Group or Process Level if Employee Group is selected
Record Dates (From/To)
Select a range of dates to include for processing. If date range is selected, cannot select Object IDs.
Object IDs (From/To)
Select a range of record Object IDs to include for processing. If object IDs are selected, cannot select a date range.
Include
Select whether or not you want to include or exclude records with service codes in a specific Service Class. Leave this field blank to select all service codes for processing.
I=Include
E=Exclude
Service Class
Select a Service Class to be included or excluded in processing.
Select whether or not you want to include or exclude records with reason codes in a specific Reason Class. Leave this field blank to select all reason codes for processing.
Reason Class
Select a Reason Class to be included or excluded in processing.
Update Option
Select whether or not you want to update the selected service transactions.
1=Report Only (default)
2=Update All
3= Update Service Status
4= Update Event Status
Report Option
Select whether or not you want to see transaction detail in the report.
1=Summary
2=Detail (default)
Sort Option
Select the order for reporting selected service transactions.
1=Employee (default)
2=Service Code
3=Reason Code
