Title and Copyright Information
This section gives you the basic implementation steps required to quickly enable you to set up Oracle Time & Labor in a test environment. For information on running Oracle Time & Labor in a production environment, please see the detailed chapters in this implementation guide.
The following steps depict the minimum items that must be present, either using existing defaults, or configuring and using new objects. Completing this quick setup will allow you to have a timecard that you can enter and submit on the test system you have defined. After you complete this quick setup, you can test that the application is installed and working properly, and you can see where you want to make configuration changes to meet your specific needs.
This quick setup assumes that you are using the delivered Oracle Time & Labor menus, responsibilities, and security, and that you have these items in place. If you have Oracle HRMS already installed, many of these items already exist. The minimum items that need to exist prior to installing Oracle Time & Labor are:
You must have also:
Installed Oracle Human Resources Release 12 with the most up-to-date patch according to the ReadMe file at the time of installation.
If you are using Oracle Projects, installed Oracle Projects Release 12 with the most up-to-date patch according to the ReadMe file at the time of installation.
Installed the latest version of the Oracle Application Framework according to the ReadMe file at the time of installation.
Optionally, consulted two documents on MetaLink that give instructions and other useful information on setting up your environment:
Configuring and Troubleshooting Oracle HTTP Server with Oracle Applications, note 139863.1
How to Implement Load Balancing Through Multiple Apache JServ Engines, note 165700.1
The Quick Setup Matrix is divided into several parts:
Step
Each step mentioned in this matrix refers to the corresponding step in chapter 2, Implementation, in this guide. Please read this chapter before beginning the quick setup.
Product Combination
The product combinations indicate the configuration of your installed Oracle products that you will use with Oracle Time & Labor.
Tips
Pertinent information about the step appears here. If the system has a default in place, it is indicated.
Choose the product combination that matches your configuration, and perform the required steps for that product combination.
Oracle Applications Flexfields Guide
Quick Setup Matrix
| Step | Product Combination | Tips |
|---|---|---|
| Create Users | Payroll HR Projects |
You should define every user of the system with a unique user name and password. You can give the same responsibility to many different users, but any data changes will be identified by Application Username. See: Users Window, Oracle Application System Administrator's Guide |
| Set User Profile Options | Payroll HR Projects |
You must define the HR:Business Group profile option for every new responsibility. By default this option is set to the setup business group. If you wish to run the Approval Process in the foreground opposed to submitting the Background Workflow Process, set the OTL:Defer Approval Process on Timecard Submission to NO. You must also set the HR:Date-Track Enabled profile option to Yes at the application level. Set the HR:User Type profile option to HR with Payroll user for OTL responsibilities. See: User Profiles, Oracle HRMS Configuring, Reporting, and System Administration Guide If you use Oracle Projects, refer to the appendix Profile Options in Oracle Projects in the Oracle Projects User Guide. |
| Set up Elements for Time and Labor Data Entry | Payroll HR |
These elements must be nonrecurring, allowing multiple entries, and have one input value called Hours. |
| Link Time Related Elements | Payroll HR |
If you are going to create eligibility rules using Premium Eligibility and Earning Policies, make sure you element link rules do not conflict with your policy rules. See: Defining Elements Links, Oracle HRMS Compensation and Benefits Management Guide |
| Define Element Sets | Payroll HR |
If you have Oracle HR or Payroll and use the Payroll retrieval rules, you define element sets to specify the elements to be fed by Oracle Time & Labor. Select the type "Run" when you define the element set. See: Defining an Element or Distribution Set, Oracle HRMS Compensation and Benefits Management Guide |
| Run Generate Flexfield and Mapping Information Process | Payroll HR Projects |
You must run this process on initial set up, and run this process later if you change the HR key flexfields, the Projects Expenditure Items flexfield, the set of elements for which you are holding information in the time store, or the input values of these elements. |
| Review OTL Information Types Descriptive Flexfield | Payroll HR Projects |
You must review the OTL Information Types flexfield to ensure your flexfields and all elements created in the element sets are enabled and visible, and the element input values are displayed correctly. Ensure that there is at least one enabled segment for each context. Check that segments are correctly marked as required or optional. |
| Define Alternate Names | Payroll HR |
You do not define any alternate names for a field's list of values, the full list of elements from the element set used in the Generate Flexfield Mapping process displays by default. The Alternate Name set created is name {Element Set Name} - Enabled. See: Defining Alternate Names |
| Define Preferences | Payroll HR Projects |
Default values exist. If you use Oracle Projects, you must use the Projects Default Preferences. Create an eligibility rule for this branch. See:Default Preferences |
This section provides a summary of what you can set up in each functional area in the sequence that you should follow. Every step gives you the names of any forms or processes that you should use for that step.
You can review the detailed task information for each step by following the page cross-references.
Setup steps are usually completed by a System Administrator after the successful installation and setup of Oracle Human Resources and Oracle Workflow.
Oracle Time & Labor supplies predefined data and functionality. You must configure this predefined data and functionality for your own implementation.
We recommend you install the Internet Explorer version 5.5. However, you can also use Microsoft Internet Explorer version 4 or 5, or Netscape Navigator version 4.08.
You must ensure your browsers do not cache web pages and keep the cache size as small as possible.
Your browser must reload web pages on each access. To do this in Internet Explorer, set he cache to clear "Ever visit to the page" and the Amount of disk space to use, to 1MB. To do this in Netscape Navigator, set the cache to clear "Every Time" and the cache to zero.
You must use a set of tools to configure Oracle Time & Labor. The tools you need are:
Oracle Applications, which you use to set up functions, menus, responsibilities, users, flexfields, time periods, element sets, web page instructions, and all the rules for time management, entry and approval.
Oracle Workflow, which you use to configure workflow approvals, and enterprise email addresses.
PL/SQL, which you can use, if necessary, to configure approval packages, retrieval packages, and create user accounts in a batch.
Text Editor, which you can use to edit loader files to configure timecard layouts.
The implementation steps are divided into three sections:
Basic Setup, which covers workflow and security setup, including defining menus and responsibilities.
Time & Labor Rules and Preferences, which includes setting up descriptive flexfields; defining time entry, approval, and retrieval rules; creating elements and mappings; customization deposit and retrieval processes, and configuring the timecards.
Time Management Structures and Policies, which covers defining rotation plans, earning policies, and other time and labor rules for calculating pay.
If you use OTL with other applications, then you must follow steps 2, 3, 4, 5, 6, 7, 8, and 10. OTL does not include defaults for steps 7, 8, and 10, and you can optionally follow steps 1 and 9.
Replace the Default Oracle Logo
Oracle Time & Labor delivers a default Oracle Logo in the upper left hand corner of the application. You can insert your own logo by replacing the file OTLBRAND.GIF with your own. You should rename your file to OTLBRAND.GIF in the /apps/media directory.
You may already have completed this step when implementing Self Service HRMS or another self service application.
See: Replacing the Personalizing Screen Images, Oracle HRMS Deploy Self-Service Capability Guide
Set Up Sysadmin ID
The Approvals process in OTL uses the default workflow error process to handle any errors in the processing. This error process sends a notification and description of the error to the Sysadmin ID.
Refer to the Oracle Workflow Guide for information on how to assign system administrator privileges to any user and how to set up email addresses in workflow.
Set up this process to take submitted timecards into the approval process.
Use the Submit Request window and a System Administrator responsibility.
Select the item type OTL Workflows for Employees, leave the threshold parameters blank, and select Yes in the Process Deferred, Process Timeout, and Process Stuck fields.
Run this process frequently during testing. In a production environment, you would normally run this process several times per day, but the frequency is dependent on other processes, the number of timecards that start the workflow process, when the approvals are acted on, and when retrievals take place.
A menu groups together a number of functions. Users' access to a menu depends on the responsibility you assign to them.
The predefined Self Service menus are:
Time and Expense Self Service menu
OTL Self Service Approval Menu
OTL Worklist Timecard Approval
OTL Authorized Delegate Timecard Entry
If you want to create your own self service menu, you must include the predefined submenu Self Service Time and Expense Application Menu, with no prompt. (The self service AK regions reference this menu.)
The Predefined professional forms menus are:
Global OTL Administrator
US OTL Administrator
Global OTL Application Developer
US OTL Application Developer
The Application Developer menus give access to all functions of the Administrator menus, plus the Deposit/Retrieval Processes (which includes retrieval rules and mappings).
If you want to rearrange these professional forms menus and add submenus for any new functions you define, then you can use the Menu window to create your own menus.
Caution: Do not modify the default functions and menus supplied with the system. On upgrade these will be overwritten.
See: Defining Menus, Oracle HRMS Configuring, Reporting, and System Administration Guide
In most Oracle Applications, you can open multiple windows from the Navigator window without closing the window you already have open. HRMS, however, does not support multiform functionality.
You must disable this feature on menus that access Oracle Time & Labor windows. You do this by adding the function Navigator: Disable Multiform (FND_FNDSCSGN_DISABLE_MULTIFORM) to a function type menu entry on the top-level menu.
You can define the groups of standard reports and processes that a user can run from the Submit Request window. Every responsibility can have access to one report group.
Use the Request Groups window.
Create your responsibilities and assign a menu and report security group to them. If you use more than one business group you must set up separate responsibilities for each group.
You can exclude particular submenus or functions of the main menu to hide them from users of this responsibility.
The predefined responsibilities for professional forms are:
Global OTL Administrator
US OTL Administrator
Global OTL Application Developer
US OTL Application Developer
The predefined responsibilities for self service are:
Self Service Time and Expenses (using the Time and Expense Self Service menu)
Self Service Time (using the Time and Expense Self Service menu with menu exclusions)
Self Service Expenses (using the Time and Expense Self Service menu with menu exclusion)
Mass Timecard Approval (using the OTL Self Service Approval Menu)
Worklist Timecard Approval (using the OTL Worklist Timecard Approval menu)
If you create your own self service responsibilities, then you do not use Oracle Internet Expenses, your responsibilities must include some menu exclusions. If you use the predefined menu (Time and Expense Self Service menu), then create three menu exclusions:
Expenses Tab Bar
Expenses Main Menu
Expenses Global Menu
If you create your own self service menu, including the predefined submenu Self Service Time and Expense Application Menu, then create one menu exclusion:
Expense Tab Bar
To create responsibilities for Self Service, select the Oracle Web Applications radio button in the Available From region in the Responsibilities window.
See: Responsibilities Window , Oracle Application System Administrator Guide
You should define every user of the system with a unique user name and password. You can give the same responsibility to many different users, but any data changes will be identified by the Application Username.
Use the User Window, or proceed to the next step to create a batch of user accounts. You must associate a person with each user that needs to be able to use the self service timecard.
See: User Window, Oracle Application System Administrator Guide
There are a set of concurrent programs to automate the creation and management of large groups of user accounts. Before you can use the concurrent programs, however, you must write custom logic to set up your customary user name and password format, responsibilities and profile options you want to associate with a user. A user hook in the hr_user_acct_api is provided for you to do this.
See: Batch Creation of User Accounts, Oracle HRMS Deploy Self-Service Capability Guide
You must define the HR:Business Group profile option for every new responsibility. By default this option is set to the setup business group.
You must also set the HR: DateTrack Enabled profile option to Yes at the application level. Set the HR:User Type profile option to HR with Payroll user for OTL responsibilities.
In addition, you may want to set other profile options for responsibilities or even for an individual user. The HXT_BATCH_SIZE profile option (which determines the number of timecard transferred to Batch Element Entries in a single batch) is set to 25 at site level by default.
To run the Defer Approval Process, set the OTL:Defer Approval Process on Timecard Submission profile option. OTL currently delivers this option with the value equal to YES. By changing the value of the profile option to NO, you will no longer need to submit the current process "Workflow Background Process".
Caution: Please note, this is a benefit to enterprises with a limited amount of data.
Use the System Profile Values window.
See: User Profiles
If you use Oracle Projects, then refer to the appendix Profile Options in Oracle Projects in the Oracle Projects User Guide.
| If you use... | Required Steps (no defaults) | Required Steps (with defaults) | Optional Steps |
| OTL with Oracle HR and Payroll | Step 26, Step 27, Step 28, Step 29, Step 30, Step 35, Step 37* | Step 11, Step 12, Step 13, Step 14, Step 15, Step 17, Step 18, Step 19, Step 20, Step 25 | Step 16, Step 21, Step 22, Step 23, Step 24, Step 31, Step 32, Step 33, Step 34, Step 36, Step 38 |
| OTL with Projects | Step 29, Step 30, Step 37* | Step 11, Step 12, Step 13, Step 14, Step 15, Step 17, Step 18, Step 19, Step 20, Step 25 | Step 16, Step 21, Step 22, Step 23, Step 24, Step 26, Step 27, Step 28, Step 31, Step 32, Step 33, Step 34, Step 35, Step 36, Step 38 |
Oracle Time & Labor provides the following descriptive flexfields, which you might need to update if you are adding fields to the timecard layout or writing new formulas:
OTL Information Types - Update this flexfield if you are adding to the timecard layout. You can add additional segments to existing context values or you can add new context values and associate segments to these values.
Running the Generate Flexfield and Mapping Information process creates contexts and segments in the flexfield automatically for the elements. HRMS key flexfields, and Oracle Projects expenditure items information that you want to capture on the timecard.
OTL Alternate Names - Update this flexfield if you are adding a field to the timecard layout and you want to configure the list of values for that field.
OTL Formulas - Update this flexfield if you write a new formula for time entry or approval rules. Create a new context for each formula you write.
You use the Oracle Projects Expenditure Items flexfield to define additional flexfield information you want to display for all expenditure types, or for particular expenditure types or expenditure type classes. You transfer these definitions to Oracle Time & Labor using the Generate Flexfield Mapping Information process.
You define flexfield value sets to validate the values that a user can enter for any segment. The attributes of the value set control the type of values that can be entered, and how many characters each segment can hold. The attributes of the value set also control how the values are to be validated. Value set can be shared by different segments of the same flexfield, or by segments of any other flexfield.
Use the Value Set widow.
See: Defining Value Set, Oracle E-Business Suite Flexfields Guide
If you are configuring the OTL Formulas descriptive flexfield, you must uncheck the Protect check box on the Descriptive Flexfields window.
Define new context and segments to hold your new field or formula information. For example, to add a new formula to the OTL formula flexfield, define a context for the formula and a segment for each formula input.
You do not need to use a value set to validate a segment. If you do not specify a value set then a user can enter any alphanumeric value up to a limit of 150 characters.
Use the Descriptive Flexfield Segments window.
See: Defining Descriptive Flexfield Structures, Oracle E-Business Suite Flexfields Guide
You can choose to use Independent validation for a value set used by a descriptive flexfield segment. If so, you must define a list of valid values for the value set.
Use the Define Segment Values window.
See: Defining Segment Values, Oracle E-Business Suite Flexfields Guide
If you configure the OTL Formulas flexfield, check the Protect check box in the Descriptive Flexfield window so it remains a protected flexfield.
You can define formula for time entry or approval rules. the predefined formulas are:
Seeded Formula for Period Maximum
(HXC_PERIOD_MAXIMUM), which checks that the number of hours worked in a particular time category does not exceed the specified limit per week (or other period) over a specified reference period (such as 14 days).
Approval Assignment Status Test (HXC_APPROVAL_ASG_STATUS) which checks the assignment status of the employee at the end of the approval period against a value specified on the Time Entry Rules window. If the statuses do not match, the time entries must be approved.
Approval Maximum Test (Seeded)
(HXC_APPROVAL_MAXIMUM), which checks whether the number of hours worked in a particular time category within an application approval periods exceed a maximum entered in the Time Entry Rules window. If it does, the time entry must be approved.
Assignment Standard Hours vs Time Category (Seeded Formula)
(HXC_ASSG_STD_HRS_Comparison), which validates hours entered on the timecard within selected time categories against an assignment's standard hours. The rule uses the standard hours recorded for the employee's primary assignment.
PTO Accrual Balance vs Absence (Seeded Formula)
(HXC_PTO_ACCRUAL_Comparison), which compares the hours entered on the timecard which decrement the accrual balance as specified in the Accrual plan definition against the PTO Accrual balance.
Period Hours vs Time Category (Seeded Formula)
HXC_TIME_CATEGORY_Comparison), which validates hours entered on a timecard against the hours defined for a period.
Override Approver WF Person Mechanism (Seeded Approval)
(HXC_OVERRIDE_APPROVER_WF_PERSON), which is the override approval style in the default Projects preferences. It send timecards to the override approver selected on the Timecard entry page.
You must define recurring time periods, which you can then select as approval periods and timecard periods.
The predefined recurring time periods is Weekly - Starts Sunday.
See: Defining Recurring Time Periods
You must define an approval period for each application, selecting from the recurring periods. You can define more than one set if you need to use different approval periods for different groups of employees.
The predefined approval period is Weekly - Starts Sunday.
See: Defining Approval Periods
Retrieval rules define which recipient applications must approve time and labor data before a retrieval process can retrieve that data. There are several predefined retrieval rules for the Oracle Projects and BEE retrieval processes.
See: Retrieval Rules
Review these rules; if they do not meet your requirements, you can create additional rules.
You can group retrieval rules into groups and associate the groups with people using the Retrieval Rule Groups preference. The following retrieval rule groups are predefined:
Projects Retrieval Rule Group - used in Projects Default Preferences
Payroll Retrieval Rule Group
Human Resources Retrieval Rule Group - used in Default Preferences
Projects and Payroll Retrieval Rule Group
Human Resources and Project Retrieval Rule Group
Human Resources and Payroll Retrieval Rule Group
HR, Payroll and Projects Retrieval Rule Group
If you create a new retrieval rule, then you must create a retrieval rule group that includes it.
See: Defining Retrieval Rule Groups
You can create time categories for reporting or to identify the types of time to be assessed by time entry rules. Categories can comprise mapping components (such as elements or projects) and other categories.
Several categories are predefined (Premium Hours, Non-Worked Hours, Billable Hours, Non-Billable Hours, and Total1 through Total10). However, there are no components or subcategories defined for these - they act as placeholders for your own definitions.
You can define formula - based validation rules for time entry. You can also define approval rules that specify what data entry or changes require approval for each application. These rules can be based on a formula or a mapping (that is, a set of fields that must be approved when they are entered or updated).
Validation rules are associated with a time entry rule group (then linked to people by preferences) and approval rules are associated with an approval style.
Predefined time entry rules for approval:
Payroll Data Approval Rule (associated with the Payroll Retrieval Process Mapping)
Projects Data Approval Rule (associated with the Projects Retrieval Process Mapping)
There is also a predefined time entry rule for validation:
Overlapping Time Entries (associated with the OTL Deposit Process mapping) - this rule uses a timecard's start and stop time entries to check whether each entry overlaps with another entry on this timecard, or an adjacent timecard period.
See: Defining Time Entry Rules
You must define time entry rule groups if you have defined time entry rules for validation. For each rule in the group, you specify an outcome: business message, warning, or error. You associate groups with people using preferences.
See: Defining Time Entry Rule Groups
If you are specifying a workflow as the approval method for an application, you must define the workflow. There is a simple predefined workflow that can serve as a template for creating your own workflows for approval. The predefined workflow item type is HXCEMP. This item type contains one process called OTL_APPROVAL_SEEDED_WF.
Use Workflow Builder and set your access level to 100.
See: Configuring Workflow Objects, Oracle HRMS Deploy Self-Service Capability Guide
Approval styles define the time entry rules and approval methods to use for each application. You can define as many approval styles as you require and link them to people using preferences.
The OTL application auto approves all timecards by default. If you want the application to approve some timecards in a different way, then you can use the Approval Rules region to set up conditional processing. You create a time entry rule for each approval rule you want to use in the Approval Styles window.
See: Defining Time Entry Rules
The predefined approval styles are:
OTL Auto Approve
Approve on Submit
See: Approval Styles
For Oracle Projects, use the Auto Approve approval style, and set the PA: AutoApprove Timecards profile option to Yes if you want timecards to be approved automatically, and to No, if you want them to be approved by the HR Supervisor. You set this at the responsibility level for the System Administrator responsibility (or whichever responsibility is used to set the profile option) and it applies to all users. If you require other rules for Oracle Projects approvals, consider customizing they Oracle Projects AutoApproval client extension.
See: Using Oracle Projects Client Extensions
If you use Oracle HRMS or Payroll, you must ensure you have defined all the elements that you will use for time and labor entry. These elements must be nonrecurring, allow multiple entries, and have one input value called Hours.
Use the Element window to define the elements (or the Earnings window if you are an Oracle Payroll user in the US or Canada).
If you are going to autogenerate values for these elements using time management structures and policies, the elements have additional required input values.
See: Setting Up Elements for Time & Labor Data Entry
Ensure you have linked all the elements that you will use for time and labor entry.
Use the Element Link window to link the elements.
Note: If you are going to create eligibility rules using Premium Eligibility and Earning policies, make sure your element link rules do not conflict with your policy rules.
See: Defining Element Links, Oracle HRMS Compensation and Benefits Management Guide
If you have Oracle HR or Payroll and use the Payroll retrieval rules, you define element sets to specify the elements to be fed by Oracle Time & Labor.
Ensure you select the Run type and add the elements to the element set individually.
See: Defining an Element or Distribution Set, Oracle HRMS Compensation and Benefits Management Guide
The Generate Flexfield and Mapping Information process creates context and segments in the OTL Information Types flexfield to hold the element, key flexfield, and projects information you want to store. It creates a context for each element and flexfield, and segment for each element input value and flexfield segment.
You must run this process on initial set up, and run this process later if you change the HR key flexfields, Projects Expenditure Items flexfield, set of elements for which you are holding information in the time store, or the input values of these elements.
See: Running the Generate Flexfield and Mapping Information Process
You must review the OTL Information Types flexfield to ensure your flexfields and all elements created in the element sets are enabled and visible, and the element input values are displayed correctly. Ensure that there is at least one enabled segment for each context. Check that segments are correctly marked as required or optional.
See: Reviewing the OTL Information Types Segments
If you added new contexts or segments to the OTL Information Types flexfields because you are adding or changing the information held in the time store or retrieved by recipient applications, you must perform this step. Otherwise, you can use the predefined mappings and mapping components.
See: Defining Mapping Components
If you define new mapping components, then you must update the predefined deposit mapping and /or define new retrieval mappings.
See: Defining Mappings
If you defined a new retrieval mapping, define a new retrieval process to use this mapping.
See: Defining Retrieval Processes
If you choose to configure the predefined timecard layouts, you must perform this step. There are five types of layouts: for data entry, review, confirmation, and detail (corresponding to the web pages in the Self Service workflow), plus a layout for exporting data for disconnected entry.
See: Timecard Layouts
You can define alternate names to create user-friendly names in list of values on the timecard and to restrict the list of values available to groups of users. for example, you could use alternate names to hide a "Shift" element from workers who do not work on shifts. You can also use alternate names to derive the value of a field that is not displayed from a field that is displayed on the timecard.
Note: You must create alternate names for the Element alternate names type if you use the Payroll or Exception layouts. You must create alternate names for Expenditure Element alternative names type if you use the Projects with Payroll layout. Associate these alternative names with the users of the layouts using the Timecard Alternate Names preference.
See: Defining Alternate Names To Configure Lists of Values
Templates store timecard data for reuse. By using templates, workers can concentrate on exception entry.
Dynamic templates are predefined. They pull data dynamically from work schedule information or Project resource Management, or the previous timecard. To enable workers to use the Work Schedule template, you must:
Set the Autogen Hours field to Yes in the Assignment Time Information window for their assignments.
Set the OTL Rules Evaluation preference to Yes, and select either HR or Payroll in the Approval Rules for Rules Evaluation segment.
Public templates are templates you create for other workers to use. You assign the templates using preferences to a specific worker or group of workers to enable them to quickly enter time and populate timecards.
You can create, update, and assign public templates only if you have either the OTL Administrator responsibility or the OTL Application Developer responsibility.
See: Timecard Templates
By default, all employees receive a set of default preferences. You can create new preference hierarchies and assign them to individuals or groups of individuals.
If you use Oracle Projects, then you must use the Projects Default Preferences. Create an eligibility rule for this branch and review the values in the Default Preferences and Projects Default Preferences.
See: Default Preferences
Note: You must ensure each worker has a value for the following preferences: Application Set, Retrieval Rule Groups, and Timecard Alternate Names (for workers who use the predefined Payroll, Exception, or Projects with Payroll timecard layouts).
You must ensure that the Retrieval Rule Group only references applications that appear in the Application Set, which means that you must create a new preference hierarchy for these to override the default preferences.
See: Defining Preferences
See: Defining Eligibility Criteria for Preferences
You can display instructions within each region of the web page and describe a page's functionality. Each instruction is delivered with sample text.
You can configure instructions to include links to external web sites or to launch a secondary window containing helpful information for your users. You could include your rules or procedures a user may need to know.
Tips are displayed next to a field and can provide guidance to a user on what information they should enter in a field. A tip is represented on screen by an icon.
Use the Messages window to configure instructions and tips.
See: Adding Instructions to Web Pages, Oracle HRMS Deploy Self-Service Capability Guide
Complete the remaining steps if you are using time management structures and policies to autogenerate timecards for some or all of your workers.
| If you are using... | Required Steps (no Defaults) | Required Steps (with defaults) | Optional Steps |
| OTL with Oracle HR Payroll | Step 39, Step 40, Step 41, Step 42, Step 43, Step 46, Step 51, Step 52 | none | Step 44, Step 44, Step 47, Step 48, Step 49, Step 50, Step 53 |
| OTL with Oracle Projects | not applicable | not applicable | not applicable |
For each element you are going to use for autogenerating values using time management structures and policies, define some additional information using the Element Time Information window. This information includes the earning category and any applicable premiums and expenditure type.
See: Entering Element Time Information
Define a holiday calendar:
To automatically generate a detail time entry line item with the correct numbers of hours
To validate hours taken are correct when a worker enters holidays manually
In conjunction with the Earning Policy to pay premium time for employees working on holidays.
See: Creating a Holiday Calendar
Define shifts to specify the start and stop times of employee work schedules. Shifts form the basis of work plans, which in turn form the basis of rotation plans.
You must define an off shift with either start and stop times of 00:00, or with hours equal to 00 before you create a work plan.
See: Creating Shifts
Work plans identify applicable shifts for the seven days of the week. Work plans are used:
In the autogeneration of hours for each person
To form the basis of rotation plans
For the calculation of day premiums and shift differential overrides
See: Creating a Work Plan
Rotation plans indicate the dates on which a person moves from one work plan to another. You assign workers to a rotation plan, even if that rotation plan only has one work plan.
If you do not use Oracle Projects, you can define projects within Oracle Time & Labor to input time and/or dollar estimates for tasks and work orders. You can track these projects by hours or by dollars using reports.
Variance tables define average, high, and low level for hours per period, by organization, location, or earnings. This information can be used to notify users that the changes in the expected number of earnings hours have been reached.
See: Defining a Variance
Earnings groups identify the earnings types you want to include in the accumulation of hours for calculating overtime limits (which are defined on the earning policy).
You can create multiple earnings groups for various groups of employees or to meet legislative requirements.
See: Creating an Earning Group
Define an hour deduction policy if you need to deduct time automatically from an employee's recorded hours to cover meals and other unpaid breaks.
See: Creating an Hour Deduction Policy
Define shift differential policies to identify the shifts that qualify (based on their start and stop times) and the earnings types to be used for the shift differential premium.
See: Creating a Shift Differential Policy
A premium eligibility policy lists the authorized premiums associated with each base hours type. You must define at least one premium eligibility policy.
Note: Although the policy defines premiums for which people are eligible, they will not automatically receive them. Eligibility is based on time ranges, actual time worked, and applicable pay rules.
See: Creating a Premium Eligibility Policy
A premium interaction policy defines how a premium should be calculated based on other premiums and in what order they should be processed.
If you have more than one authorized premium per base hours type on a premium eligibility policy, and one premium is to be used as a base for another, then you must create a premium interaction policy to indicate that one is to be applied to another. If you only have one authorized premium per base hours type on a premium eligibility policy, or if all of them apply only to a base hour, you do not need to create a premium interaction policy.
See: Creating a Premium Interaction Policy
Each earning policy is a grouping of rules and a holiday calendar that is assigned to each person. The earning policy identifies the daily/weekly base and overtime rules, the holiday calendar, and the premium policies to be used in calculating pay.
Define an earning policy for each of your enterprises' pay policies.
See: Creating an Earning Policy
For all workers whose time you want to validate or generate using time management structures and policies, you must enter details in the Assignment Time Information window. Here, you assign people to a rotation plan, earning policy, shift differential policy, and hour deduction policy. You also specify whether their timecard should be autogenerated from this information.
See: Entering Assignment Time Information
When you enter absences through the professional forms Timecard window, you may see the following warning message: "APP_HXT_39260: Absence not part of PTO accrual plan associated with this assignment". If you want to suppress this message - for example, to speed up data entry - you can do so by updating the HXT Timecard Validation lookup type. The default tag value for the ABS_NOT_ASG_TO_ACRL, lookup is WRN. You can update it to SKIP, meaning that the validation is disabled.
The other lookups in this lookup type are for validation performed by the Validate for BEE process. You can set their tags to ERR, WRN, or SKIP in the same way.
See: Configuring the Validate for BEE Process
Use the Application Utilities Lookups window.
If your enterprise wants to archive timecard data in order to release disk storage space, then you must set up a special responsibility with the appropriate security for archiving data.
See: Archive and Restore Overview
Set up the OTL Advanced Process Administrator responsibility. You set up the OTL Advanced Process Administrator responsibility to define data sets and run the archive and restore processes.
Select Standard as the security group.
Note: The OTL Advanced Administrator responsibility does not belong to a business group.
Select the OTL Advanced Processes Request Group.
See: Responsibilities Window, Oracle E-Business Suite System Administrator's Guide - Security
Set the following profile options:
OTL: Archive Restore Chunk Size
OTL: Minimum Age of Data Set for Archiving
OTL: Max Errors in Validate Data Set
The OTL Advanced Process Administrator can now archive and restore timecards using the archive and restore processes.
See: Archiving and Restoring Timecards
Set up the following information to transfer timecard data to Oracle Projects.
Set up a salary basis and salary proposal in HR for your workers. This setup ensures that the Transfer to Project Accounting process can access the data.
See: Defining a Salary Basis, Oracle HRMS Compensation and Benefits Management Guide
See: Starting Salary and Salary Proposals, Oracle HRMS Compensation and Benefits Management Guide
Run the Transfer to Project Accounting process.
Run the PRC: Transaction Import process to complete the projects transfer.
Time Entry Validation and Approval
Oracle Time and Labor Elements
Converting Day Entries to Hours
Retrieval and Deposit Processes
Self Service Timecard Configuration
Time Entry and Transfer Process
Info Online Links from Enwisen to OTL
OTL Rollback Processes for Payroll
Windows and their Navigation Paths