Otl Setups For Payroll PDF

http://oracleapps88.blogspot.
com/
OTL SETUPS FOR PAYROLL

1. CREATING CUSTOM RESPONSIBILITY
1.1 OAMC OTL Setup
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
Responsibility Name P OAMC OTL
Setup
Profile Option Name A Site Responsibility
E
OTL : Allow TK locking of Queried records Yes
L
OTL : Archive Restore Chunk Size 150
C
OTL : Max Warnings in Validate Data Set 500
A
OTL: Allow Change Group Timekeeper Yes
R
OTL: Allow Self Service Time Entry for Terminated Employees No
O
OTL: Code Level
OTL: Data Volume for Upgrade Program Worker
OTL: Days a TimeKeeper can access Contingent Worker's timecard beyond
termination
OTL: Debug Check Enabled No
http://oracleapps88.blogspot.com/
OTL: Default Approval Action for Mass Timecard Approver Approve

OTL: Defer approval process on timecard submission Yes
OTL: Enable Archive/Restore Detailed Logging
OTL: File Separators for the Import Export Functionality ,
OTL: Max Errors
OTL: Minimum Age of Data Set for Archiving 6 M
OTL: Number of past days for which retrieval considers changes (days) 365 O
.C
OTL: RDB - Default Application Payroll
T
OTL: RDB - Run Post Retrieval Snapshot Automatically
OTL: Transfer Batch Size 3000
O
Both OTLR and
OTL: Transfer to OTLR and / or BEE BEE
P
S HR with
G
HR:User Type Payroll User
OTL: Use Upgraded Retrieval Process
O
1.2 OAMC HRMS Self Service Time L
.B
8
8
S
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
Responsibilty Name
S
OAMC HRMS Self Service Time
Profile Option Name
PSite Responsibility
P
HXT: All / Selected Earning Categories Selected Earning Categories
HXT: Approver Required
A Y
HXT: Batch Size
E 25
L
HXT: Compare Special Rules Evaluation
C
HXT: Holiday Hours from Holiday Calendar Yes
A
HXT: Hours per Year 2050
R
HXT: Include Premium Hours to PA Y
HXT: Merge Batch Timecards
O Daily/Weekly/Special
Overtime only and Holiday
HXT: Overtime Functionality on Holidays Rule
HXT: Rollup Batch Hours No
OTL : Allow TK locking of Queried records Yes

OTL : Archive Restore Chunk Size 150
OTL : Max Warnings in Validate Data Set 500
OTL: Allow Change Group Timekeeper No
OTL: Allow Self Service Time Entry for
Terminated Employees No
M
OTL: Code Level
O
.C
OTL: Data Volume for Upgrade Program Worker
OTL: Days a TimeKeeper can access Contingent
Worker's timecard beyond termination
T
OTL: Debug Check Enabled No
O
OTL: Default Approval Action for Mass Timecard
P
S
Approver Approve
OTL: Defer approval process on timecard
submission Yes G
OTL: Enable Archive/Restore Detailed Logging
O
OTL: File Separators for the Import Export
L
.B
Functionality ,
OTL: Max Errors
OTL: Minimum Age of Data Set for Archiving 6 8
OTL: Number of past days for which retrieval 8
considers changes (days)
S 365
OTL: RDB - Default Application
P Payroll
OTL: RDB - Run Post Retrieval Snapshot
P
Automatically
A
E
OTL: Transfer Batch Size 3000
L
OTL: Transfer to OTLR and / or BEE Both OTLR and BEE
C
HR with
HR:User Type Payroll User
A
OTL: Use Upgraded Retrieval Process
R
O
1.3 Create employee and attach that to the user, which in turn is used for doing all the setups.
1.4 Alternate Names

Before creating alternate names, all the elements and its links have to be created and linked to respective payrolls.
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
Alternate names not visible issue
L
Once all the element are created and linked to payrolls, please check the payrolls are attached to all employees, If this is not
C
done then alternate names will not be visible on the self service timecard.
A
After elements are linked create element sets for all the OTL elements and run navigate to OTL Application developer
R
responsibility and run the concurrent program name called Generate Flexfield mapping and mention the Element set name
O
in the parameter. Note: It is very important to keep the datetrack to the same date i.e. 01-jan-1951 while doing all the setups
1.5 Time Categories

There are so many requirements for Time categories, For summary Total to be displayed on the timecard for Regular Hours
or any kind of hours type then OTL has Provided Total1.Total10 attributes .
As shown below Total1 and Total2 are used for displaying the Hours Totals.
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
1.6 Time Entry Rules
OTime entry rules are used for controlling the entire time entry on the TC.
M
O
.C
T
O
P
S
G
O
L
Let us take an example that user should not enter Regular Hours more than 40 hours a week then the following has to
.B
designed in the rule
Name: - OAMC Rule -4

8
8
Description: - Regular hours cannot be more than 40 (Description is mandatory because on the TC description will be shown
S
as message) if this left blank then a seeded message will be displayed.
Usage: - Submission / Resubmission (This will decide when the validation will come into effect i.e. when submitting or
Resubmitting. P
P
Formula: - Seeded formula for Period Maximum
A
The inputs are as follows
E
L
C
A
R
O
Lets take another example that overtime should not be more than 10hours per week.
Name: - OAMC Rule -3

Description: - Overtime hours cannot be more than 10 hours per week (Description is mandatory because on the TC
description will be shown as message) if this left blank then a seeded message will be displayed.
Usage: - Submission / Resubmission (This will decide when the validation will come into effect i.e. when submitting or
Resubmitting.
Formula: - Period Hours vs Time Category ( Seeded formula )
The inputs are as follows M
O
.C
T
O
P
S
G
O
1.7 Time Entry Rule Group L
.B
This is a combination of rules which is created in sec 1.6 we can select specific rule or all rules and mention each Outcome can
8
be 1. Error 2. Warning 3. Business Message 4.Reason as shown in the below screen shot
8
Note: - Time Entry Rule group is applied to preferences.
S
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
1.8 Recurring Periods E
L
Recurring period is the given set of days or months which is displayed in the TC.
C
Usually Recurring period will have start date which will determine the TC period, this date can be start of the year or start date
A
of the payroll run and this is a business decision.
R
O
M
O
.C
In the above screen shot I have created OAMC Recurring Period which has start date as 01-jan-2012
T
O
1.9 Approval Style
This is the method in which a TC will be approved.
This has two sections 1. Approval Rules 2. Approval Style Components P
S
In 1.Approval Rules Section we can mention which time entry rule comes under which application
G
In 2. Approval Style Components we can attach the application to the specific approval type as shown in the screen shot
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
There are different types of approval mechanism as listed below
R
O
M
O
.C
T
O
P
S
G
O
L
.B
Splitting the time card on the basis of approval
8
8
There is business mechanism in which the Regular Hours or Any kind of Hours type has to be Auto approved and the
S
remaining hours has to go for approval process. In this case the following steps have to be done.
In 2. Approval Style Components choose the application and then select Entry Level Approval as the type. We can observe
P
P
A
that the button will be enabled and then click on the button and provide the
E
details as shown in the screenshot.
L
C
A
R
O
M
O
.C
T
O
P
S
G
Let the Default Entry level Approval Style be as HR Supervisor, if you choose anything else then the whole time card will be
approved differently. O
L
Create a time category for the specific Hours Type and then select the type as Auto Approve, By doing this only the
.B
particular hours type will be auto approved and the rest of the components will go for approval cycle. If there are more than
one component then create separate time category for the same.
8
2.0 Approval Periods
8
S
Approval periods will allow the approver to approve specific days of the TC only like Weekly or monthly.
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
2.1 Recurring Period
Recurring Period are the range of the dates i.e. the time card is dependent on.
8
8
S
P
P
A
E
L
C
A
R
2.2 Preferences
O
This is the setting which will determine how a timecard will look like what will be the rules and validations and where all the
Preferences will be used.
The following preferences have to be applied on the timecard for Payroll integration.
2.2.1
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.2
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
2.2.3
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
2.2.4
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.5 A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.6 A
R
Before integrating absence with OTL check the profile option HR: Absences Integration with OTL and set it to Yes at Site level
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8 or not in US OTL Application Developer responsibility.
Check if the menu called Absence integration Setup is visible
S
P
P
A
E
L
C
A
Relement set and run the Generate flex field and Mapping Information with parameters as shown below.
Create absence
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Navigate to Absence Integration Setup and provide the Element Set name as shown in the below screen shot
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
Select on all the absences and save and then click on Go
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
Click on Generate Time Category
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
Apply the preferences for the absences.
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
2.2.7
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
2.2.8
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.9
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.10 A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
2.2.11 R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.2.12 A
R
Create the Time Category and use the same
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
2.2.13 How to apply Preferences
R
O
Once all the preferences are completed then the preferences have to be applied to the group or organization or it can be applied
to individual person. As shown in the below screen shot the preferences OMAC Preferences has been applied to all the people.
Note: - The precedence should be a unique number which will decide the order of application of preferences.
M
O
.C
T
O
P
The Link by in the lov as shown in the below screenshot where one can choose where all the preferences can be applied
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
2.3 How to create Timekeeper

Navigate to OTL Super Timekeeper Timekeeper Group
Provide the Name and select the timekeeper. In the person section, choose the persons i.e. who all comes under respective TK, as
shown in the screenshot.
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
Set the profile option, HR:User Type, to be update able at the site, application, responsibility or user level so that a value can be
P
entered.
A
OTL: Allow Change Group Timekeeper resp_level =Yes for the profile option HR:User Type
E
2.4 Time Keeper Preferences
L
C
A
R
O
2.4.1
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
2.4.2
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
2.4.3 A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
2.2.4
After time card preferences are done then the same has to be applied to individual timekeepers i.e.
Employees as shown in the screen shot or TK can be any named person in the organization.
M
O
.C
T
O
P
S
G
O
L
.B
8
8
Preferences Details
S
Preference Name in P Value in Default Default Value for
Tree (Preference Name) Description
Append Templates on Y/N. If setA
P
to Yes, the worker can select more than one
Preferences Hierarchy Projects
No Yes
Timecard (Self Service
Eon the timecard.
template and the data from all the selected templates
L
Functionality to Append appears
C
Templates on the
Timecard)
Business MessagesA
Rto Show a validation are displayed to the worker on the timecard.
(Self Y/N. If set to Yes, business messages from time entry rule Yes Yes
Service Ability
O
Business Message)
Create Personal Y/N. If set to Yes, workers can create their own personal No Yes
Templates (Self Service timecard templates. A Create Template button is displayed
Create Template on the Templates page.
Functionality)
Date Formats (Self Determines the display of date formats for the timecard. December 31, 2002. [None]
Service Date Format You can choose the date format for the Period List, Tue, Dec 31.Tuesday,
Functionality) Timecard Table Day Header, and Timecard Details Page December 31, 2002
M
Day Header.
O
Default Approver If the Enter Override Approver preference is set to Yes, [None] [None]
(Worker Default then you can select any supervisor in the business group to
Approver) be the default value in the Override Approver field.
.C
Disconnected Entry (Self Upload/Download, or None. None
T Upload/Download
Service Disconnected Determines whether workers can enter time and labor data
O
P
Entry Option for Worker) using a spreadsheet (import) and whether they can
download data to the spreadsheet (export).
S
G
Timecard Allows Display Reduce potential validation errors by displaying the accrual
of Accrual Balances balances on the timecard. Self-service users can view the
O
accrual balance before submitting their absences. Select yes
L
in the Display Balance segment to display the balance
.B
component on the timecard. The application uses the HR:
Accrual Plan Element Set profile option if you leave the
8
Element Set as Null. Select an evaluation date for the
8
accrual balances to display. The application uses the
S
Accrual Evaluation Date you select to display the accrual
Pworkers can enter negative hours on

balances.
their timecard. P
Enter Negative Hours Y/N. If set to Yes, then No Yes
A
(Self Service Ability to
Enter Negative Hours)
Eset to Yes, then workers can enter an override
L on the timecard. You must also set the Override
Enter Override Approver Y/N. If No Yes
Enter an Overriding CApproval Style segment of the Approval Style preference to

(Worker Preference to approver
Approver)
A Projects Override Approver.
R Rows The
Number of Empty number of empty rows to display on the worker's 1 1
ServiceO
on the Timecard (Self default timecard.
Number of Empty
Rows on the Timecard)
Number of Recent The number of previously entered timecards to display. 5 5
Timecards Displayed
(Self Service Number of
Recent Timecards on
Time Entry Screen)
M
OTL Rules Evaluation Y/N. Set the Evaluate OTL Rules segment to Yes for No No
(Self Service Preference workers whose time is subject to OTL rules based on a
to Allow Rules rotation plan and earnings policy. If set to Yes, use the
O
.C
Evaluation) Approval Rules for Rules Evaluation segment to select the
applications that approve the data before you can run the
Transfer to BEE process. You may also select an Overtime
T
O
Recurring Period to calculate overtime for non-weekly
P
payrolls.
Public Template Groups Determines the Self Service Timecard Template Group
S
Dynamic Templates
Group
GNo
O
Save as Templates on Y/N. If set to Yes, then the Save As A Template button Yes
L
Timecard (Self Service displays on the worker's timecard.
Save as Template
.B
Functionality on
8you use the Change

Timecard)
Self Service Flow
8If set to Standard, then you
Audit or Standard. If set to Audit, then [None] [None]
choose not to use Change S

and Late Audit Preference node.
P by the system administrator.

and Late Audit.
P
Template Assigned Value Default template assigned [None] [None]
A
- Administrator (Self
Service Default Template
Assigned by Sys Admin) E
L template selected by worker. Check the Editable by
- End User (Self ServiceCUser check box if you want workers to be able to select
Template Assigned Value Default [None] [None]
Default Template
A their own default template.
R
Selected by User)
O Template Y/N.
Template Functionality
(Self Service
Select Yes in the Template Functionality for a Worker
segment to enable workers to use templates.
No Yes
Functionality for a Y/N. Select Yes in the Create Zero Hours Last Timecard
Worker) segment to enable users to create timecards using the last
timecard template. The default is set to No.
If you set this segment to Yes, and the worker creates a

timecard based on the last timecard template, then the
application applies the template to the timecard with zero
hours for the first day and blank hours for the other days.
M
Timecard Alternate Determines the set of alternate names used to configure lists [None] [None]
Names (Self Service of values on workers' timecards. You must define Timecard
Timecard Alternate Name Alternate Names.
O
.C
Set Defined for a User)
T
Timecard Delete Allowed Yes/No. If set to Yes, then you provide workers the ability [None] [None]
to delete a timecard. If you select No, then you disable the
delete timecard feature.
O
Timecard Layout (Self- Determines which timecard layouts workers use for data P
Exception Layout - Projects Timecard
Service Timecard entry, review, confirmation, detail page, and for export. S
Time card Entry Page Layout
Review, and If you leave the Export segment blank, then the Timecard
G
O
Confirmation Layout entry layout is used for export.
L
Pages) If you use Entry Level Approvals, then select the Approval
Fragment Layout to route all approver comments to the
.B
worker.
8
If you use Inline Notifications, then select the appropriate
notification layout.
8
Displays a concatenated entry of Project Number and Task
Details.
S
Timecard Period (Self
Service Timecard Period timecard entry. P
P time period workers use for
Determines which recurring Weekly - Starts Sunday Weekly - Starts
Sunday
for Worker)
A
Timecard Unit of Easthedays,unitshours,
Determines in which workers enter time and labor Hours HH:mm Hours HH:mm
Measure (Self Service L
data, such pieces, and time units as well as
Used on a Timecard C
Unit of Measure to be the format for entering time.
A
R
Timecard Status Allowing Determines the timecards you can edit, according to their New, Working, rejected Retro
O
Edits (Self Service status and data. Select a status in the Status Allowing Edits Day fields are blank, Day fields are
Timecard Status that field: meaning there is no time blank, meaning
Allows User Edits) Submitted - Workers can edit submitted, new, working, and limits on entering and there is no time
rejected timecards. editing timecards. limits on entering
Approvals Initiated - Workers can edit, delete, and resubmit New_Working_Rejected and editing
new, working, rejected, and submitted timecards, plus those - Workers can only edit timecards.
for which an approval process has been initiated. unsubmitted timecards,
Note: Workers can edit timecards in this status only if the or timecards in a
recipient application has not retrieved them. working or rejected
status.
Retro - Workers can edit all timecards, including submitted,
M
O
approved and processed timecards. Adjustments made at
this point would create a Retro Time Adjustment.
.C
In the Past Number of Days field, enter the age of the oldest
T
timecard a worker can edit. Timecards for the period in
which this day falls will be editable.
In the Future Number of Days field, enter how many days
O
in advance a worker can enter a timecard. For example, if
P
S
you enter 28, a worker can enter timecards for all periods
up to and including the period that includes the 28th day.
Note: A timecard is editable only if it has a status that G
O
allows edits and if the timecard period falls within the date
limits set by this preference.
L
.B
In the Future Time Period Limit field, choose the time
8
period as Active Assignment to generate timecard periods
8
up to the actual termination date, otherwise, choose
S
Assignment up to Final Termination to generate timecard
periods up to the final termination date.
P
Note: Although all time periods are available on a
P
terminated employee's timecard, they cannot submit a
A
timecard after the actual termination date.
Time Store
E
L
The time store hierarchy contains the preferences that relate to the functionality of the time store and applications.
C Description Default Value
A
Preference Default Value for Projects
R
Absences Functionality Enable Integration with Absences - determines if time store No
O
absence integration is set up for worker No
Allow Edit on Imported Absence Entries - determines if workers Error
can edit absence entries.
Action for Absences Pending Approval - determines if the
worker views an error or a warning.
Retrieval Rule for Absences - determines the method to use for

online retrieval. You can choose from Use Retrieval Rule Group
Preference, Working, Submitted, Approved.
Display Absence Status Region on Timecard - determines if the
absence status region displays on workers' timecards.
Note: The settings you choose here determine if the Show
M
O
Absences Screen Option in Timekeeper displays as
shown/hidden.
.C
T
Action for Overlap and PTO Validations - determines if the
application displays an error, warning or ignores overlaps and
validation inconsistencies.
O
Action for Absences Pending Confirmation - determines if the
P
S
application displays and error or a warning to workers.
Exclude Absences from Timecard Totals determines if the
G
timecard total in the time entry, review, confirmation and
O
notification pages displays totals for both hour and day based
absences.
L
.B
Application Set (Time Determines which applications retrieve workers' timecard - you Human Resources Projects
Store Application Set) must define at least one application set: Human Resources -
Note: To ensure proper set 8
Oracle Human Resources; Payroll - Oracle Payroll; Projects -
up, your application set 8
Oracle Projects; HR/Projects - Human Resources and Projects;
values must match those
S
HR/Payroll - Projects and Payroll; HR/Payroll/Projects - Human
defined for your retrieval
P
Resources, Payroll and Projects.
P
rules.
Approval Periods (Time
A
Determines the approval time periods for each application. Weekly Periods - Weekly Periods
Store Approval Periods)
E Starts Sunday - Starts Sunday
L
Approval Style (Time Store Determines the approval rules and method for each application. Auto Approve (no Auto Approve
Approval Style)
C To enable override approver functionality, you must ensure that value for Override Project Override
A
the Enter Override Approver preference is set to Yes. This can Approval Style Approver (for
display the Override Approver field on the projects, payroll, segment) Override
R exception, and combination layouts, where a worker can select Approval Style
O
Auditing Requirements
anyone in the business group.
Determines whether entries will be audited using Change and [None]
segment)
[None]
(Time Store Audit Late Audit. If Change and Late Audit is selected, then you must
Requirements) enter your Change and Late Audit rules.
Entry Level Processing Defined the entry level processing time entry rules used to [None] [None]
Rule Groups validate the workers timecards.
Note: To ensure proper set
up, your entry level
processing rule groups
should be defined to
M
O
include the values defined
in your application set, and
.C
your retrieval rules.
Retrieval Dashboard Time Store Retrieval Dashboard Setup for Worker - determines
T
O
Functionality if the application selects the snapshot during timecard
P
submission process or at a later stage.
Retrieval Rule Groups
(Time Store Retrieval Rule S
Determines the retrieval rules for each recipient application's
retrieval process. The retrieval rules define the approval status
Human Resources
Retrieval Rule
HR, Payroll and
Projects
Groups) G
data must achieve before it can be retrieved. You must define a Group Retrieval Rule
Note: To ensure proper set Retrieval Rule Group.
O Group
up, you retrieval rules must Projects Retrieval Rule Group
L
.B
match those defined for Payroll Retrieval Rule Group
your application set. Human Resources Retrieval Rule Group
8
Projects and Payroll Retrieval Rule Group
8
Human Resources and Projects Retrieval Rule Group
S
Human Resources and Payroll Retrieval Rule Group
HR, Payroll, and Projects Retrieval Rule Group
P
Note: Ensure that a worker's retrieval rule group does not contain
P
rules for applications that are no in the application set.
Timecard Required (Time Lists anyA
applications that do not require a timecard. [No applications] [No
Store Time Required for E applications]
Worker)
L
Time Entry Rule Groups C Defines the time entry rules to be used to validate the worker's [None] [None]
A
(Time Store Time Entry timecards.
Rules)
R
O
Time Store Days to Hours
Conversion
Converts day timecard entries to hours for Projects Applications. [None] [No
applications]
Validate on Save (Time Determines whether the OTL application runs the Recipient
Store Validate on Save) Update and Recipient Validate Processes when the user chooses
the Save for Later option.

If you set this preference to Yes, then the OTL application runs
the Recipient Update and Recipient Validate Processes. If you
set this preference to No, then the OTL application does not run
the Recipient Update and Recipient Validate Processes.
For Oracle Projects, however, the application runs the Recipient
M
O
Update and Recipient Validate Processes irrespective of this
preference.
.C
You can retain the rows with blank hours in a timecard after
T
saving the timecard, by setting the segment Restrict timecard
row(s) without any hours to No on the timecard.
Timekeeper O
The Timekeeper node contains the predefined preferences for the Timekeeper feature.
P
S Value in Default
Preference Name in
G Preferences Default Value for
O
Tree (Preference Name) Description Hierarchy Projects
Timekeeper Entry -
L
Determines the items to display on the timekeeper page. You No, Yes, No, No, Yes, No,
.B
Display Options can choose to display, In/Out time entries, Person Name, [none], and [none], [none], and [none]
(Timekeeper Misc Setup Person Number, Attribute Item Name for detail Information, respectively respectively
Items)
Timekeeper Timecard
8
and Descriptive Flexfields to display.
Determines which columns to 8 display on the Timekeeper [None] [None]
Layout (Timekeeper Timecard Layout. S
Layout Attributes)
P
Additional Features with Preferences
P
A
The following features have preferences. You cannot change or delete these values, however, you can create new preference values for
these features.
E
L
Change and Late Audit
The Change and Late Audit node contains the predefined preferences for Change and Late Audit functionality. You cannot change or
C can create new preference values.
delete these values, however, you
Preference NameA in Tree Value in Default Default Value for
R
(Preference Name) Description Preferences Hierarchy Projects
O
CLA - Delete Timecards Determines whether workers can delete their
(Timecard Delete Allowed) timecards. This value must be set at No when using
No No
change and late audit feature.

Timekeepers can delete timecards irrespective of this
preference.
CLA - Layout Determines which timecard layouts workers use for Projects layout is Projects layout is
(Self-Service Timecard, data entry, review, confirmation, detail page, export defaulted for all values defaulted for all values
Review and Confirmation and audit. If you leave the export segment blank, the except Export. Export is except Export. Export
Layout Pages for a Worker) Timecard entry layout is used for export. [None] is [None]
M
CLA - Process Flow Determines which process flow is to be used during Audit Audit
(Self Service Flow) time entry
CLA - Rule Group Defines the time entry rules to be used to validate [None] [None] O
(Time Store Audit workers timecards
.C
T
Requirements)
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O

Otl Setups For Payroll PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Otl Setups For Payroll PDF

Uploaded by

Copyright:

Available Formats

http://oracleapps88.blogspot.

OTL SETUPS FOR PAYROLL

OTL: Default Approval Action for Mass Timecard Approver Approve

OTL : Allow TK locking of Queried records Yes

1.4 Alternate Names

1.5 Time Categories

Name: - OAMC Rule -4

Name: - OAMC Rule -3

2.3 How to create Timekeeper

Pworkers can enter negative hours on

Enter an Overriding CApproval Style segment of the Approval Style preference to

8you use the Change

choose not to use Change S

P by the system administrator.

If you set this segment to Yes, and the worker creates a

C Description Default Value

Retrieval Rule for Absences - determines the method to use for

the Save for Later option.

change and late audit feature.

You might also like