<Insert Picture Here>

Shift Premium Rule as Timecard Attribute

Ashok Rajagopal
Oracle Time and Labor Development
2010 Oracle Corporation Proprietary and Confidential

Contents

Requirement and Business Justification

Solution Components
Configuration steps for Self Service use
Configuration steps for Timekeeper use
Steps for Timestore Deposit API

2010 Oracle Corporation Proprietary and Confidential

Requirement and Business Justification

Customer(s) have a requirement to attribute time worked in non
regular shifts to be attributed to the Stop time rather than Start
time.
The current architecture of OTL Time Store and Rules Engine
does not support time calculation based on Stop time.
As a work around, customer requests an option to select a
Shift/Shift rule along with Self Service/Timekeeper Time entry, so
the onus is on the Timecard creator to select the right shift and
right date to attribute the time to, with no start and stop times.

2010 Oracle Corporation Proprietary and Confidential

Solution Components
Patch 18631093 with the following components
New Mapping Component: SDR_NAME (short for Shift Differential
Rule Name; available to be configured on SS/TK/API created
Payroll timecards).
Modified OTL Deposit Process and BEE Retrieval Process
mappings to enable deposit and retrieval of the above component as
a Time Attribute.
New Profile option HXT: Display Override Shift Differential Premium
Rule to toggle display of the new field in Entry/Validation/Approval
screen for Administrators.
Associated code to support time entry, deposit, retrieval and Shift
Premium generation for time entries that also specify a shift
differential rule.

2010 Oracle Corporation Proprietary and Confidential

New Mapping Component: SDR_NAME

2010 Oracle Corporation Proprietary and Confidential

Modified Deposit Process Mapping

2010 Oracle Corporation Proprietary and Confidential

Modified BEE Retrieval Process Mapping

2010 Oracle Corporation Proprietary and Confidential

New Profile option HXT: Display Override

Shift Differential Premium Rule

Available at Site, Responsibility and User Levels.

Decides whether to show and allow override of Shift Premium rule in
Entry/Validation approval screen.

2010 Oracle Corporation Proprietary and Confidential

How to implement the solution for time entry?

Ensure OTLR setup including Shift Differential Policy is in place

for employee(s).
Create SS timecard layout with additional layout attribute to allow
display and selection of Shift Diff Premium rule for the employee.
Create Timekeeper layout attribute to allow display and selection
of Shift Diff Premium rule for Timekeeper.
Modify any existing Timestore deposit API wrappers to allow
creation of Shift Diff Rule attribute.

2010 Oracle Corporation Proprietary and Confidential

Configuration steps for SS use

Create/Alter required DB views

Create required AK attributes and add to HXC_CUI_TIMECARD
region.
Modify SS Time Entry, Review and Confirmation layouts to add
the new component.
Attach the new/modified layouts to the employees preferences.

2010 Oracle Corporation Proprietary and Confidential

Self Service Timecard Layout customization

The example below shows creation of a new layout with Shift
Differential Rule added as an additional attribute in seeded
Payroll layout. Result expected is as below.

2010 Oracle Corporation Proprietary and Confidential

Create/Alter DB View to be used

This example uses HXC_CUI_CUSTOM2_V and Custom2VO to
display the new component.
Modify the definition of HXC_CUI_CUSTOM2_V as below.
CREATE OR REPLACE FORCE VIEW HXC_CUI_CUSTOM2_V
AS
SELECT sdr.name value,
sdr.name display_value
FROM fnd_user fu,
per_all_assignments_f asg,
hxt_add_assign_info_f ati,
hxt_shift_diff_rules sdr
WHERE fu.user_id = FND_GLOBAL.user_id
AND fu.employee_id = asg.person_id
AND SYSDATE BETWEEN asg.effective_start_date
AND asg.effective_end_date
AND ati.assignment_id = asg.assignment_id
AND SYSDATE BETWEEN ati.effective_start_date
AND ati.effective_end_date
AND ati.shift_differential_policy = sdr.sdp_id
AND SYSDATE BETWEEN sdr.effective_start_date
AND sdr.effective_end_date

2010 Oracle Corporation Proprietary and Confidential

 The above query is meant to pick up the logged in user, and thru his
assignment, get the Shift Differential Policy assigned to him.
The example in this document uses HXC_CUI_CUSTOM2_V and
Custom2VO available for SS timecard customization. Any VO already
available ( of the name CustomXVO, where X is 1..10 may be used).
Customer is also welcome to use a completely new VO and View
structure they have in place.
For an authorized delegate based time entry, this definition might not
suffice, and there must be further configurations in terms of a bind
variable. Please refer Timecard Config UI WP.
If the layout created is assigned to an employee who has no OTLR
setup at all, or no shift differential policy attached, or no Premium
Eligibility Policy attached, the choicelist would be empty.
Any additional validation on the value to be chosen or values already
chosen etc can be configured with Time Entry rules and fast formulas,
seeded or custom.

2010 Oracle Corporation Proprietary and Confidential

Create AK label for the new component

2010 Oracle Corporation Proprietary and Confidential

Add to HXC_CUI_TIMECARD region to

enable use of this label in SS timecard

2010 Oracle Corporation Proprietary and Confidential

Modify LDT files to add the new component

BEGIN HXC_LAYOUT_COMPONENTS "Ash-EATON Timecard Layout - SDP Rule"
OWNER = "ORACLE12.1.0"
COMPONENT_VALUE = "SDPRULE"
REGION_CODE = "HXC_CUI_TIMECARD"
REGION_CODE_APP_SHORT_NAME = "HXC"
ATTRIBUTE_CODE = "HXC_CUI_SDP_RULE_LABEL"
ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
SEQUENCE = "210"
COMPONENT_DEFINITION = "CHOICE_LIST"
RENDER_TYPE = "WEB"
PARENT_COMPONENT =
"Ash-EATON Timecard Layout - Day Scope Building blocks for worker timecard matrix"
LAST_UPDATE_DATE = "2005/07/19
BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Ash-EATON Timecard Layout - SDP Rule"
OWNER = "ORACLE12.1.0"
QUALIFIER_ATTRIBUTE_CATEGORY = "CHOICE_LIST"
QUALIFIER_ATTRIBUTE1 = "Custom2VO"
QUALIFIER_ATTRIBUTE4 = "N"
QUALIFIER_ATTRIBUTE8 = "DisplayValue"
QUALIFIER_ATTRIBUTE9 = "Value#STRING"
QUALIFIER_ATTRIBUTE10 =
"oracle.apps.hxc.selfservice.timecard.us.server.Custom2VO"
QUALIFIER_ATTRIBUTE17 = "OraTableCellText"
QUALIFIER_ATTRIBUTE20 = "N"
QUALIFIER_ATTRIBUTE21 = "Y"
QUALIFIER_ATTRIBUTE22 = "L"
QUALIFIER_ATTRIBUTE25 = "FLEX"
QUALIFIER_ATTRIBUTE26 = "OTM"
QUALIFIER_ATTRIBUTE27 = "Attribute2"
LAST_UPDATE_DATE = "2005/07/19"
END HXC_LAYOUT_COMP_QUALIFIERS
END HXC_LAYOUT_COMPONENTS

2010 Oracle Corporation Proprietary and Confidential

Key Points to note

The new component needs to be added to Time Entry, Review

and Confirmation layouts at the minimum.
If the approval notification needs to display the new field,
Notification layout needs to be modified as well.
The following key qualifier attributes must be precisely set to the
right values

Qualifier_attribute2 VO used
Qualifier_attribute26 Attribute category, OTM
Qualifier_attribute27 Attribute column, Attribute2
Qualifier_attribute9 column to store and datatype Value#STRING

2010 Oracle Corporation Proprietary and Confidential

Assign to Employees preferences

2010 Oracle Corporation Proprietary and Confidential

Layout is ready to use for Time entry

Above screenshot shows the Review page showing Shift Premium Rule
and explosion according to the new functionality. Here, we see Shift
Premium paid to the employee even though time is entered in Hours and
not start and stop time.

2010 Oracle Corporation Proprietary and Confidential

Configuration steps for Timekeeper use

Create Value set of Table type to list premium rules for

employee.
Create Alternate name mapping for the created Value sets.
Create Alternate name definition based on the above mapping.
Attach the Alternate Name to TK Layout Attributes in Employees
preferences.

2010 Oracle Corporation Proprietary and Confidential

Create new Value set Table type to use for

TK Alternate Name

2010 Oracle Corporation Proprietary and Confidential

Value set - contd

2010 Oracle Corporation Proprietary and Confidential

Complete text for Value set creation

Table Name:
per_all_assignments_f asg,
hxt_add_assign_info_f ati,
hxt_shift_diff_rules sdr

Where/Order By:
WHERE asg.person_id = FND_PROFILE.VALUE('OTL_TK_RESOURCE_ID')
AND SYSDATE BETWEEN asg.effective_start_date AND asg.effective_end_date
AND ati.assignment_id = asg.assignment_id
AND SYSDATE BETWEEN ati.effective_start_date AND ati.effective_end_date
AND ati.shift_differential_policy = sdr.sdp_id
AND SYSDATE BETWEEN sdr.effective_start_date AND sdr.effective_end_date

Value:

sdr.name

ID:

sdr.name

2010 Oracle Corporation Proprietary and Confidential

 2010 Oracle Corporation Proprietary and Confidential

Create Alternate Name Mapping

2010 Oracle Corporation Proprietary and Confidential

Create Alternate Name Definition

2010 Oracle Corporation Proprietary and Confidential

Attach to Timekeeper Layout Attributes

2010 Oracle Corporation Proprietary and Confidential

Timekeeper timecard may now be entered

2010 Oracle Corporation Proprietary and Confidential

To enter Shift Premium Rules thru API

hxc_Timestore_Deposit.create_attribute
(
p_building_block_id => l_time_building_block_id,
p_attribute_name => SDR_NAME,
p_attribute_value => Night Shift Prem Rule,
p_app_attributes => x_app_attributes
);

In the Timestore Deposit API wrapper programs/scripts, an additional call

to create the Shift premium rule may be added.

2010 Oracle Corporation Proprietary and Confidential

After Xfer time from OTL to BEE, verify time

in Entry/Validation/Approval screen

2010 Oracle Corporation Proprietary and Confidential

Points to remember
Though the facility to key in Shift Premium Rule is provided in various Time entry screens,
any rules entered thus has a value only for time keyed in as Hours and not as Start and Stop
times.
In other words, the timecards may not error out as such if a premium rule is overridden on a
time entry with start and stop times, however overtime explosion should see no impact.
As mentioned previously in this document, the added shift premium rule has an impact only if
the employee has a valid Shift Differential Policy attached and the Premium expected to be
awarded is attached to the worked hours thru Premium Eligibility policy.
The new component available to be added to timecards, SDR_NAME is available to be used
in all timecard configurations (in LOVs, dependent LOVs, Hidden values etc. ) and all
standard OTL configurations like Time Categories.
Profile option HXT: Display Override Shift Premium Rule decides whether to display the SDP
rule in Entry/Validation/Approval screen. However, turning off this profile option keeps the
data in the backend table intact.
The Entry/Validation/Approval screen shows overridden SDP Rule in the Summary record.
However, amongst the exploded details, only the premium hours awarded shows SDP Rule.
A timecard that stores Shift Premium Rule in Self Service/TK stores Shift Premium rule in the
second attribute of HXC_TIME_ATTRIBUTES, in attribute_category OTM.
In the OTLR schema, the overridden Shift Premium Rule is visible in
HXT_SUM_HOURS_WORKED_F.sdp_rule and HXT_DET_HOURS_WORKED_F.sdp_rule.
The above data can be verified by running OTL Analyzer programs.

2010 Oracle Corporation Proprietary and Confidential