Registering Functions

You must register functions to access them when you build a formula for the hourly rate or hours worked fields in the Timecard Automation programs. Functions are registered specifically for use with timecard templates, retroactive pay rules, or overtime rule sets. The functions that are included with the Timecard Automation module are already registered. Occasionally, you might need to use a function that is not registered, such as any custom functions that you create. You can use functions alone or in formulas.

When you register a function, you can define it as active or inactive. An active field or function is one that other users can access from a Timecard Automation program. You can use inactive mode to verify whether the function works properly before you make it active for other users.

Before registering a function, you should identify the usage code that the system uses to determine the program in which the function is used. Usage codes include:

• THRF - Identifies a timecard template hourly rate function.

• THWF - Identifies a timecard template hours worked function.

• RHRF - Identifies a retroactive pay rule hourly rate function.

• RHWF - Identifies a retroactive pay rule hours worked function.

• OHRF - Identifies an overtime rule hourly rate function.

• OCRI - Identifies an overtime change rules IF statement.

• OCRT - Identifies an overtime change rules THEN statement.

• OCR - Identifies a custom overtime rule that is created using a custom business function.

In addition to specifying the usage codes for a function, you should also identify this information for each function:

• The source module, which is the object name to which the function belongs.

  Object names that are associated with named event rule business functions begin with N. For example, N1861411 is the object name (or source module) that contains the various overtime hourly rate functions.

• The function name within the source module.

  Event rule logic and data structures are attached to individual functions within a source module.

• The status of the field availability (either active or inactive).

  Note:

  You can use the Field/Function Definition form to revise information about a function, such as its active status. The changes that you make to functions affect all batches of timecards that use changed fields and functions and that are processed after the change. Changes do not affect timecards that have already been processed.

  You can delete a function from the Fields and Functions program, thereby making it unregistered in the Timecard Automation module. Deleting a function removes it from the search list for the appropriate Hourly Rate or Hours Worked field, but does not remove it from the system.