Residual Web-based Entry, Processing, Inquiry, and Correction System (EPIC Web), History Correction Update Processing System (HCUP) Packages

EPIC Web and HCUP packages that do not contain a starting/ending indicator are also known as residual EPIC Web HCUP packages.

Prior to starting a new HCUP package, the processor should search to determine if previous actions or HCUP packages exist. When there are applied actions or HCUP packages, they must be rolled back and incorporated into a new HCUP package, or the user must wait until the following Pay Period (PP) to process the new package. When there are no existing actions or packages, the processor can start a new HCUP package. The residual HCUP packages are found when a processor receives a message indicating EPIC Web HCUP package already exists even though the search revealed no packages or actions. The residual HCUP packages are created for a variety of reasons. The reasons include, but are not limited to:

• Two different Agencies each entering a single action or a HCUP package for the same employee that process through the same pass of Personnel Input and Edit System (PINE). This occurs when more than one Agency is correcting historical personnel records on the same employee on the same day. The actions merge into one HCUP package and depending on the security access levels the whole package may or may not be seen by the different Agencies. If one Agency can only see a partial package and deletes that package, the other portion is left without the starting and/or ending HCUP indicators.

• When actions are submitted for processing on an employee who has been paid, PINE puts a single action into a Future status and deletes all PINE error messages. If the actions comprise a HCUP package, the most current action of the package is sent to the Future file and all other actions are deleted when the error messages are deleted. On Monday during the first pass of PINE after Payroll Computation System (PAYE) runs, PINE looks to marry the Future actions with any HCUP packages. If the packages are in the job stream PINE allows the actions to process normally. If the packages are not in the job stream (i.e., the user deleted the HCUP package), PINE codes the actions for deletion. On Tuesday, normal processing routines resume.

Note: It is important to pay attention to the payroll processing cycle when processing history correction actions, and review/validate all actions prior to entering an action or HCUP package. History corrections cannot be processed until after PAYE runs the second pass of PINE for the current PP. Example: PAYE for the previous PP generally runs the first Thursday evening of the current PP and first pass of PINE for the current PP runs the second Monday of the PP, which means history packages cannot be started or changed on Friday, Saturday, Sunday, or Monday after PAYE runs. Correction actions can first be processed the second Tuesday of the current PP.