Detecting Errors

To determine whether an error has occurred after running the Calculate Deductions or Deduction Confirmation processes, first refer to the Review Deductions and Review Error Messages components.

See Reviewing Deductions.

To determine whether an error has occurred after running the Export or Import processes, first refer to the Error Messages (PI_MESSAGES) component and various reporting components.

See Reviewing Exports or Imports.

Error Messages

If the explanation in the Error Message component is not clear, you can use the message number to determine where in the COBOL routine the problem occurred. For example, suppose message 004030 returns the following information:

The Dedcalc process was not confirmed. This data is not available until the confirm is processed. The message data below identifies 2 field values. 1. Company 2. Paygroup.

To locate the problem:

  1. Search for 004030 in PSCPYMSG.CBL to determine the corresponding 88 level name for MSGID.

    In this case, it is MSGID-DEDCALC-NOT-CONFIRMED.

  2. Using a search tool, do a search against PI*.CBL to look for all the occurrences of MSGID-DEDCALC-NOT-CONFIRMED.

    The result is in PIPINRUN.CBL, paragraph MM100-CONFIRM-DEDCALC.

The location of the error in the COBOL routine may point to a SQL statement or array search that may give additional clues to the problem.

Error: Dynamic SQL Failure Due to Invalid PS Table Setup

If you use PeopleSoft Application Designer to change any of the tables or fields that are set up in the PS Tables (PS_TABLES) component, you must make sure that these changes are reflected in the PS Tables component as well. If you do not, the Export process will end when attempting to run the dynamically created SQL statement. If it is not obvious which table or field is causing the error, you can run the Export process from a DOS prompt.

To run PIPINRUN from the DOS prompt:

  1. From the DOS prompt, run PIPINRUN with the SQL Trace turned on.

  2. At the SQL Trace prompt, enter 191.

    A trace file is written to C:\TEMP\PS\<dbname>\COBSQL_. The SQL causing the process to end should be toward the end of the trace file with a SQL statement name such as S_JOB, S_GENL_DEDUCTION, and so on.

  3. Copy the SQL to the database's SQL Inquiry tool and run it using the parameters listed below the statement in the trace file.

    The SQL Inquiry tool should point to the problem field.

See PeopleTools: Application Designer Developer’s Guide

Error: Maximum Number of Export Records Exceeded for EMPLID

PIEXPT-COUNT-MAX represents the maximum number of records that can be generated for an EMPLID. During the Export process, this maximum number can be reached when you are processing files that comprise a high number of rows in PS_JOB.

PIEXPT-COUNT-MAX is set to 200 by default. If you want to increase this number, you need to modify to the COBOL in two places:

  • In PICIEXPT.CBL, insert the desired number where you see 200 in bold.

    88 PIEXPT-COUNT-MAX VALUE 200

  • In PIPIEXPT.CBL, insert the desired number where you see 200 in bold.

    02 PIEXPT-DATA OCCURS 200

Be sure to recompile the programs when you are done.

You may encounter similar error messages for "Maximum number of export records exceeded." Again, just follow the code line through and increase the 88 VALUE and the corresponding OCCURS values.