Exceptions

Exceptions are user- and system-defined warnings and errors to indicate a problem with a time reporter's time or a problem in the system. Exceptions are tied to the Time and Labor message sets in the message catalog. Defining exception conditions gives control over time reporting messages and warnings. You can keep an audit trail on resolved exceptions for problems, such as how many times an employee is tardy. If you choose to have the exception archived, you can run a query on resolved exceptions to track trends. By making exceptions allowable, you can track low-severity exceptions, and the system will create payable time without the need to make changes to reported time.

The system creates exceptions based on rules, which are defined in Time Administration, or errors that have been generated as a result of reporting time (specifically in the Time Validation process).

Almost all of the system-delivered exceptions have an exception severity of High and are defined as Not Allowable. These exceptions must be resolved before the Time Administration process creates payable time. You can change the severity and the allowable flag for system-delivered exceptions.

Exceptions that begin with TLX work with delivered attendance tracking and validations. The exceptions for attendance tracking are of a low severity, whereas the exceptions for validation are of high severity. These include validations for task reporting, time reporting codes, compensatory and leave time validations, and time reporter status validations.

The system-delivered validation sets are ST_SUBMIT, ST_TA and ST_ALL. If you don't want to have all the validations in this set run during processing, create a validation set and define which validation definitions to include. The ST_TA validation set represents all validations selected to run in Time Administration but not Submit Time. The ST_SUBMIT validation set represents all validations selected to run in Submit Time, but not in Time Administration. The ST_ALL validation set has all validations selected to run in both Submit Time and Time Administration. Each validation is configurable as to whether it is run in Submit Time, Time Administration, neither or both.

Establishing exceptions is the first part of setting up validation criteria so that the Time Validation process can generate exceptions correctly. You also need to set up PeopleSoft Application Engine sections and validation definitions in order for the system to generate exceptions through the Submit Time process. Validation definitions tie the SQL and exception information together to provide the system with a reference and a way to execute exceptions.

This graphic illustrates the areas that need to be set up so that the system can generate exceptions and perform validations during processing.

To establish user-defined exceptions, set up Time and Labor messages in the message catalog using PeopleTools. See the product documentation for PeopleTools: PeopleSoft Application Designer Developer's Guide.