Troubleshooting Payroll for North America1

PeopleSoft Payroll for North AmericaPeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines 37PeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines What should you do when something goes wrong in your PeopleSoft Payroll system? We hope that nothing will, of course. But in a complicated process like generating full and accurate paychecks, it’s almost inevitable that you will hit a few snags, from processing sequence errors to difficulties with COBOL configurations. This document will help you identify and resolve problems as they arise during payroll processing. In this document, we discuss the following: • • • • A troubleshooting checklist. Understanding error resolution. Process overview. Troubleshooting tools. A Troubleshooting Checklist When troubleshooting, follow these steps: 1. Determine the impact of the problem. 2. Isolate the problem. 3. Diagnose the problem. 4. Fix the problem. 5. Test the solution. Determine the Impact of the Problem When determining the impact of the problem, ask the following questions: • • • • Is the problem occurring in the production environment? What is the business impact? Who is affected by the problem? Is there a reasonable workaround? Isolate the Problem When isolating the problem, ask the following questions: • Specifically, what is the problem? What is the expected result? What result are you getting? PeopleSoft Proprietary and Confidential 1 PeopleSoft Payroll for North America PeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines • • • • What is the simplest set of conditions that consistently causes the problem to occur? Remove unnecessary variables from the test. Can these steps be duplicated? Can the problem be replicated in the DEMO database? Has this problem occurred before? If not, when did it last work? What has changed since then? Have there been any modifications in this area? Diagnose the Problem When diagnosing the problem, do the following: • • • Compare program file dates and sizes to make sure you are using the correct version. Use diagnostic tools such as traces and audit programs. See Troubleshooting Tools. Search in Updates and Fixes in Customer Connection to determine if this is a known problem. Customer Connection is on PeopleSoft’s website. Fix the Problem When fixing the problem, do the following: • • Correct the data (employee, table setup). Correct the program and apply the fix. Test the Solution When testing the solution, do the following: • • • Test the fix under relevant conditions. Test in the development environment. Test in the production environment. Understanding Error Resolution In this section, we provide descriptions of and solutions for some errors that can occur in your PeopleSoft Payroll system. A number of errors might happen during online procedures, but the majority are inconsistencies that are revealed by payroll processing. In this section, we discuss: • • • • Online processing errors. CALENDAR process errors. PAYSHEET process errors. CALCPAY process errors. PeopleSoft Proprietary and Confidential 2 PeopleSoft Payroll for North America PeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines • • • • CONFIRM process errors. UNCNFRM process errors. REPRINT process errors. REVERSAL process errors. Online Processing Errors These errors might appear when you are performing actions online. No Matching Buffer Found For Level (Paysheets) This error indicates that a child record has been left without a ‘parent’ record (in other words, the record is orphaned). Run PRECALC.SQU to identify the orphan record. To resolve the problem, delete the orphaned records as well as their associated records. Typically, these are the tables involved: • • • • • • • PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_GARN_OVRD PS_PAY_CTX_OVRD If Pay Calculation has been run, additional tables are affected as well. For assistance with this process, please call the PeopleSoft Global Support Center. Prompting Earnings Code Returns Too Many Rows on Additional Pay Page Prompting for the earnings code returns all earnings codes associated with all earnings programs (as opposed to just those earnings codes associated with the earnings program to which the employee is assigned). This function was designed this way. All codes are displayed, because the earnings code you enter is at level 1 on the page and the Effective Date is at level 2. Therefore, when you enter the code, you have not yet entered the Effective Date. Because the page does not have the Effective Date, it cannot look up the pay group. As a result, it cannot look up the earnings program. Note. The Effective Date is set at level 2, so general deductions and additional pays can be future-dated. Prompting Deduction Code Returns Too Many Rows on General Deduction Page PeopleSoft Proprietary and Confidential 3 PeopleSoft Payroll for North America PeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines Prompting for the deduction code returns all deduction codes associated with all benefit programs (as opposed to displaying only those deduction codes associated with the benefit program to which the employee is assigned). This function was designed this way. All codes are displayed, because the deduction code you enter is at level 1 on the page and the Effective Date is at level 2. Therefore, when you enter the code, you have not yet entered the Effective Date. Because the page does not have the Effective Date, it cannot look up the pay group. As a result, it cannot look up the benefit program. CALENDAR Process Errors You may encounter the following errors while running the Calendar process. SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. Recreate the stored commands for the database. This procedure is documented in the platformspecific System Administration documentation. SQL Error 208: Stored Command Has Been Invalidated An index, field, or table has been changed or dropped since the command using this object was stored. Recreate the stored commands for the database. This procedure is documented in the platformspecific System Administration documentation. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform, if you have linked with an incorrect Oracle library. CANNOT EXECUTE This error occurs on the Oracle platform, when trying to run the process from UNIX, if the permissions have not been created for execute purposes. PAYSHEET Process Errors The Paysheet process might produce one of the following errors. SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. Recreate the stored commands for the database. This procedure is documented in the platformspecific System Administration documentation. SQL Error 208: Stored Command Has Been Invalidated An index, field, or table has been changed or dropped since the command using this object was stored. Recreate the stored commands for the database. This procedure is documented in the platformspecific System Administration documentation. PeopleSoft Proprietary and Confidential 4 CANNOT EXECUTE This error occurs on the Oracle platform. 2. Make sure this deduction is set up on the Deduction Table with an Effective Date that is ≤ the Effective Date of the benefit program and ≤ the Pay End Date of this payroll cycle. 3. EMPLID=99999.PeopleSoft Payroll for North America PeopleSoft 8. LINE#=00. Ensure that this deduction is set up in the Company General Deduction Table and that this table has an Effective Date ≤ the Pay End Date of this payroll cycle. if the permissions have not been created for execute purposes. CALCPAY processing also has its own set of error messages: Payroll Error 5: Deduction Code Not Found The deduction code displayed in the message data was not found in the Deduction Table. EMPLID= . when trying to run the process from UNIX. 1. if you have linked with an incorrect Oracle library. CALCPAY Process Errors At the beginning of CALCPAY. this error might display itself as a -302 error on PSPUPSHT_I_LINE. 2. the Paysheet Update process is executed to update the paysheets with any job changes... SQL Error 0805: Non-Unique Data (PSPUPSHT) An example of the complete error is: INSERT-PAY-LINE 0805 non-unique data PAGE#=0444. Verify that the employee has a location in the job record. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform. Check the Effective Date of the location table for the employee’s location.. LINE#=001. It must be ≤ the Pay End Date for this payroll cycle. If you receive an error message during this step. PeopleSoft Proprietary and Confidential 5 . review the error messages listed in the PAYSHEET Process section. and so on. Determine the employee’s benefit program. GET-NEXT-JOB (PSPPARRY) 00001 end of fetch BUILD-PAYSHEETS (PSPPYSHT) 00001 end of fetch This error occurs when the employee is not assigned to a benefit program on the Benefit Program Participation page. 1..3 Payroll for North America Troubleshooting Guidelines End of Fetch (PSPPYGEM) The complete error is: LOAD-JOB (PSPPYGEM) 00001 end of fetch PAGE#=00001. On the DB2 platform.EMPLRCD#=8224 PROCESS-JOB (PSPUPSHT) 0805 non-unique data SELECT-PAY-CALENDAR (PSPPYSHT) 0805 non-unique data START-RUN (PSPSTRUN) 0805 non-unique data This error occurs if there are one or more employees who have an invalid location.. x). it can indicate: a. For more information about this Oracle bug. resulting in the above errors. PS_PAY_TAX_OVRD." PeopleSoft Proprietary and Confidential 6 . which reflects the SUT rate at the beginning of the year. 1. There are orphaned records in PS_PAY_EARNINGS.x: Message 000017 . the tables involved are PS_PAY_LINE. use the RULE-based optimizer until the bug is fixed. North American Payroll. You only have a different quarter set up in addition to the quarter 1 record if the rate changes mid-year. Run PRECALC. • The SUT rate for the agency and state displayed in the message data was not found in the Agency/State Tax Table. Check to see if there is a Quarter 1 record for unemployment set up in the Agency/State Tax Table. PS_PAY_EARNINGS.Federal tax data not found for this employee SPECIFIC TO: Enterprise.Federal tax data not found for this employee Details: SOLUTION 16900: EPY8. PS_PAY_OTH_EARNS. You are using the COST-based optimizer on the Oracle platform (version 7. 2.x releases ISSUE: Paycalc error message 000017 "Federal tax data not found for this employee.SQU to identify the orphaned records. and PS_PAY_CTX_OVRD. If so. Typically. Payroll Error 17: Federal Tax Data Not Found The federal tax data record was not found for the employee. To resolve the problem. you delete the orphaned records as well as their associated parent and child records. The system assumes you have a quarter 1 record set up. 8. Change to the RULE-based optimizer to see if it resolves the problem. please contact Oracle Support Solution from PS support: EPY8.PeopleSoft Payroll for North America PeopleSoft 8.0.3 Payroll for North America Troubleshooting Guidelines Payroll Error 13: SUT Rate Not Found • The SUT rate for the company and state displayed in the message data was not found in the Company/State Tax Table. If this error is accompanied by errors 32: Personal Data Not Found and 89: Benefit Not Found. Check to see if there is a Quarter 1 record for unemployment set up in the Company/State Tax Table. Check the Effective Date on the employee Federal Tax Data page for the company that you are processing and make sure that it is ≤ the check date of this payroll cycle. PS_PAY_ONE_TIME.x: Message 000017 . PS_PAY_GARN_OVRD. This optimizer has a bug that causes some SQL statements to be ordered incorrectly. b. please call the PeopleSoft Global Support Center. For assistance with this process. Some customers implement it this way. Payroll Error 31: Rate Coverage Not Found The coverage code displayed in the message data was not found for the rate schedule specified in the message data. the rate schedule page appears to have rows. Verify that the employee is enrolled in this benefit plan with an Effective Date ≤ the Effective Date of the Benefit Program Table. The state on the paysheet is derived from the Location Table using the location in the employee’s job record. Check the Effective Date on the Employee State Tax Data page for the company that you are processing and make sure it is ≤ the check date of this payroll cycle. because the deductions are calculated in a different manner. was not found for the employee. SQR . Therefore. run Presheet (PAY034. 2. Payroll Error 27: Benefit Plan Not Found The benefit plan displayed in the message data was not found in the appropriate benefit table. Verify that the state on the paysheet is set up on the employee State Tax Data page and the Effective Date is ≤ the check date of the payroll cycle. Make sure the Benefit Program Table has an Effective Date that is ≤ the Pay End Date of this payroll cycle and that the program includes this benefit plan. Errors. Sometimes a customer sets up the rates that are all 0. However. in this order: 1. 1. WORKAROUND: N/A SEE ALSO: Solution 31467 KEYWORDS: Pay Calc. 1. 2. Determine the employee’s benefit program. PeopleSoft Proprietary and Confidential 7 . because the default values are displayed.3 Payroll for North America Troubleshooting Guidelines SOLUTION: Do the following. Check the Rate Schedule Table and make sure that the coverage code and amount are included.) Recalc All (with no other action) sometimes resolves this error message. 2.SQR) for data errors. for the state displayed in the message data. 3. Payroll Error 18: State Tax Data Not Found The state tax data record. the record cannot be saved with only default values.) If Recalc All does not resolve.SQR) and Precalc (PAY035.PeopleSoft Payroll for North America PeopleSoft 8. For assistance with this process. and PS_PAY_CTX_OVRD. To prevent this error.SERVICE_DT) is null. and it’s left at zero.SQU to identify the orphaned records. To locate all employees whose service date is null. delete the orphaned records as well as their associated parent and child records. because some customers only have the HR application and might not use leave accruals. you must have saved a row in the PS_RATE_SCHED_COVG table. PS_PAY_GARN_OVRD. The above statement requires this field. Currently. Payroll Error 44: Negative Net The net pay calculated for this check is negative. service date is not a required field on the employment record. Typically. This error occurs when the statement PSPEARRY_S_JOB fails for the employee. Verify that this shift code is set up on the Shift Table and that the Effective Date is ≤ the Pay End Date of this pay cycle. • • PeopleSoft Proprietary and Confidential 8 . The employee does not have a benefit program participation record. resulting in the above errors.0. please call the PeopleSoft Global Support Center.PeopleSoft Payroll for North America PeopleSoft 8. PS_PAY_OTH_EARNS. It is also used in the calculation of leave accruals. Therefore.3 Payroll for North America Troubleshooting Guidelines For example. PS_PAY_ONE_TIME. Negative net pay is only allowed on a paysheet for a manual check (MANUAL_CHECK of PS_PAY_LINE = ‘Y’). no rate set up is required. the tables involved are PS_PAY_LINE. Here are examples that cause this statement to fail: • The service date in the employment table (PS_EMPLOYMENT. Payroll Error 49: Shift Not Found The shift displayed in the message data was not found. If this error is accompanied by errors 17: Federal Tax Data Not Found and 89: Benefit Not Found. Payroll Error 32: Personal Data Not Found Personal data was not found for this employee. use the RULE-based optimizer until the bug is fixed. SERVICE_DT FROM PS_EMPLOYMENT WHERE SERVICE_DT IS NULL. so it is associated with a general deduction. Enter a row with any value in the amount field in order to save the record. PS_PAY_TAX_OVRD. This optimizer has a bug that causes some SQL statements to be ordered incorrectly. it can indicate:  There are orphaned records in PS_PAY_EARNINGS. the carrier sends a tape with the deduction amount. 1. To resolve the problem. or that record is not valid. Change to the RULE-based optimizer to see if it resolves the problem. PS_PAY_EARNINGS. execute the following query: SELECT EMPLID. For more information about this Oracle bug.  You are using the COST-based optimizer on the Oracle platform (version 7.x). please contact Oracle Support. If so. Run PRECALC. because this date is used by the service rate calculations for various benefits. Payroll Error 92: Local Tax Not Found The local tax record for the locality defined below cannot be found for this employee. Note the value of the PAYCHECK_STATUS on the rows that are returned. If an employee has off-cycle checks on multiple pages for the same payroll cycle. The check(s) calculated are not a part of this run. Identify the outstanding off-cycle checks for an employee by executing the following query: SELECT * FROM PS_PAY_EARNINGS WHERE EMPLID=:1 AND OFF_CYCLE=’Y’ AND PAY_END_DATE <= :2. Using the values you enter. You might want to review the DEMO database for an example of how to set up TableSets for the Shift Table. :2). because the employee has check(s) that have been calculated and not confirmed. Payroll Error 59: Cannot Calculate for Employee This check cannot be calculated. Insert the EMPLID and Pay End Date that you are processing into the bind variables (in other words :1. execute the following query: SELECT * FROM PS_PAY_CHECK WHERE EMPLID= :1 AND PAY_END_DATE <= :2. until all are calculated. PeopleSoft Proprietary and Confidential 9 . before the current check can be calculated. only one can be marked OK to Pay at a time. before you can calculate the current check. :2). or marked Not OK to Pay and recalculated. 1. or marked Not OK to Pay and recalculated. The system checks the existence of PAY_CHECK records to determine if the employee has any other calculated checks that have not been confirmed. To identify the outstanding checks that have been calculated. Make sure the SetID specified in the Shift Table is consistent with the SetID specified for this pay group on the TableSet Record Group Controls page. you must enter the gross and net pay as well as all earnings. so you do not need to enter them on the paysheet. Payroll Error 51: Manual Check Error The calculated values for total gross and net pay displayed in the message data do not match the values entered on the manual check. The Page # of the other calculated off-cycle check displays in the message data.3 Payroll for North America Troubleshooting Guidelines 2. The CALCPAY process automatically calculates the employer-paid taxes and deductions. unless you want to override them. and deductions. net pay. Another option is to combine all paysheets into one and mark the remainder Not Pay. because the employee has another off-cycle check calculated and not confirmed. 2. When you enter a manual check paysheet. The CALCPAY process uses the values you enter and does a gross-to-net calculation to make sure the gross and net values you enter are correct. Note the value of the PAY_LINE_STATUS and OK_TO_PAY fields on the rows that are returned. taxes. All outstanding off-cycle checks for an employee must be on the same page. Insert the EMPLID and Pay End Date that you are processing into the bind variables (in other words :1. TableSets are discussed in your PeopleTools documentation.PeopleSoft Payroll for North America PeopleSoft 8. Payroll Error 86: Cannot Calculate For Employee This check cannot be calculated. and earnings are entered. do a manual gross-to-net calculation. These other calculated checks must be confirmed. These checks must be confirmed. Verify that the gross amount. Make sure all work localities are tied to the locality using the Other Work Locality field on the Employee Local Tax Data page.3 Payroll for North America Troubleshooting Guidelines 1. field. Recreate the stored commands for the database. local tax data must be set up for any employee with a work locality. or table has been changed or dropped since the command using this object was stored. See PeopleSoft 8.3 Payroll for North America PeopleBook. An employee can have two records for the year if the residential status changes (for example. he or she is still taxed in the original locality. Payroll Error 112: Tax Status Rates Not Found The tax status tax rates for the tax entity displayed in the message data cannot be found. Not all Indiana localities have taxes. a transfer). there must be one that is valid as of January 1. it ignores it. If the system sees an Indiana local tax record with an Effective Date greater than the first day of the current year. Verify that the employee’s tax status is set up in the Federal/State Tax table and that the Effective Date of that table is ≤ the check date of the payroll cycle. Users get an error 000092 if the local tax data is missing for an employee. “Maintaining Payroll Data. even though the Effective Date of hire is a later date. The locality on the paysheet comes from the Location Table based on the location entered in the employee’s job record. Recreate the stored commands for the database. In prior releases. taxing locality in the location table to determine default taxation. As of release 3. This change in setup was a result of Indiana local tax requirements. 1. SQL Error 208: Stored Command Has Been Invalidated An index. the system used the U. SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected.” Entering Local Tax Data. This procedure is documented in the platformspecific System Administration documentation. An employee hired mid-year must provide an Indiana employer where he or she lived on the first day of the year. An employee who is not an Indiana resident on the first day of the year is not subject to local tax for that year. Indiana Local Tax Incorrect An employee is subject to Indiana local taxes based on the locality in which he or she resides on the first day of the year.PeopleSoft Payroll for North America PeopleSoft 8. Verify that the locality on the paysheet is set up on the Employee Local Tax Data page and that the Effective Date is ≤ the check date of the payroll cycle. an employee who worked in that locality was taxed as a non-resident. If an employee moves to a different locality during the year.01. PeopleSoft Proprietary and Confidential 10 . Make sure that you are using the correct version of the program PSPTCALC and that it is compatible with the other tax calculation programs. the employer must set up the state and local tax data records with an Effective Date as of January 1.S. 2. This procedure is documented in the platformspecific System Administration documentation. 2. If it was in Indiana. ” Checks Already Calculated This number represents the number of PS_PAY_LINE records where JOB_CHANGE <> R. Note. it increments the Employee(s)/Jobs Checked for Update counter. If you make any online change to employee data that affects the calculation of a Pay Check. remember to only use the 3-digit numeric Indiana local tax IDs from the Local Tax Table. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform if you have linked with an incorrect Oracle library. Employee(s)/Jobs Checked for Update This counts the number of changes made to the PS_JOB record that affect the PS_PAY_LINE data. CONFIRM Process Errors Running the Confirm process can trigger any of a set of error messages. If it detects a change. PeopleSoft Proprietary and Confidential 11 . if the permissions have not been created for execute purposes. If the JOB_PAY flag=Y and the paysheet isn’t modified online. and so on. CANNOT EXECUTE This error occurs on the Oracle platform. review the error messages listed under the PAYSHEET Process Errors section. Do not use any of the local tax IDs that contain the 2-letter alpha suffixes (such as CA. If the JOB_PAY flag on PS_PAY_EARNINGS is equal to Y. then the PAY_EARNINGS rows are updated with the new job data. The program compares the job data between the paysheet and the base table. CE. If you receive an error during this step. the Paysheet Update process is executed to update the paysheets with any job changes. Checks To Calculate This number represents the number of PS_PAY_LINE records where JOB_CHANGE = R. It will not always be synchronized with the updates counter (Employee(s)/Jobs Checked for Update).’ “Calculation required.3 Payroll for North America Troubleshooting Guidelines Note. If JOB_PAY flag=N.PeopleSoft Payroll for North America PeopleSoft 8. At the beginning of CALCPAY. the JOB_CHANGE flag is set to ‘R. and CO). then the system assumes that online changes were made and merges the online changes in the PAY_EARNINGS row. Employee(s)/Jobs Had Their Paysheet Updated This counts the number of physical paysheets that were modified or updated online. when trying to run the process from UNIX. then the program increments the Paysheet Updated counter. This count does not include changes made to tax or deduction data. When setting up Indiana local taxes for employees. :2. Pay Group. :2. E). SELECT * FROM PS_PAY_CALENDAR WHERE AGENCY=:1 AND PAYGROUP=:2 Insert the Company. set up a run control for the CALCPAY process and clear the check box for Preliminary Calculation. SELECT * FROM PS_PAY_EARNINGS WHERE AGENCY = :1 AND Insert the Company. The checks selected here must be calculated successfully or marked Not Pay before you can run CONFIRM. :4). :3). :4). This error indicates that there is an on-cycle run that has not been confirmed. and Run ID that you are processing in the associated bind variables (:1. Pay Group. :2. Check the pay calendar that you are attempting to confirm.PeopleSoft Payroll for North America PeopleSoft 8. Pay End Date. Check the pay calendar that you are attempting to confirm.’ indicating that this calendar has confirmed successfully. Pay Group. This automatically runs a final calculation when you execute the CALCPAY process. U. PeopleSoft Proprietary and Confidential 12 .3 Payroll for North America Troubleshooting Guidelines Payroll Error 12: Already Confirmed The pay calendar entry to be processed has already been confirmed. :2. because a prior run has not been confirmed. :3. Insert the Company. To determine which checks have not been calculated. Pay Group. To identify the pay calendar that has not been confirmed. Payroll Error 20: All Checks Not Calculated None of the checks for the pay calendar have been calculated and therefore cannot be confirmed. Payroll Error 16: Pay Calculation Is Not Final The pay calculation has not been finalized and therefore cannot be confirmed. The PAY_CONFIRM_RUN flag is probably set to ‘Y. :3. execute the following query: SELECT * FROM PS_PAY_EARNINGS WHERE COMPANY = :1 AND PAYGROUP = :2 AND PAY_END_DT = :3 AND OK_TO_PAY = ‘Y’ AND PAY_LINE_STATUS IN (I. execute the following query: SELECT * FROM PS_PAY_CALENDAR WHERE COMPANY=:1 AND PAYGROUP=:2 AND PAY_END_DT<=:3 AND RUN_ID<>’ ‘ AND RUN_ID<>:4 AND (PAY_CONFIRM_RUN=’N’ OR PAY_OFF_CYCLE=’Y’) Insert the Company. and Run ID that you are processing in the associated bind variables (:1. You must make sure that there are no errors generated from the final calculation before you can run CONFIRM. and Pay End Date that you are processing in the associated bind variables (:1. Pay End Date. Payroll Error 64: Prior Run Not Confirmed The selected run cannot be confirmed. and Pay End Date that you are processing in the associated bind variables (:1. To resolve the problem. :3). P. or there are offcycle checks that are outstanding for this company and pay group. The Payroll Calculation Run? check box (PAY_CALC_RUN) is not selected. indicating that a final calculation has not been run. the error might have the description “Insert/update of unique constrained columns with duplicate data. SEPCHK=000.” PeopleSoft Proprietary and Confidential 13 . EMPLRCD#=0000. SQL Error 0805: Non-Unique Data (PSPCBUPD) Here is an example of the complete error on SQLBase: INSERT-BALANCE PAGE#=0001. The select in PSPSTUPD_S_PAGE can be done manually to determine which page has off-cycle checks that are not confirmed.WT. SELECT * FROM PS_PAY_PAGE WHERE AGENCY=:1 AND PAYGROUP=:2 AND PAY_END_DATE <= :3 AND OFF_CYCLE='Y' AND CONFIRMED='N'.3 Payroll for North America Troubleshooting Guidelines Payroll Error 65: Reversal Outstanding Cannot confirm the selected run with an unconfirmed reversal existing for an employee with a calculated check in this run. It occurs if any rows are selected by STORE PSPSTUPD_S_PAGE in PSPSTUPD. The error is generated from PSPSTUPD. LINE#=001. using the data from the run that you are trying to process. field.PeopleSoft Payroll for North America PeopleSoft 8. Recreate the stored commands for the database. SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. Insert the appropriate values for the bind variables above. Execute the following query to determine which employee has an outstanding reversal: SELECT * FROM PS_PAY_CHECK WHERE PAYCHECK_OPTION = ‘R’ AND PAYCHECK_STATUS =’C’. SQL Error 208: Stored Command Has Been Invalidated An index. To identify the off-cycle pages that have not been confirmed.CBL. Payroll Error 66: Off-Cycle Outstanding Cannot confirm the selected run with a prior run with off-cycle pages not confirmed. This procedure is documented in the platformspecific System Administration documentation. This procedure is documented in the platformspecific System Administration documentation. It takes the pay calendars selected by STORE PSPSTUPD_S_CAL and then does PSPSTUPD_S_PAGE using these calendars. This reversal must be confirmed or deleted before you can confirm the current payroll. or table has been changed or dropped since the command using this object was stored. execute the query below: SELECT * FROM PS_PAY_PAGE WHERE COMPANY=:1 AND PAYGROUP=:2 AND PAY_END_DATE <= :3 AND OFF_CYCLE=’Y’ AND CONFIRMED=’N’. Recreate the stored commands for the database. NAME= PROCESS-CHECK (PSPCBUPD) 0805 non-unique data MAIN (PSPPYUPD) 0805 non-unique data PROCESS-CONFIRMATION (PSPPYWKS) 0805 non-unique data This error varies by platform: • On DB2. EMPLID=0008. e. CONFIRM picks up where it left off and confirms the remainder of the pay run. c. Typically. Review the pay calendar you are trying to confirm and note the month code. Review the query output and determine if there is a balance record for a MONTHCD > than the month code in the pay calendar that you are processing. The system attempts to post to the month indicated in the MONTHCD field on the pay calendar. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform. Issue the following query to update the pay calendar as if confirm has not been started: UPDATE PS_PAY_CALENDAR SET PAY_CONFIRM_START = ‘N’ WHERE COMPANY = :1 AND PAYGROUP = :2 AND PAY_END_DT = :3. Modify the search record for the paysheet page to select records that have been confirmed. quarter. and month. d. the error is “2509: Index uniqueness or unique/primary key constraint violated. if you have linked with an incorrect Oracle library. To resolve this error. 3. (This check is not fully confirmed yet. Reset the search record back to its original state. you are trying to post to a previous month. AGENCY = [employee's agency] ORDER BY CALENDAR_YEAR. Balance records are stored by year.3 Payroll for North America Troubleshooting Guidelines • • • On Allbase. Issue the following query: SELECT * FROM PS_CHECK_YTD WHERE EMPLID = [EMPLID in the error] AND COMPANY = [employee’s company] ORDER BY CALENDAR_YEAR. the system doesn’t allow you to update a March balance. the error is “ORA-00001: Unique constraint violated” or “ORA-00001: Duplicate key in index. QTRCD.” On Rdb. To determine whether this situation is causing the problem. and confirm. the error is “-803: %RDB-E-NO_DUP. :2. MONTHCD. QTRCD. Once you have posted to a month. index field value already exists. For example.PeopleSoft Payroll for North America PeopleSoft 8.) b. this error occurs if you try to post to a previous month after you have posted to the current month. The bind variables (:1. once you have posted an April balance. duplicates not allowed for Unique Index. UPDATE PS_PAY_CALENDAR SET PAY_CONFIRM_START = 'N' WHERE AGENCY = :1 AND PAYGROUP = :2 AND PAY_END_DT = :3. If you are unable to access the paysheet online.” The CONFIRM process is attempting to insert a check balance record that already exists. You can now mark the paysheet Not Pay. you cannot post to a previous month. If so. you must mark the paysheet Not OK to Pay and then confirm. because all statuses have not been updated. :3) must be set to the values of the calendar you are processing. MONTHCD. recalculate where needed. CALCPAY and CONFIRM ignore the checks that have confirmed successfully.” On Oracle. you need to complete the following steps: a. 2. PeopleSoft Proprietary and Confidential 14 . follow these steps: 1. INT from $PS_HOME\INT and copying them to $PS_HOME\BIN (keeping the extension as . field. This is the complete error: PSPSQLRT . SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. CANNOT EXECUTE This error occurs on the Oracle platform. PSPDCLIM.INT. if the permissions have not been created for execute purposes.ERROR IN SELECT SETUP/DATA STATEMENT=PSPCARRY_S_UGRN PSPSQLRT . if the permissions have not been created for execute purposes. when trying to run the process from UNIX. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform. or table has been changed or dropped since the command using this object was stored. SQL Error 208: Stored Command Has Been Invalidated An index.ERROR IN SELECT SETUP/DATA VARIABLE#=016 This error is resolved by taking the programs PSPDEDLD. This procedure is documented in the platformspecific System Administration documentation. This procedure is documented in the platformspecific System Administration documentation.3 Payroll for North America Troubleshooting Guidelines CANNOT EXECUTE This error occurs on the Oracle platform.GNT versions of these three files.PeopleSoft Payroll for North America PeopleSoft 8. Error In Select Setup/Data (PSPCARRY) This error typically occurs on the Oracle platform. when trying to run the process from UNIX.ERROR IN SELECT SETUP/DATA STATEMENT=PSPCARRY_S_UGRN VARIABLE#=015 INVALID CHARACTER IN SETUP=1 PSPSQLRT . PeopleSoft Proprietary and Confidential 15 .INT). if you have linked with an incorrect Oracle library.INT. Recreate the stored commands for the database. UNCNFRM Process Errors The following errors might appear when you run the Unconfirm process. Then delete the . Recreate the stored commands for the database. REPRINT Process Errors The Reprint process may invoke the following errors. and PSPCARRY. CANNOT EXECUTE This error occurs on the Oracle platform. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform. This procedure is documented in the platformspecific System Administration documentation.3 Payroll for North America Troubleshooting Guidelines SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. field. field. Recreate the stored commands for the database. SQL Error 208: Stored Command Has Been Invalidated An index.PeopleSoft Payroll for North America PeopleSoft 8. if the permissions have not been created for execute purposes. CANNOT EXECUTE This error occurs on the Oracle platform. Recreate the stored commands for the database. Recreate the stored commands for the database. This procedure is documented in the platformspecific System Administration documentation. USAGE IS INPUT_FILE OUTPUT_FILE This error occurs on the Oracle platform. when trying to run the process from UNIX. or table has been changed or dropped since the command using this object was stored. if the permissions have not been created for execute purposes. SQL Error 208: Stored Command Has Been Invalidated An index. SQL Error 207: Command Not Found For Retrieval The stored command was not found when selected. if you have linked with an incorrect Oracle library. Recreate the stored commands for the database. PeopleSoft Proprietary and Confidential 16 . if you have linked with an incorrect Oracle library. REVERSAL Process Errors You may encounter the following errors while running the Reversal process. when trying to run the process from UNIX. This procedure is documented in the platformspecific System Administration documentation. or table has been changed or dropped since the command using this object was stored. This procedure is documented in the platformspecific System Administration documentation. except where noted. All tables are the same for U.3 Payroll for North America Troubleshooting Guidelines Process Overview To help you pinpoint faulty processing in the system. This table is updated with any standard payroll error messages that are encountered during the process.S. Pay calendars can be created using the CALENDAR (Pay Calendar Creation) process or they can be manually entered online. we discuss the following payroll processes and tables: • • • • • • • • CALENDAR PAYSHEET CALCPAY CONFIRM REVERSAL REPRINT PAYUNSHT UNCNFRM CALENDAR You use the pay calendar to schedule payroll cycles for your pay groups. Tables From Which the CALENDAR Process Selects Balance ID: • • • PS_BALANCE_ID_DEF PS_BALANCE_ID_QTR PS_BALANCE_ID_TBL Tables Into Which the CALENDAR Process Inserts: PS_PAY_CALENDAR This table is updated with the number of pay calendars equivalent to the period of time requested on the run control. In this section. Table From Which the CALENDAR Process Selects: PS_PAY_CBLD_RUNCTL The process selects the run control record that is added by the user before running the process. this section provides a brief description of each payroll process and the tables that are used. This table is updated with the Balance ID information PS_PAY_MESSAGE PS_PAY_CAL_BAL_ID PeopleSoft Proprietary and Confidential 17 . and Canada.PeopleSoft Payroll for North America PeopleSoft 8. We don’t discuss these tables (which begin with PS_WRK) in detail here. Many of the processes use work tables during processing. they can also be created manually online or through a time interface (such as PeopleSoft Time and Labor). earnings code for regular or overtime pay). • Once paysheets are created. Paysheets are normally created using the PAYSHEET (Paysheet Creation) process. Page number is also used for off-cycle check processing. Otherwise. Each page may be the parent to several PeopleSoft Proprietary and Confidential 18 . it might be necessary if any high-level information on the paysheet changed (for example. and off-cycle indicator. you must first create paysheets. pay group. pay end date. If you need to recreate paysheets. However. The process selects the Balance ID for the calendar year. Messages from the prior run are deleted by company. the process selects the appropriate pay calendar information. PeopleSoft delivers the programs PAYEDIT. Points to Consider When Running the PAYSHEET Process • The PAYSHEET process can be run before or after a time interface. Tables From Which the PAYSHEET Process Selects: PS_PAYSHEET_RUNCTL PS_PAY_CALENDAR PS_INSTALLATION The process selects the run control record that is added by the user prior to running the process. the process doesn’t recreate a paysheet for an employee who already has one.SQU to assist you in editing and loading paysheet data using an interface. However.PeopleSoft Payroll for North America PeopleSoft 8. It depends on whether the time interface is designed to load the majority of the paysheet data or simply other earnings. PAYSHEET Before you can run any payroll calculations.3 Payroll for North America Troubleshooting Guidelines for the calendar.SQU and PAYUPDT. Using the Run ID. Tables Into Which the PAYSHEET Process Inserts PS_PAY_PAGE This table contains the paysheet pages that are created. Tables From Which the CALENDAR Process Deletes: PS_PAY_CBLD_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. it can be rerun and the process continues processing where it left off (after the last commit to the database). it is recommended that you run PAYUNSHT first to delete the current paysheets. you don’t normally rerun this process. • If an error occurs during this process. it appears on the payroll messages page. Each paycheck might contain several pay earnings records. This table contains individual pay earnings records. A user has updated the record online since it was originally entered or calculated. some statuses might remain as a ‘P’ until reprocessed. Calculated successfully. If an error occurs during processing. Updated by operator. for calculation). If this field is set to ‘N. Confirmed successfully.’ the calculation process bypasses PS_PAY_EARNINGS SEPCHK PAY_LINE_STATUS I U C E F P JOB_PAY OK_TO_PAY PeopleSoft Proprietary and Confidential 19 . This is determined based on the supplemental tax method (SUPPL_SEP_METHOD) specified on the Federal/State Tax Table (PS_STATE_TAX_TABLE). Deductions aren’t taken on a separate check if the separate check indicator (SEPCHK_DED) on the Deduction Table (PS_DEDUCTION_CLASS) is set to ‘N. Indicates whether this record should be processed. Here are some key fields on this table: Determines whether these earnings are associated with a separate check. Pay in Progress. An error occurred in the processing of these earnings.3 Payroll for North America Troubleshooting Guidelines paylines. This information might have changed since the paysheet was created or last calculated. The pay earnings entered but not calculated. Otherwise. Earnings records with this status must be corrected or marked Not OK to Pay before the calculation process completes successfully. PS_PAY_LINE This table contains individual paylines. the error displays on the screen where the process was executed or in the JCL. The pay processes sets the status to ‘P’ if the record has been selected for processing (that is. Directs the process to update the paysheet with the most current job information. PeopleCode sets this status. Error. Each employee is created on a separate payline during oncycle processing. These are the valid values: Initial Load. Supplemental taxes might be calculated differently on separate checks. A record marked Not OK to Pay remains with an ‘I’ status until it is deleted by the CONFIRM process.PeopleSoft Payroll for North America PeopleSoft 8. These pay earnings records might represent one or more checks.’ Indicates whether the earnings record is calculated or confirmed successfully. If it is a standard payroll error. Each payline might be the parent to several pay earnings records. and off-cycle indicator.3 Payroll for North America PeopleBook. Page number is also used for off-cycle check processing.3 Application Fundamentals for HRMS PeopleBook. There might be multiple other earnings records for one PS_PAY_EARNINGS record. “Setting Up Payroll Tax Tables” PeopleSoft 8.’ no deductions are taken for this check. Other Earnings records might also be added online or through a time interface. Messages from the prior run are deleted by company. pay group. DED_TAKEN TAX_PERIODS Directs the system how to take deductions.PeopleSoft Payroll for North America PeopleSoft 8. pay end date.3 Payroll for North America Troubleshooting Guidelines this record. This table is updated with standard payroll error messages that are encountered during the process. PS_PAY_OTH_EARNS PS_PAY_MESSAGE Table That the PAYSHEET Process Updates: PS_PAY_CALENDAR The PAY_SHEETS_RUN flag on the pay calendar is set to ‘Y’ to indicate that the PAYSHEET process has run successfully. Tables From Which the PAYSHEET Process Deletes: The PAY_SHEETS_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. Records added in this manner should have the ADDL_SEQ field set = 0.3 Payroll for North America PeopleBook. The PAYSHEET process might generate these records automatically from the additional pay data records under Employee Payroll Data. “Appendix B: Configuring Batch Processes” PeopleSoft Proprietary and Confidential 20 . This table contains other earnings records that are added to the paysheet. Indicates the number of tax periods used for the calculation of taxes. “Working with Paysheets” PeopleSoft 8. See Also PeopleSoft 8. additional pay isn’t processed correctly. If this field is set to ‘N. Otherwise. This field can drastically affect the amount of tax calculated. Records added from additional pay have the ADDL_SEQ field set to a value > 0. P. even if they were already calculated successfully. Additionally. or E. the process selects the appropriate pay calendar information. it can be rerun and the process continues processing where it left off (after the last commit to the database). Tables From Which the CALCPAY Process Selects PS_PAY_CALC_RUNCTL The process selects the run control record that is added by the user prior to running the process.PeopleSoft Payroll for North America PeopleSoft 8. when running Final Calculation with the Continue With Errors option selected. The table information for the paysheet update process has not been duplicated below. If there are changes to an employee's record that could cause a recalculation. Using the PAY_LINE_STATUS on PS_PAY_EARNINGS and the CALC_SELECT field on PS_PAY_CALC_RUNCTL. deductions. A preliminary calculation can be run as many times a necessary However. a paysheet update process is done. Points to Consider When Running the CALCPAY Process • • CALCPAY can be rerun as many times as necessary. and net pay. until CONFIRM is started. This is similar to the PAYSHEET process and is designed to update the paysheets with any employee changes that were made after paysheets were created. even if they were already calculated.3 Payroll for North America Troubleshooting Guidelines CALCPAY The CALCPAY (Pay Calculation) process uses the paysheet data to calculate earnings. Final Calculation cannot be run a second time. Lines for the calendar being processed are selected. If the run control specifies CALCULATE WHERE NEEDED. this doesn’t happen when a final calculation is run. One-time deductions for the calendar being processed PS_PAY_CALENDAR PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_ONE_TIME PeopleSoft Proprietary and Confidential 21 . all records are calculated. Using the Run Control ID. Pages for the calendar being processed are selected. If the run control specifies CALCULATE WHERE NEEDED. all records with OK_TO_PAY = ‘Y’ are calculated. the system only calculates those records where OK_TO_PAY = ‘Y’ and the PAY_LINE_STATUS is I. the system looks at the PAY_LINE_STATUS to determine which records to calculate. The run control might be set up to RECALCULATE ALL or CALCULATE WHERE NEEDED. the system selects the records to be calculated. • If an error occurs during this process. If the run control specifies RECALCULATE ALL. taxes. At the beginning of the CALCPAY. Other earnings for the calendar being processed are selected. U. If the run control specifies RECALCULATE ALL. you must run a final calculation before running CONFIRM. Other employees who meet this condition have their PAY_LINE_STATUS set to 'E. This table contains current period deductions.3 Payroll for North America Troubleshooting Guidelines are selected. This table is used by Canadian payroll only. This table is updated with standard payroll error messages that are encountered during the process. the error is only reported on the payroll messages for the first employee who meets this condition. This table contains the current pay period. The assumption is that once the Deduction Table is added. as well as previous periods. If the error that occurred is a high-level error (for example. tax class. PS_PAY_TAX PS_PAY_TAX_CAN PS_PAY_GARNISH PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS PS_PAY_MESSAGE PeopleSoft Proprietary and Confidential 22 .S. and pay end date. This table is the Canadian version of PS_PAY_TAX.PeopleSoft Payroll for North America PeopleSoft 8. (Canadian only. This table contains current period information. it fixes the error for all employees. PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_GARN_OVRD One-time taxes for the calendar being processed are selected (U. This table contains the current pay period. This table is updated with the earnings totals that make up the special accumulators. deduction. as well as prior periods.' but they aren’t reported in the payroll messages. only). This table is updated with the garnishment deductions taken for each check. If a low-level error is encountered (for example. One-time taxes for the calendar being processed are selected.) One-time garnishments for the calendar being processed are selected. and pay end date. as well as prior periods. This table is updated with all deductions taken on each check. It is updated with Canadian unemployment earnings information for each check. Tables Into Which the CALCPAY Process Inserts PS_PAY_CHECK PS_PAY_DEDUCTION This table is updated with the gross-to-net information for each paycheck. It is stored by employee. this error is reported in the payroll messages for all employees who meet this condition. This table is updated with all taxes taken for each check. This prevents the PAY_MESSAGE table from filling up with duplicate messages. Deduction Table not found). It is stored by employee. as well as previous periods. employee tax data not found). Check for payroll messages or other errors. PAYCHECK_STATUS is set to ‘C’ for calculated. Calculation error. Messages from the prior run are deleted by company. new employees that were hired since PAYSHEET or CALCPAY were last run).3 Payroll for North America Troubleshooting Guidelines Tables That the CALCPAY Process Updates PS_PAY_CALENDAR The PAY_PRECALC_RUN flag is set to ‘Y’ when a preliminary calculation process runs successfully. The PAY_CALC_RUN flag is set to ‘Y’ when a final calculation process runs successfully. new employees that were hired since PAYSHEET or CALCPAY were last run). When a check is recalculated. taxes. Earnings or other paysheet fields might be updated as a result of a job change or new hires made since paysheets or CALCPAY were last run.’ New records might be added to this table as a result of the paysheet update process (in other words. It then reinserts into these tables. See Also PeopleSoft 8. pay end date. Other earnings might be updated as a result of a change on the Additional Pay Data pages. Page number is also used in off-cycle check processing. This check is recalculated when CALCPAY is rerun. The PAY_LINE_STATUS is updated as follows: Calculated successfully. “Calculating Pay” PeopleSoft Proprietary and Confidential 23 . PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS C E P PS_PAY_OTH_EARNS PS_PAY_CHECK Tables From Which the CALCPAY Process Deletes PS_PAY_CALC_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. New records might be added to this table as a result of the paysheet update process (in other words.PeopleSoft Payroll for North America PeopleSoft 8. You aren’t allowed to run the CONFIRM process until the PAY_CALC_RUN flag is set to ‘Y. the process deletes the old entries from the paysheet tables that were inserted into above. pay group. and off-cycle indicator. An error occurred that prevented CALCPAY from completing.3 Payroll for North America PeopleBook. Earnings. or deduction amounts might be updated as a result of a change on the paysheet. Special accumulator amounts for the calendar being processed are selected. In addition. it can be rerun and the process continues processing where it left off (after the last commit to the database).PeopleSoft Payroll for North America PeopleSoft 8. Tables From Which the CONFIRM Process Selects PS_PAY_CONF_RUNCTL The process selects the run control record that is added by the user prior to running the process. If an error occurs during this process. Taxes taken for the calendar being processed are selected (Canadian only). because this process cannot simply be rerun once it has completed. The system also assigns check and advice numbers.3 Application Fundamentals for HRMS PeopleBook.3 Payroll for North America Troubleshooting Guidelines PeopleSoft 8. Paychecks where PAYCHECK_STATUS = ‘C’ are selected. the process selects the appropriate pay calendar information. garnishments. Using the Run Control ID. Lines for the calendar being processed are selected. Taxes taken for the calendar being processed are selected.3 Payroll for North America PeopleBook. this process deletes all paysheet and paycheck records for those paysheets where OK_TO_PAY = ‘N’ on the PAY_EARNINGS record. No history of these records is kept. Points to Consider When Running the CONFIRM Process • • You should back up the database before running CONFIRM. taxes. deductions. “Appendix B: Configuring Batch Processes” CONFIRM During the Pay Confirmation process. The process selects the Balance ID for the calendar year. Pay earnings where PAY_LINE_STATUS = ‘C’ are selected. the system updates all balances for earnings. This is necessary. PS_PAY_CALENDAR PS_INSTALLATION PS_PAY_PAGE PS_PAY_LINE PS_PAY_CHECK PS_PAY_EARNINGS PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS PS_PAY_TAX PS_PAY_TAX_CAN PeopleSoft Proprietary and Confidential 24 . and arrears. “Setting Up Payroll Tax Tables” PeopleSoft 8. Unemployment insurable earnings for the calendar being processed are selected (Canadian only). Pages for the calendar being processed are selected. Earnings balances are updated with earnings and special accumulator data for the current period. Canadian version of PS_EARNINGS_BAL. This balance table is updated with the current period check information. depending on the payroll cycle being run. Garnishment balances are updated with the current period amounts. * These tables might be inserted into or updated. Deductions taken for the calendar being processed are selected. Canadian version of PS_DEDUCTION_BAL.3 Payroll for North America Troubleshooting Guidelines PS_PAY_GARNISH PS_PAY_DEDUCTION Garnishments taken for the calendar being processed are selected. Deduction balances are updated with the current period amounts. This table is updated with the check information that is later used by the check reconciliation process.PeopleSoft Payroll for North America PeopleSoft 8. This process also selects from some employee and pay process tables. The pay distribution table is updated with PeopleSoft Proprietary and Confidential 25 . Unemployment insurable earnings balances are updated with the current period amounts (Canadian only). Canadian version of PS_CHECK_YTD. This table is updated with standard payroll error messages that are encountered during the process. Tax balances are updated with the current period amounts. Tables Into Which the CONFIRM Process Inserts PS_BOND_LOG* PS_PAY_DISTRIBUTN The bond log table is updated with bond deductions taken in the current period. Canadian version of PS_TAX_BALANCE. Tables Into Which the CONFIRM Process Inserts PS_BOND_LOG* PS_PAY_DISTRIBUTN PS_PAY_MESSAGE PS_PAY_CHECK_DUE PS_CHECK_YTD* PS_EARNINGS_BAL* PS_DEDUCTION_BAL* PS_TAX_BALANCE* PS_GARN_BALANCE* PS_CAN_CHECK_YTD* PS_CAN_ERN_BALANCE* PS_CAN_DED_BALANCE* PS_CAN_TAX_BALANCE* PS_INS_EARNS_BAL The bond log table is updated with bond deductions taken in the current period. The pay distribution table is updated with check and advice information. PS_PAY_CHECK_DUE PS_CHECK_YTD* PS_EARNINGS_BAL* PS_DEDUCTION_BAL* PS_TAX_BALANCE* PS_GARN_BALANCE* PS_CAN_CHECK_YTD* PS_CAN_ERN_BALANCE* PS_CAN_DED_BALANCE* PS_CAN_TAX_BALANCE* PS_INS_EARNS_BAL Tables the CONFIRM Process Updates PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_CHECK PS_DED_ARREARS PS_ADDL_PAY_DATA PS_GARN_SPEC PS_GENL_DEDUCTION CONFIRMED flag is set to ‘Y. Tax balances are updated with the current period amounts.’ Deduction arrears balances are updated to reflect the current arrears balances. Canadian version of PS_TAX_BALANCE. This balance table is updated with the current period check information. Deduction balances are updated with the current period amounts. Additional pay data is updated to reflect the new goal balance (GOAL_BAL). Garnishment balances are updated with the current period amounts. Canadian version of PS_CHECK_YTD. This table is updated with the check information that is later used by the check reconciliation process. Canadian version of PS_EARNINGS_BAL.PeopleSoft Payroll for North America PeopleSoft 8. Unemployment insurable earnings balances are updated with the current period amounts (Canadian only). Garnishment specification data is updated to reflect the new limit balance (GARN_LIMIT_BAL).’ CONFIRMED flag is set to ‘Y.3 Payroll for North America Troubleshooting Guidelines check and advice information. Earnings balances are updated with earnings and special accumulator data for the current period. Employee general deduction data is updated to reflect PeopleSoft Proprietary and Confidential 26 .’ PAY_LINE_STATUS is set to ‘F.’ PAYCHECK_STATUS is set to ‘F. PS_PAY_MESSAGE This table is updated with standard payroll error messages that are encountered during the process. Canadian version of PS_DEDUCTION_BAL. Messages from the prior run are deleted by company. (Canadian version of PS_PAY_TAX. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted.3 Payroll for North America Troubleshooting Guidelines the new goal balance (GOAL_BAL). A leave accrual record is inserted. Unprocessed data fields are updated on employee leave accrual records. PS_VACATION_BEN PS_LEAVE_ACCRUAL Employee vacation benefit table is updated to reflect the new goal balance (GOAL_BAL). Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. pay group. Page number is also used for off-cycle check processing. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. The PAY_CONFIRM_RUN flag is set to ‘Y’ when the process runs to completion successfully. PS_PAY_FORM_TBL PS_PAY_CALENDAR Tables From Which the CONFIRM Process Deletes PS_PAY_CONF_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. The LAST_FORM#_USED is updated on the form table. The PAY_CONFIRM_START flag is set to ‘Y’ when the process is started initially. Records where OK_TO_PAY = ‘N’ are deleted. if the employee has not yet been processed through the ACCRUAL process. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. and off-cycle indicator. Records whose PS_PAY_LINE entries are no longer there. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted.) PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_PAY_GARN_OVRD PS_PAY_DEDUCTION PS_PAY_TAX PS_PAY_TAX_CAN PeopleSoft Proprietary and Confidential 27 . Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted.PeopleSoft Payroll for North America PeopleSoft 8. pay end date. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Tables From Which the CONFIRM Process Deletes PS_PAY_CONF_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. and off-cycle indicator.PeopleSoft Payroll for North America PeopleSoft 8. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted (Canadian only). Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. (Canadian version of PS_PAY_TAX. Page number is also used for off-cycle check processing. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. pay end date. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted.) Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted.3 Payroll for North America Troubleshooting Guidelines PS_PAY_GARNISH PS_PAY_CHECK PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS Records whose PS_PAY_EARNINGS have OK_TO_PAY = ‘N’ are deleted. Records where OK_TO_PAY = 'N' are deleted. Messages from the prior run are deleted by company. Records whose PS_PAY_LINE entries are no longer there. PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_PAY_GARN_OVRD PS_PAY_DEDUCTION PS_PAY_TAX PS_PAY_TAX_CAN PS_PAY_GARNISH PeopleSoft Proprietary and Confidential 28 . pay group. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted (Canadian only). The process selects the run control record that is added by the user prior to running the process. Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted. In this case. you need to do a manual check to back out the amounts. Tables From Which the REVERSAL Process Selects PS_PAY_CALENDAR PS_PAY_REV_RUNCTL The current calendar that the off-cycle reversal is processed with is selected. The deductions taken on the original check are selected. This is the parent record on the run control page. See Also PeopleSoft 8. The taxes taken on the original check are selected. The other earnings on the original check are selected. “(USF) Setting Up and Processing Agency Interfaces” REVERSAL You use the REVERSAL (Paycheck Reversal) process to create a reversal paysheet or a reversal/adjustment paysheet. This is the child record on the run control page. The line of the original check is selected. Points to Consider When Running the REVERSAL Process • • You cannot reverse a check that was not confirmed in the PeopleSoft system. All reversals are automatically created as off-cycle checks. If you create a reversal only. After creating a reversal/adjustment. The check(s) to be reversed or adjusted are selected.3 Payroll for North America PeopleBook. PS_PAY_CHECK_REVRS PS_PAY_CHECK PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_DEDUCTION PS_PAY_TAX PeopleSoft Proprietary and Confidential 29 .3 Payroll for North America Troubleshooting Guidelines PS_PAY_CHECK PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS Records whose PS_PAY_EARNINGS have OK_TO_PAY = 'N' are deleted.PeopleSoft Payroll for North America PeopleSoft 8. The process selects the run control record that is added by the user. you only need to run the CONFIRM process for the off-cycle reversal paysheet. you must run the CALCPAY process and the CONFIRM process for the off-cycle reversal/adjustment. The page of the original check is selected. The earnings on the original check are selected. The garnishment overrides on the original check are selected. but the amounts are negated. This record is created with the original other earnings amounts. but the amounts are negated. The tax overrides on the original check are selected. The reversal is inserted on a new line associated with the current off-cycle calendar. but the amounts are negated. but the amounts are negated (Canadian version of PS_PAY_TAX). but the amounts are negated. This record is created with the original taxes taken. The earnings that updated the special accumulators on the original check are selected. The Canadian tax overrides on the original check are selected.3 Payroll for North America Troubleshooting Guidelines PS_PAY_TAX_CAN PS_PAY_GARNISH PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_PAY_GARN_OVRD PS_PAY_INS_EARNS PS_PAY_SPCL_EARNS The taxes taken on the original check are selected (Canadian version of PS_PAY_TAX). This record is created with the original earnings that updated the special accumulators. but the amounts are negated. This record is created with the original taxes taken. This record is created with the original earnings amounts.PeopleSoft Payroll for North America PeopleSoft 8. This record is created with the original unemployment insurable earnings. The unemployment insurable earnings on the original check are selected (Canadian only). The reversal is inserted on a new page associated with the current off-cycle calendar. The deduction overrides on the original check are selected. This record is created with the original garnishments PS_PAY_INS_EARNS PS_PAY_DEDUCTION PS_PAY_TAX PS_PAY_TAX_CAN PS_PAY_GARNISH PeopleSoft Proprietary and Confidential 30 . The garnishments taken on the original check are selected. This record is created with the original deductions taken. but the amounts are negated. Tables Into Which the REVERSAL Process Inserts PS_PAY_CHECK PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_SPCL_EARNS The reversal check is inserted. DEAD_CHECK_REASON. but the amounts are negated. This record is created with the original tax overrides. you can run the report that actually reprints the checks (PAY003) or advices (DDP003).PeopleSoft Payroll for North America PeopleSoft 8. so the new check and advice numbers can be assigned. Page number is also used in off-cycle check processing. The LAST_FORM#_USED is selected for each form. PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD This record is created with the original deduction overrides. but the amounts are negated.3 Payroll for North America Troubleshooting Guidelines taken. but the amounts are negated. This record is created with the original garnishment overrides. CHECK#. and off-cycle indicator. Tables Into Which the REPRINT Process Inserts PS_PAY_CHECK_DEAD This table is updated with the FORM_ID. Messages from the prior run are deleted by company. The checks/advices to be reprinted are selected. but the amounts are negated. but the amounts are negated (Canadian version of PS_PAY_TAX_OVRD). pay group. and CHECK#_REPLACED_BY information of checks that are reprinted. See Also PeopleTools PeopleBook: Process Scheduler. PS_PAY_GARN_OVRD Tables From Which the REVERSAL Process Deletes PS_PAY_REV_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated. This record is created with the original tax overrides. PeopleSoft Proprietary and Confidential 31 . pay end date. Once this is complete. Tables From Which the REPRINT Process Selects PS_PAY_PRNT_RUNCTL PS_PAY_CHECK PS_PAY_FORM_TBL The process selects the run control record that is added by the user prior to running the process. “Submitting a Process Request” REPRINT The REPRINT (Paycheck Reprint) process enables you to reassign check numbers for one or more checks or advices. It is very important that you understand exactly what records are selected for deletion by PAYUNSHT. PAYUNSHT is typically used in a testing environment. Tables From Which the REPRINT Process Deletes PS_PAY_PRNT_RUNCTL PS_PAY_MESSAGE The run control is deleted after the process is initiated.3 Payroll for North America Troubleshooting Guidelines Tables That the REPRINT Process Updates PS_PAY_CHECK PS_PAY_DISTRIBUTN PS_PAY_FORM_TBL This table is updated with the new CHECK# assigned by the REPRINT process. pay group. pay end date. Messages from the prior run are deleted by company.PeopleSoft Payroll for North America PeopleSoft 8. This table is updated with the new LAST_FORM#_USED after check/advice numbers have been reassigned. It might be used if there is a high-level table change that affects the way paysheets are created. because it allows users to rerun paysheets multiple times for the same period.3 Payroll for North America PeopleBook. To run this process you execute the SQR PAYUNSHT as you would any other SQR. This process is necessary if you change the Location Table after creating paysheets. See Also PeopleSoft 8. PAYUNSHT is rarely used. including the results of any Pay Calculations run on those paysheets. In a production environment. Page number is also used in off-cycle check processing. the process selects the calendar whose paysheet records is deleted. and off-cycle indicator. We recommend that you call the PeopleSoft Global Support Center before running this process in a production environment. PeopleSoft Proprietary and Confidential 32 . This table is updated with the new CHECK# assigned by the REPRINT process. “Working with Checks” PAYUNSHT The PAYUNSHT (Payunsheet) process is an SQR that deletes all records associated with a specified Run ID. Note. Tables From Which the PAYUNSHT Process Selects PS_PAY_CALENDAR Using the Run Control ID entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered (Canadian version of PS_PAY_TAX). Records are deleted that are associated with the Run ID that was entered (Canadian only). Records are deleted that are associated PeopleSoft Proprietary and Confidential 33 . Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered.PeopleSoft Payroll for North America PeopleSoft 8. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. PS_PAY_GARNISH PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS Tables From Which the PAYUNSHT Process Deletes PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered.3 Payroll for North America Troubleshooting Guidelines Tables From Which the PAYUNSHT Process Deletes PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_OTH_EARNS PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_PAY_GARN_OVRD PS_PAY_CHECK PS_PAY_DEDUCTION PS_PAY_TAX PS_PAY_TAX_CAN Records are deleted that are associated with the Run ID that was entered. PeopleSoft Proprietary and Confidential 34 . In a production environment. Records are deleted that are associated with the Run ID that was entered (Canadian only). PS_PAY_ONE_TIME PS_PAY_TAX_OVRD PS_PAY_CTX_OVRD PS_PAY_GARN_OVRD PS_PAY_CHECK PS_PAY_DEDUCTION PS_PAY_TAX PS_PAY_TAX_CAN Records are deleted that are associated with the Run ID that was entered. you execute the process for UNCNFRM. This is the same page you use to set up a run control to run CONFIRM.PeopleSoft Payroll for North America PeopleSoft 8. It might be used if there is a high-level table change that requires the recalculation of all paychecks. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered.3 Payroll for North America Troubleshooting Guidelines with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. PS_PAY_GARNISH PS_PAY_SPCL_EARNS PS_PAY_INS_EARNS UNCNFRM The UNCNFRM (Pay Unconfirmation) process is used to unconfirm a payroll cycle that has been confirmed. you set up a run control using the Pay Confirmation Run Control page. Records are deleted that are associated with the Run ID that was entered (Canadian version of PS_PAY_TAX). 3. 2. To run this process. because it enables users to rerun a payroll cycle once it has been confirmed. Records are deleted that are associated with the Run ID that was entered. UNCNFRM is typically used in a testing environment. Next. this process is rarely used. Records are deleted that are associated with the Run ID that was entered. Backs out all of the detail from the employee balance tables for the specified payroll cycle. Records are deleted that are associated with the Run ID that was entered. Resets the status on the paysheet records to a calculated status. Records are deleted that are associated with the Run ID that was entered. Records are deleted that are associated with the Run ID that was entered. Updates the pay calendar to reflect that CONFIRM has not been run. This process completes the following steps: 1. We recommend that you call the PeopleSoft Global Support Center before running this process in a production environment. depending on the actual situation. The process selects the Balance ID for the calendar year. Using the Run ID. The PS_PAY_FORM_TBL might need to be updated manually. the process selects the appropriate pay calendar information. Amounts added by CONFIRM are backed out. The PeopleSoft Proprietary and Confidential 35 .’ Fields such as LOCATION. Tables the UNCNFRM Process Updates PS_PAY_CALENDAR PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_CHECK PS_EARNINGS_BAL PS_DEDUCTION_BAL PS_TAX_BALANCE PS_GARN_BALANCE PS_CHECK_YTD PS_DED_ARREARS PS_CAN_CHECK_YTD* PS_CAN_ERN_BALANCE* The PAY_CONFIRM_START flag is set to ‘N’ and the PAY_CONFIRM_RUN flag is set to ‘Y. The amounts added by CONFIRM are backed out. you must rerun CALCPAY.’ The CONFIRMED flag is set to ‘N. The amounts added by CONFIRM are backed out.PeopleSoft Payroll for North America PeopleSoft 8. The amounts added by CONFIRM are backed out. • The CONFIRM process deletes paysheet records where OK_TO_PAY = ‘N. CHECK#. Canadian version of PS_EARNINGS_BAL. The amounts added by CONFIRM are backed out.3 Payroll for North America Troubleshooting Guidelines Important! It is crucial that you understand exactly what UNCNFRM does in your particular situation before using it. Points to Consider When Running the UNCNFRM Process • After running UNCNFRM. Otherwise.’ The PAY_LINE_STATUS is set to ‘C.’ The CONFIRMED flag is set to ‘N. The recovery steps necessary might differ. The amounts added by CONFIRM are backed out.’ The PAYCHECK_STATUS is set to ‘C.’ The UNCONFIRM process does not add these records back. so CONFIRM can reassign the check numbers correctly. and CHECK_DT are blank. we recommend that you run a backup before you run the CONFIRM process. Canadian version of PS_CHECK_YTD. the location field on PS_PAY_CHECK isn’t repopulated. Therefore. The amounts added by CONFIRM are backed out. Tables From Which the UNCNFRM Process Selects PS_PAY_CONF_RUNCTL PS_PAY_CALENDAR PS_INSTALLATION The process selects the run control record that is added by the user prior to running the process. CHECK#. and CHECK_DT are blank.PeopleSoft Payroll for North America PeopleSoft 8.3 Payroll for North America Troubleshooting Guidelines amounts added by CONFIRM are backed out.' The CONFIRMED flag is set to 'N. Canadian version of PS_CHECK_YTD. Canadian version of PS_EARNINGS_BAL. Tables the UNCNFRM Process Updates PS_PAY_CALENDAR The PAY_CONFIRM_START flag is set to 'N' and the PAY_CONFIRM_RUN flag is set to 'Y. The amounts added by CONFIRM are backed out. The amounts added by CONFIRM are backed out (Canadian only). The amounts added by CONFIRM are backed out. The amounts added by CONFIRM are backed out. Canadian version of PS_TAX_BALANCE. The amounts added by CONFIRM are backed out. Canadian version of PS_DEDUCTION_BAL. PS_CAN_DED_BALANCE* PS_CAN_TAX_BALANCE* PS_INS_EARNS_BAL Canadian version of PS_DEDUCTION_BAL. The amounts added by CONFIRM are PS_PAY_PAGE PS_PAY_LINE PS_PAY_EARNINGS PS_PAY_CHECK PS_EARNINGS_BAL PS_DEDUCTION_BAL PS_TAX_BALANCE PS_GARN_BALANCE PS_CHECK_YTD PS_DED_ARREARS PS_CAN_CHECK_YTD* PS_CAN_ERN_BALANCE* PS_CAN_DED_BALANCE* PS_CAN_TAX_BALANCE* PeopleSoft Proprietary and Confidential 36 . The amounts added by CONFIRM are backed out.' The PAYCHECK_STATUS is set to 'C. Amounts added by CONFIRM are backed out.' The CONFIRMED flag is set to 'N. The amounts added by CONFIRM are backed out. The amounts added by CONFIRM are backed out. Canadian version of PS_TAX_BALANCE. The amounts added by CONFIRM are backed out. The amounts added by CONFIRM are backed out. The amounts added by CONFIRM are backed out.' The PAY_LINE_STATUS is set to 'C.' Fields such as LOCATION. SQR This SQR reports inconsistencies between the PeopleTools tables (for example. Page number is also used for off-cycle check processing. Traces These tools for tracking errors are found at several levels your system architecture. pay group. Exceptions reported here should be reported to the Global Support Center for resolution. They are especially useful for identifying missing tables and orphaned records. In this section. pay end date. and off-cycle indicator. we discuss: • • • Audit programs. This section provides an overview of how you can use these tools.3 Payroll for North America Troubleshooting Guidelines backed out. DDDAUDIT is discussed in more detail in your PeopleSoft PeopleTools documentation. PSRECDEFN and PSPNLDEFN) and the System Tables (such as. PS_INS_EARNS_BAL The amounts added by CONFIRM are backed out (Canadian only). PeopleSoft Proprietary and Confidential 37 . Such inconsistencies can cause online errors as well as errors in the payroll processes. SYSTABLES and SYSCOLUMNS). Traces.SQR This SQR reports inconsistencies within the PeopleTools tables. Audit Programs These programs check the validity of the employee data and the table setup for payroll and benefits.PeopleSoft Payroll for North America PeopleSoft 8. SYSAUDIT is discussed in more detail in your PeopleSoft PeopleTools documentation. *These tables may be inserted into or updated depending on the payroll cycle being run. Troubleshooting Tools PeopleSoft provides a variety of tools to help with your troubleshooting. Tracking payroll errors. SYSAUDIT. Tables From Which the UNCNFRM Process Deletes PS_PAY_MESSAGE Messages from the prior run are deleted by company. DDDAUDIT. LINE#=001. GET-NEXT-JOB (PSPPARRY) 00001 end of fetch BUILD-PAYSHEETS (PSPPYSHT) 00001 end of fetch In the above error. It is used to determine exactly what data is being selected. Use. Use. inserted. You would initiate the trace from the page right before you execute the transaction you want to trace. Utilities. You receive the “Check Messages” message. and deleted from the database.. You activate this trace by navigating to PeopleTools. When a standard payroll error occurs. It is useful in determining whether the PeopleCode being executed is correct. EMPLID=99999. the default settings are sufficient for tracing the PeopleCode activity. Debugging Standard Payroll Error Messages It is common to receive standard payroll error messages when running a payroll process. “Trace SQL” Tracking Payroll Errors Finding the reason for the error may involve identifying and reviewing the relevant program code. The trace stays on until you turn it off or close all PeopleSoft menus. At times. you minimize the size of the trace. Normally this trace is turned on right before you execute the transaction that you want to trace. PSPPARRY. Trace PeopleCode and selecting the level of trace you require. updated.3 Payroll for North America Troubleshooting Guidelines PeopleCode Trace This trace captures all PeopleCode that is executed online by the client. The program that generates the error is PSPPYGEM. The other programs are listed because they are called prior to PSPPYGEM. and message data. it’s useful to start at the end of the trace and work your way back to the beginning.. You do not have to turn it on at the beginning of your PeopleSoft session. SQL Trace A SQL trace captures all SQL statements that are executed during an online session. and the procedure that is executing is LOAD_JOB. Interpreting the Error Sometimes when you receive an error.. it references many programs. Following are some considerations on finding and debugging payroll errors. This way. Trace SQLPeopleCode and selecting the level of trace you require. and PSPPYSHT. How do you know which program actually generated the error? Below is an example of an error: LOAD-JOB (PSPPYGEM) 00001 end of fetch PAGE#=00001. You activate this trace by navigating to PeopleTools. PeopleSoft Proprietary and Confidential 38 . erroneous data can mimic a programming problem.. message description. Typically. When reviewing the output of the trace.. you receive a Message ID. three programs are identified: PSPPYGEM. though. Utilities. “Trace PeopleCode” PeopleTools PeopleBook: Data Management.PeopleSoft Payroll for North America PeopleSoft 8. See Also PeopleTools PeopleBook: Data Management. sometimes it’s difficult to determine the exact conditions that cause a standard payroll error. if the message data does not provide enough information. * * ************************************************************** COMPANY OF PSLCT TO COMPANY OF S-CHKCAL PAYGROUP OF PSLCT TO PAYGROUP OF S-CHKCAL PAY-END-DT OF PSLCT TO PAY-END-DT OF S-CHKCAL RUN-ID OF PSLCT TO RUN-ID OF BIND-DATA OF S-CHKCAL **** MOVE MOVE MOVE MOVE CALL ‘PTPSQLRT’ USING ACTION-SELECT OF SQLRT SQLRT SQL-CURSOR-COMMON OF SQLRT SQL-STMT OF S-CHKCAL BIND-SETUP OF S-CHKCAL BIND-DATA OF S-CHKCAL SELECT-SETUP OF S-CHKCAL SELECT-DATA OF S-CHKCAL IF RTNCD-ERROR OF SQLRT MOVE ‘CHECK-CONFIRM(SELECT)’ PERFORM ZZ000-SQL-ERROR END-IF INITIALIZE SELECT-DATA OF S-CHKCAL CALL ‘PTPSQLRT’ USING ACTION-FETCH OF SQLRT SQLRT SQL-CURSOR-COMMON OF SQLRT IF RTNCD-ERROR OF SQLRT IF RTNCD-END OF SQLRT SET RTNCD-OK OF SQLRT TO TRUE TO ERR-SECTION OF SQLRT PeopleSoft Proprietary and Confidential 39 . JD000.3 Payroll for North America Troubleshooting Guidelines The message data points to the problem.XRF COBOL cross-reference report. Using the steps below.Prior Run Not Confirmed: PSPPYGRP NOT-CONFIRMED 000064 2. and EMPLID. Review the COBOL program(s) to find what condition from Step 1 above causes the error.PeopleSoft Payroll for North America PeopleSoft 8. One way to determine what is causing the error is to check the COBOL program that issues the error. Examples of message data are RunID. However. Locate the error message number on the MSGIDPAY. you can track the cause of these errors. this is the COBOL calling this error: ************************************************************* **** * * JD000-CHECK-CONFIRM SECTION. Alternatively. Typically it is the result of a SQL statement. you can look up the message in COBOL copy member PSCPYMSG. As an example. For error 64. 1. here is the information for Payroll Error 64 . benefit plan.CBL and then scan your COBOL code for the 88 level name for that error message. deduction code. This gives the program(s) that generates this error. these statements are stored in the PS_SQLSTMT_TBL by statement name. pay group. 3. The error occurs when the statement PSPPYGRP_S_CHKCAL returns one or more rows. erroneous data that was converted from an SQR that did not perform the normal online edit checking. Run a trace that identifies the SQL statement that is executing when the error occurs. For all other platforms.PeopleSoft Payroll for North America PeopleSoft 8. many times they are caused by erroneous data that the program is not designed to trap. 2. Correct all exceptions that are reported. 4.3 Payroll for North America Troubleshooting Guidelines ELSE MOVE ‘CHECK-CONFIRM(FETCH)’ TO ERR-SECTION OF SQLRT PERFORM ZZ000-SQL-ERROR END-IF ELSE SET MSGID-NOT-CONFIRMED OF PYMSG TO TRUE MOVE RUN-ID OF SELECT-DATA OF S-CHKCAL TO MSGDATA1 OF PYMSG PERFORM ZM000-MESSAGE SET RTNCD-USER OF SQLRT TO TRUE END-IF . Below are some things you can do to narrow down the condition that is causing the error: 1. and pay end date of the calendar you are processing. Debugging SQL and Database Errors These errors are the most difficult to track down. you specify the company. for example. Here is the SQL statement that generates error 64: STORE PSPPYGRP_S_CHKCAL SELECT RUN_ID FROM PS_PAY_CALENDAR WHERE COMPANY=:1 AND PAYGROUP=:2 AND PAY_END_DT<=:3 AND RUN_ID<>’ ‘ AND RUN_ID<>:4 AND (PAY_CONFIRM_RUN=’N’ OR PAY_OFF_CYCLE=’Y’) . these statements are stored in the SYSCOMMANDS table by statement name. However. Run the audit programs described in this section. CHECK-CONFIRM-EXIT. You need to fill in the bind variables based on the information you are processing. On the SQLBase platform. they can only be resolved by reviewing the COBOL and possibly adding display statements. They are designed to identify erroneous data. You can then execute this statement manually using a query tool such as SQLTalk. In this example. Review the SQL stored statement to determine what condition is being met. At times. PeopleSoft Proprietary and Confidential 40 . PeopleSoft Proprietary and Confidential 41 . It is useful to query these status fields to get an overall picture of where the payroll process is for one or all checks. In some cases. Review the error and determine the program and procedure that is executing when the error occurs. You can then look more closely at this employee. only the PS_PAY_CHECK table still shows the check as calculated.PeopleSoft Payroll for North America PeopleSoft 8. and you can research it after the payroll is complete. 3. and the data doesn’t cause a problem until the current program uses it. However. This might show exactly what SQL statement is executing. Key Status Fields There are four fields that determine the overall status of a paycheck: • • • • PAY_LINE_STATUS of PS_PAY_EARNINGS PAYCHECK_STATUS of PS_PAY_CHECK CONFIRMED of PS_PAY_LINE CONFIRMED of PS_PAY_PAGE The programs to determine what has been processed so far and what still needs to be processed use these fields. after an error occurs. if you get a “duplicate on insert” in CONFIRM when updating balances. The other tables show that the check is confirmed. This is what enables the processes to be run again and to continue where they leave off if an error occurs. sometimes the SQL statement is executed in a previous program. For example. Or you may decide to mark this employee Not Pay.3 Payroll for North America Troubleshooting Guidelines The trace may give the values of the bind variables that identify the employee on which the error is occurring. some of statuses will have been updated and others will not have been updated. This prevents holding up the payroll for one employee.