OTL Custom Timecard Validation

Below are the steps you need to follow in order to create your customers validation logic.

1. System Administator > Create an OTL Formula flexfield context.  This is an optional step and is only necessary in cases where you wish to configure variable inputs i.e.- you wish to create a series of validation rules that can be configured using different input parameter values.

2. HRMS Manager > Create an OTL Time Entry Rule Formula that returns a value for success or error.

The fast formula needs to return either "S" meaning the time entry was successful or an "E" meaning the timecard entries failed the validation.  In the case of "E" an error message should be referenced via the Application Messages table with the message value being returned to the users self service timecard.  The error condition can be configured as a warning message(which allows time entry to continue) or an error message(that stops the time entry process until the condition is resolved).

In addition the application message may also use the token "&TER" which then returns the time entry rule name in the self service timecard as the actual timecard warning/error message.  This produces the most flexibility as the formula can be re-used with many different input parameters and display a different message based on the condition triggered.  The only limitation here is that a time entry rule name can be no longer than 80 characters in length.

It is also worth noting that OTL formulas can be created for any or all of the modules that you are integrating with i.e.- fast formulas in this context are not limited to just the Oracle Payroll module.

3. OTL Application Developer > Create your Time Entry Rule or Rules.  If you have created a flexfield with variable inputs you may create mutliple rules for a single formula subject to variable inputs.  As outlined in step 2 the time entry rule name specified here can also double as the acutal error message to be displayed on the timecard to the end user.

4. OTL Application Developer > Create your Time Entry Rule Group and add the necessary time entry rules created at step 3 for the group of workers you are planning the validation to apply to.

5. OTL Application Developer > OTL Preference Settings > Add the Time Entry Rule Group created at step 4 to the Time Store Time Entry Rules Preference in an appropriate folder.

6. OTL Application Developer > Assign the OTL Preference Eligibility Criteria i.e.- specify the worker or workers who will be subject to the timecard validations you have created.

A step 7 would then entail entering a timecard and performing both positive and negative tests against the time entry rules you have created.  Keep in mind you may need to bounce apache from time to time if your initial test fails and you need to modify the fast formula code.

The OTL framework enables a virtually unlimited capacity for the creation of custom validation and configuration messages with a relatively low overhead in development time.  It is one of OTL's most powerful but least understood features.

The creation of custom timecard validation rules will go a long way towards eliminating keystroke errors at point of timecard entry with the added obvious benefit in also reducing the volume of corrections that take place at a later date.  Not just in the timecard but more importantly for the downstream processes such as Distribution of Costs, Payroll Processing, Billing, etc.

Conversely you need to balance this approach and be careful not to create too much validation.  Put too much validation in place and users will simply work around the validation with whatever it takes to get their timecard submitted.  Which ironically may lead you back to square one where incorrect data is being processed through the timecard.