Creating Rules in Time Administration

This chapter provides overviews of time administration and rules, and discusses how to:

• Create value lists.

• Define rule elements.

• Specify table access.

• Define table relationships.

• Define template-built rules.

• Create rules with actions and conditions.

• Create SQL objects.

• Work with User Exits.

• Define attendance programs.

• Assemble rules.

• Export, import, and recompile rules.

• Add rules to a rule program.

Understanding Time Administration

This section discusses:

• The create rules component

• The batch processing component

• The online processing component

Although the Time Administration processes are complex and varied, the Time Administration business process has these main components:

Create Rules Component

The Create Rules component has these online tools for defining rules:

See Also

Defining Template-Built Rules

Creating Rules with Actions and Conditions

Creating SQL Objects

Enterprise PeopleTools PeopleBook: Application Engine

Batch Processing Component

The batch process in Time and Labor generates payable time. It executes the rules defined using the Time and Labor online tools for rule creation, selects the appropriate time reporters for processing, combines time reporters into batches for efficient processing, determines the period to process, and calculates prior period adjustments.

See Also

Understanding the Batch Process in Time Administration

Online Processing Component

Time and Labor enables you to define online rules and immediately estimate the effect of applying these rules to weekly elapsed and punch time. You can invoke the Apply Online Rules process from the Timesheet page. When you do, the system executes an abbreviated version of the Time Administration process for a selected time reporter, applying only those rules that are defined for both batch and online processing. (You specify the maximum number of online rules that can be added to a rule program when you complete the Time and Labor Installation page during implementation.)

The system begins by looking at the transactions entered on the Time Reporting page. Depending on your rule definitions, it may pull in and process time for a day, week, or specified time period and will display the results accordingly.

When you define a rule for both online and batch use, be sure the time period that the rule evaluates will handle day, week and time periods that may be defined on the timesheet. Templates for attendance rules, such as templates 360, 360A, 360B as well as templates for exception rules 300, 310, and 320 may be better suited for batch processing.

Estimated payable time that is created by the online process is assigned the payable time status Online Estimate (OE). The next time you run the Time Administration batch process, the system deletes online estimates and replaces them with payable time in an Estimated(ES) or Needs Approval (NA) payable status.

To create actual payable time, run your rules as part of the Time Administration batch process; however, online processing enables you to preview the effect of weekly elapsed and punch time rules directly, online, in advance of the batch run. In addition, you can detect and resolve user-defined exceptions that result from the application of online rules.

Online Processing Steps

The Apply Online Rules process bypasses these phases of processing, which are executed during the batch Time Administration run:

• Attendance processing.

• Offset processing.

• Compensatory time balance validation.

• Calculation of estimated gross for rule override transactions.

• Update of TA_STATUS and EARLIEST_CHGDT.

Understanding Rules

This section discusses:

• General setup steps.

• Rules from actions and conditions and SQL objects.

• Rule step creation guidelines.

All rules in Time and Labor are written in SQL. You don't have to be a SQL expert to create rules because you will probably create most rules using templates, and the templates contain the basic logic, underlying structures, and necessary SQL objects. However, an understanding of SQL is helpful, particularly if you use actions and conditions, or SQL objects to define your rules, since these tools give direct access to SQL logic and language. In addition, to properly create, test, and troubleshoot rules, you should understand the structure of a SQL statement and the basic procedures for converting business rules into SQL rules.

General Setup Steps

Perform these two setup steps before creating rules if you are using either actions and conditions, or SQL objects to define the rules:

• Specify which tables (or records) to access and which SQL actions rule's developers can access.

  You'll do this using the Working Tables page.

• If you create a condition that references a field that is not part of the record being updated, define a relationship definition (or join) between the record you are updating and the external record.

  To do this, use the TL Relationship Definitions page. Setting up a relationship definition eliminates the need to code this relationship. If you are creating rules using actions and conditions, set up this relationship definition beforehand (if you must refer to external tables). You cannot define a table join within the rule itself. If you are using SQL objects, create a table join directly in the rule.

See Also

Specifying Table Access

Creating SQL Objects

Rules from Actions and Conditions and SQL Objects

When you use the Actions and Conditions or the SQL Objects pages, you won't create complete rules, but the building blocks of rules: rule components. To define a complete rule, you must:

• Link the components to other components.

• Place the components in the proper order for processing (define rule steps).

• Specify the period of interest for the resulting rule.

• Group rules into rule programs and then link these rules to time reporters through workgroups.

Note. Template-built rules are fully defined rules. This means that you don't need to define the rule steps that make up a template-built rule. However, you do need to add template-built rules to rule programs on the Rule Programs page, and assign the rule program to a workgroup.

To complete a rule definition:

1. Define the rule components.

   Use Actions and Conditions or SQL Objects.

2. Define the rule period.

   Specify the period of interest for the rule using the Define Rule Header page. Valid periods include PeopleSoft-delivered periods and any time periods created using the Time Period pages. The system uses time periods to determine the data for a particular span of time on which the rule will act. The Time Administration program also uses the time period to determine which reported time to load into the working tables during processing.

3. Define rule steps.

   Once you define the individual building blocks that make up a rule using actions and conditions or SQL objects, you must combine these components into complete rules and place them in the correct processing order by arranging them into rule steps. Each rule can have one or multiple steps. You'll order individual rule components into rule steps on the Define Rule Steps pages. SQL processes the records in sets. Rule steps must be properly ordered for set processing. Review delivered rule templates (with the rule ID prefix of TEMPLATE) to see how rule steps are organized for set processing. Test the SQL statement for each rule step with the database query tool to ensure that it produces the desired results before continuing with the next step. You may need to replace meta-SQL with platform–specific SQL before testing the SQL statement.

4. Assign the rule to a rule program.

   Add your rules to a rule program using the Rule Program and Program Detail pages. The rule program specifies the set of rules and the order in which the Time Administration process executes them.

   Note. The number of online rules you can include in a rule program is determined by the entry in the Maximum Online Rules field on the TL Installation page.

   Note. Rule programs are effective-dated, but the individual rules contained within them are not. You cannot modify a rule once you assign it to a rule program. However, you can remove the rule from the rule program and replace it, if appropriate, with a new rule. This feature ensures the referential integrity of rules processing.

5. Attach the rule program to a workgroup.

   Use the Workgroup page. The rule program determines which rules are processed for the time reporters in the workgroup. If a rule does not exist in the rule program associated with a workgroup, no member of the workgroup is processed using that rule.

See Also

Creating Rules with Actions and Conditions

Creating SQL Objects

Establishing Workgroups

Assembling Rules

Rule Step Creation Guidelines

When you create rules in Time Administration, you translate the organization's business rules into SQL statements for the system. The Time Administration pages enable you to implement rules, but they are not design tools. Before you enter any information in these pages, design and organize your rule steps, consider the SQL involved, and decide which Time Administration options to use. This section provides guidelines for understanding, designing, and organizing rule steps. The end of this section provides an example that outlines more explicitly how to enter rule steps into the system.

Note. Use the simplest building blocks when creating rules. Whenever possible, use or modify the delivered rule templates rather than creating new actions and conditions or SQL objects to define rules.

Design and Organize Rule Steps

Determine whether you can use one of the delivered rule templates or if you must create either actions and conditions or SQL objects. Consider which rules or parts of rules to reuse. If you can use part of a rule repeatedly or in many ways, create an action or condition or a SQL object so that you can reuse that part of the rule.

Think about dependencies: what should be checked or processed first. If you want to act on a subset of data or the results of a query, define that data or subquery first. If you want to act only if a certain condition exists, create the statement to determine if the condition is true before inputting the action. If you want to perform multiple actions on a single row, think about processing order. For example, if you must compare daily reported time to daily scheduled hours, sum the daily reported time and scheduled time first. Although the comparison and summation could be a single step, keep each step relatively simple for maintenance and troubleshooting. Specify and order rule steps on the Define Rule Steps page.

Avoid broad or redundant querying or processing. For optimal performance, create conditions that retrieve the fewest possible records and still satisfy your data needs. For example, specifying certain column names in your Select statements is more efficient than selecting all columns. Use the logical operator IN instead of OR, since IN is processed faster than OR.

If you want to create a rule that concerns a certain period of time, define a valid rule period ID for that rule.

Use all the tools available to you. When possible, use PeopleSoft-delivered objects. Create value lists instead of multiple conditions. Several working tables are delivered within rules, but you can create your own working tables. They must be temporary tables.

Warning! Do not modify delivered working tables. If any of the delivered working tables are modified, template-built rules do not function properly and may generate unexpected results.

Translate Business Rules into SQL Rules

Before you create rules in Time and Labor, have a clear idea of how you manage both time and time reporters, and have the business rules in front of you when you begin. Certain terminology in these documents has counterparts in particular SQL conditions and actions. Words such as update, replace, and substitute frequently imply the SQL action update. Words such as where, if, when, and in case of imply dependencies and conditions.

Use Working Tables within Rules

Before Time Administration can execute a rule, it moves the time reporter data needed to run the rule from scheduled and reported time into a data store known as Intermediate Payable Time. Rules are applied to information in the data store rather than to data in scheduled or reported time to protect the integrity of the source data. The Intermediate Payable Time data store comprises these five tables:

• TL_IPT1

• TL_IPT2

• TL_IPT3

• TL_IPT4

• TL_IPT5

In addition to the Intermediate Payable Time tables, you can access a number of other working tables in the system. Most of these working tables start with the prefix TL_WRK.

Note. You can create your own working tables to store data temporarily, but they must be temporary tables.

Rules for Using Working Tables

When you create rules in Time Administration, remember that:

• Time Administration automatically loads much of the data for executing rules into the Intermediate Payable Time table TL_IPT1.

  In the rules, you can move data back and forth between this table and the other Intermediate Payable Time tables. For example, the rule can move time data from TL_IPT1 to TL_IPT2, apply a specific TRC to this time, and then update the original row of data in TL_IPT1 with the new TRC-associated data.

• You must decide when and how to move data from TL_IPT1 to other working tables.

  After the rules process and modify the data in other tables, return any processed data to send to Payable Time back to TL_IPT1, which is the table containing the original, raw data. That is, push the data in its final form—the form in which to the data to Payable Time—back to TL_IPT1. If the data does not exist in TL_IPT1, it will not become part of Payable Time.

• You must always truncate (or clear) working tables before moving data into them.

  This ensures that the data that remains in those tables from previous rules processing does not interfere with or corrupt the new data. To truncate any working table, use the %TruncateTable command, which is included in the list of meta-SQL commands supported by PeopleSoft. However, never truncate or delete the data in TL_IPT1; it contains raw time data to execute the rules. If you delete this data, the rules have nothing to process.

• You can move data from external tables (nonworking tables) into working tables.

  If you do not plan to process or modify this data, but you must verify it (in a condition statement, for example), consider reading the external tables directly rather than moving large quantities of information into the working tables. Moving large quantities of data into TL_IPT1 can affect processing speed.

Example: Translating Business Rules into SQL Rules

This example illustrates how to translate a business rule into a SQL rule, and how the resulting SQL rule moves data from TL_IPT1 to other working tables in the system. Suppose that your business rule states: All hours worked in excess of 40 hours in any one week shall be paid at the rate of 1.5 times the employee's applicable hourly rate.

The first step is to rewrite the business rule in a simpler sentence. If possible, translate business concepts into Time and Labor terms. For example, you recognize that the rate of 1.5 times the normal rate implies a different (overtime) TRC. Rewrite this business rule as: Replace all hours in excess of 40 in a week with TRC OT 1.5.

Next, determine what type of action the system will take. Most business rules require an insert or update and may require subqueries to determine more precisely which rows to affect. This example requires the update action.

Note. If your business rules require you to store the original rows and add rows only where the TRC changes, you would create an insert action.

Next, consider what conditions exist in the statement. In our example, in excess of 40 hours and in one week are conditions.

To accomplish this rule, you need seven steps. Steps one through two are actions; steps three through seven are SQL objects:

1. Delete TL_IPT2 (truncate working table).

2. Delete TL_IPT3 (truncate working table).

3. Insert affected row (Friday, 10, 46, REG) into TL_IPT2 with hours over threshold and new TRC.

4. Insert rows after affected row (Saturday, 6, 52, REG) into TL_IPT3.

5. Calculate TL_QTY-TL_QTY in work record (TL_IPT2) and update row (Friday, 10, 46, REG becomes Friday, 4, 40, REG) in TL_IPT1.

6. Insert new row (Friday, 6, 46, OT1.5) into TL_IPT1 with new sequence number.

7. Update TL_IPT1 TRC with 'ot1.5' where exists in TL_IPT3.

The shaded rows in these tables represent Intermediate Payable Time created by these rule steps. Changes to the original TL_IPT1 data are in italics:

Data in IPT1

This table lists the data in IPT1:

Data in IPT2

This table lists the data in IPT2:

Data in IPT3

This table lists the data in IPT3:

Data in IPT1 After Processing

This table lists the data in IPT1 after processing:

Note. This simple example ignores the TRC. A more complicated example could also include a daily rule run before this and might also create overtime.

Using Value Lists within Rules

When you want the condition or action clause of a rule to apply to multiple values—such as multiple TRC codes, multiple shifts, or multiple task groups—create value lists rather than defining multiple conditions.

For example, you have a rule that tells the system to create premium time when a time reporter reports more than 40 hours to time reporting codes Regular, Sick, Vacation, and Holiday. Before you create this rule, you set up a TRC value list and add the TRCs for Regular, Sick, Vacation, and Holiday. When Time Administration executes the rule, it will refer only to the four TRCs in your list. For another example, you want to restrict the punch types that can follow an In punch. You can create a value list that includes only those punch types you deem valid. You can then use Rule Template240 to create a rule that generates an exception when an invalid punch type follows an In punch. Value lists are used within template-built rules.

This table shows each type of list you can create and where the values are defined:

Rule Elements within Rules

To control how and when rules are applied to different groups of time reporters, use rule elements. You can define up to five rule elements to represent any type of data, and then use these elements within the conditions for your rules.

Rule elements are associated with time reporters by:

• Assigning rule elements directly to time reporters on the Create Time Reporter Data page or the Maintain Time Reporter Data page.

• Positively reporting rule elements when entering time.

Example: Defining and Using Rule Elements

You define a rule element called Jobs. You also create these values for Jobs: HOST, CASHIER, ASST MGR, WAITER. Next, you build a rule that creates a premium if a worker positively reports the value ASST MGR for rule element 1. As an alternative, you might build your rule so that the system creates a premium whenever time is reported by a person for whom the value ASST MGR is entered in the Rule Element 1 field on the Create Time Reporter Data page or the Maintain Time Reporter Data page.

Note. Both the Time Reporting Template page and the Rapid Time Template page include options to override rule elements.

Meta-SQL within Rules

Use meta-SQL as an alternative to creating complex SQL commands on your own. Meta-SQL enables you to perform many SQL functions by giving you access to complex SQL operations in a shorthand form. Meta-SQL functions expand to platform-specific SQL statements. Time and Labor uses meta-SQL to interface with different database platforms. A meta-SQL operand begins with a percent (%) sign and returns a scalar value. Almost all meta-SQL constructs that are visible in Time and Labor are PeopleTools meta-SQL constructs that are processed at run time.

Common HR Data in Rules

To use Human Resources or Time and Labor employee data within your rules, check whether the data exists in TL_PROF_WRK before creating multiple joins to tables in Human Resources. TL_PROF_WRK is a temporary table created at the beginning of the Time Administration batch run. It contains employee-related data retrieved from various HRMS and Time and Labor source tables, effective as of the current run. Instead of accessing the various source tables to create a rule, you can create a single join to this table to retrieve information relating to all the time reporters you must process.

Warning! Do not alter the structure of TL_PROF_WRK. Time Administration references this table at different times during the batch run.

TL_PROF_WRK contains fields derived from these source tables:

Note. This table contains data on the employees in each batch of time reporters for the period of interest defined by the Build Rule Map process. Because it only contains data for the period of interest defined by the rule map process, you cannot use it as a source of human resources data for periods extending beyond the period of interest.

Prioritizing Rules in Rule Programs

Consider rule priority when dependencies exist among the rules in a rule program. For example, you've defined these rules for the organization:

• Default TRC: Set any blank TRC to REG.

• Daily 8: Pay overtime (OT1.5) for hours worked in excess of 8.0 per day.

• Daily 12: Pay double time (OT2.0) for hours in excess of 12 per day.

• Weekly 40: Pay overtime (OT1.5) for hours worked in excess of 40 per week.

In this example, the second, third, and fourth rules evaluate time with a TRC of REG. In addition, they are replace-type rules, for which REG is reduced to the threshold number and a new TRC is created for the excess hours. Based on this information, order your rule program as follows:

1. Default TRC

   Other rules must evaluate TRC REG.

2. Daily 12

   This must execute before the Daily 8 rule because REG is set to 12 if hours are over 12. If the Daily 8 rule runs first, the Daily 12 rule does not generate double time because all records with hours over 12 are set to 8.

3. Daily 8

   Daily 12 reduces hours in excess of 12 to 12.

4. Weekly 40

   Executed last because it needs to capture all the REG hours (including REG hours that are reduced by daily rules and REG hours that are not altered by daily rules).

Time Period Selection for A Rule

When creating rules, carefully analyze the time period to use. For rules that apply to punch time reporters, evaluate your daybreaker and the relationship between the out punch of one day and the in punch of the next day. In many cases, you may need to apply a time period greater than a day for the proper evaluation of a daily rule.

Rules Testing

Always test any rule you create using an interactive SQL tool. Otherwise, the system could generate incorrect results when it processes the rules.

Note. When testing a template-built rule, you may need to replace meta-SQL with platform specific code and enter values for variables that users would normally insert into the template's condition and action statements through the template pages.

See Also

Setting Up Time Reporters

Creating Rules with Actions and Conditions

Step 5: Building Time Reporter Profiles

Establishing Time Periods

Setting Up Day Breaker Options

Creating Rules from A Template

Creating Value Lists

To create value lists, use the Value List (TL_VALUE_LST_PNL) component.

This section discusses how to group codes into value lists.

Page Used to Create Value Lists

Grouping Codes Into Value Lists

Access the Value List page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Value List, Value List).

Value List Detail

Defining Rule Elements

To define rule elements, use the Rule Element 1 through Rule Element 5 (TL_RULE_ELEM1_PNL, TL_RULE_ELEM2_PNL, TL_RULE_ELEM3_PNL, TL_RULE_ELEM4_PNL and TL_RULE_ELEM5_PNL) components. Use the TL_RULE_ELEM1_PNL, TL_RULE_ELEM2_PNL, TL_RULE_ELEM3_PNL, TL_RULE_ELEM4_PNL and TL_RULE_ELEM5_PNL component interfaces to load data into the tables for these components.

This section discusses how to create user-defined rule elements.

Page Used to Define Rule Elements

Creating User-Defined Rule Elements

Access the appropriate Rule Element page (Set Up HRMS, Product Related, Time and Labor, Time Reporting, Rule Element 1 through Rule Element 5, Rule Element 1 through Rule Element 5).

Note. If you want to relabel the rule element fields, see the instructions in your PeopleTools PeopleBook.

Specifying Table Access

To specify table access, use the Working Tables (TL_TA_WORK) component.

Before creating rules using actions and conditions or SQL Objects, identify the tables (or records) to access and the actions to allow or prevent on these tables. This task consists of granting access to tables in Time and Labor and Human Resources.

Page Used to Grant SQL Access to Tables

Granting SQL Access to Tables

Access the Working Tables page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Working Tables, Working Tables).

The tables listed in the Record (Table) Name column are the records and tables to which you can grant (or deny) SQL access. Although we have predefined access to many tables in the Time and Labor system, you can change the delivered settings and can insert new rows for additional tables that you must access within your rules. All tables in the HRMS system are available for rules development. The only tables you do not have access to are PeopleTools tables.

SQL Action Elements

Additional Elements

Working Tables

All working tables that are truncated during batch processing must be identified on the Working Tables page and marked as Time Administration Runtime tables. If a runtime table is not listed in the Working Tables page and is not defined for deletion, it isn't truncated during the batch run. The Working Tables page is delivered with the PeopleSoft-delivered runtime tables for Time Administration preselected for deletion (truncation). If you create new runtime tables, enter rows for these tables on the Working Tables page and specify the AE program that they belong to.

Defining Table Relationships

To define table relationships, use the Relationship Definitions (TL_RELATIONSHIP) component.

Defining table relationships consists of joining fields on different record tables.

Page Used to Define Table Relationships

Creating Table Relationship Definitions

Access the Relationship Definitions page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Relationship Definitions, Relationship Definitions).

Fields

Define a relationship definition when you use a condition that references a field that is not part of the updated record.

Example

If a time reporter belongs to Union 'ABC' and reports more than eight hours per day under TRC REG, change REG to DBL.

The action for this statement is:

UPDATE PS_TL_IPT1
                
SET TRC = 'DBL'

The two conditions for this statement are:

WHERE PS_TL_IPT1.TRC = 'REG'
                
AND PS_JOB.UNION_CD = 'ABC'

To identify the correct effective-dated row and sequence from the JOB table, we would need several additional lines of code comparing the employee IDs, employee record numbers, and dates in the TL_IPT1 and JOB tables. Setting up a relationship definition eliminates the need to code this relationship individually.

Defining Template-Built Rules

To define template-built rules, use the Template-Built Rules (TL_TA_RULE_TMPLT) component.

Time and Labor delivers more than 40 rule templates. Use templates to create a variety of rules for the Time Administration program to execute when processing reported or scheduled time. You can create compensation rules for overtime and holidays, notification rules for irregular attendance, and rules for other time-reporting situations that require special processing.

Rules consist of condition and action statements. When using a template to create a rule, enter values for the variables within the template's condition and action statements. For example, to pay overtime when a time reporter reports more than 40 hours per week, you might use one of the Period Threshold templates to create the rule. The rule text of Template020 says:

"When a time reporter reports time under time reporting code a and the sum of hours is greater than b in the specified period c, then all hours in excess of b will be paid using TRC d."

To create a rule, open Template020, enter values for variables a, b, c, and d, and then save the new rule with a unique rule ID. Add the rule to a rule program on the Rule Programs page and assign the rule program to a workgroup.

Rules Created with Templates

After you save a template-built rule and include it in a rule program, you cannot change the values in the action or condition statements. However, you can modify rules by changing the actions or conditions (not simply the values within the conditional clauses), or by defining your own SQL Objects.

Before you modify a template-built rule, you need to understand how the values you have defined are stored and accessed. When you save your rule with a unique rule ID, the rule is compiled and the values you entered are stored in the record TL_TMPLT_RULE2, replacing a generic rule parameter in the template called %RuleTemplate(), which acts as a placeholder for each variable you defined. (A rule parameter is a variable that is substituted with a user-defined value when a template-built rule is compiled.) The record TL_TMPLT_RULE2 tracks the values that will be resolved in each rule step by rule ID. Because the same rule parameter represents all the values you define in a template-built rule, and there may be multiple instances of %RuleTemplate() in a single rule and in a single rule step, the record TL_TMPLT_RULE2 identifies the different occurrences of %RuleTemplate by step and sequence number.

You have several options for modifying a rule you have defined using the Define Template-Built Rules component:

1. Copy the rule and name a new rule using the Copy Rules page. When you copy the rule, however, you need to change the AE section to represent the new rule. In addition, for every occurrence of %RuleTemplate(), you need to substitute actual values by defining your own SQL Objects. The reason for this is that the connection is broken between the original rule ID and the values stored in the record TL_TMPLT_RULE2.

2. Modify the existing rule using the Define Rules component by changing one of the rule steps, or by adding a new step or substituting a different SQL object or action and condition in place of one originally created from the rule template. You must then compile this new rule. However, if you customize a rule in this way, the only way to view or make future changes to the rule is to use the Define Rules component; you can no longer access the rule through the Define Template-Built Rules component.

   Although this modification may not break the connection between the rule and the values contained in TL_TMPLT_RULE2, we recommend that you do not rely on this connection, but instead do the following:

   • To add a new step to a rule or change an existing step or object, hard code the values you want to use in that step (replace %RuleTemplate() with actual values), and recompile the rule.

   • To delete a step, recompile the rule; you do not need to worry about the connection being broken.

     Note. When modifying a rule, always test the rule to make sure that it functions as you expect.

3. Create a new rule ID from the same rule template, modify this rule using the Define Rules component, and compile the new rule. In this way, you retain the original rule, and have a newly modified rule to work with.

   Note. To change a rule that is already in a rule program, temporarily remove the rule from the rule program before changing it. After changing the rule, reassociate the rule to a rule program. This safeguard protects the integrity of the data generated by the original rule. After saving the new rule, be sure to update the appropriate rule program.

Example: Multiple Jobs and Rules

This example shows a Daily Overtime Rule and a Period Threshold rule, and shows how the overtime hours for all jobs are calculated:

Daily Overtime: The system totals the overtime for the day, checks where the threshold falls, and applies it to the job accordingly.

Note. In this example, overtime is defined as any time over eight hours.

Weekly Overtime:

Note. In this example, overtime is defined as any time over 40 hours.

Delivered Templates

The following tables list the rule templates delivered with Time and Labor. They are presented alphabetically by template type. The possible variables are in uppercase letters.

The Combine Data? heading identifies whether the Time Administration process combines the results for time reporters with multiple jobs. Results are combined only if each job (employee record) is in the same workgroup. (The employee records do not need to be in the same run of the Time Administration process to be combined.)

The Punch, Elapsed or Both Column indicates whether the rule template applies to punch time reporters, elapsed time reporters or both types of time reporters.

Accumulator Templates

Approval Required Template

Attendance Templates

Consecutive Days Templates

Daily Threshold Template

Default Template

Exception Templates

*When an OUT punch is missing for a day, the system does not know if the current shift should extend into the next day or end on the current day. As a result, the following work day cannot be processed correctly in Time Administration, as it does not know how to process the following day. It can look as if there is an improper order of punches (IN from the last work day, and an IN on the current work day, without an OUT, BREAK or MEAL punch in the middle.) Use Exception Rule Template 250 to trigger an exception when a particular punch type exceeds a certain number of hours, such as an IN punch. Use Exception Rule Template 240 to trigger an exception for an invalid order of punch types. Alternatively, you can create a custom rule to insert an OUT punch for a day in Reported Time, if one is missing, after "x" hours has passed.

Guaranteed Hours Templates

Holiday Templates

For proper evaluation of all holiday rules, use a time period that is greater than one day for the rule.

Note. For all "create" holiday rules, the system will create holiday pay in addition to reported or scheduled time. For all "replace" construct holiday rules, only scheduled time will be replaced with holiday pay. Any reported time will not be replaced with holiday pay.

Meal Template

Miscellaneous Templates

Missing Punch Templates

Period Threshold Templates

Premium Zone Templates

Schedule Deviation Templates

Shift Template

Specific Day Template

Task Template

See Also

Adding Rules to a Rule Program

Pages Used to Create Rules from A Template

Creating Rules from A Template

This section discusses how to:

1. Define and view general information for a rule.

2. Define the condition and action for the rule.

Defining and Viewing General Information for A Rule

Access the Template Header page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Template-Built Rules, Template Header).

Note. Template-built rules are not effective-dated; however, they are associated with an effective-dated rule program.

Punch Type

Select one or more punch types to apply the rule to, and select Include Elapsed Time, when applicable. For example, if you're creating an overtime rule, select Include IN Punch, Include BREAK Punch, and Include XFER Punch. When a template applies only to punch time reporters, the option to include elapsed time is unavailable.

Use Task Profile Indicator

When defining a rule that creates rows of time, select a task profile indicator to tell the system which task-related data to associate with the new row. This feature applies only to rules that create data. The options in this region are unavailable if a rule replaces data or generates an exception.

Template020 is an example of a rule that creates data. It states: "When a time reporter reports time under TRCs x and the sum of hours is greater than y in a specified period z, then all hours in excess of y will be paid under TRC z. A new TRC is created for each reported TRC affected by this rule."

Template110 is an example of a rule that replaces data. It states: "When a time reporter reports more than a hours under TRCs b in a day for c consecutive days, then all time reported for day c will be paid under TRC d."

We'll use Template020 and the following reported times to illustrate how each option in this region works. Assume we're creating an overtime rule that states if a person reports more than 40 hours in a week, create all hours over 40 with the TRC named OT. (The shaded row in this table represents the created time.)

In this example, the time reporter crosses the 40–hour boundary on Friday, so the system creates four hours as OT. The task data that it associates with the four hours (in this case, department), depends on the selected task profile indicator:

Run Location Indicator

These fields are available only if you activate the Run On-line Rules option on the TL Installation page.

See Also

Understanding Time and Labor Implementation

Adding Rules to a Rule Program

Defining Task Reporting Requirements

Defining and Viewing Template Rule Conditions and Actions

Access the Approval Required page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Template-Built Rules, Approval Required).

Explanation	Describes the action of the rule when you run the Time Administration process. The description includes both a condition and an action.
Update Rule Text	Click to see the values entered on this page inserted in the explanation of the rule as it appears in the Explanation field.
Modify Conditions	This button is available once a template-built rule is saved. It takes you to the Entering Basic Information About a Rule, which you can use to modify the conditional clause of the rule. This feature is for SQL users. If you use the Entering Basic Information About a Rule to modify the condition within a template-built rule, you cannot view the rule or change its values in the Template-Built Rules component. All future changes must be made on the Define Rules page.

Criteria (Conditions)

Use the fields in this region to define the exact conditions that must be met to trigger the rule. Enter a value for each of the numbered variables in the conditional clause of the explanation. The conditional clause (known as the Where clause in SQL), often begins with if or when. For example, the conditional clause shown contains two variables labeled (1) and (2):

If an elapsed time reporter doesn't report time to TRC (1)SPECIFIED_TRC for (2)SPECIFIED_DURATION days, create (3)SPECIFIED_HOURS hours of TRC (4)SPECIFIED_TRC. Use this template to compensate employees reporting elapsed time for perfect attendance.

Note. The fields that appear in the Criteria (Conditions) region vary by template. All possible fields are listed alphabetically and described:

Result (Action)

Use the fields in this region to define the action for the system to take when the condition is met. Enter a value for each of the numbered variables in the action clause of the explanation. For example, the action clause shown contains two variables labeled (3) and (4):

If an elapsed time reporter doesn't report time to TRC (1)SPECIFIED_TRC for (2)SPECIFIED_DURATION days, create (3)SPECIFIED_HOURS hours of TRC (4)SPECIFIED_TRC. Use this template to compensate employees reporting elapsed time for perfect attendance.

Note. The fields that appear in the Result (Action) region vary by template. All possible fields are listed alphabetically and described:

You can click the links at the bottom of the template page to access other pages within this component.

Creating Rules with Actions and Conditions

To create rules with actions and conditions, use the Actions and Conditions (TL_ACTION and TL_CONDITIONS) components.

When you define actions and conditions in Time and Labor, you define them independently of one another, which enables you to reuse the same actions or conditions in more than one rule without having to define them again. Using actions and conditions does not require a mastery of SQL.

This section discusses how to:

1. Define general information for a SQL action.

2. Create the text of a SQL action.

3. Copy an action.

4. Define general information for a SQL condition.

5. Create the text of a SQL condition.

6. Copy a condition.

Pages Used to Create Rules with Actions and Conditions

Defining and Viewing General Action Information

Access the Action Header page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Actions, Action Header).

Some fields on the Action Header page always appear; others appear only in connection with the action type of Insert. These elements always appear:

These fields appear only if you select an action type of Insert:

Note. Click the links at the bottom of this page to access other pages in this component.

Creating Action Text

Access the Action Detail page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Action Detail, Action Detail).

If the action type on the Action Header page is Update or Insert, provide additional information about the fields in the target record (table) on which you are performing the action. For example, answer these questions: what fields are you updating or inserting data into and what are the sources (and types) of data that you are using to perform the insert or update?

The specific information to enter depends on the type of action specified on the Action Header page and the value entered in the Insert Source Indicator field.

Enter the action details on the Action Details 1 and Action Details 2 tabbed grids. These grids work in combination; when you select a value on the Action Details 1 grid, related fields become available on the Action Details 2 grid.

Note. The Action Detail page is not available if your action type is Delete. Because you are deleting the contents of an entire record (table), do not enter field-level information on the Action Detail page.

Action Detail

This page displays additional fields, depending on the source field indicator selected on the Action Detail 1 page:

Copying Actions

Access the Copy Action page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Copy Actions, Copy Actions).

Duplicate the action by changing the name. Then you can modify the action and combine it with other actions and conditions to form new rules.

Note. You cannot modify individual actions or conditions after they are part of a rule and the system is in production (that is, after Production Environment is selected on the Installation Options page).

Note. After copying an action, use the Define Actions component (in correction mode) to modify the copy.

Defining and Viewing General Condition Information and Creating SQL Condition Text

Access the Conditions page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Conditions, Conditions).

Note. Template-built rules are not effective-dated; however, they are associated with an effective-dated rule program.

To define a condition on the Conditions page, specify the exact relationship that must occur between the elements before an action occurs. The action occurs only if the defined relationship is true. For example, you can specify that an action occurs only if a field equals a certain value or you can specify that an action occurs only if a field value is greater than another defined value. You specify the kinds of elements to compare (for example, a field value to a constant) in the Left Side and Right Side group boxes in the Expression Type fields. You define the precise relationship to occur between these elements (before an action can occur) in the Operator field.

The Define Condition page contains several fields that appear permanently, and others that display or hide depending on the left and right condition expression type. The following fields always appear:

Depending on the values in the Expression Type fields, these additional fields appear:

Copying Conditions

Access the Copy Conditions page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Copy Conditions, Copy Conditions).

First, duplicate the condition. Second, rename and modify the condition. Then, combine the condition with other actions and conditions to form new rules.

Note. You cannot alter individual actions or conditions after they are part of a rule and the system is in production (that is, after Production Environment is selected on the Installation Options page).

After you copy the condition, use the Define Conditions component (in correction mode) to modify the copy.

Creating SQL Objects

To create SQL objects, use the SQL Objects (TL_SQL_OBJECT) component.

SQL objects are the most complex Time and Labor rule objects that PeopleSoft delivers. Use them to define rules that are more complicated than those accommodated by templates or actions and conditions.

SQL objects are complete SQL statements that consist of an action and may consist of one or more conditions. They can include select statements, insert statements, table joins, and subqueries. If you prefer to write free-form SQL statements, use an expression text box within the SQL object pages to enter and format the SQL statements. If you do not want to use free-form SQL statements, the SQL object pages provide guidance for each aspect of an action and condition.

If you create a SQL statement, modify a PeopleSoft-delivered object using the Copy SQL Object page to create and modify a copy. Or, use the SQL Object component to build the statement.

We use this example for discussing most pages in the SQL Object component. This SQL statement applies to the SQL Objects, Tables, Automatic Joins, Select Fields, and Where Expressions pages. It does not apply to the Expression Text, Insert, or Update pages.

INSERT INTO PS_TL_WRK02 
                
  (DUR
                
 , EMPLID
                
 , TL_QUANTITY) 
                
SELECT
                
   A.DUR
                
 , A.EMPLID
                
 , SUM(A.TL_QUANTITY) - %RuleTemplate()
                
  FROM PS_TL_IPT1 A
                
     , PS_TL_WRK01 B 
                
 WHERE A.EMPLID = B.EMPLID
                
   AND A.DUR = B.DUR
                
   AND A.SEQ_NBR <= B.SEQ_NBR
                
   AND A.PUNCH_TYPE IN %RuleTemplate()
                
   AND A.TRC IN %RuleTemplate() 
                
 GROUP BY A.DUR, A.EMPLID 

Note. PeopleSoft recommends that you have adequate SQL training before attempting to use these pages. Use templates, actions, and conditions whenever possible.

Defining SQL Objects

For any SQL object you create, designate a name, several descriptions, and the type of object you are building. Although this component has eight pages, you see a maximum of five. The visible pages depend on the type of SQL object you are building. Here are some questions to consider when defining a SQL object:

• What type of SQL statement do I want to create?

• What is the driver table for the statement?

• What is the result table for the SQL Select statement?

• What do I want to name the resulting SQL statement?

• What other tables do I want to join to the driver table?

• For each table added, how do I want to join this table to the driver table?

  Do I want to do this later?

• What fields do I want to select?

• What fields on the driver table do I want to update?

• How do I want to determine the scope of the Where clause statement?

In the example, we want to create a select with Insert statement. We select from TL_IPT1 and insert the results of the query into TL_TA_RESULTS. Entries on the SQL Object page provide this clause of the original example:

INSERT INTO PS_TL_WRK02
                
(DUR
                
 , EMPLID
                
 , TL_QUANTITY)

Setup Tasks

Creating SQL objects comprises the following tasks:

1. Selecting the type of action and creating descriptions of the SQL statement.

2. Creating free-from SQL text.

3. Entering values in the record field of a particular table.

4. Defining meta-SQL parameters.

5. Creating expression text.

6. Updating a record field.

7. Designating which tables you will use in this SQL object.

8. Creating expression text for tables.

9. Joining tables.

10. Creating the first clause of a Select statement.

11. Creating expression text for the first clause of a Select statement.

12. Creating the Where clause of your SQL statement.

13. Creating expression text for the Where clause of a SQL statement.

14. Copying a SQL object.

SQL Object Component

The SQL Object component changes according to the type of SQL statement you are building. Use this table to determine which pages are visible for each type of SQL statement:

Pages Used to Create SQL Objects

Selecting Action Types and Creating SQL Descriptions

Access the SQL Object page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, SQL Object).

Note. SQL objects are not effective-dated, but they are associated with rules that are included in effective-dated rule programs.

Click the links at the bottom of this page to access other pages within this component.

See Also

Adding Rules to a Rule Program

Designating Tables in a SQL Object

Access the Tables page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Tables). In our example, TL_IPT1 is assigned an alias of A and TL_WRK01 is assigned an alias of B. The clause covered by this page is:

FROM PS_TL_IPT1 A
                
  , PS_TL_WRK01 B 

Update Where Clause

Click to update the Where clause of the SQL statement. The system automatically generates a SQL Where clause based on the effective date option.

Tables

Click the links at the bottom of this page to access other pages within this component.

Creating the First Clause of A Select Statement

Access the Fields page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Fields).

All the options that you include in the text of the statement are available as field values. Using this page, you can create the SQL text for this part of the example:

SELECT
                
   A.DUR
                
 , A.EMPLID
                
 , SUM(A.TL_QUANTITY) - %RuleTemplate()
                
GROUP BY A.DUR, A.EMPLID 

Click the links at the bottom of this page to access other pages within this component.

Joining Tables

Access the Joins page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Joins).

You can only create inner joins in Time and Labor. You can join on any fields using custom-selecting or by selecting the key fields option. Because of platform constraints, you cannot perform three-way joins or unions using the Automatic Joins page, but you can make several selects into a working table and use the data from there. You can also use the Expression Text page to write free-form SQL text that can include three-way joins or unions.

We want to join the TL_IPT1 table to the TL_WRK01 on the EMPLID and DUR columns in the following clauses:

WHERE A.EMPLID = B.EMPLID
                
  AND A.DUR = B.DUR

Click the links at the bottom of this page to access other pages within this component.

Creating the Where Clause of A SQL Statement

Access the Where Expressions page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Where Expressions).

In the example, the statement is true where the date under report is greater than or equal to itself.

AND A.SEQ_NBR <= B.SEQ_NBR
                
   AND A.PUNCH_TYPE IN %RuleTemplate()
                
   AND A.TRC IN %RuleTemplate() 

The system displays the record and correlation ID you selected for reference while creating the Logical Operator/Where clause.

Entering Values in the Record-Field of a Table

Access the Insert Fields page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Insert Fields).

Complete both the SQL Object and Insert Fields pages to create a complete Insert statement.

Click the links at the bottom of this page to access other pages within this component.

This page does not allow you to remove a field from the list that can have a null value. PeopleTools does not allow the insertion of data into a table without specifying a value for numeric and character fields. Therefore, fields that can have a null value cannot be removed from the list.

Entering Meta-SQL Parameters

Access the TL SQL Insert SecPNL page.

Updating A Record-Field

Access the Update Fields page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Update Fields). You can update a field with a constant, the result of a subquery, or an other value. You can perform basic mathematical functions on this constant before the final update of the field.

UPDATE PS_TL_IPT1
                
   SET TL_QUANTITY = TL_QUANTITY −
                
       (SELECT DISTINCT A.TL_QUANTITY
                
          FROM PS_TL_WRK02 A, 
                
               PS_TL_WRK01 B
                
         WHERE A.EMPLID = B.EMPLID
                
           AND A.DUR = B.DUR
                
           AND A.EMPLID = PS_TL_IPT1.EMPLID
                
           AND A.DUR = PS_TL_IPT1.DUR), TL_RULE_ID = %RuleTemplate()
                
 WHERE PS_TL_IPT1.SEQ_NBR = (SELECT DISTINCT B.SEQ_NBR
                
                               FROM PS_TL_WRK01 B
                
                              WHERE B.EMPLID = PS_TL_IPT1.EMPLID
                
                                AND B.DUR = PS_TL_IPT1.DUR)
                
   AND EXISTS (SELECT 'X'
                
                 FROM PS_INSTALLATION I
                
                WHERE 'R' = %RuleTemplate())

Field	Select the record field to update. The result of the subquery or math operation is placed in the specified field.
Value Source and Value Source 2	Select the source of the value to act upon. Valid options are: Constant, Another Field, Meta-SQL, Subquery, Template, Variable. Only one of the Value Source fields can be set to Subquery at a time. When you choose Subquery, the SQL Object Bind Variables link becomes available.
Field Name	Select the record field you want as the basis.
Math. Operator	To perform a mathematical function, select the operator. If you do not want to perform any mathematical functions, select (none). Valid options are: -, +, *, /.
SQL Object ID	This field is used to add a subquery to a Set clause.
SQL Object Bind Variable	Link to the SQL Bind Mapping page, this is available when Value Source is set to Subquery.
Constant and Constant 2	This field is available when you set the Value Source or Value Source 2 field to Constant.
Variable (2)	you can enter a state variable in this field when the Value Source 2 is set to Variable.
MetaSQL	You can enter a value in this field when the Value Source field is set to MetaSQL. This field is not available for any values in the Value Source 2 field.
	This icon links to the MetaSQL Parameters page, it is available when the Value Sourcefield is set to MetaSQL.

Copying SQL Objects

Access the Copy SQL Object page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Where Expressions, click the Left/Right Bind button on the Where Expressions page).

Use the Copy SQL Objects function to copy an existing SQL object.

To copy a SQL object:

1. Duplicate a SQL object by giving it a different name.

2. Modify the new SQL object.

   The copy function is similar to a Save As command and occurs when saving the page.

Note. You cannot modify SQL objects after they are part of a rule and the system is in production (that is, once Production Environment is selected on the Installation Options page.

After copying the SQL object, use the SQL Object component (in Correction mode) to modify the copy. Remember that the component will be modified according to the type of statement built.

Entering a complete Statement Using Free-Form Text

Access the Expression Text page.

Access the Expression Text page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, SQL Objects, Expression Text).

Enter up to 254 characters in the expression text box.

Show Text as Formatted SQL

You can click this button to view the formatted SQL statement. The formatted text is shown on the same page as view-only text. The name of this button then changes to Show Entered Text, which enables you to view and edit the text as it was originally entered.

See Also

Rule Step Creation Guidelines

Working with User Exits

User exits are an optional feature that can add PeopleCode and AE sections to regular Time and Labor processing. When you write user exits, add AE sections to the AE program TL_TA_RULES. Use all the AE constructs supported by PeopleTools (SQL, PeopleCode, looping constructs like Do When, Do While, and so on).

Note. If you create AE sections, they must have eight-character names. This is a PeopleSoft Application Engine requirement.

Note. Have adequate Application Engine and PeopleCode training before creating AE sections.

See Also

Enterprise PeopleTools PeopleBook: Application Engine

Defining Attendance Programs

To define attendance programs, use the Attendance Programs (TL_ATTEND_PGM_PNLG) component.

PeopleSoft Attendance Tracking is an optional feature that enables you to control time and administer attendance. You can track when punch-time reporters are late for work, leaving work early, or taking long lunches and breaks. The Attendance subfeature tracks punch-related attendance infractions. You do not have to create Time Administration rules to track attendance, which would be extremely cumbersome. This is a PeopleSoft-delivered set of rules to use if your business requires attendance tracking.

Attendance tracking prevents a time reporter from taking advantage of rounding rules. For example, suppose your organization rounds clock punches to the nearest quarter hour. If a time reporter clocks in late and clocks out early for every scheduled punch, this can result in paying the time reporter for almost 2.5 hours of nonwork time every week. Moreover, if you are paying overtime to this time reporter, the overtime rate will begin before the employee has worked 40 hours.

Attendance tracking compares punch-time, scheduled time, and attendance settings. Attendance infractions include tardiness, long lunches, early outs, and long breaks. The tracking can occur by three methods: fixed period, rolling period, and step period. The purpose for tracking punch-related infractions is to report user-defined recommended actions to be taken when tracking thresholds are met. This type of tracking provides a history of time reporters' attendance habits. We store this history information even when the period changes. Attendance processing occurs after IPT tables are loaded, but before rule are run.

A point system weights the severity of each infraction. While taking a long break might be a minor infraction, arriving at work late and clocking out early at the end the day might be major infractions. After you set up the recommended actions, the system automatically monitors a time reporter's behavior according to the information from the TCD.

A time manager can override or cancel any action scheduled by the system, and you can change the settings of attendance tracking any time the business rules or union regulations change. Although the system is delivered with standard actions, you can create custom actions.

Attendance tracking enables you to define the attendance characteristics and maintain those changes. When setting up, specify the tracking method, period ID, tracking items (tardies, long lunches, early outs, and long breaks), and points associated with each tracking item. Define the recommended actions and threshold of each action. You can choose a recommended action from a predefined list of actions or create a custom action. If you choose to create custom actions, choose Other and enter comments that describe the action.

See Also

Understanding the Batch Process in Time Administration

Understanding Tracking Methods

You can choose from three tracking method types: fixed period, rolling period, and step period. Each method is described in this table:

Understanding Attendance Program Tasks

Defining attendance programs and tracking attendance violations comprises the following tasks:

1. Specifying infractions to track, grace periods to allow, and the severity of each infraction.

2. Specifying which actions and when actions occur when infractions are committed.

3. Adding attendance programs to a rule program on the Program page.

4. Viewing, by employee ID, the action thresholds that a time reporter has crossed.

5. Viewing a time reporter's violation history.

   Note. You must link your attendance programs to rule programs, and then associate both to workgroups.

Pages Used to Define Attendance Programs

Specifying Attendance Infractions

Access the Attendance Program page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Attendance Programs, Attendance Program).

Attendance Tracking Detail

Use this group box to specify the particular rules and limits of your attendance program.

See Also

Setting Up Basic Tables

Specifying Attendance Infraction Actions

Access the Attendance Actions page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Attendance Programs, Attendance Program, Attendance Actions).

Action # (action number)	The system populates this column with the next consecutive sequence number. Although the numbers are automatic, enter actions in any order. Lower-numbered items occur first, so enter the least severe actions at the top of this list. Note. The order in which you enter attendance actions is crucial to system accuracy and data integrity. If you enter actions in the wrong sequence, the system does not reorder or re-prioritize them.
Attendance Action	Select the recommended action for this sequence number. Valid values are: Letter, Other, Suspension, Terminate, Verbal 1, Written 1, Written 2, Written 3. Letters are placed on file without the employee's knowledge. Written warnings are signed by the employee and manager as an acknowledgement that the employee was notified of the infraction. You can write an API to send a message when an action occurs, but the system only identifies infractions and displays the recommended action—it does not take any action. You cannot publish warnings or messages back to the TCD. The process does not progress if a manager excuses a step.
Points	Select when you want this action to occur. The system invokes this action when the time reporter's total number of points for the current tracking period is equal to or greater than the value in this field. The entry does not have to be a whole number; you can enter a three-digit number with up to two decimal places. The value must be a multiple of the highest point value on the Attendance Program page to prevent recommended actions from being skipped.
Comment	This 30-character, alphanumeric field is available only if you selected Other in the Attendance Action field. Enter a description of, or comment about, the action. You can create custom actions. For example, you might dock a time reporter's pay.

Viewing Action Thresholds

Access the Review Attendance Actions page (Time and Labor, View Exceptions and Attendance, Attendance Actions, Review Attendance Actions).

Viewing Attendance Violation History

Access the Attendance History page (Time and Labor, View Exceptions and Attendance, Attendance History, Attendance History).

Date Under Report	This field displays the date that applies to this row of data.
Description	The system description of the exception that occurred.
In Period	The system selects this check box if this row is in the current period. The system clears this check box for all history rows (archived data).

Assembling Rules

To assemble rules, use the Rules (TL_RULES) component.

Once you have defined the individual building blocks that make up a rule using actions and conditions or SQL objects, you need to combine these components into complete rules and place them in a logical order by arranging them into rule steps using the pages described in this section.

You'll also use these pages to modify existing rules or copies of rules. For example, you can take an existing rule (whether template built or of another type), open it within the Define Rules component, modify or add new actions or conditions to it, and then recompile the rule.

Rule Assembly Tasks

Assembling rules comprises the following tasks:

1. Entering basic information about a rule.

2. Defining the steps of the rule.

3. Creating descriptions for each rule step.

4. Viewing the SQL text of the rule step you are adding to a rule.

5. Copying rules.

Pages Used to Assemble Rules

Entering Basic Information About a Rule

Access the Rules page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules, Rules).

Compiled	The system populates this field automatically to signify whether the rule was compiled. When this field is selected, the rule was compiled and hasn't changed since that compilation.
Time Period ID	Select the time period of interest that applies to this rule. Values include the values delivered by the PeopleSoft system and any time periods that you created using the Time Period pages. The system uses the time period to determine the date range for the selection criteria of the rule. The Time Administration program also uses the time period to determine which reported time to load into the working tables during processing.
Run Location	You can update this field only if you activate the Run Online Rules option on the TL Installation page. Valid values are: Batch Only: Select for the system to apply this rule when you run the Time Administration batch process. Online and Batch: Select for the system to apply this rule when you run the Time Administration batch process or the Apply Online Rules process that you start from the elapsed timesheet or the punch timesheet.
User Exit	Select if the components of the rule are written in PeopleSoft Application Engine or in PeopleCode. If you select this option, the Compiled and Last Compiled fields are unavailable and the Define Rule Steps page is unavailable. The system locates the created section in the TL_TA_RULES library. Create a user exit by creating a new AE section within the TL_TA_RULES library. Add the AE section name to the AE section list on the AE Section page.
AE Section (application engine section)	Select the AE section to use to process this rule. This section is inserted into TL_TA_RULES library when you compile the rule. Note. Do not modify Time and Labor objects in the AE library. Use the Time and Labor pages.
Core Component	This field is display-only and is system-maintained. Many rules are delivered with Time and Labor. These rules are used in rule templates. If the rule you are viewing was created by the PeopleSoft system, then this field is set to Y. If you created this object, the system sets this field to N. When you add a new rule, the system sets the Core Component field to N.
Last Compiled	The system-maintained field that displays the last date and time that this rule was compiled.
Explanation	Enter a detailed description of the rule. You can include examples of how this rule is used and how it affects data in different scenarios.

Define Rule Steps - Rule Step Details Tab

Use this grid to enter the steps of the rule.

Note. Multiple views of this portion of the Define Rule page are available by selecting the tabs in the scroll area. We document fields that are common to all views first.

Rules usually begin with steps to truncate working tables (TL_IPT2-5 and other working tables) to create spaces within the working tables for processing steps in the rule.

Warning! Never truncate TL_IPT1. Doing so destroys the data.

Generally, order the rules by period. For example, if you have daily rules and weekly rules, the system should resolve the daily rules first.

Define Rule Steps - Description Tab

Access the Description tab on the Define Rule page.

See Also

Understanding the Batch Process in Time Administration

Establishing Time Periods

Building and Viewing Time Period Calendars

Rule Step Creation Guidelines

Rule Step Creation Guidelines

Viewing the SQL Text of A Rule Step

Access the Rule SQL Text Resolution page (click the Compile Rule button on the Define Rule Steps page).

Copying Rules

Access the Copy Rules page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Copy Rules, Copy Rules).

To copy a rule:

1. Duplicate a rule by giving it a different name.

2. Modify the new rule.

   The copy function is similar to a Save As, and is performed when you save the page. Use the Define Rule Header page to modify the copy.

Exporting, Importing, and Recompiling Rules

To move rules from one database to another, use the Rules Export (TL_EXP_RULE) component to export rules and the Rules Import (TL_IMP_RULE) component to import rules. Use the Rules Recompile (TL_RULE_RCMP) component to recompile Time and Labor rules.

Time and Labor enables you migrate rules across databases, which means that you can easily transfer rules created in an isolated testing environment into your production database.

Understanding Rules Migration

Moving Time and Labor Rules from one environment to another uses three distinct phases:

• Selecting rules for export and exporting all of the required rule elements.

• Importing rules from a rules export file.

• Recompiling rules for PeopleSoft templates.

Time and Labor uses PeopleTools DataMover and two DataMover scripts to complete the migration of Time and Labor rules from one environment to another. The system uses an Application Engine (AE) process to create the DataMover scripts required to export and then import the selected rules. The AE process then packages the rules and scripts into a DataMover DAT file in a location you specify from the run control page.

Note. You can only move rules created from PeopleSoft delivered templates.

Execute the Import and Recompile rules processes when the processes do not conflict with existing Time Administration processes. This is because the Import rules process transfers shared objects from records where a separation from the rule itself was not possible. In addition, any template modified during the Recompile rules process can affect existing rules, and a conflict with a Time Administration batch process would cause the batch process to crash.

You should execute the Import and Recompile rules processes in your Production environment when you run the existing Refresh Dynamic Groups process. This is because the Refresh Dynamic groups process is run daily and has the same potential conflicts.

The Export process does not change any existing structures in the environment. You can safely select rules and export the required rule elements at any time.

Pages Used to Export, Import, and Recompile Rules

Exporting Rules

Access the Rules Export page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules Export).

Include related Rule programs	Select this check box to include the most current effective-dated rows for the Rule Programs associated with the selected rules in the export file. If you do not select this field, then you must manually associate each imported rule to the corresponding rule program.
Create Scripts	Click to perform the following steps: Verify that the indicated script location path is correct. Analyze the content of each row in the Rules Export area of the page, resolve the selection of rules and store the results. Write the DataMover scripts for both the Export and Import rules processes.
Run	Click to perform the following steps: Initiate a DataMover process scheduler request to generate the rules DAT file based on the Export script created by the Create Scripts process. List each rule that is selected and processed in the message log file and indicate the completion of the DataMover process.
Script Location	Enter the location used by the system to store the DataMover scripts and DAT file created by the Export process.
Rule ID	Enter a specific rule to include in the exported rules file.
Template ID	Enter a Rules Template name to select all of the rules associated with that template for export
Template Type	Select a Template Type to specify that all of the rules associated with all of the rules templates for the specified template type are selected for export.

Importing Rules

Access the Rules Import page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules Import) and enter the location of the DataMover DAT file created by the Export rules process in the Script Location field.

Recompiling Rules

Access the Rules Recompile page (Set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules Recompile).

Recompile All Rules	Select to recompile all existing rule templates. Clearing this check box enables you to view the Rules Recompile region of the page.
Rule ID	Enter a specific rule to recompile.
Template ID	Enter a Rules Template name to select all of the rules associated with that template for recompiling
Template Type	Select a Template Type to specify that all of the rules associated with all of the rules templates for the specified template type are recompiled.

Adding Rules to a Rule Program

To add rules to a program, use the Rule Programs (TL_RULE_PGM) component.

After you organize the components of your rules in the proper order, you need to add your rules to a rule program using the Rule Program and Program Detail pages. The rule program specifies the set of rules the Time Administration process executes and the order in which it executes the rules. Rules programs are also the method by which you assign attendance programs to time reporters.

If you have elected to use online rule processing, the number of online rules you can include in a rule program is determined by your entry in the Maximum Online Rules field on the TL Installation page.

Adding rules to a rule program comprises the following tasks:

1. Naming and describing the rule program.

2. Linking an attendance program to the rule program.

3. Selecting the rules in the program and the order in which the Time Administration feature executes them.

Note. To activate a rule program (and its associated attendance program), you must link the program to a workgroup on the Workgroup page.

Note. Rule programs are effective-dated, but the individual rules contained within them are not. You cannot modify a rule once you assign it to a rule program. However, you can remove the rule from the rule program and replace it, if appropriate, with a new rule. This feature ensures the referential integrity of rules processing.

Pages Used to Add Rules to A Rule Program

Assigning an Attendance Program to a Rule Program

Access the Program page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Rule Programs, Program).

Attendance Program	Select the attendance program to associate with this rule program, if applicable. Attendance programs contain rules that track various attendance issues.
Description	Enter a complete description of the rule program in this field.

See Also

Defining Attendance Programs

Selecting Rules for a Program

Access the Program Detail page (Set Up HRMS, Product Related, Time and Labor, Rules and Workgroups, Rule Programs, Program Detail).

Note. The maximum number of online rules you can add to a rule program is determined by the entry in the Maximum Online Rules field on the Time and Labor Installation page.