Character

CHAR

Alphanumeric; fixed length.

Long character

LONGVAR

Alphanumeric; variable length.

Date

DATE

Dates; stored as fixed length; displayed in various formats.

Number or signed number

SMALLINT

Numeric; integers only (no decimals); 1 to 4 digits (and 5 digits if RawBinary).

Number or signed number

INTEGER

Numeric; integers only (no decimals); 5 to 9 digits (and 10 digits if RawBinary).

Number or signed number

DECIMAL

Numeric; either (1) 10 or more digits or (2) contains decimal positions.

INDEX-1

Indexes are defined in PeopleSoft Application Designer and not found in the database.

Use PeopleSoft Application Designer to create the index.

INDEX-2

Indexes are defined in the database and not found in PeopleSoft Application Designer.

If the index is valid, use PeopleSoft Application Designer to define the index.

Otherwise, drop the index.

INDEX-3

Uniqueness or the number of keys in the Index Definition do not match between PeopleSoft Application Designer and the database.

See INDEX-1.

TABLE-1

SQL table names are defined in the Data Designer that are not blank and not the same as the record name.

Use Application Designer to enter the record name as the Non-Standard SQL Table Name.

TABLE-2

SQL tables are defined in the Data Designer and not found in the database.

If you want to delete the record definition, use PeopleSoft Application Designer (select File, Delete).

Otherwise, to create the SQL table, use Application Designer. This command also creates the appropriate indexes for keys, duplicate order keys, alternate keys, and list items.

TABLE-3

SQL tables are defined in the database and not found in the Data Designer.

SYSINDEXES and SYSTABLES can be ignored in these results.

For Informix: PSALTERLONG can also be ignored.

If the table is not valid, drop it.

Otherwise, define a new record in PeopleSoft Application Designer.

TABLE-4

Tablespace is not defined for the SQL table in PeopleSoft Application Designer.

If you're using or migrating to a relational database management system that uses table spaces, you should use PeopleSoft Application Designer to assign table spaces to these tables.

TABLE-5

Table contains more than 500 fields.

Use PeopleSoft Application Designer to adjust the number of fields on the table, as needed.

VIEWS-1

Views are defined in the Data Designer and not found in the database.

If you want to delete the view definition, use PeopleSoft Application Designer (select File, Delete).

Otherwise, to create the SQL view, use Application Designer.

VIEWS-2

Views are defined in the database and not found in the Data Designer.

If the view is not valid, Drop it.

Otherwise, define a new view in PeopleSoft Application Designer.

TRIGGER-1

Trigger defined in the PeopleSoft Application Designer and not found in the database.

Delete the definition if it is not needed.

Otherwise, use PeopleSoft Application Designer to create the trigger in the database.

Audit AE Integrity

Audits PeopleSoft Application Engine program definitions and components.

Audit Clear List Integrity

Audits the SYSCLRLIST* component.

Audit EDI Manager Integrity

Audits the EC* component for EDI Manager.

Audit Field Integrity

Audits the DBFLD* component for PeopleSoft Application Designer fields.

Audit Integration Broker

Runs a collection of audits to on the Integration Broker configuration.

Audit Menu Integrity

Audits the MENU* component for PeopleSoft Application Designer menus.

Audit Optimization Integrity

Audits the definitions for Optimization Engine.

Audit Page Integrity

Audits the PNL* component for PeopleSoft Application Designer pages.

Audit PeopleCode Integrity

Audits the PCM* and PRG* components for PeopleCode programs.

Audit Query Integrity

Audits the QRY* component for PeopleSoft Query.

Audit Record Integrity

Audits the REC* and VIEWT* components for PeopleSoft Application Designer records.

Audit Related Lang Integrity

Audits Related Language Integrity. Query the *LANG component.

Audit Security Integrity

Audits the AUTH*, OPRDF* components for PeopleTools Security.

Audit SQL Integrity

Audits the referential integrity of the tables supporting SQL objects in the db component.

Audit Tree Integrity

Audits the TREE* component.

Audit Translates Integrity

Audits the XLAT* component.

Audit PSLOCKS Version Integrity

Audits the VERSN* component.

Audit XML Publisher Integrity

Audits the referential integrity of the tables of the definitions that are associated with XML Publisher.

AE-01

This audit lists the AE programs without any sections.

If the affected program is delivered by PeopleSoft and is not modified, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, use the Application Engine designer to either create valid sections for the program or remove the program. It is not possible to recover the missing sections.

AE-02

This audit lists the AE sections without AE programs.

If the affected program is delivered by PeopleSoft and is not modified, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

If the affected program is a customization, it is not possible to recover the missing program. Restore it from a backup if needed.

Run SysAECleanUp.dms to remove any orphans remaining after you have followed the steps above.

AE-03

This audit lists the AE state records without AE programs.

If the affected record is delivered by PeopleSoft, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, ignore the warnings or restore the program from a backup. It is not possible to recover the missing program.

AE-04

This audit lists the AE state records without record definitions.

If the affected record is delivered by PeopleSoft, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, use Application Designer to remove invalid records from the program definition or create record definitions.

AE-05

This audit lists the AE section details without base section definitions.

If the affected program is delivered by PeopleSoft and is not modified, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, ignore the warnings or restore the program from a backup. It is not possible to recover the missing sections.

AE-06

This audit lists the AE steps without sections.

If the affected program is delivered by PeopleSoft and is not modified, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

If the affected program is a customization, it is not possible to recover the missing program. Restore it from a backup if needed.

Run SysAECleanUp.dms to remove any orphans remaining after you follow the steps above.

AE-07

This audit lists the AE Call Section actions referring to nonexistent sections

If the affected program is delivered by PeopleSoft and is not modified, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, use the Application Engine either to open the program containing the Call Section and change it to call the correct section, or create the required section.

AE-08

This audit lists the AE Log Message actions without an AE step.

If the affected record is delivered by PeopleSoft, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

If the affected program is a customization, it is not possible to recover the missing program; restore it from a backup if needed.

Run SysAECleanUp.dms to remove any orphans remaining after you follow the steps above.

AE-09

This audit lists the AE actions without an AE step.

If the affected record was delivered by PeopleSoft, contact the GSC.

If the affected program was converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

If the affected program is a customization, it is not possible to recover the missing program; restore it from a backup if needed.

Run SysAECleanUp.dms to remove any orphans remaining after you follow the steps above.

AE-10

This audit lists the AE temp tables that are attached to invalid AE programs.

If the affected temp table was delivered by PeopleSoft, contact the GSC.

If the affected program is converted as part of an upgrade, this may be a symptom that the conversion failed. Contact the GSC.

Otherwise, ignore the warnings or restore the program from a backup. It is not possible to recover the missing programs.

AE-11

This audit lists the orphaned AE PeopleCode.

Because of platform issues and Structured Query Report (SQR), this check may not be included in the audit report. Run SysAECleanUp.dms to clean up these orphans.

AE-12

This audit lists the orphaned AE SQL objects.

Because of platform issues and SQR, this check may not be included in the audit report. Run SysAECleanUp.dms to clean up these orphans.

AE-13

This audit verifies that PS_AEONLINEINST contains the correct number of rows.

Run ps_aeonlineinst.dms. If you do not have the Data Mover script, contact the GSC.

AE-14

This audit verifies that PS_AEINSTANCENBR contains the correct number of rows.

Run ps_aeinstancenbr.dms. If you do not have the Data Mover script, contact the GSC.

AE-15

This audit verifies that PS_AELOCKMGR contains a row .

Resolution may vary based on implementation. Contact the GSC.

SYSCLRLIST-01

Entries in PSACTIVITYDEL and PSACTIVITYDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-02

Entries in PSAEAPPLDEL and PSAEAPPLDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-05

Entries in PSCOLORDEL and PSCOLORDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-06

Entries in PSFMTDEL and PSFMTDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-07

Entries in PSHOLIDAYDEL and PSHOLIDAYDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-09

Entries in PSIMPDEL and PSIMPDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-10

Entries in PSMENUDEL and PSMENUDEFN are not mutually exclusive

Run the VERSION Application Engine program.

SYSCLRLIST-11

Entries in PSPCMPROGDEL and PSPCMPROG are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-12

Entries in PSPNLDEL and PSPNLDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-13

Entries in PSPNLGRPDEL and PSPNLGRPDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-14

Entries in PSPRCSRUNCDEL and PSPRCSRUNCNTL are not mutually exclusive

Run the VERSION Application Engine program.

SYSCLRLIST-15

Entries in PSPROJECTDEL and PSPROJECTDEFN are not mutually exclusive

Run the VERSION Application Engine program.

SYSCLRLIST-16

Entries in PSQRYDEL and PSQRYDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-17

Entries in PSRECDEL and PSRECDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-18

Entries in PSRECURDEL and PS_PRCSRECUR are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-19

Entries in PSSTYLEDEL and PSSTYLEDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-20

Entries in PSTOOLBARDEL and PSTOOLBARDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-21

Entries in PSTREEBRADEL and PSTREEBRANCH are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-22

Entries in PSTREEDEL and PSTREEDEFN are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-23

Entries in PSTREESTRDEL and PSTREESTRCT are not mutually exclusive.

Run the VERSION Application Engine program.

SYSCLRLIST-24

Entries in XLATTABLEDEL and XLATTABLE are not mutually exclusive.

Run the VERSION Application Engine program.

ECINMPFL-1

Inbound work records that are not found in the PSRECDEFN table.

Either modify the inbound map definition to not use the Inbound Row ID Work Record (ECINMAPFILE), or create the Work Record Definition.

ECINMPFL-2

Inbound work record EC Map ID is not found in the PS_ECMAPDEFN table.

Create an entry in the map definition table (ECMAPDEFN).

ECINMPFD-1

Inbound work record fields are not found with valid EC Map ID and EC File Row ID combination from the PS_ECINMAPFILE table

Either remove the invalid map ID from the Inbound Work Record (ECINMAPFLD), or create an Inbound Row ID Work Record entry.

ECINMPFD-2

Inbound work record fields from PS_ECINMAPFLD are not found in PSRECFIELD

Either remove the invalid entry in the inbound work record or create the record/field definition.

ECINMPRC-1

Target inbound records are not found in the PSRECDEFN table

Either modify the inbound map definition to not use the Inbound Row ID Target Record (ECINMAPREC), or create the Work Record Definition.

ECINMPRC-2

Target inbound EC Map ID is not found in the PS_ECMAPDEFN table

Either remove the invalid map ID from the Inbound Row ID Target Record or create an entry in the Map Definition table.

ECINMPRF-1

EC Map ID/EC File Row ID combination is not found in PS_ECINMAPREC for the target inbound record field in PS_ECINMAPRECFLD

Remove the invalid map ID from the Inbound Target Record.

ECINMPRF-2

A Field for a Record in PS_ECINMAPRECFLD was not found in PSRECFIELD

Create the appropriate definitions in PSRECFIELD or remove the invalid map ID from the Inbound Target Record.

ECINMPRF-4

A related record in PS_ECINMAPRECFLD is not found in PSRECDEFN

Either create the record definition or remove the reference to the related record in the Inbound Target Record.

ECINMPRF-5

An EC Related Record in PS_ECINMAPRECFLD does not have a valid EC Related Row ID from PS_ECINMAPREC

Either remove the reference to the related record from the Inbound Target Record or create an appropriate entry in the Inbound Row ID Target Record.

ECINMPRF-6

A related field in PS_ECINMAPRECFLD is not found in PSRECFIELD

Either remove or correct the reference to the related field record from the Inbound Target Record or create the correct definition in PSRECFIELD.

ECOTMPRC-1

Target outbound records are not found in the PSRECDEFN table

Either modify the outbound map definition to not use the Outbound Target Record, or create the record definition.

ECOTMPRC-2

Outbound work record EC Map ID is not found in the PS_ECMAPDEFN table

Create an entry in the map definition table.

ECOTMPRC-3

Parent records from the outbound work record are not found in the PSRECDEFN table

Remove the reference to the parent record or create a record definition for the parent.

ECOTMPRC-4

File records from the outbound work record are not found in the PSRECDEFN table

Create a record definition for the file record.

ECOTMPFD-1

Outbound work record fields are not found with a valid EC Map ID and EC File Row ID combination from the PS_ECOUTMAPREC table

Either remove the entry from the Outbound Work Record (ECOUTMAPFLD) or create an entry in the Outbound Target Record (ECOUTMAPREC).

ECOTMPFD-2

Outbound work record fields from PS_ECOUTMAPFLD are not found in PSRECFIELD

Create the appropriate definitions in PSRECFIELD or remove the invalid map ID from the Outbound Work Record.

SYSECMGR-1

Inbound work record field does not exist in the type definitions in PSDBFIELD

Call PeopleSoft GSC for resolution.

FIELD-3

This query lists invalid default fields.

Modify the default value in record field properties.

FIELD-4

This query lists fields that are used in record definitions but do not exist in PSDBFIELD.

Define the field in PeopleSoft Application Designer.

FIELD-5

This query lists fields that have multiple default field labels in PSDBFLDLABL.

Open the field, select the default label, and save.

FIELD-06

This query lists deleted fields that have orphaned field labels in PSDBFLDLABL.

Run this SQL:

DELETE FROM PSDBFLDLABL
WHERE FIELDNAME NOT IN
 (SELECT FIELDNAME 
  FROM PSDBFIELD)

IBRK-01

Message parts referencing a message/version that does not exist.

Most likely caused by moving a container message in a project and not including all the part messages. Always make sure that when moving a container message in a project, every part message is also included if it doesn’t already exist in the target database.

IBRK-02

Rowset based messages referencing records that do not exist.

Most likely caused by moving a message in a project and not including records referenced in the message. Always make sure that when moving a rowset-based message in a project, every record that is not in the target database is also included in the project.

IBRK-03

Message parts must reference message/versions that are defined as part messages.

Most likely caused by moving a container message in a project and not including records referenced in the message. By definition, only part messages can be found in a container message. Always make sure that when moving a container message in a project, every part message contained is also in the project, unless the part message is already in the target database defined as a part message.

IBRK-04

Service operations need at least one version, the default.

Service operations cannot exist without a service operation version. These are separate managed objects and can therefore be added individually into a project. However, care must be taken when moving service operations in projects to always include the default version if it doesn’t already exist in the target database.

IBRK-05

Service operations must be associated with a service that exists

Every service operation is tied to a unique service. Both of these are managed objects which can be independently moved in a project. Care must be taken when moving service operations to always include the Service that’s tied to it in the project, unless the Service already exists in the target database.

IBRK-06

Service operation versions must have a valid Service operation

Service operations and service operation versions are separately managed objects. When moving service operation versions in a project, be sure to include the service operation with the same name unless the service operation already exists in the target database.

IBRK-07

Handlers must have a valid service operation.

Service operation handlers and service operations are separately managed objects. When moving handlers, be sure to include the related service operation unless the operation already exists in the target database.

IBRK-08

Routings must reference a valid service operation version.

Note. Routing IB_ADMIN_ROUTING is excluded because it is a dummy routing used during upgrade to 8.48.

Service operation routings and service operation versions are separately managed objects. When moving routings, be sure to include the related service operation version unless the operation version already exists in the target database.

IBRK-09

Routings must reference valid nodes

Service operation routings and nodes are separately managed objects. When moving routings, be sure to include any related Node that doesn’t exist in the target database.

IBRK-10

Routings must reference valid service operation handlers

Service operation routings and service operation Handlers are separately managed objects. When moving routings, be sure to include the related service operation Handlers that appear in the routing component unless the Handlers already exist in the target database.

IBRK-11

Routing parameters must reference valid transform application engine programs

Service operation routings reference application engine transform programs. When moving routings, be sure to include any referenced Application Engine programs unless the programs that appear in the routing parameter component already exist in the target database.

IBRK-12

Routing parameters must reference valid message/version combinations.

Service operation routings reference messages. When moving routings, be sure to include any referenced messages unless the messages that appear in the routing parameter component already exist in the target database.

IBRK-13

Service operation versions need to reference valid messages

Service operation versions reference messages. When moving versions in a project, be sure to include any referenced messages unless the messages that appear in the service operation or service operation versions component already exist in the target database.

IBRK-14

Service operation versions need to reference valid queues

Service operation versions reference Integration Broker queues. When moving versions in a project, be sure to include any referenced queues unless the queues that appear in the service operation or service operation versions component already exist in the target database.

IBRK-15

Service operation versions need to reference valid transform programs

Service operation versions reference application engine transform programs. When moving versions in a project, be sure to include any referenced application engine programs unless the programs that appear in the service operation versions component already exist in the target database.

IBRK-16

Service operation versions with validation turned on require each -- message to have a schema defined

Service operations versions with validation turned on (see the Service Operations component), require all referenced messages to have schemas defined. When moving service operation versions that have validation turned on, include all referenced messages unless the referenced messages already exist in the target database with valid schemas. Also note that when moving messages in projects the related schemas are not brought along. These need to be moved via data mover scripts. (see PSIBMSGSCHEMA_IMP.DMS and PSIBMSGSCHEMA_EXP.DMS)

IBRK-17

Component interface handlers should reference valid component interfaces.

Service operation handlers that are of type CI reference component interfaces. When moving service operation handlers, be sure to also include any referenced component interfaces in the project unless the CIs already exist in the target database.

IBRK-18

Application class handlers should reference valid application packages

Service operation handlers that are of type Application Class reference application classes. When moving service operation Handlers, be sure to also include any referenced application classes in the project unless they already exist in the target database. Care must be taken to make sure that the referenced application class PeopleCode is also included in the project.

IBRK-19

Part messages need to have a schema defined.

When moving messages in projects, the related schemas are not brought along. The schemas need to be moved using Data Mover scripts. (see PSIBMSGSCHEMA_IMP.DMS and PSIBMSGSCHEMA_EXP.DMS). For part messages, having a schema is mandatory.

IBRK-20

Container messages need to have a schema defined.

When moving messages in projects, the related schemas are not brought along. These need to be moved using Data Mover scripts. (see PSIBMSGSCHEMA_IMP.DMS and PSIBMSGSCHEMA_EXP.DMS). For container messages, having a schema is mandatory.

IBRK-21

Operations with duplicate routings.

There never should be multiple active routings where the sender and receiver node are identical. Inactivate or delete one of the duplicate routings.

IBRK-22

Duplicate Any to Local routing.

There never should be multiple active Any to Local routings for a given Service Operation. Inactivate or delete one of the duplicate routings.

MENU-01

A row in the MenuItem table has no corresponding row in the MenuDefinition table.

Issue the following SQL:

DELETE FROM PSMENUITEM
WHERE MENUNAME = 'x';

MENU-02

A component-type menu item specifies no component.

Use the Menu Designer to change each of these menu items to reference an existing component.

MENU-03

A menu item has a specified component, but that component has no corresponding row in the ComponentDefinition table.

Use the Menu Designer to change each of these menu items to reference an existing component.

MENU-04

A PeopleCode-type menu item has a specified enabling component, but that component is not specified for any component-type menu item within the same menu. (Such menu items never get enabled at runtime.)

Use the Menu Designer to change each of these menu items to reference a component that is associated with a component-type menu item within the same menu.

MENU-05

A menu has no rows in the MenuItem table.

Use the Menu Designer to add any appropriate menu items to each of these menus.

OPTZN-01

Problem type records that do not have matching record definitions.

Execute the following SQL:

DELETE FROM PSOPTREC
WHERE RECNAME = 'recordname';

DELETE FROM PSOPTFIELD 
WHERE RECNAME ='recordname';

OPTZN-02

Optimization delete records that do not have matching definitions.

In PeopleSoft Application Designer, open the base record definition properties. Clear the optimization delete record name, and perform an alter.

OPTZN-03

Optimization base record has fields that delete record does not.

Using PeopleSoft Application Designer, delete the optimization delete record definition, drop the table, and recreate it by cloning the base record. Run Build. You may need to recreate triggers on the base record on some platforms where deferred processing is not done.

OPTZN-04

Optimization delete record has fields that base record does not.

Using PeopleSoft Application Designer, delete the optimization delete record definition, drop the table and recreate it by cloning the base record. Run Build. You may need to recreate triggers on the base record on some platforms where deferred processing is not done.

OPTZN-06

Optimization base record defn has the trigger flag set but has no delete record name, or vice versa.

Using PeopleSoft Application Designer, open the record definition properties, make sure that the optimization delete record name is set, and save. Build the record with the create triggers check box set to create optimization triggers.

OPTZN-07

Optimization records that need to have trigger flag set and do not.

Using PeopleSoft Application Designer, open the record definition properties, make sure that the optimization delete record name is set, and save. Build the record with the create triggers check box set to create optimization triggers.

OPTZN-08

Optimization records that have trigger flag set but are not marked readable in any problem type.

Using PeopleSoft Application Designer, open the record definition properties, clear the optimization delete record name and alter the record to drop optimization triggers as they are no longer needed but affect performance.

OPTZN-10

Optimization Tools table PSOPTSYNC does not have an entry for the listed opt records, that are marked READABLE in PSOPTREC.

Open the problem type definition in Application Designer, make sure that the readable flags are set correctly for each readable record, and save the problem type definition.

OPTZN-11

Optimization Tools table PSOPTSYNC does not have an entry with PROBINST = $ALL$ and is marked as NON SCENARIO_MANAGED and READABLE in PSOPTREC.

Using Problem Type Designer, make sure that the readable flags are set correctly for each readable record. Make sure that the scenario_managed flags are set correctly. Save the problem type definition.

OPTZN-12

Optimization Tools table PSOPTSYNC has extra entries for the listed record names that are not there in PSOPTREC.

Submit the following SQL to remove extra entries in PSOPTSYNC table.

DELETE FROM PSOPTSYNC
WHERE RECNAME NOT IN
 (SELECT RECNAME
  FROM PSOPTREC)

OPTZN-13

The following record names in Optimization Tools table PSOPTREC do not have at least one field listed in the PSOPTFIELD table.

Open the problem type definition in Application Designer. Make sure that for every record in the problem type definition at least one field is selected to be loaded in the problem instance.

OPTZN-14

For the following transaction parameter of type RECARRAY, the default value contains an invalid record name.

Open the problem type definition in PeopleSoft Application Designer. Inspect the offending transaction parameter and make sure that the default value contains a valid record name.

OPTZN-15

PSOPTSOLVERCODE table is empty for the listed problem types.

You may ignore this if none of the problem types need a third-party solver. Otherwise, populate the PSOPTSOLVERCODE table with the third-party solver license key. Select PeopleTools, Utilities, Optimization, Solver Licenses.

OPTZN-16

PSOPTSOLVERCODE table has a null licence key for the listed problem types.

You may ignore this if the plugin does not need a third-party solver. Otherwise populate the PSOPTSOLVERCODE table with the third-party solver licence key. Select PeopleTools, Utilities, Optimization, Solver Licenses.

OPTZN-17

This query identifies readable base records in an analytic type that don't have an optimization delete record specified.

In Application Designer, either specify a delete record for the analytic type record, or clear the Readable check box for the analytic type record.

OPTZN-18

This query identifies base records in an analytic type that have an optimization delete record specified, but aren't readable.

In Application Designer, either select the Readable check box for the analytic type record, or don't specify an optimization delete record for the analytic type record.

OPTZN-19

This query identifies base records and their associated delete records in an analytic type that don't have all fields in the same order.

In Application Designer, change the field order of one of the records to match the field order of the other record.

OPTZN-21

This query identifies fields in main records used in an analytic model that aren't selected in the analytic type associated with that model.

In Application Designer, either specify an appropriate record in the analytic model, or select the appropriate corresponding fields in the analytic type definition.

OPTZN-22

This query identifies fields in aggregate records used in an analytic model that aren't selected in the analytic type associated with the model.

In Application Designer, either specify an appropriate record in the analytic model, or select the appropriate corresponding fields in the analytic type definition.

PAGE-01

Page definition's page field count is not equal to the count of its page fields in the PageField table, and there is at least one row in the PageField table for that page.

Enter the following SQL:

SELECT COUNT(*)

FROM PSPNLFIELD
WHERE PNLNAME = 'x';

UPDATE PSPNLDEFN
SET FIELDCOUNT = count
WHERE PNLNAME = 'x';

PAGE-02

Page definition's page field count is not equal to zero, but there are no rows in the PageField table for that page definition.

Enter the following SQL:

UPDATE PSPNLDEFN
SET FIELDCOUNT = 0
WHERE PNLNAME = 'x';

PAGE-03

A subpage contains itself as a page field.

Use the Page Designer to change each of these page fields to reference a different subpage.

PAGE-04

A row in the PageField has no corresponding row in the PageDefinition table.

Issue the following SQL:

DELETE FROM PSPNLFIELD
WHERE PNLNAME = 'x';

PAGE-05

A subpage-type page field has no corresponding row in the Page Definition table for its specified subpage.

Use the Page Designer to change each of these page fields to reference an existing subpage.

PAGE-06

A page field's specified record/field has no corresponding row in the RecordField table.

Use the Page Designer to change each of these page fields to reference an existing record/field.

PAGE-07

A row in the ComponentItem table has no corresponding row in the ComponentDefinition table.

Issue the following SQL:

DELETE FROM PSPNLGROUP
WHERE PNLGRPNAME = 'x';

PAGE-08

A component item's specified page has no corresponding row in the PageDefinition table.

Use Application Designer to replace each of these component items with one that references an existing page.

PAGE-09

A component's specified access detail page has no corresponding row in the PageDefinition table.

Use Application Designer to change each of these components to reference an access detail page that exists.

PAGE -10

A component's specified search record has no corresponding row in the RecordDefinition table.

Use Application Designer to change each of these components to reference a search record that exists.

PAGE-11

A component's specified add search record has no corresponding row in the RecordDefinition table.

Use Application Designer to change each of these components to reference an add search record that exists.

PEOPLECODE-1

The PeopleCode Name table contains a program name that does not exist in PcmProgram table

Run the following SQL:

DELETE FROM PSPCMNAME
WHERE NOT EXISTS
 (SELECT 'X'FROM PSPCMPROG B
  WHERE B.OBJECTID1 =
   PSPCMNAME.OBJECTID1 AND
  B.OBJECTVALUE1 =
   PSPCMNAME.OBJECTVALUE1 AND
  B.OBJECTID2 = 
   PSPCMNAME.OBJECTID2 AND
  B.OBJECTVALUE2 = 
   PSPCMNAME.OBJECTVALUE2 AND
  B.OBJECTID3 =
   PSPCMNAME.OBJECTID3 AND
  B.OBJECTVALUE3 =
   PSPCMNAME.OBJECTVALUE3 AND
  B.OBJECTID4 =
   PSPCMNAME.OBJECTID4 AND
  B.OBJECTVALUE4 =
   PSPCMNAME.OBJECTVALUE4 AND
  B.OBJECTID5 =
   PSPCMNAME.OBJECTID5 AND
  B.OBJECTVALUE5 =
   PSPCMNAME.OBJECTVALUE5 AND
  B.OBJECTID6 = 
   PSPCMNAME.OBJECTID6 AND
  B.OBJECTVALUE6 = 
   PSPCMNAME.OBJECTVALUE6)

PEOPLECODE-2

The PeopleCode Program table contains a program name that does not exist in the PcmName table.

Run the following SQL:

DELETE FROM PSPCMPROG
WHERE NAMECOUNT <> 0 AND
NOT EXISTS
 (SELECT 'X'FROM PSPCMNAME B
  WHERE PSPCMPROG.OBJECTID1 =
   B.OBJECTID1 AND 
  PSPCMPROG.OBJECTVALUE1 =
   B.OBJECTVALUE1 AND
  PSPCMPROG.OBJECTID2 =
   B.OBJECTID2 AND
  PSPCMPROG.OBJECTVALUE2 =
   B.OBJECTVALUE2 AND
  PSPCMPROG.OBJECTID3 =
   B.OBJECTID3 AND 
  PSPCMPROG.OBJECTVALUE3 =
   B.OBJECTVALUE3 AND 
  PSPCMPROG.OBJECTID4 =
   B.OBJECTID4 AND 
  PSPCMPROG.OBJECTVALUE4 =
   B.OBJECTVALUE4 AND
  PSPCMPROG.OBJECTID5 =
   B.OBJECTID5 AND
  PSPCMPROG.OBJECTVALUE5 =
   B.OBJECTVALUE5 AND 
  PSPCMPROG.OBJECTID6 =
   B.OBJECTID6 AND
  PSPCMPROG.OBJECTVALUE6 =
   B.OBJECTVALUE6)

PEOPLECODE-3

The PeopleCode Program table name count does not match the record count in PcmName table.

Run the following SQL:

UPDATE PSPCMPROG
SET NAMECOUNT =
(SELECT COUNT(*)
 FROM PSPCMNAME C
 WHERE C.OBJECTID1 = 
  PSPCMPROG.OBJECTID1 AND
 C.OBJECTVALUE1 = 
  PSPCMPROG.OBJECTVALUE1 AND
 C.OBJECTID2 = 
  PSPCMPROG.OBJECTID2 AND 
 C.OBJECTVALUE2 = 
  PSPCMPROG.OBJECTVALUE2 AND
 C.OBJECTID3 = 
  PSPCMPROG.OBJECTID3 AND
 C.OBJECTVALUE3 = 
  PSPCMPROG.OBJECTVALUE3 AND
 C.OBJECTID4 = 
  PSPCMPROG.OBJECTID4 AND
 C.OBJECTVALUE4 = 
  PSPCMPROG.OBJECTVALUE4 AND
 C.OBJECTID5 = 
  PSPCMPROG.OBJECTID5 AND
 C.OBJECTVALUE5 = 
  PSPCMPROG.OBJECTVALUE5 AND
 C.OBJECTID6 = 
  PSPCMPROG.OBJECTID6 AND
 C.OBJECTVALUE6 = 
  PSPCMPROG.OBJECTVALUE6)

PEOPLECODE-4

PeopleCode contains invalid FILELAYOUT References.

Open the PeopleCode program in PeopleSoft Application Designer and correct the invalid reference.

PEOPLECODE-5

PeopleCode reference to an invalid record or field.

Open the PeopleCode program in PeopleSoft Application Designer and correct the invalid reference.

PEOPLECODE-6

PeopleCode reference to an invalid field.

Open the PeopleCode program in PeopleSoft Application Designer and correct the invalid field name.

PEOPLECODE-7

There is orphaned Application Package PeopleCode.

Run the following SQL:

DELETE FROM PSPCMPROG
WHERE OBJECTID1 = 104
  AND OBJECTID2 = 107
  AND OBJECTVALUE2 NOT IN
  (SELECT APPCLASSID
   FROM PSAPPCLASSDEFN P 
   WHERE P.PACKAGEROOT =
    OBJECTVALUE1 AND 
   P.APPCLASSID = 
    OBJECTVALUE2)

PEOPLECODE-8

There is orphaned Application Package PeopleCode.

Run the following SQL:

DELETE FROM PSPCMPROG
WHERE OBJECTID1 = 104
  AND OBJECTID2 = 105
  AND OBJECTID3 = 107
  AND OBJECTVALUE3 NOT IN
  (SELECT APPCLASSID 
   FROM PSAPPCLASSDEFN P
   WHERE P.PACKAGEROOT =
    OBJECTVALUE1 AND 
   P.QUALIFYPATH =
    OBJECTVALUE2 AND
   P.APPCLASSID =
    OBJECTVALUE3)

PEOPLECODE-9

There is orphaned Application Package PeopleCode.

For Microsoft SQL Server, run the following SQL:

DELETE FROM PSPCMPROG 
WHERE OBJECTID1 = 104
  AND OBJECTID2 = 105
  AND OBJECTID3 = 106
  AND OBJECTID4 = 107
  AND OBJECTVALUE4 NOT IN
  (SELECT APPCLASSID 
   FROM PSAPPCLASSDEFN F
   WHERE F.PACKAGEROOT =
    OBJECTVALUE1 AND 
   F.QUALIFYPATH = 
    RTRIM(OBJECTVALUE2)+ ':'+ 
    RTRIM(OBJECTVALUE3) AND 
   F.APPCLASSID = OBJECTVALUE4)

For Informix, run the following SQL:

DELETE FROM PSPCMPROG 
WHERE OBJECTID1 = 104
  AND OBJECTID2 = 105
  AND OBJECTID3 = 106
  AND OBJECTID4 = 107
  AND OBJECTVALUE4 NOT IN
  (SELECT APPCLASSID 
   FROM PSAPPCLASSDEFN F
   WHERE F.PACKAGEROOT = 
    OBJECTVALUE1 AND
   QUALIFYPATH =
    TRIM(P.OBJECTVALUE2) || ':'
    || TRIM(P.OBJECTVALUE3) AND
   F.APPCLASSID = OBJECTVALUE4)

For all other DB platforms

DELETE FROM PSPCMPROG WHERE OBJECTID1 = 104
  AND OBJECTID2 = 105
  AND OBJECTID3 = 106
  AND OBJECTID4 = 107
  AND OBJECTVALUE4 NOT IN
 (SELECT APPCLASSID FROM
  PSAPPCLASSDEFN F
  WHERE F.PACKAGEROOT =
   OBJECTVALUE1 AND
  QUALIFYPATH =
   RTRIM(P.OBJECTVALUE2) || ':'
   || RTRIM(P.OBJECTVALUE3) AND
  F.APPCLASSID =
   OBJECTVALUE4)

PRCSSCHED-01

SQR-Related Process Definitions (PS_PRCSDEFN) that override the PARMLIST field from the Process Type Definition (PS_PRCSTYPEDEFN).

For the listed processes, select Process Scheduler, Processes, Override Options. Remove the value that is assigned to the Parameter List field.

Note. The PRRSCHED-01 query is intended to be a warning. If the override of the parameter list that is specified in the process type definition is intentional, then the above action can be bypassed.

PRCSSCHED-03

Process Definitions (PS_PRCSDEFN), where the OUTDESTTYPE should be set to NONE.

For the listed processes, select Process Scheduler, Processes Destination. In the Output Destination Options group, set the Type option to (None).

PRCSSCHED-04

Process Definitions, where the API AWARE should be set to true.

For the listed processes, select Process Scheduler, Processes, Process Definition. Select the check box that reads API Aware.

If API Aware is not marked, this process gets an incorrect run status when it's viewed from Process Monitor. For additional information, please refer to the Process Scheduler PeopleBook.

PRCSSCHED-05

Process Definitions, where process type is not found in the Process Type Definition .

This occurs when a Process Definition is copied from another PeopleSoft database by using project upgrade. However, the Process Type definition that is associated with this Process Definition is not copied into the database. Review the project upgrade that is used to create the Process Definition. Create another project upgrade to copy Process Type definition from the database where the Process Definition originated.

PRCSSCHED-06

Process Job Item (PS_PRCSJOBITEM), where Process Type is listed as a job item, but is not found in the Process Definition (PS_PRCSDEFN).

This occurs when a PSJob is copied from another PeopleSoft database by using a project upgrade. However, the Process Definition for one or more job items in the PSJob is not copied from the database. Review the project upgrade that is used to create the PSJob. Create another project upgrade to copy the Process Definitions that are identified in this report from the database where the PSJob originated.

PRCSSCHED-07

Server Class List (PS_SERVERCLASS), where Process Type is not found in the Process Type Definition (PS_PRCSTYPEDEFN).

This occurs when a Server Definition is copied from another database by using a project upgrade. However, a process type in the Server Class list is not found in the Process Type Definition. Create another project upgrade to copy the Process Type definition from the database where the Server Definition is created.

PRCSSCHED-08

Process Definitions, where the process category is invalid

For the listed processes, select Process Scheduler, Processes, Process Definition. Correct the Process Category.

PRCSSCHED-09

Job Definitions, where the process category is invalid.

For the listed jobs, select Process Scheduler, Jobs, Job Definition. Correct the Process Category.

PRCSSCHED-10

Process Definitions, where the process category is missing.

For the listed processes, select Process Scheduler, Processes, Process Definition. Specify a Process Category.

PRCSSCHED-11

Job Definitions, where the process category is missing.

For the listed jobs, select Process Scheduler, Jobs, Job Definition. Specify a Process Category.

PRCSSCHED-12

Server Categories, where a category defined for a server does not exist in process category definition.

For the listed servers, select Process Scheduler, Servers, Server Definition. Remove the invalid Process Category.

PRCSSCHED-13

Server Categories, where a server is missing a process category definition.

For the listed servers, select Process Scheduler, Servers, Server Definition.

A warning message appears when you open the page, and the missing Process Category is added to the server when the page is saved.

PRCSSCHED-14

Process Scheduler Queue, where a queued/pending request specifies a category that does not exist in process category definition.

Run the following SQL:

DELETE FROM PSPRCSQUE S 
WHERE S.RUNSTATUS IN
 ('5', '16') AND
 S.SERVERNAMERQST <> ''
 AND S.PRCSCATEGORY NOT IN
 (SELECT PRCSCATEGORY 
  FROM PS_SERVERCATEGORY
  WHERE SERVERNAME = 
  S.SERVERNAMERQST AND 
  MAXCONCURRENT > 0)

PRCSSCHED-15

Process Definitions, where a process specifies an invalid destination folder.

For the listed processes, select Process Scheduler, Processes, Destination. Correct the Destination Folder or blank it out.

PRCSSCHED-16

Process Definitions, where a process definition specifies a recovery process that does not exist.

For the listed processes, select Process Scheduler, Processes, Process Definition Options. Correct the recovery process or blank it out.

PRCSSCHED-17

Job Definitions, where a job definition specifies a recovery process that does not exist.

For the listed jobs, select Process Scheduler, Jobs, Job Definition Options. Correct the recovery process or blank it out.

QUERY-01

Query Definition Select count does not match the record count that is in the Query Select table. The query definition is corrupt.

Run the following SQL:

DELETE FROM PSQRYDEFN
WHERE OPRID = 'X' AND
 QRYNAME = 'Y' 

DELETE FROM PSQRYSELECT
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYRECORD
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYFIELD
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYCRITERIA
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYEXPR
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYBIND
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

QUERY-02

Query Definition Expression count does not match the record count in the Query Expression table.

Run the following SQL:

UPDATE PSQRYDEFN
SET EXPCOUNT =
 (SELECT COUNT(*)
  FROM PSQRYEXPR C 
  WHERE OPRID = ‘X’ AND
   QRYNAME = ‘Y’)
WHERE OPRID = ‘X’ AND
 QRYNAME = ‘Y’

QUERY-03

Query Definition Bind count does not match the record count in the Query Bind table

Run the following SQL:

UPDATE PSQRYDEFN
SET BNDCOUNT =
 (SELECT COUNT(*)
  FROM PSQRYBIND 
  WHERE OPRID = ‘X’ AND
   QRYNAME = ‘Y’)
WHERE OPRID = ‘X’ AND
 QRYNAME = ‘Y’

QUERY-04

Query Definition Record name does not exist in the Record Definition table.

See resolution for QUERY-07.

QUERY-05

Query Definition Record JoinRecord name does not exist in the Query Record table

See resolution for QUERY-01.

QUERY-06

Query Definition Record JoinField name does not exist in the Query Field table.

See resolution for QUERY-01.

QUERY-07

Query Field Record Name does not exist in Record Definition Table

To salvage the query, you must use PeopleSoft Application Designer to re-create the record definition.

Having re-created the record, run Query and open the offending query. Remove or repair the affected areas and save the query.

Or, if the query is not important, you can delete the entire query definition by using the resolution for QRY-01.

QUERY-08

Query Definition Field name does not exist in the Field Definition table

If the record on which this field appears is deleted, you have seen errors for every referenced field that belongs to the deleted record. If this is the case, see the resolution for QUERY-1.

If this is not the case, some fields that the query depends on are either deleted or renamed. Run Query and open the offending query. Query automatically repairs itself and updates the query definition in the database.

QUERY-09

Query Selection Record count does not match the record count in Query Record table.

See resolution for QUERY-01.

QUERY-10

Query Selection Field count does not match the record count in Query Field table.

See resolution for QUERY-01.

QUERY-11

Query Selection Criteria count does not match the record count in Query Criteria table.

See resolution for QUERY-01.

QUERY-11A

Query Selection Criteria having count does not match the record count in Query Criteria table.

See resolution for QUERY-01.

QUERY-12

Query Selection Parent select number does not exist in Query Select table.

See resolution for QUERY-01.

QUERY-13

Query Criteria Selection-Left does not exist in the Query Selection table.

Run Query and delete the corrupted criteria entry. If you can't open the query, run the following SQL to delete the corrupted criteria entry:

DELETE FROM PSQRYCRITERIA
WHERE OPRID = 'X'AND
 QRYNAME ='Y' AND
 CRTNUM = count

QUERY-14

Query Criteria Selection-Right1 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-15

Query Criteria Selection-Right2 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-16

Query Criteria Field-Left does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-17

Query Criteria Field-Right1 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-18

Query Criteria Field-Right2 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-19

Query Criteria Expression-Right1 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-20

Query Criteria Expression-Right2 does not exist in the Query Selection table.

See resolution for QUERY-13.

QUERY-22

This audit identifies queries that were created without PUBLIC access.

This is normal; the audit insures that PeopleSoft does not deliver nonpublic queries as part of its standard delivered products.

QUERY-23

This audit identifies queries that reference non-existent database records. The query definitions are corrupt.

This is an internal PeopleSoft audit. Call PeopleSoft GSC for resolution.

Run the following SQL:

DELETE FROM PSQRYDEFN
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYSELECT
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYRECORD
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYFIELD
WHERE OPRID = 'X'
 AND QRYNAME = 'Y'

DELETE FROM PSQRYCRITERIA
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYEXPR
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

DELETE FROM PSQRYBIND
WHERE OPRID = 'X' AND
 QRYNAME = 'Y'

QUERY-24

This audit identifies queries that were created with the name UNTITLED.

Queries should not be saved as UNTITLED. Either rename or delete these queries.

QUERY-25

This audit identifies queries that were created with blank query names.

You must either rename or delete these queries.

QUERY-26

This audit identifies queries that contain unions but select an unequal number of fields.

Ensure that every select statement in the query has an equal number of fields selected. These fields must also match in display type and length.

QUERY-27

This audit identifies the queries that reference query translate fields that have been incorrectly modified to a non-translate type. When run in Microsoft Windows Query Manager, queries that reference these fields might return an inaccurate zero result set because the query metadata is corrupt.

Run the following SQL:

UPDATE PSQRYFIELD 
SET XLATTYPE = 1 
WHERE FIELDNAME IN 
 (<list of fieldnames
  from the audit>)

RECORD-1

Record Definition Field count does not match the number of records in Record Field table.

Run the following SQL:

SELECT COUNT(*) 
FROM PSRECFIELD
 WHERE RECNAME = 'X';
UPDATE PSRECDEFN 
SET FIELDCOUNT =
 COUNT
 WHERE RECNAME = 'X';

RECORD-2

Record Definition Fields do not exist in Record Field table.

Run the following SQL:

UPDATE PSRECDEFN 
SET FIELDCOUNT = 0
WHERE RECNAME = 'X';

Or

DELETE FROM PSRECDEFN 
WHERE RECNAME = 'X';

RECORD-3

Record Definition Parent Record does not exist in Record Definition table.

Use Application Designer to open the definition.

Select File, Object Properties, Use and specify a valid parent record.

RECORD-4

Record Definition SubRecord does not exist in Record Definition table.

Use Application Designer to open the definition.

Select File, Object Properties, Type and specify a valid subrecord.

RECORD-5

Record Definition Query Security Record does not exist in Record Definition table

Use Application Designer to open the definition.

Select File, Object Properties, Use and specify a valid query security record.

RECORD-6

Record Field definitions contain record names that do not exist in the Record Definition table.

Run the following SQL:

DELETE FROM PSRECFIELD 
WHERE RECNAME = 'X'

RECORD-7

DBField records do not exist for the following RecField table Fields.

Use PeopleSoft Application Designer to open the definition and fix the invalid fields.

RECORD-8

Record definitions do not exist for the following RecField table SubRecords.

Use PeopleSoft Application Designer to open the definition and fix the invalid fields.

RECORD-9

Invalid record definitions in record group definitions.

Run the following SQL:

DELETE FROM PS_REC_GROUP_REC 
WHERE RECNAME NOT IN
(SELECT DISTINCT RECNAME 
 FROM PSRECDEFN)

RECORD-11

Record definitions that contain more than two Long character field types.

Note. The use of LONG data types can introduce performance overhead for multiple database platforms.

For DB2 zOS, the use of multiple LONG fields in a single record definition is highly discouraged. The use of the LONG data type for DB2 zOS creates situations in which the maximum row length is determined by the page size, less the sum of the lengths of the columns that precede the LONG column in the row. This means that the length becomes variable as the size of the LONG changes. This can lead to performance overhead, and in some cases, LONG data that no longer fits the row. Judicious use of the LONG data type for DB2 zOS is required, and placing multiple LONGs in a single record definition is discouraged.

For the Oracle platform, the judicious use multiple LOB datatypes in a single record definition is recommended. The use of multiple LONG fields in a single record definition has been supported since the PeopleTools release 8.48. Multiple LONG support is made possible with the adoption of the CLOB (Character Large Object) and BLOB (Binary Large Object) Oracle LOB datatypes. While technically possible, you should exercise caution when using multiple LOBs in a single record definition because of potential performance overhead which might occur based on the placement and actual size of the LOB.

RECORD-12

Record definitions with a blank or null record name value.

Run the following SQL:

DELETE FROM PSRECDEFN
 WHERE RECNAME = ''

RECORD-13

Temp records that specify a non-standard SQL table name.

Run the following SQL:

UPDATE PSRECDEFN 
SET SQLTABLENAME = ' '
WHERE RECTYPE = 7 AND
 SQLTABLENAME <> ' '

RECORD-14

The Field Number field in the RecordField table has an invalid value.

If the reported record was delivered by PeopleSoft or generated as part of an upgrade, contact the GSC. Run the following SQL to determine which fields need to be updated:

SELECT FIELDCOUNT 
FROM PSRECDEFN 
WHERE RECNAME='X';

SELECT FIELDNUM 
FROM PSRECFIELD 
WHERE RECNAME='X' 
ORDER BY FIELDNUM;

Note. The PSRECFIELD.FIELDNUM values should be numbered sequentially 1 through PSRECDEFN.FIELDCOUNT. If any value is skipped then renumber the FIELDNUM values accordingly.

SYSLANG-01

Base language records that are found in the PSRECDEFNLANG table.

Run the following SQL:

DELETE FROM PSRECDEFNLANG
WHERE LANGUAGE_CD =
 (SELECT B.LANGUAGE_CD 
  FROM PSOPTIONS B)

SYSLANG-02

Base language fields that are found in the PSDBFIELDLANG table.

Check the value of LANGUAGE_CD on PSOPTIONS; this is the base language. Entries with this language code are found in PSDBFIELDLANG. Base language entries should only be in PSDBFIELD.

After you establish that the base language entries in PSDBFIELD are correct, you delete them from PSDBFIELDLANG as follows:

DELETE FROM PSDBFIELDLANG
WHERE LANGUAGE_CD =
 (SELECT LANGUAGE_CD
  FROM PSOPTIONS)

SYSLANG-03

Foreign language records that are found in PSRECDEFNLANG table without related base records from PSRECDEFN.

Run the following SQL:

DELETE FROM PSRECDEFNLANG
WHERE NOT EXISTS
 (SELECT 'X' FROM PSRECDEFN B
 WHERE PSRECDEFNLANG.RECNAME =
  B.RECNAME) AND
 PSRECDEFNLANG.LANGUAGE_CD <>
 (SELECT C.LANGUAGE_CD
  FROM PSOPTIONS C)

SYSLANG-04

Foreign Language fields that are found in the PSDBFIELDLANG table without related Base Fields from PSDBFIELD.

Run the following SQL:

DELETE FROM PSDBFIELDLANG
WHERE NOT EXISTS
 (SELECT 'X'
  FROM PSDBFIELD B
  WHERE PSDBFIELDLANG.FIELDNAME=
   B.FIELDNAME)
AND
 PSDBFIELDLANG.LANGUAGE_CD <>
 (SELECT LANGUAGE_CD
  FROM PSOPTIONS)

SYSLANG-05

Foreign Language translate fields that are found in the XLATTABLE table without related base language translate fields.

Either delete the offending entries via SQL, or use PeopleSoft Application Designer to add the equivalent entries in the base language of the database.

SYSLANG-07

Related Language records which are not valid records.

In Application Designer, delete the specified Related Language Records.

SYSLANG-08

The displayed Related Language Records are effective-dated but do not have an EFFDT field defined.

In Application Designer, add EFFDT to the specified related language table.

SYSLANG-09

The displayed Related Language records point to another Related Language record

In Application Designer, delete the related language reference for each record that is listed.

SYSLANG-10

The displayed Related Language Records do not contain a LANGUAGE_CD as a key field.

In Application Designer, make the LANGUAGE_CD field a key on the specified Related Language Tables.

SYSLANG-11

The displayed Related Language views have the wrong structure defined.

In Application Designer, make the key structures that are on the specified Related Language view identical to the key structure that is on the Base Table/view.

SYSLANG-12

The displayed Related Language records have the wrong key structure defined.

In Application Designer, make the key structures on the specified Related Language Tables identical to the key structure on the Base Table.

SYSLANG-13

Identify related language records that have more than one base record defined.

In PeopleSoft Application Designer, remove the related language table link to one of the base records.

SYSLANG-14

Identify related language records that have the wrong structure defined.

In Application Designer, make the key structures on the specified Related Language tables identical to the key structure that is on the base table. Also remove any fields, except LANGUAGE_CD, on the related language record that do not exist on the base record.

SYSLANG-15

The displayed Related Language fields in the PSDBFLDLABLLANG table are orphaned.

Using the platform query tool, first, perform a SELECT to verify the rows indicated in the report. Then, delete the selected rows.

This is sample SQL for the Microsoft SQL Server database:

SELECT A.FIELDNAME, A.LANGUAGE_CD
FROM PSDBFLDLABLLANG A
WHERE NOT EXISTS 
 (SELECT 'X'
  FROM PSDBFIELD B
  WHERE A.FIELDNAME =
   B.FIELDNAME)
ORDER BY 1,2

DELETE FROM PSDBFLDLABLLANG A
WHERE NOT EXISTS 
 (SELECT 'X'
  FROM PSDBFIELD B
  WHERE A.FIELDNAME =
   B.FIELDNAME)

SEC-1

Authorized Signon Operator does not exist in the Class Definition table. Incomplete permission list: Orphan signon times:

(Verifies the existence of permission lists owning signon times.)

Delete the extra signon times. If this is a permission list that should exist, recreate it through PeopleTools Security.

DELETE FROM PSAUTHSIGNON
WHERE CLASSID='x'

SEC-2

Incomplete permission list: Orphan page permissions:

(Verifies the existence of permission lists owning page permissions.)

Delete the extra page permissions. If this is a permission list that should exist, recreate it through PeopleTools Security.

DELETE FROM PSAUTHITEM
WHERE CLASSID='x'

SEC-3

Incomplete permission list: Orphan process groups:

(Verifies existence of permission lists owning process groups.)

Delete the extra process group authorizations. If this is a permission list that should exist, recreate it through PeopleTools Security.

DELETE FROM PSAUTHPRCS
WHERE CLASSID='x'

SEC-4

Incomplete permission list: Orphan process profiles:

(Verifies existence of permission lists owning process profiles.)

Delete the extra process profiles. If this is a permission list that should exist, recreate it through PeopleTools Security.

DELETE FROM PSPRCSPRFL
WHERE CLASSID='x'

SEC-5

Permission list references a nonexistent process group:

(Verifies the existence of process groups.)

Delete the extraneous process groups. If this group should exist, recreate it.

DELETE FROM PSAUTHPRCS
WHERE CLASSID='x' AND
 PRCSGRP = 'y'

SEC-6

User profile references a role that does not exist:

Open the user profile in PeopleTools Security and remove the reference to the Role that does not exist.

SEC-7

Role references a permission list that does not exist:

Open the Role in PeopleTools Security and remove the reference to the Permission List that does not exist.

SEC-8

Role references a user that does not exist in the PSOPRDEFN table.

Remove the user from the PSROLEUSER table.

SEC-9

Permission list references a role that does not exist in the PSROLEDEFN table.

Remove the role from the PSROLECLASS table.

SEC-28

Invalid entries in the PSAUTHITEM table.

(Continues in next row)

Run the following SQL:

DELETE FROM PSAUTHITEM
WHERE (PSAUTHITEM.MENUNAME 
 NOT LIKE 'WEBLIB_%'AND
 PSAUTHITEM.MENUNAME NOT IN
 ('CLIENTPROCESS', 
  'DATA_MOVER',
 'IMPORT_MANAGER',
 'OBJECT_SECURITY',
 'QUERY', 'PERFMONPPMI') AND
 PSAUTHITEM.MENUNAME NOT LIKE
 ('APPLICATION_DESIGNER%')
 AND PSAUTHITEM.MENUNAME <>
  'REN' AND NOT EXISTS
 (SELECT 'X' 
  FROM PSMENUITEM MI
  WHERE PSAUTHITEM.MENUNAME =
   MI.MENUNAME AND
  PSAUTHITEM.BARNAME =
   MI.BARNAME AND
  PSAUTHITEM.BARITEMNAME =
   MI.ITEMNAME AND
  (MI.ITEMTYPE IN (0, 1, 2,
   3,4, 6, 7, 8, 10, 11) OR
  (MI.ITEMTYPE = 5 AND EXISTS
  (SELECT 'X' 
   FROM PSPNLGRPDEFN GD,
   PSPNLGROUP GI
   WHERE MI.PNLGRPNAME = 
    GD.PNLGRPNAME AND
   MI.MARKET = GD.MARKET AND
   GD.PNLGRPNAME =
    GI.PNLGRPNAME AND
   GD.MARKET = GI.MARKET AND
   PSAUTHITEM.PNLITEMNAME =
    GI.ITEMNAME))

SEC-28

(Continued)

OR (MI.ITEMTYPE = 9 AND EXISTS
 (SELECT 'X' 
  FROM PSPCMNAME PCN,
  PSPCMPROG PCP 
  WHERE PCN.OBJECTID1 = 3
  AND PCN.OBJECTVALUE1 = 
   MI.MENUNAME AND
  PCN.OBJECTID2 = 4 AND
  PCN.OBJECTVALUE2 = 
   MI.BARNAME AND
  PCN.OBJECTID3 = 5 AND
  PCN.OBJECTVALUE3 = 
   MI.ITEMNAME AND
  PCN.OBJECTID4 = 12 AND
  PCN.OBJECTVALUE4 = 
   'ItemSelected' AND
  PCN.OBJECTID1 =
   PCP.OBJECTID1 AND
  PCN.OBJECTVALUE1 =
   PCP.OBJECTVALUE1 AND
  PCN.OBJECTID2 =
   PCP.OBJECTID2 AND
  PCN.OBJECTVALUE2 =
   PCP.OBJECTVALUE2 AND
  PCN.OBJECTID3 =
   PCP.OBJECTID3 AND
  PCN.OBJECTVALUE3 =
   PCP.OBJECTVALUE3 AND
  PCN.OBJECTID4 =
   PCP.OBJECTID4 AND
  PCN.OBJECTVALUE4 =
   PCP.OBJECTVALUE4)) OR
  (MI.ITEMTYPE = 12
   AND EXISTS 
  (SELECT 'X'
   FROM PSXFERITEM XI
   WHERE MI.MENUNAME =
    XI.MENUNAME AND
   MI.ITEMNAME = 
    XI.ITEMNAME)))))

SEC-28

(Continued)

OR
 (PSAUTHITEM.MENUNAME LIKE
 'WEBLIB_%' AND NOT EXISTS 
 (SELECT 'X'
  FROM PSPCMPROG PCP
  WHERE PCP.OBJECTID1 = 1 AND
   PCP.OBJECTVALUE1 =
    PSAUTHITEM.MENUNAME AND
   PCP.OBJECTID2 = 2 AND
   PCP.OBJECTVALUE2 = 
    PSAUTHITEM.BARNAME))OR
   (PSAUTHITEM.MENUNAME IN 
   ('CLIENTPROCESS',
    'DATA_MOVER',
    'IMPORT_MANAGER',
    'OBJECT_SECURITY',
    'QUERY', 'PERFMONPPMI')
 AND 
  (PSAUTHITEM.BARNAME <> ' '
 OR
  PSAUTHITEM.BARITEMNAME <>
  ' ' OR
  PSAUTHITEM.PNLITEMNAME <>
  ' ')) OR
 (PSAUTHITEM.MENUNAME LIKE
 ('APPLICATION_DESIGNER%')
 AND ((PSAUTHITEM.BARNAME
  <> ' ' AND
 PSAUTHITEM.BARNAME NOT IN
 (SELECT OBJNAME
  FROM PS_APP_DES_OBJECTS
  WHERE PSAUTHITEM.BARNAME = 
   OBJNAME)) OR
  PSAUTHITEM.BARITEMNAME 
   <> ' ' OR
  PSAUTHITEM.PNLITEMNAME 
   <> ' ')) OR
  PSAUTHITEM.MENUNAME = 'REN'
  AND
 ((PSAUTHITEM.BARNAME <> ' '
   AND PSAUTHITEM.BARNAME
   NOT IN 
   (SELECT OBJNAME 
    FROM PS_APP_DES_OBJECTS
    WHERE PSAUTHITEM.BARNAME =
     OBJNAME)) OR
    PSAUTHITEM.BARITEMNAME 
    <> ' 'OR
    PSAUTHITEM.PNLITEMNAME 
    <> ' ' ))

SEC-29

The displayed PSPRSMPERM rows contain invalid PORTAL_PERMTYPE values.

Run the following SQL:

DELETE FROM PSPRSMPERM
WHERE PORTAL_PERMTYPE = ' '
 AND EXISTS 
(SELECT 'X' 
 FROM PSPRSMPERM PP2
 WHERE PSPRSMPERM.PORTAL_NAME =
  PP2.PORTAL_NAME
 AND PSPRSMPERM.PORTAL_REFTYPE = 
  PP2.PORTAL_REFTYPE
 AND PSPRSMPERM.PORTAL_OBJNAME = 
  PP2.PORTAL_OBJNAME
 AND PSPRSMPERM.PORTAL_PERMNAME
 = PP2.PORTAL_PERMNAME
 AND PP2.PORTAL_PERMTYPE 
 <> ' ');

UPDATE PSPRSMPERM 
SET PORTAL_PERMTYPE = 'P'
WHERE PORTAL_PERMTYPE = ' '
 AND EXISTS 
(SELECT 'X' FROM
 PSCLASSDEFN
 WHERE CLASSID = 
 PSPRSMPERM.PORTAL_PERMNAME);

SEC-30

Missing users in the PS_ROLEXLATOPR table.

Every User that is defined in the PSOPRDEFN table should have a corresponding Role User entry in the PS_ROLEXLATOPR table.

SQL-01

SQL text without a base definition.

Run the following SQL:

DELETE FROM PSSQLTEXTDEFN
WHERE SQLID NOT IN
 (SELECT DISTINCT SQLID
  FROM PSSQLDEFN)

SQL-02

SQL definitions without SQL text.

Run the following SQL:

DELETE FROM PSSQLDEFN
WHERE SQLID NOT IN 
 (SELECT DISTINCT SQLID
  FROM PSSQLTEXTDEFN)

SQL-03

SQL descriptions without a base definition.

Run the following SQL:

DELETE FROM PSSQLDESCR
WHERE SQLID NOT IN 
 (SELECT DISTINCT SQLID
  FROM PSSQLDEFN)

SQL-04

SQL descriptions without associated SQL text.

Run the following SQL:

DELETE FROM PSSQLDESCR
WHERE SQLID NOT IN
 (SELECT DISTINCT SQLID
  FROM PSSQLTEXTDEFN)

SQL-05

AE SQL without SQL definitions.

This reveals Application Engine SQL Actions that do not contain any SQL code within them.

Open the Application Engine program and complete the entry of the SQL before attempting to run the program.

If the empty SQL actions are delivered by PeopleSoft, open an incident with the GSC to report the corrupt AE program.

SQL-06

AE SQL that's not referenced.

This reveals an Application Engine SQL object that is not being referenced by an AE program. This indicates that the AE program is deleted but the associated SQL is not. The orphaned SQL does not cause issues other than consuming disk space.

If the orphaned SQL is delivered by PeopleSoft, open an incident with GSC to make sure that it is not a symptom of a larger problem, such as a corrupted AE application.

SQL-07

Record Views/Dynamic Views without SQL definitions.

Complete the entry of the record view or dynamic view before attempting to build or create the view. Each record should be opened, and the SQL should be entered as required.

SQL-08

View SQL that are not referenced by record or dynamic views.

Run the following SQL:

DELETE FROM PSSQLDEFN
WHERE SQLTYPE = 2 AND
 SQLID NOT IN
  (SELECT DISTINCT RECNAME
   FROM PSRECDEFN
   WHERE RECTYPE = 5 OR
   RECTYPE = 1)

DELETE FROM PSSQLDESCR
WHERE SQLTYPE = 2 AND
 SQLID NOT IN
  (SELECT DISTINCT RECNAME
   FROM PSRECDEFN
   WHERE RECTYPE = 5
   OR RECTYPE = 1)

DELETE FROM PSSQLTEXTDEFN
WHERE SQLTYPE = 2 AND
 SQLID NOT IN
  (SELECT DISTINCT RECNAME 
   FROM PSRECDEFN 
   WHERE RECTYPE = 5 
   OR RECTYPE = 1)

TREE-01

Tree Structure table contains Level Record name that does not exist in Record Definition table

Use Tree Manager to open the structure and fix the invalid fields.

TREE-02

Tree Structure table contains Level Page name that does not exist in Page Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-03

Tree Structure table contains Node Record name that does not exist in Record Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-04

Tree Structure table contains Node Field name that does not exist in RecordField table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-05

Tree Structure table contains Node Page name that does not exist in Page Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-06

Tree Structure table contains Detail Record name that does not exist in Record Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-07

Tree Structure table contains Detail Record name that does not exist in Record Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-08

Tree Structure table contains Detail Page name that does not exist in Page Definition table.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-09

Tree Structure table contains Summary Tree that does not exist in Tree Level table.

See the following section on Notes for TREE-09.

TREE-10

Tree Structure table contains Level Menu-Menu Bar combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-11

Tree Structure table contains Node Menu-Menu Bar combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-12

Tree Structure table contains Detail Menu-Menu Bar combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-13

Tree Structure table contains Level Menu-Page combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-14

Tree Structure table contains Node Menu-Page combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-15

Tree Structure table contains Detail Menu-Page combination that does not exist.

Use Tree Manager to open the structure and fix the invalid fields.

TREE-16

Tree Definition Level count does not match the record count in Tree Level table.

Set the Count in the Tree Definition table to reflect the actual number of records that are in the PSTREELEVEL table for this tree branch. Note that a problem may occur if some levels are missing and there are still nodes referencing them. In this case, the nodes do not open the tree correctly. The third SELECT checks for the previous situation. If this is the problem, run PSTED, and define the missing levels, save the tree, and then close and reopen it.

SELECT COUNT(*) 
FROM PSTREELEVEL
WHERE TREE_NAME = 'tree_name'
 AND SETID = 'setid'
 AND EFFDT = 'effdt';

UPDATE PSTREEDEFN 
SET LEVEL_COUNT = $count
WHERE TREE_NAME = 'tree_name'
 AND SETID = 'setid'
 AND EFFDT = 'effdt';

TREE-17

Tree Definition Node count does not match the record count in Tree Node table.

Set the count in the Tree Definition table to reflect the actual number of the records that are in the PSTREENODE table for this tree branch.

SELECT COUNT(*) FROM PSTREENODE
 WHERE TREE_NAME = 'tree_name'
 AND SETID = 'setid'
 AND EFFDT = 'effdt' AND 
 TREE_BRANCH = 'tree_branch_name';

UPDATE PSTREEDEFN 
SET NODE_COUNT =  $count
WHERE TREE_NAME = 'tree_name'
 AND SETID = 'setid'
 AND EFFDT = 'effdt' AND
 TREE_BRANCH = 'tree_branch_name';

For branched trees, use following SQL for each branch in the tree.

Note. For trees with branches, the UPDATE also uses a different TABLE NAME and there are two UPDATE statements.

SELECT COUNT(*)
FROM PSTREENODE
WHERE TREE_NAME = 'tree_name' 
AND SETID = 'setid' 
AND EFFDT = 'effdt' 
AND TREE_BRANCH = 
 'tree_branch_name';

UPDATE PSTREEBRANCH
SET NODE_COUNT = $count
WHERE TREE_NAME = 'tree_name' 
AND SETID = 'setid' 
AND EFFDT = 'effdt'
AND TREE_BRANCH = 
 'tree_branch_name'

UPDATE PSTREEDEFN
SET NODE_COUNT = 0, 
WHERE TREE_NAME = 'tree_name' 
  AND SETID = 'setid' 
  AND EFFDT = 'effdt'
  AND TREE_BRANCH =
 'tree_branch_name'

For trees without branches, do not include the "TREE_BRANCH=" lines. For example:

SELECT COUNT(*)
FROM PSTREENODE
WHERE TREE_NAME = 'tree_name' 
AND SETID = 'setid' 
AND EFFDT = 'effdt' 

SELECT COUNT(*)
FROM PSTREENODE
WHERE TREE_NAME = 'tree_name' 
AND SETID = 'setid' 
AND EFFDT = 'effdt'

UPDATE PSTREEDEFN
SET NODE_COUNT = 0, 
WHERE TREE_NAME = 'tree_name' 
AND SETID = 'setid' 
AND EFFDT = 'effdt'

TREE-18

Tree Definition Leaf count does not match the record count in Tree Leaf table.

Set the Count in the Tree Definition table to reflect the actual number of records that are in the PSTREELEAF table for this branch.

SELECT COUNT (*) 
FROM PSTREELEAF
WHERE TREE_NAME = 'tree_name'
AND SETID = 'setid' 
AND EFFDT = 'effdt'
AND TREE_BRANCH = 
 'tree_branch_name';

UPDATE PSTREEDEFN
SET LEAF_COUNT = $count
WHERE TREE_NAME = 'tree_name'
AND SETID = 'setid' 
AND EFFDT = 'effdt'
AND TREE_BRANCH = 
 'tree_branch_name';

TREE-19

Tree Definition contains Structure ID that does not exist in Tree Structure table

Use Tree Manager to create the structure that you desire by using the name that is reported in this audit.

TREE-20

Tree Definition contains Query Access Group structure with undefined levels and leaves.

Query trees should have no leaves and no levels. This audit finds exceptions to that case in the definition counts.

UPDATE PSTREEDEFN 
SET LEVEL_COUNT = 0,
 LEAF_COUNT = 0
WHERE TREE_STRCT_ID = 
 'ACCESS_GROUP' AND
 (LEVEL_COUNT <> 0 OR
  LEAF_COUNT <> 0);

TREE-21

Tree Selector Control contains Tree name that is not defined in Tree Definition table.

This audit flags records in the PSTREESELCTL tables for records that don't have a corresponding record in the PSTREEDEFN table.

DELETE FROM PSTREESELCTL A
WHERE NOT EXISTS
 (SELECT 'X' FROM  PSTREEDEFN B
  WHERE B.SETID = A.SETID
  AND B.TREE_NAME = A.TREE_NAME
  AND B.EFFDT = A.EFFDT)

TREE-22

Tree Definition Level count does not match level use.

See the section titled “Notes for TREE-22” below.

TREE-23

Tree Level does not exist in Tree Definition table.

Tree Level records in the PSTREELEVEL table exist for trees that don't exist in the PSTREEDEFN table.

DELETE FROM PSTREELEVEL A
WHERE NOT EXISTS
 (SELECT 'X'
  FROM PSTREEDEFN B
  WHERE B.SETID = A.SETID
  AND B.TREE_NAME =
   A.TREE_ NAME AND
  B.EFFDT = A.EFFDT)

TREE-24

Tree Node does not exist in Tree Definition table.

Tree Node records in the PSTREENODE table exist for trees that don't exist in the PSTREEDEFN table.

DELETE FROM PSTREENODE A
WHERE NOT EXISTS
 (SELECT 'X' FROM PSTREEDEFN B
  WHERE  B.SETID = A.SETID
  AND B.TREE_NAME =
   A.TREE_NAME AND
  B.EFFDT = A.EFFDT)

TREE-25

Tree Leaf does not exist in Tree Definition table.

Tree Leaf records in the PSTREELEAF table exist for trees that don't exist in the PSTREEDEFN table.

DELETE FROM PSTREELEAF A
 WHERE NOT EXISTS
 (SELECT 'X' FROM PSTREEDEFN B
  WHERE B.SETID = A.SETID
  AND B.TREE_NAME = A.TREE_NAME
  AND B.EFFDT = A.EFFDT)

TREE-26

Tree Leaf ranges are not valid in Tree Definition table.

Finds records in the PSTREELEAF table where RANGE_FROM is less than RANGE_TO.

Use Tree Manager to open the tree and correct the invalid range values.

TREE-27

Tree Leaf does not have parent Tree Node in Tree Definition table.

Run this SQL:

DELETE FROM PSTREELEAF A
WHERE NOT EXISTS
 (SELECT 'X' FROM PSTREENODE B
  WHERE  B.SETID = A.SETID
  AND B.TREE_NAME =
   A.TREE_NAME AND
  B.EFFDT = A.EFFDT AND
  B.TREE_NODE_NUM =
   A.TREE_NODE_NUM)

TREE-28

Tree Branch does not exist in Tree Branch table.

Refer to the "Tree Audit and Repair Utilities" chapter in the Tree Manager PeopleBook and run the Unbranch Tree Repair Utility so that all branches are removed from the tree.

TREE-29

Tree Branch does not exist in Tree Branch table.

Refer to the "Tree Audit and Repair Utilities" chapter in the Tree Manager PeopleBook and run the Unbranch Tree Repair Utility so that all branches are removed from the tree.

TREE-30

Tree Branch Node count does not match the record count in Tree Node table.

See Resolution for Tree-29.

TREE-31

Tree Branch Leaf count does not match the record count in Tree Leaf table

See Resolution for Tree-29.

TREE-32

Tree Node Num, Node Num End, or Level Num is invalid in Tree Branch table.

See Resolution for Tree-29.

TREE-33

Identify all orphan access group definitions as well as invalid access group definitions in the access group security.

Open Query Access Group Tree in Query Access Group Manager and update the identified Access Group so that a record is created in the Access Group Table.

TREE-34

Tree Definition Node Count Does Not Equal 0 for a Branched Tree.

See Resolution for Tree-29.

TREE-35

Tree Definition Leaf Count Does Not Equal 0 for a Branched Tree.

See Resolution for Tree-29.

XLATT-1

Translate table Field does not exist in database Field.

Create the field by using PeopleSoft Application Designer.

XLATT-3

Translate fields do not have associated translate values defined.

Edit translate field and enter translate value.

Manager-XXX

Where XXX is the associated three-letter code of the object type.

Version Check of listed table against PSVERSION.

Run the VERSION Application Engine program.

XMLP-1

Query Data Source does not exist in Query Definition table.

Remove the data source and all report definitions using the data source.

XMLP-2

Data Source Definition used by a Report Definition but does not exist in Data Source Definition table.

If this error is observed after the upgrade copy process, try copying the data source object from source database. If this is not the case, remove the report definition.

XMLP-3

Template Definition used by a Report Definition but does not exist in Template Definition table.

If this error is observed after the upgrade copy process, try copying the missing template definition from the source database. If this is not the case, remove the report definition.

XMLP-4

Template Definition not associated with any Report Definition.

Remove the template object.

XMLP-5

Template Definition associated with more than one Report Definition.

Delete all the report definitions using the template object and recreate them again from the user interface.

XMLP-6

Sub-Template Definition associated with any Report Definition.

Delete all the report definitions using the template object and recreate them again from the user inferface.

XMLP-7

Template File does not exist in file table.

If this error is observed after the upgrade copy process, try copying the missing file definition from the source database. If this is not the case, the template definition should be deleted and recreated.

XMLP-8

PDF Map File does not exist in file table.

If this error is observed after the upgrade copy process, try copying the missing file definition from the source database. If this is not the case, the template definition should be deleted and recreated.

XMLP-9

XLIFF File does not exist in file table.

If this error is observed after the upgrade copy process, try copying the missing file definition from the source database. If this is not the case, the template definition should be deleted and recreated.

XMLP-10

File definition not used by template file definition.

Delete the file object.

XMLP-11

File data not referenced by file definition.

Run Application Engine program PSXPCLEAN to delete orphan file definitions

XMLP-12

File definitions not referenced by file data.

Run Application Engine program PSXPCLEAN to delete orphan file definitions