Вы находитесь на странице: 1из 11

WHITE PAPER

Oracle Time & Labor


Overriding Earning Policies
When Transferring Time Entries
From the Time Store to OTLR



Copyright Information

Oracle Time and Labor, Releases 11i and 12
Copyright 2005 Oracle Corporation
All rights reserved.

Primary Author: Kris Van der Ploeg & John Finnegan
Contributors: Mark Vilrokx
Creation Date: 09-Mar-06
Last Updated: 15-Mar-06

This software was not developed for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It is the customer's responsibility to take all appropriate measures to ensure the safe
use of such applications if the programs are used for such purposes.
This software/documentation contains proprietary information of Oracle Corporation; it is provided under a
license agreement containing restrictions on use and disclosure and is also protected by copyright law.
Reverse engineering of the software is prohibited.
If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense,
then it is delivered with Restricted Rights and the following legend is applicable:
Restricted Rights Legend Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013,
Rights in Technical Data and Computer Software (October 1988).
Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
If this software/documentation is delivered to a U.S. Government Agency is not for use within the
Department of Defense, then it is delivered with Restricted Rights", as defined in FAR 52.227-14, Rights
in Data - General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. Oracle Corporation does not warrant that this document
is error free. No part of this document may be reproduced or transmitted in any form or by any means
electronic or mechanical, for any purpose without the express written permission of Oracle Corporation.
Oracle is a registered trademark and ConText, Enabling the Information Age, Oracle7, Oracle8, Oracle8i,
Oracle Access, Oracle Application Object Library, Oracle Financials, Oracle Discoverer, Oracle Web
Customers, Oracle Web Employees, Oracle Workflow, Oracle Work in Process, PL/SQL, Pro*C,
SmartClient, SQL*, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, and SQL*Report are
trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of
their respective owners.

Table of Contents
1. Introduction _____________________________________________________________________________4
1.1 Purpose of this Document _____________________________________________________________4
1.2 Intended Audience ___________________________________________________________________4
1.3 Definitions __________________________________________________________________________4
2. Overview of the Solution ___________________________________________________________________5
3. General Implementation Steps ______________________________________________________________6
4. Appendix Document References & Further Reading __________________________________________11


1. Introduction
1.1 Purpose of this Document
Many of Oracle Time and Labors (OTL) customer need to explode various timecard
entries differently based on a number of factors. For example, some bargaining units
require overtime and double time to be calculated differently for Saturdays and Sundays
than for week days. OTLs standard functionality only allows one earning policy to be
attached to a workers assignment record, though. This limitation poses no problem in
the professional timecard, because the timecard preparer can manually override the
default earning policy for individual time entries. The Self Service timecard has no
means for users to provide such overrides, however. This document describes a
straightforward, noninvasive customization for customers who wish to use Self Service
timecards but require the ability to apply more than one earning policy to the time entries
on their timecards.
1.2 Intended Audience
This document is intended to assist those customers whose timecard preparers would
have manually overridden the earning policy on various time entries on the professional
timecard, but are not entering time directly into the professional timecards. Those
customers who wish to have their workers enter their time through the Self Service
timecard but require the flexibility of applying more than one earning policy to a single
timecard may benefit from this document.
1.3 Definitions
Explosion
Applying the policy rules such as overtime rules often results in the creation of additional
entries, so the user sees an exploded number of time entries.
OTL
Objects in the HXC schema, including preferences, alternate names, approval styles, time
categories, etc., and the time store
OTLR (Oracle Time & Labor Rules)
Objects in the HXT schema, including work schedules, rotation plans, earning groups,
earning policies, etc., as well as the professional timecard
Time Store
The HXC schema where time entries, created or modified through the Self Service
timecard, Line Manager Self Service, Authorized Delegate, and Timekeeper, are stored in
the database.

2. Overview of the Solution
Current OTLR functionality in the professional timecard enables the timecard preparer to
override the workers default earning policy for individual lines on the timecard.
Overrides of earning policies apply the rules from an alternate earning policy to the
specified line entries, rather than the rules in the workers default earning policy.
Current OTL functionality does not pass a value for an earning policy from the Self
Service timecard to the OTLR professional timecard. It is possible, though, to convert a
Self Service Hours entry into an earning policy entry, thereby executing an earning policy
other than the workers default policy on the entered values.
This customization to convert the Hours type to an earnings policy will:
Allow users to enter an Hours entry on their Self Service timecard
Store the Hours entry in the OTL time store
NOTE: The display of OTLR rules applied to users hour entries is not altered,
but we recommend that no OTLR information be displayed on the Self Service
Review page.
Convert the Hours entry to an earning policy entry, based on the association of the
Hours entry to an earnings policy.
NOTE: You may make this association through the logic you add to the Transfer
Time from OTL to BEE process, or you may wish to set up a user table with those
associations and retrieve the appropriate earning policy from there.
Display the earning policy entry on the OTLR professional timecard and apply the
earning policys rules to the line entry.
Considerations about this solution:
Modifying the Transfer Time from OTL to BEE process is strictly considered a
customization.
This modification of the Transfer Time from OTL to BEE is very straightforward
customization.
o If you experience any issues with your transfer process, Oracle Support
will only be able to assist you if the delivered process causes the same
issues. You must be able to run the unaltered version of the transfer
process that Oracle Development delivers, so you will be responsible for
keeping an unaltered version of the code delivered for your patching level.
o As with any customizations, you risk having your additions affected by
patch applications. Be sure that you can easily recreate your changes in
the version of the code that your patch delivers.



3. General Implementation Steps
1. Set the workers Self Service Preference to Allow Rules Evaluation to "Yes" so that your
timecards transfer to the professional timecard (the HXT schema).
NOTE: Because of this preferences value, normally your users would be able to see the
timecards explosion upon reviewing their Self Service timecards if you assign the review
layout with OTLR details to them. Because OTL cannot use the alternate earning policy
for the explosion in the Self Service timecards, the explosion they would see in Self
Service would be different than the explosion that your professional users would see in
the professional timecard. To minimize confusion, you may wish to show no explosion
to your Self Service users by assigning the review layout with no OTLR details to them.

To reduce confusion, no explosion is displayed to the user on the timecards review page.
2. Create the default earning policy (or policies) for your workers and assign it to them with
OTLRs Assignment Time Information records.
3. Create your alternate earning policy (or policies) with the element(s) you need for
applying the different rules to the selected Hours type.
NOTE: This earning policy will not be attached to your workers Assignment Time
Information records.
4. Create a user defined table where you can associate your Self Service Hours types to your
earning policies that should be sent to the OTLR professional timecard. If you do not
wish to set up a table, we recommend that you name your alternate earning policies with
the same names as the elements you assign to these earning policies.
5. Copy and save the Hxt_Otc_Retrieval_Interface.pkh & Hxt_Otc_Retrieval_Interface.pkb
with another name to create your custom version of the package. Save the original
version in a safe directory to recover if necessary.

6. Copy and save the Pay_Hr_Otc_Retrieval_Interface.pkh &
Pay_Hr_Otc_Retrieval_Interface.pkb package with another name to create your custom
version of the package. Save the original version in a safe directory to recover if
necessary.
7. Inside your custom version of the package created in Step 5 find the call to the
Hxt_Otc_Retrieval_Interface.transfer_to_otm procedure. Replace this call with a call
to the procedure in your renamed package from step 4.
8. Inside the transfer_to_otm procedure you will find another procedure called transfer to
BEE. Insert logic into that procedure to test if another earning policy should be used. If
so, find the different earnings policy and replace the default one from the additional
assignment information record for the rest of the processing.
If an element entered on the timecard is not in the workers default earning policy,
find the alternate policy that contains that element.
To find the appropriate earning policy, you will either look in the table with the
associations that you set up in Step 4, or look for an earning policy with the same
name as the element you need to apply.
9. Define your new transfer procedure in the Concurrent Manager so that it runs your
modified code.
10. Complete all other necessary setups for your workers to enter their time.
11. Create timecards for some workers and transfer them to the professional timecard to
carefully test your procedure. You will need to ensure that it transfers your time entries
successfully to the OTLR tables, and that the explosion in the professional timecard
correctly applies the overriding earning policy. Your professional timecards should look
something like the timecards in the illustrations below. Note the different earning
policies on the various days, and the different Hours types applied to the exploded hours
because of the different earning policies.


Mondays overtime policy explodes the 10 entered hours into 8 hours of regular and 2 hours of overtime.

The default Earning Policy on the workers Assignment Time Information record is applied to explode Mondays
entered time.


The policy applied to Saturdays hours explodes the 10 entered hours into 8 hours of regular and 2 hours of
double time.

The default Earning Policy on the workers Assignment Time Information record is overridden to explode
Saturdays entered time differently than Mondays was exploded.


The policy applied to Sundays hours explodes the 10 entered hours into 8 hours of regular and 2 hours of
double time.

The default Earning Policy on the workers Assignment Time Information record is overridden to explode Sundays
entered time differently than Mondays was exploded.

4. Appendix Document References & Further Reading
Configuring, Reporting and System Administration in Oracle HRMS (Metalink Note:
214791.1)
Oracle Applications Online Help, Setting Up User Tables, Columns and Rows &
Entering Table Values
Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.1)
Oracle Time & Labor Mini-Pack About Documents
HXT.G (Metalink Note: 258309.1)
HXT.H (Metalink Note: 282087.1)
HXT.I (Metalink Note: 303755.1)
HXT.J (Metalink Note: 344022.1)
NOTE: Always apply the most recent rollup patch or cumulative backports patch
appropriate to the patching level of your OTL system as soon as possible after the
backports patches are released, as these patches provide critical fixes for your OTL
system. Always also carefully read the documentation that is delivered with each patch;
in addition to important information about the patch, you can check if OTL Development
has delivered any modifications to the packages that you customized for this solution.

Оценить