Oracle Time & Labor Implementing or Upgrading to OTL in an Oracle Projects Environment

Disclaimer: The following is intended to outline our general product direction and is intended for information purposes. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
Copyright © 2006 Oracle Corporation All Rights Reserved

Copyright Information

Oracle Time and Labor, Releases 11i and 12 Copyright 2005 Oracle Corporation All rights reserved. Primary Author: Kris Van der Ploeg Contributors: Alison Crabbe, Derek Morgan, Debbie Hendrix-Woolery, John Finnegan, Faz Assadi, Arul Senapathi Creation Date: 06-Dec-05 Last Updated: 14-Apr-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.

2

Table of Contents
1. 1.1 1.2 1.3 1.4 1.5 2. 3. 4. 5. 6. 7. 8. 9. 9.1 9.2 9.3 9.4 10. 11. 12. 13. 14. 15. Introduction ________________________________________________________________________________ 4 Purpose of this Document _________________________________________________________________ 4 Intended Audience ________________________________________________________________________ 4 Document Orientation _____________________________________________________________________ 4 Key Differences Between OTL and OIT______________________________________________________ 5 Definition of Terms ________________________________________________________________________ 5 Licensing Requirements for OTL _____________________________________________________________ 8 Steps for Implementing OTL _________________________________________________________________ 9 HR Foundation (Shared HR) to Full HR_______________________________________________________ 11 HR and Assignment Records _______________________________________________________________ 15 Preferences _______________________________________________________________________________ 17 Single vs. Multiple Timecards per Time Period________________________________________________ 18 Expenditure Items Descriptive Flexfield in OTL _______________________________________________ 20 Time Entry_________________________________________________________________________________ 23 Self Service timecards____________________________________________________________________ 23 Timekeeper ______________________________________________________________________________ 24 Line Manager Self Service ________________________________________________________________ 25 Authorized Delegate______________________________________________________________________ 26 Templates _________________________________________________________________________________ 27 Disconnected Time Entry ___________________________________________________________________ 30 Change and Late Audit (CLA) _______________________________________________________________ 31 Timecard Approval Styles __________________________________________________________________ 34 Timecard Approvers________________________________________________________________________ 36 Timecard Retrieval and Transfer to Oracle Projects and Other Applications_____________________ 39

Appendix A – Frequently Asked Questions about OTL with Projects _________________________________ 40 Appendix B – Document References & Further Reading _____________________________________________ 42

3

1. Introduction
1.1 Purpose of this Document As of November 2004, the Oracle eBusiness Suite has replaced time entry in Oracle Internet Time (Oracle iTime, or OIT) with OTL. OTL is now a single point of time entry for multiple applications in the eBusiness Suite. A number of OIT customers are currently upgrading from their OIT modules to OTL, or are planning their upgrade. To assist those customers, as well as any customer considering implementing OTL in a Projects environment, this document describes OTL's features that replace OIT's and deliver a powerful, flexible solution that complements Oracle Projects. We have also received feedback and questions from customers who have implemented OTL in a Projects environment. We would like to share that information from this common pool of knowledge in this document, and address the most common questions that customers have raised as well. This document also provides a number of additional resources available to assist customers with their OTL implementation. For customers considering upgrading from OIT to OTL, OTL provides the functionality available in OIT as well as a number of new features that are not available in OIT. This document will also examine some of the important differences between the two products, and some key new features in OTL that customers may find very beneficial. If you are currently an OIT customer, this document assumes that your setup in OTL will resemble your setup in OIT. OTL provides many additional options for configuration if you find that your business requirements have expanded to more than just capturing time for integration with Oracle Projects, though. For example, you may find that OTL’s integrations with Oracle HR, Oracle Payroll, Oracle Purchasing, and Oracle Enterprise Asset Management would enable your business to benefit more fully from your licenses of those products. Please refer to OTL’s implementation and user guide, and to its online help manual, for more specific information about how to implement these other aspects of OTL’s functionality. NOTE: This document does not replace or duplicate existing documentation. Rather, it provides a brief description of items for the reader to consider when implementing OTL in a Projects environment, and refers the reader to appropriate additional sources for further information about each of the items. 1.2 Intended Audience This document assumes the reader has some familiarity with Oracle’s eBusiness Suite of applications but may not necessarily be familiar with OTL. Its intended audience is functional or technical administrators or consultants who may be deciding if OTL is a suitable product for the company’s business requirements, or who may be currently implementing OTL in a Projects environment. We will indicate which sections are intended for a more technical audience in the orientation below and inside each section. 1.3 Document Orientation If you are looking for specific information or have specific questions, this list provides an orientation for where you can find that information in this document. • • • • • • • • Key differences between OTL and OIT: Section 1.4 Definition of terms: Section 1.5 Licensing requirements for OTL: Section 2 Overview of the setups required for implementing OTL: Section 3 HR installation for OTL: Section 4 HR and assignment records – required and useful data: Section 5 OTL’s preferences: Section 6 Entering a single timecard per time period: Section 7
4

o o o o o • • • Enterprise Asset Management – employees or contingent workers can charge time to work orders Human Resources Payroll – Oracle and 3rd party Purchasing – contingent workers can charge time to work orders Any combination of these applications OTL can be the single point of entry for all data transferred to these other applications. contingent workers are not paid via Oracle Payroll. Some examples are: o o o o o Timekeeper and Line Manager time entry Preferences that allow time to be entered and approved differently for subpopulations of workers Configurable timecard layouts Dynamic and public templates User definable lengths of time periods 1. Contingent Worker A worker who does not have a direct employment relationship with an enterprise and is typically a selfemployed individual or an agency-supplied worker. OTL can be integrated with 3rd party time collection devices. or on an ad hoc basis Change and Late Audit Allows you to track reasons for late timecards and to track all changes to new timecards. OTL’s time entry is very streamlined and flexible. as well as previously saved and submitted timecards.4 Key Differences Between OTL and OIT The following list provides a quick reference to some of the key differences between OTL and OIT: • OTL integrates with more than just the Projects applications. 5 .5 Definition of Terms Authorized Delegate An OTL user who enters time for another worker or a group of workers either on an ongoing basis.• • • • • • • • • • Using the Expenditure Items Descriptive Flexfield with OTL: Section 8 Methods for entering time in OTL: Section 9 Using templates to streamline time entry: Section 10 Entering time offline: Section 11 Audit data – entering reasons for late or changed time entries: Section 12 Methods for approving time: Section 13 How to approve time: Section 14 Transferring timecard data to other applications in Oracle eBusiness Suite: Section 15 FAQs about OTL with Projects: Appendix A Further information and documentation: Appendix B 1.

to define how individual workers or groups of workers can use the application. Restricted Use HR License The set of HR features and functions available to users who are not licensed for full HR. OTL provides several methods of time entry.Disconnected Time Entry Allows you to record your time when away from the office using a spreadsheet and then upload the spreadsheet into OTL for review and submission. Entry Level Processing Allows you to capture data for multiple applications in one timecard by defining rules to specify which data is optional and which data is required by each recipient application. and whether or not your timecard data requires approval Recipient Application An application other than OTL that uses timecard data Responsibility and Menu A level of authority in an application Each responsibility lets you access a specific set of Oracle Applications forms. into which applications you will retrieve data about a worker's time. reports. according to your business rules. menus. Several users can share a responsibility. and so makes more shared processes available for use. All entered time is available for retrieval by any of the applications that require your workers' data. You set up your own navigation menus for your responsibilities. OTL Preferences Rules that permit you. You can subject the time entries to various approval processes. and a single user can have multiple responsibilities. for example. Expenditure Items Descriptive Flexfield Used to define additional Flexfield information to display for all expenditure types. including the ability for your workers to enter their own time. Oracle HR Foundation provides a restricted set of responsibilities and database objects to carry out selected HR tasks. Oracle HR has delivered a new responsibility that groups together a set of forms that can be used by other Oracle Applications. This functionality delivers more processes than the current HR Foundation facility. HR Foundation (formerly known as Shared HR) A new responsibility available for bundling with specified Oracle Applications. but who have licensed certain Oracle Applications eBusiness Suite products such as Oracle Time and Labor that require features not provided by HR Foundation. Oracle Internet Time (OIT) A web application for entering timecards that was integrated only with Oracle Projects Oracle Time and Labor (OTL) Oracle Time & Labor is a single point of time entry for use by multiple applications that meets your time entry needs for employees and contingent workers for the entire eBusiness Suite. 6 . In order to further Applications integration. and data to fulfill your business role. Retro Adjustment A change made to a timecard after it has been transferred to a recipient application. or for particular expenditure types or expenditure type classes You can display this same Flexfield’s segments that are available in Oracle Projects on the timecard’s detail page using the Generate Flexfield and Mapping Information process. to suit the needs of different users.

You also can use the API to update or remove existing timecard data. positions and employee and applicant records within the Business Group. your timecard data may be entered in a "heads-down" data entry mode. updates. System administrators use them in defining users' responsibilities. and the time period in question are displayed Timecard Matrix The section of the timecard layout where the fields for the individual time entries and their attributes are displayed Timekeeper The set of features in Oracle Time & Labor that allows you to enter and maintain timecard information for multiple workers in a single session Using Timekeeper. 7 . Timecard Header The section of the timecard layout where the fields with information such as the worker’s name. Timekeeper Group A group of workers whose timecards the timekeeper enters.Security Profile Controls access to organizations. and submits. or in a mass edit mode that allows your Timekeepers to enter or update timecards for a number of workers simultaneously. Time Store Deposit API OTL's API for storing timecard data in the time store The system validates and stores this time data in the time store just as it would if you entered it through the Self Service timecard. On this page that your workers access from their timecards. You can set up the segments on this page so that they are context sensitive. employee number. Shared HR See HR Foundation above. Time Store OTL's central repository where all time data is stored The time store serves as a gatekeeper of data to all other Oracle applications. they may enter provide additional information related to your expenditure items. Timecard Details Page If workers have Projects in their applications set. you may assign a layout for the details page.

as well as what parts of HR you may use if you choose the Restricted Use HR license. o o • Transferring your OIT support contract o Your Oracle Support sales representative can assist with transferring your support contract. you will need to discuss the following with an Oracle sales representative: • • Transferring your OIT license to OTL HR licensing o Although you must upgrade your system from HR Foundation to a full HR installation to implement OTL. For example. 8 .2. if you are upgrading from OIT to OTL. you would need to buy the full license. Licensing Requirements for OTL Your application and support licensing needs depend on a number of factors. you can run OTL with the Restricted Use HR license that is included with your OTL license. Your Oracle account representative will help you determine which license is appropriate for your installation. You will require a license for a full HR implementation if you wish to use more of Oracle HR than absolutely necessary for your OTL implementation. For example. or you may choose to purchase a full HR license. if you wish to use Oracle HR’s appraisal functionality.

assign the appropriate responsibilities and security to each user. including defining expenditure items Descriptive Flexfields (DFFs). Steps for Implementing OTL Setups in Oracle Projects • Complete all necessary setups in Oracle Projects. Run hrglobal. Set up HR security. • • • • • • • OTL profiles applicable to your implementation – required Recurring periods – required Approval styles – required if using configured approval styles rather than delivered ones Schedule Workflow Background Process – required unless using Approve on Submit for all timecards. • Optional Oracle Projects setups when using both Oracle Projects and OTL: o o o Multi-organization Access Control Client extensions Project Resource Management General setups (all required) • • • • • • Change HR Foundation (Shared HR) to fully installed HR.drv for the initial installation of full HR on your system. including the most recent rollup at that patching level. this step only applies to current Projects and/or OIT customers who have not already implemented Oracle HR. including setting up your workers with person and assignment records in Oracle HRMS.1) for a complete listing of setup steps specific to OTL as well as more complete information about the steps. Please refer to the implementation guide for Oracle Projects for more specific setup information. Set up all HR objects required. responsibilities.3. Download and read all about documents and readmes for OTL's latest mini-packs and rollups. Not all setups may be necessary for your business’s needs. and users. Setups in OTL This list of setup steps provides a high level overview of the steps to implement OTL. Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. or if the profile has been set to not defer workflows Entry level processing rules and rule groups – optional Time categories – optional Time entry rules and time entry rule groups – optional 9 . apply any more recent rollups as necessary. menus. NOTE: Former OIT customers will likely already have all of the necessary setups for Oracle Projects in place. Confirm that your OTL installation has the highest patching level available. these steps are noted as optional.

If your OIT timecards were entered for periods during which the worker did not have an active assignment record. 10 .• • • • • • • • • • • • • • • Change and late audit rules and rule groups – optional OTLR objects – optional Define mapping components and mappings – optional Generate Flexfields and Mappings process – optional Alternate names – optional Retrieval rules and rule groups – required if using configured rules rather than delivered rules Configurations of timecard layouts – optional Public templates and template groups – optional Preferences – required Timekeeper configurations – required only if timekeepers are entering time for other workers Timekeeper groups – required only if timekeepers are entering time for other workers Authorized delegates – required only if authorized delegates are entering time for other workers Line Manager Self Service – required only if line managers are entering time for their workers Testing of setups – required Migrate timecards from OIT to OTL – optional and only applies to former OIT customers NOTE: If the OTL setups are incomplete or invalid. your timecards will not migrate correctly. those timecards will also not transfer to OTL.

a Position form that also emulates the Position form in HR Foundation is available in an additional patch as well. For this reason. no further data entry is required for this upgrade if you already are using HR Foundation. macro-style language that allows customers to configure their rules according to their own requirements. NOTE: The process. but work in a full HR environment. though. A patch applied on top of your upgraded HR installation allows you to use forms that emulate the HR Foundation forms for your person records. Fast Formula functionality is only available to the OTL customer with full HR. unique needs. must be run this one time only for the initial upgrade to full HR. 5. If you have a Restricted Use HR license. you may use the standard HRMS person and assignment forms. a. read all of the documentation about the latest patching levels before proceeding.drv. 4.I). Also. Run hrglobal.drv after applying an OTL patch for delivery of its seeded data. To use these forms. take the following steps: 1. Run datainstaller. For patching levels at HXT. Ensure that HR is patched at least to Family Pack D. HR Foundation (Shared HR) to Full HR OTL requires a full installation of Oracle HR because it is the most suitable environment for OTL’s customers to take maximum advantage of OTL’s current and future functionality. Run the license manager. Since each company has its own requirements for validation and approval. you may apply patches that deliver forms that emulate the HR Foundation forms. including with the Restricted Use HR license. Several enhancements exist that will make your upgrade as painless and transparent to your users as possible. OTL requires running hrglobal. as OTL is certified on that level or higher. you may not wish to train your users on the functionality of Oracle HR. Moreover. A new form. but include only those data that you need for OTL and that are allowable with a Restricted Use HR license.drv be run upon application of its patches. we want to ensure that all of our customers can take full advantage of future product enhancements. or to determine which time entries require approval with OTL’s Time Entry Rules feature.drv. Check that the form function parameter RESTRICTED_USE is set to Yes to switch off HR’s Date Track functionality. though. or you may wish to make your system appear to still be using HR Foundation. Time entry rules are based on the 'Fast Formula' language. If you have a Restricted Use HR license and wish to allow your users to use HR in the same way they have been accustomed to with your shared install. hrglobal. Patch 3882817 delivers this form. 11 . unless you have elected to purchase the full HR license. 3. b. For patching levels lower than Mini-pack I (HXT. Firstly. HR Foundation Enter Employee Template. select only the global option.I or higher. full HR – with either a full license or a Restricted Use license – is best ‘future platform’ for OTL’s customers. as OTL’s functionality continues to grow.4. an end-user. For example. Do not run it for any legislative options. As with any application. customers currently can create or configure rules to validate or audit time entries. assists you to manage the data you require for your person and assignment records. many of OTL’s customers use this functionality to meet their own. 2. Once you have applied the patch. If you have a full HR license. you can add this template to your responsibilities’ menus. OTL no longer requires that hrglobal. Once your system has been upgraded to full HR. Lastly. a. take the following steps: 1. select the legislative options you require. To upgrade to full HR.

NOTE: By setting this parameter. Check that the profile HR:National Identifier is set to appropriately validate the national identifier on this form (error/warning/no validation). any updates will overwrite existing data.e. all entries will be made as date track corrections. i. at the appropriate level to disable the Date Track reminders upon entering the form. The validation is based on the Fast Formula NL_VALIDATION. DateTrack:Reminder. c. Set the profile. Enter Employee template to emulate HR Foundation 12 . rather than retaining the original data with an effective end date and introducing the updated data with an effective start date that is later than the original data’s effective end date. b. and is legislative specific..

Other forms to emulate HR Foundation 13 .

you will need to apply patch 3968264. based on your HR records. Please also see Supplement for Using the Enter and Maintain Employee Information Template (HR Foundation) (Metalink Note: 284027. Confirm that you will be able to assign OTL’s preferences to the correct workers. See the section on OTL’s preferences below for more information about setting up and assigning preferences. 14 . Please refer to Migrating from Shared to Full HR (Metalink Note: 304002.1) for more information on how to add this template to your menu and its functionality. If you are currently using the Position form in HR Foundation and wish to continue to use the same form in after full HR has been installed.2. 3. You should ensure that your data will allow you to uniquely identify the workers to whom you wish to assign preferences while not inadvertently causing any omissions from your eligibility criteria rules.1) for more specific information about your HR installation and upgrade.

for example. 15 . that field is optional from OTL’s perspective and the perspective of its integrating applications. you must also add the supervisors’ names to the assignment records. By default. If you have upgraded your system from HR Foundation to full HR. you will need to set them up in the HR application. you may wish to set up the People Group Key Flexfield and use one or more of its segments to allow you the flexibility you need in defining eligibility for OTL’s preferences.5. If you are implementing OTL without upgrading from OIT. they must have a certain amount of HR data and an active assignment as part of their personnel record in the HR application. they must have a job on their assignment record. you may wish to consider providing those optional data. You can find all of these implementation guides on Metalink. to help you assign OTL preferences. If those data assist you with your business requirements. If your business requires a more robust definition of organizations. and which application that integrates with OTL requires the data. OTL will first notify the worker’s direct supervisor of timecards needing approval. If you wish to have your workers’ direct supervisors approve their timecards. To add a job to the assignment record. you will want to ensure that the assignment records include the following items if they are appropriate to your business’s needs: • All assignment records must have an HR organization on them. your business group is the organization on the record. please refer to the HR implementation guide for your specific localization. OTL’s preferences may be linked to your workers based on a number of criteria based on fields on their assignment records such as by organization. if your workers are in the United States. or by location. Positions are not required to enter time on Projects timecards. you must have an organization set up as a Government Reporting Entity. though. These records allow your Oracle applications to build the supervisor hierarchy. as GRE is a required field on US assignment records. For example. Many of the required fields have default values. you must have set up jobs in the HR application. Please be advised that you must consult your account representative about the licensing implications if you choose to use any of the optional data. The table below indicates which HR data is required. NOTE: Localizations and legislative requirements are only available if you have purchased a full HR license. • • • To enter Projects information on their timecards. • • For more specific information on these setups. though. though. Many localizations have fields on the assignment record for capturing required data for managing workers’ records in that country. your assignment records should already have these data on your workers’ assignment records. which are indicated in the table as well. If you select HR Supervisor as the approval method for your timecard data. If that supervisor does not respond to the notification. You may optionally set up positions and use them and the position hierarchy. If a field exists on the person or assignment record that is not listed here. HR and Assignment Records Before your workers can enter time in OTL. Please refer to the appropriate HR implementation guide for the specific requirements for your localization. If none of these fields suit your needs. by job. OTL will forward the notification to the next supervisor in the hierarchy and will continue to climb the hierarchy until the timecard has been approved.

HR Data Enterprise Asset Management X X X Value defaulted from action used to create person record Human Resources Payroll Projects Purchasing Last name Gender Person Type X X X Value defaulted from action used to create person record X X X Value defaulted from action used to create person record X X X X Value defaulted from action used to create person record X X X Value defaulted from action used to create person record National Identifier Date of birth Address information Organization X Value defaulted from business group X Value defaulted from business group X X X Value defaulted from business group X Value defaulted from business group X X Value defaulted from business group Job Payroll Assignment Status X Value defaulted from action used to create person record X Value defaulted from action used to create person record X X Value defaulted from action used to create person record X Value defaulted from action used to create person record X Value defaulted from action used to create person record X Purchase Order Information 16 .

Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.1) for more specific information about preferences. OTL’s default value is Human Resources. and rules about Self Service timecard entry. Be sure to override that preference in your setups to specify the correct application set for your needs. Following the example above. you can define one set of preferences and assign them to all workers in your consulting organization. may have their timecards approved in different ways. and which ones they can edit. You can set up OTL such that each set of workers may enter time on different timecard layouts. is a required preference. There are rules for the time store. consultants. and you may have engineers.6. 17 . you may have contingent workers who report time against purchase orders. OTL's preferences enable you to define rules about how individual workers or groups of workers can use the application. In an Oracle Projects environment. you may have exempt employees who only report exceptions to their normal work schedule such as absences (sick or vacation time). Preferences You may have a variety of types of users in your business. For example. OTL allows you to assign preferences to different groups of users with eligibility criteria rules. plus any other applications that you may be integrating with your OTL installation. such as which set of applications can retrieve data about a worker's time. the application set must at minimum include Projects. such as whether the worker can enter a negative number of hours. or construction workers who report all time against projects and tasks. define another set of preferences and assign them to all of your contingent workers. and their timecard data may be transferred to different Oracle applications. NOTE: The preference. Time Store Application Set. and define yet another set of preferences and assign them to all workers at your company's headquarters. You can also choose which preferences workers can see.

approved. OTL on the other hand allows only one timecard per time period. Single vs. Once you have transferred your projects timecard data to Oracle Projects. Because you assign time periods to your workers via OTL’s preferences. a single timecard per time period may seem too restrictive to OIT customers. you can also define time periods of different lengths and assign them to the appropriate workers. You can enable this functionality with OTL’s Self Service Timecard Status That Allows User Edits preference. so that your approvers can approve the timecards daily if necessary. to suit your business’s needs. from a single day to a month or longer. The definition of time periods provides the clue to why OTL’s solution of a single timecard per period actually works better for our customers. In OTL. a time period had a fixed length of one week (seven days). This feature ensures appropriate accounting of your users’ time and prevents any duplication of data. they will see fields for entering their time on only the current day. you may define your time periods to be of any length. your users can update their timecards retroactively if necessary. NOTE: If you use a weekly timecard period for timecards with Projects in the application set. At first glance. the approval notification will be sent after all timecards for that period have been properly submitted. Even after your timecards have been submitted. your users may update existing entries. the system will prevent your users from updating or deleting existing time entries in OTL regardless of how their status allowing edits preference is set. if you change the time entry in Oracle Projects though. In OIT. or they may even add time entries as needed. or they can approve the timecards for several weeks with a single action. NOTE: If your approval period is longer than your timecard period. particularly for government contracts.7. though. When your users open their timecards. depending on your requirements. you should start your time period on the same day of the week that your projects start. and transferred to Projects. OTL allows you to define the time entry period for these users to be for a single day. Many users in a Projects environment must create timecards on a daily basis. Depending on how you set this preference. thereby reducing the chance of user error. You can also define an approval period for any length of time. Multiple Timecards per Time Period OIT allowed users to create and submit more than one timecard per time period. 18 .

19 .1) for more specific information about defining and assigning time periods.Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.

If you make these segments optional. 3. even if they are required in the Expenditure Items flexfield. 5. They will be able to click on the Details icon displayed in each row of the timecard. Run OTL’s Generate Flexfield and Mapping Information process. At this point. In the Segments Summary window. 4. Recompile the OTL Information Types flexfield. If the segments are required in the OTL Information Types flexfield. you must enter values for all the instances of the required field on the Details page (each day of the week). and for each context field value.8. o o In the Context Field Values area. You cannot close the page until all the values are entered. just as if they had been entered in the Projects applications. query the Expenditure Items flexfield. the validation will happen when the users complete their entry and submit their timecards. Select a Details page layout in the Details Page segment of the Timecard Layout preference for your Projects workers. making sure you select Yes in the Include Expenditure Items Flexfield field. Make sure that the contexts you want to use in Oracle Time & Labor are enabled. the system validates the entries on the Details page against the Expenditure Items flexfield. To enable the details page on your Self Service timecards: 1. and that there is at least one enabled segment for each context. Expenditure Items Descriptive Flexfield in OTL Your workers can provide information in their OTL timecards that you wish to capture in the Projects Expenditure Items Descriptive Flexfield (DFF). Review the contexts and segments that the process generated in the OTL Information Types flexfield (the names you provided plus a system-generated prefix). define the segments for the global data element context (these fields appear for every expenditure type). Those data will transfer to Oracle Projects along with the rest of the timecard data and will be available for use there. making sure you enter either SYSTEM_LINKAGE_FUNCTION (used for Expenditure Type Class) or EXPENDITURE_TYPE in the Reference Field. 20 . 2. Suggestion: Consider making all the segments that will appear on the Details page optional. Set up this flexfield. enter a line for each expenditure type class or expenditure type for which you want to display a context-sensitive field on the timecard’s details page. In the Descriptive Flexfield Segments window.

Set up the Timekeeper Layout Attributes preference with the TK Expenditures List in one of the Timekeeper Layout Item fields. Be sure you have completed steps 1-4 above for the basic setups for the expenditure item DFF. 21 . 2.To enable the details page in the Timekeeper Time Entry form: 1.

4.10+ (Metalink Note: 304340. and then select the appropriate context to enter values in the associated DFF segments. click on the Details button.1) for information about how to configure the timecard layout to add expenditure item segments with a global context to the timecard’s matrix 22 . To enter details with timecard data in the Timekeeper Time Entry form.3. Please also refer to Oracle Time & Labor Timecard Configuration 11. select the appropriate row among the time entries.5. Assign the branch with these preferences to the appropriate timekeepers.1) for more information about displaying expenditure item DFF segments in the OTL timecard. Please refer to the online help or the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. Enter the same Timekeeper Layout Item in the Attribute Item Name for Detail Information Segment as you used for your TK Expenditures List attribute and the value in the Descriptive Flexfield to Display segment. 5. Add the Timekeeper Misc Setup Items preference.

9. Time Entry Oracle Time and Labor (OTL) provides a number of methods for entering time: • Time Store Deposit API o You can upload data from a third party system or a time collection device such as a time clock to create or modify time entries using this API. o • Line Manager Self Service timecards o Line managers enter time for the workers in their organization on a timecard-by-timecard basis. They also have template and disconnected entry functionality in this user interface. o • Self Service timecards o Workers can enter their own time directly into a timecard by either manually creating the time entries or by applying templates with predefined time entries. For more specific information on how to use this API. This user interface permits time entry on a timecard-by-timecard basis. enter time in a "heads down data entry" mode for a large group of workers. • Authorized delegate time entry o A delegated user enters time for other workers in a Web-based user interface. and dynamic Disconnected entry for downloading a template into a spreadsheet. 23 . This method is useful for those customers who require decentralized time entry by a user other than the worker. usually clerical personnel. o • Timekeeper o Timekeepers.1 Self Service timecards OTL provides a number of features to make entering time as efficient as possible for your workers: • • • Configurable layouts Templates – public. please refer to Oracle OTL HXC TimeStore Deposit API (Metalink Note: 223987. modifying. but the timecard preparer has no access to the professional forms. and provides template and disconnected entry functionality as well. The Timekeeper user interface is available in the professional forms.1). and uploading into a timecard. and then upload the spreadsheets upon next logging in to them. Users can use disconnected entry to create and modify spreadsheets when not connected to the Oracle applications. private. o 9.

9. A timekeeper can perform mass edits on the entire group of workers or a selected subset. called a timekeeper group. You can choose to add or delete specific workers from the chosen criteria and place them in another timekeeper group. a timekeeper might change an entered project code for a designated subset of the workers in that timekeeper group.2 Timekeeper Oracle Time & Labor provides a heads-down approach to enter time for multiple workers in a single session using the Timekeeper feature. and submits the timecards for approval. Timekeepers define their groups using various criteria. The timekeeper enters time. A super timekeeper can define a timekeeper group across the entire business group. Because the timekeeper will see many timecards for a large number of employees on one screen. you may assign three preferences to your timekeeper responsibilities: 24 . For instance. then validates. Timekeepers can also enter information for workers who do not have an active assignment. reviews. and not all of them may have identical preferences assigned to them though. and perform time entry for individuals or the entire group in a window called the Timekeeper Entry window. and corrects time entry errors. including OTL Self Service. although an approval responsibility may be assigned to a user who has a timekeeper responsibility. Timekeepers select a specific timekeeper group which they have responsibility to maintain. Timekeepers enter time for a large group of workers. the timekeepers are acting on behalf of the workers in their groups. In most respects. A Timekeeper is not necessarily an approver. just as the line managers and authorized delegates are. In general. and give a group to another timekeeper to process and maintain. and organizations. they are subject to the workers' assigned preferences. such as assignment sets defined in Oracle HRMS. A person in the role of a timekeeper can: • • Enter time for other employees from a paper-based system filled out by the employee Review and make changes to timecards imported from other time collection devices. such as making adjustments after a worker has been terminated.

• • Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. NOTE: The Self Service Line Manager user interface allows you to enter time only on a timecard-bytimecard basis. add them as the values for the segments on this preference. The timecard that they see for each worker is the same timecard that the workers themselves would see if they were entering their own time through the Self Service timecard. and expenditure types as the attributes of your workers' time entries. you can restrict them from doing so in two ways: 25 . If your business requires a large number of timecards to be entered in heads-down data entry mode. Timekeeper Misc Setup Items – determines if the timekeeper will see start / stop time columns and the workers' names or employee numbers. This function allows managers to record timecards for absent workers. Line managers can access workers using the supervisor hierarchy. Clicking on the Action icon in the hierarchy sets the context for the selected worker and displays the Recent Timecards page for that worker. whom to notify about the entered data. and if any is entered. if you want your timekeepers to enter project. This preference also determines which fields will require the timekeeper to enter reasons if the timecard data changes. based upon the workers' preferences: the managers are acting on behalf of their workers. If you do not wish to allow them to enter their own timecards through this interface.3 Line Manager Self Service Line managers can create.1) for more specific information about Timekeeper's features and setups. Timekeeper Change and Late Audit Items – allows you to specify if your timekeepers must enter CLA information. edit. task. displayed in a hierarchy. 9. Timekeeper is a better option. where the manager can expand the list to see workers reporting to the manager's direct reports.• Timekeeper Layout Attributes – determines which columns will appear on the Timekeeper Time Entry form. and submit timecards for workers in their organization within their assigned security profile. For example. or using the SSHR My List function to access workers within their security profile. The managers can also use the 'My List' submenu option to select workers that are not shown in the hierarchy. By default. The Self Service Line Manager functionality allows your managers to see a list of the workers in their organizations. line managers can enter their own timecard information using their assigned Line Manager responsibility. or for workers who may not be available to enter their time before the timecard data must be transferred to a recipient application.

Do not modify delivered menus or responsibilities.1) for more specific information about Self Service Line Manager's features and setups. Like in Self Service Line Manager. you can restrict from doing so by setting an additional parameter on the time entry function on the responsibility's menu. If you do not wish to allow them to enter their own timecards through this interface. and to Configuring. 26 . you may wish to use this method of time entry. but those personnel do not have access to the professional forms of the Oracle applications. just like for Self Service Line Manager (see above). Do not modify delivered menus or responsibilities. By default. to ensure delivered they update properly in future patches. Please refer to Authorizing Delegates for Time Entry (Metalink Note: 344280.4 Authorized Delegate If you need to delegate time entry for your workers to designated time entry personnel other than line managers. The timecard that they see for each worker is the same timecard that the workers themselves would see if they were entering their own time through the Self Service timecard.1) and to Configuring. ADDITIONAL INFORMATION: Use delivered menus and responsibilities as an example only for configuration. Timekeeper is a better option. • Set an additional parameter. you may wish to authorize executive assistants to enter time for their managers. You assign the list of workers whose timecards they will enter to your authorized delegates by means of an HR security profile. on the Timecard Mgr menu function (HXC_TIMECARDS_MGR). so the workers' preferences determine how the authorized delegate may use the system. then the security profile 'Exclude User ' is not evaluated. authorized delegates can enter their own timecard information using their assigned responsibility. the authorized delegates act on behalf of the workers for whom they enter time. If your business requires a large number of timecards to be entered in heads-down data entry mode. 9. Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. Reporting and System Administration in Oracle HRMS (Metalink Note: 214791. NOTE: The authorized delegate can only enter time on a timecard-by-timecard basis.1). to the Oracle Time & Labor Implementation And User Guide (Metalink Note: 207333.1) for more specific information regarding Authorized Delegate functionality and its setups. then enters or updates timecards on behalf of that worker. to ensure they update properly in future patches. ADDITIONAL INFORMATION: Use delivered menus and responsibilities as an example only for configuration.• Set the security profile 'Exclude User' if the 'My List' sub menu is enabled for the Line Manager responsibility. The authorized delegate selects a worker from within that security profile. For example. or to have a clerical worker submit timecards for all workers at a given construction site or only for workers while they are on vacation.1). Reporting and System Administration in Oracle HRMS (Metalink Note: 214791. pManagerEnabled. NOTE: If your Line Manager responsibility's menu does not include the 'My List' sub menu.

Templates While accounting for your workers’ time is necessary for many businesses. etc. PJRM (Projects assignments) – If you have implemented Oracle Project Resource Management for your workers' assignments. and by adding new entries. OTL provides templates that store timecard data for reuse. Rotation Plan. you can update the entries created from the template just as you would any other entry. and hours information held in that module. including start and stop times as appropriate. You can add more entries. and another four hours per day charged to the same project but a different task. Work Schedule – OTL provides a number of objects such as Work Schedule. For example. To that end. this template generates time and labor entries from the project. type. that when set up. You typically use this template when an employee is working on the same project week after week. Templates help users to avoid repetitive and error-prone data entry. OTL has three types of templates: • Dynamic templates o Last Timecard – This template uses the time entry data from the most recently submitted timecard. depending on your assigned preferences. provide the information needed to auto-populate your user’s timecard with the basic structure of their work schedule. eliminating the need for repetitive entry of project and task numbers. After applying the template to the timecard. o o 27 .10. and can even append any other appropriate template to the existing entries. you might define a project-specific template for a weekly timecard that records four hours per day charged to one project and task. Your workers can focus on entry of any time that is different from their expected working pattern by simply correcting any entries that need to change. most managers would like time entry to happen as rapidly and as accurately as possible.

• Private templates o You can grant some or all of your users the ability to create their own templates. 28 . There are two ways to create a private template: by saving a timecard as a template. or by creating a new template from scratch. a group of workers. o • Public templates o Since your administrative users often have more information about your projects and tasks. Your administrative users can create groups of public templates and assign them to a specific worker. o NOTE: OTL delivered public template functionality in Mini-pack J. they can create templates and assign them to your users to simplify and speed up your users’ time entry. using preferences. much as you would create a timecard. Your users can then create and save templates that contain time entries whose attributes consist of your users’ most frequently entered or current projects and tasks. or to all workers through OTL's preferences.

29 .1) for more specific information about using templates and enabling templates for your users.Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.

if that is your spreadsheet application of choice. and submit the timecard.csv file for MS Excel. Self Service users. and then upload the spreadsheet into OTL for review and submission. Once the time has been recorded offline. Please refer to Formatting an Exported OTL Template (Metalink Note: 283593. Oracle Development recognizes that customers use a wide variety of spreadsheet applications. 30 . so by default the exported file (. enter the new values.11. your users can edit the uploaded values. Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. OTL delivers seeded export layouts for each predefined timecard layout. line managers.1) to assist you in formatting your downloaded . and authorized delegates can upload the data directly into OTL.csv file) is not formatted for any particular spreadsheet application. Disconnected Time Entry You can record your time when away from the office using a spreadsheet.1) for more specific information about disconnected entry in OTL. though. then set the Enable Export of Defined Project List segment of the Self Service Disconnected Entry Option for Worker preference to Yes. Once the data appears in the timecard. You can assign the appropriate layout of an exported timecard for your workers to use by the value of the Export segment of the Timecard Layout preference. If you want to define a list of projects and tasks that you currently work on to export to a spreadsheet. Many former OIT customers find the MS Excel formatting of the template for disconnected entry useful. just as they would if they were entering the time in a blank timecard.

The Audit Information page requires the worker to enter a reason code for each day of the modified timecard. You cannot delete timecards or time entries from your timecards when using CLA. NOTE: Even if you have enabled CLA for some of your workers. you may choose not to have your timekeepers enter reasons for late or changed entries if you consider that doing so would slow down their time entry too much. You can even make your configured timecard layouts. • Your authorized delegates and line managers can use the CLA feature as well. You may decide that your paper timecards contain sufficient audit information. Timekeepers can also use the CLA feature to enter change and late-entry reasons when entering time for other workers. The Timekeeper Group and Timekeeper Entry windows display the workers for whom timekeepers can enter reasons and comments. When prompted to enter a reason for a changed or a late time entry.12. Change and Late Audit (CLA) This optional feature assists our customers whose time entry data are subject to audits. If the user attempts to enter any time entered after the due date has passed. the Audit Information page automatically appears after a worker selects Review from the time entry page. This update creates a change record. the system will require the user to enter a reason. You can track all changes to new timecards. you can enter zero (0) in the Hours field. The user interfaces for line managers and authorized delegates behave just as the Self Service timecard would. • • • • • 31 . your users may only select from the reason codes that you include in this list. instead of deleting a line item from the timecard. particularly those customers who work closely with the US Government’s Defense Contractors’ Audit Agency (DCAA). because deleting timecards and time entry data eliminates accurate audit trails. including columns that you add. You may also enter a comment to correspond with the changes made to each line item. You may use the delivered rules. However. OTL delivers rules defining when reasons for late or changed entries must be entered. even those with no government contracts. Many customers. You may define your own reason codes to fit your business's requirements. have found this functionality useful for their own auditing purposes. Features of CLA: • • • You may define when a timecard is considered late. or you may configure your own rules to meet your business's needs. For Self Service users using the Change and Late Audit feature. and entering it into OTL may be unnecessary for your business. so the system will require authorized delegates or line managers to enter reasons under exactly the same circumstances as it would for any Self Service users. so the system will require your user to enter a change reason. subject to CLA rules. as well as to previously saved and submitted timecards.

Original timecard Changed timecard 32 .

Audit page – enter reasons for changes to saved or submitted timecard Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. 33 .1) for more specific information about CLA's features and its implementation.

For example. With this approval style. You can write code to determine if your timecards require approval. OTL offers a variety of very flexible approval mechanisms for routing timecards or portions of timecards to the appropriate approvers. OTL categorizes the time entries on your timecards according to the associated Projects data for you. you do not need to re-code it or migrate your code during the upgrade. If you implemented a client extension in OIT. OTL also delivers two approval styles. In this case. the appropriate approvers will receive notifications and will only see the relevant data in their notifications. based on the data entered on the timecard Workflow – you may develop your own workflow for handling notifications. If the same manager is identified for more than one category. Timecard Approval Styles If your business requires that your workers' timecards be approved. if your business requires no human intervention in the approval process.13. OTL combines the data for each category into a single notification. known as data interdependency rules. Formula (Selects mechanism) – you may write a FastFormula that determines what approval style is necessary. you may select from the following options: • • • Person – a designated individual to whom the timecards are always routed HR Supervisor – the supervisor entered on the worker's assignment record Entry Level Approval – a means to route portions of your timecards to various approvers. you can set up categories for different types of time entries and specify the appropriate approval style for each time category. if you are integrating OTL with Oracle Payroll as well as with Oracle Projects. though. AutoApproval and Approve on Submit. For further flexibility. The approvers will only see the portion of the timecard that requires their approval. For example. OTL will override the HR supervisor hierarchy with yours. OTL will automatically detect your existing code that determines if approval is required. or you can define an approval hierarchy. Based on the configuration of your approval style. you can configure a rule such that it will detect when overtime has been entered on the timecard and thus route the notification to the approver that you specify. you may wish to have the HR Supervisor approve the payroll data on the timecard. approval rules. • • • You can also use a combination of these mechanisms on your approval styles. so the manager does not receive multiple notifications. rather than using the functionality in OTL’s workflow for notifying approvers. 34 . OTL then determines the appropriate project manager for each category it has identified and sends the time entries to that project manager. OTL also supports Projects client extensions that allow you to control how your timecards are approved. provide a means to specify under which conditions the timecard data requires approval. Project Manager – Because the Projects data changes frequently in many organizations using Oracle Projects and maintaining time categories for each project would be quite time-consuming and prone to human error. if you only require approval of overtime. but still have the Project Manager approve the Projects-related data. Since this style is a special case of Entry Level Approval. and no other timecard data. each of the project managers will see only the timecard data related to their own projects. OTL will execute any client extension that determines if timecards are required. If you require that a person or persons approve entered time. and will execute a client extension that specifies an approval hierarchy if you set your approval method to HR Supervisor. and it will detect your existing code that defines an approval hierarchy if you set your approval method to HR Supervisor.

1) for more specific information about timecard approvals and client extensions in OTL. 35 .Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.

Your approvers may perform this task from: • The Worklist Timecard Approval interface – The timecard approvers may review and approve or reject individual timecards in this interface.14. Timecard Approvers When your users submit their timecards. then identifies the appropriate person(s) to notify about timecards requiring approval. 36 . OTL's approval workflow determines if the timecard data requires approval.

and may select a number of timecards to approve or reject with one action in this interface.• The Mass Timecard Approval – The timecard approvers may review individual timecards. 37 . • The email notification – If you configure your system to send email notifications. the timecard approvers may review individual timecards and approve or reject them directly from the notification.

The timecard is sent to this approver only. 38 . based on assigned preferences. and the usual approval style is not activated. or authorized delegate can select anyone in the business group as the override approver. You can restrict the list of values for the Override Approver field by modifying the Overriding Approver view.1) for more specific information about approving OTL timecards. line manager. Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. The worker. The predefined Oracle Projects timecard layout has an Override Approver field.You can also allow your timecard preparers to enter override approvers.

or any updates at all. even after you have transferred it to Oracle Projects or other applications. Such changes are called "retro adjustments". If you permit your users to update their timecards retroactively. OTL's retrieval rules permit you to define in what status your timecards may be retrieved and transferred into other applications. Once you have run this process. etc. you run PRC: Transaction Import to transfer your approved timecard data from OTL to Oracle Projects. such as Oracle Purchasing. NOTE: If you make any changes to the timecard data within Oracle Projects. For example. by defining and assigning OTL's Timecard Status Allowing Edits preference. but you may need to transfer timecards to Oracle Payroll as soon as they have been submitted. so you can check the results of the retrieval and transfer processes such as PRC: Transaction Import. Your timecard data may be modified. NOTE: Using other applications with OTL requires the appropriate licenses.15. You will receive an error when you try to submit a retro adjusted timecard. you can re-run the PRC: Transaction Import to transfer only changed data to Oracle Projects. using an Oracle Projects responsibility. Please refer to the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333. they are ready to be retrieved by the recipient applications that use the data. depending on your business’s needs. you cannot edit the timecard within Oracle Time & Labor. If you transfer your timecard data to other recipient applications. or deleted in OTL. For example. Oracle Projects allows you to only transfer approved timecards from OTL to Oracle Projects. Your setups in Oracle Projects also indicate whether the incoming time entries should be designated as billable during this process. You can also prevent your users from making retro adjustments. all transferred timecard data is available for normal processing – billing. project accounting. even prior to the timecard's approval. Timecard Retrieval and Transfer to Oracle Projects and Other Applications Once your timecards have been submitted and/or approved in OTL. updated. – within Oracle Projects. Please contact your account representative if you need to enter time and transfer it to any applications other than Oracle Projects. 39 . OTL also provides the Retrieval Error Handling Report. regardless of how you have defined the Timecard Status Allowing Edits preference. once the timecard data has again been approved. each application can have its own rules for what timecards may be retrieved.1) for more specific information about retrieving and transferring OTL timecards to recipient applications.

Projects locks the timecard data regardless of your OTL configuration to prevent duplicated or conflicting data from appearing in 40 . approved. to trigger the entry of audit reasons. and Oracle Human Resources. What applications does OTL integrate with? OTL currently integrates with Oracle Projects. You will require a license for a full HR implementation if you wish to use more of Oracle HR than absolutely necessary for your OTL implementation. Oracle Payroll. Why does OTL require full HR to be installed? OTL requires a full installation of HR to operate the Fast Formulas that are the basis of its time entry rules. NOTE: If you add applications other than OTL. See Section 2 for more information about licensing requirements. or to configure your own formulas to use in your rules. What’s included with a Restricted Use HR License? The Restricted Use HR License includes the set of HR features and functions available to users who are not licensed for full HR. though. 4. If you require more specific information. you can run OTL with the Restricted Use HR license that is included with your OTL license. then these applications may have additional requirements for HR data. Basing OTL’s functionality on full HR allows you to configure time entry rules that use OTL’s delivered formulas. all of the time entries directed to that project manager will be combined into a single notification. but who have licensed certain Oracle Applications eBusiness Suite products such as Oracle Time and Labor that require features not provided by HR Foundation. as well as what parts of HR you may use if you choose the Restricted Use HR license. and transferred to Projects? Yes. Do I need to pay additional license fees for a full HR license? Although you must upgrade your system from HR Foundation to full HR to implement or upgrade to OTL. the notifies the appropriate project manager for approval. and to specify under what circumstances your timecards require approval. See Sections 13 and 14 for more information about timecard approvals. Can my users update timecards after they have been submitted. 5. If you make any updates to your timecard data in Projects. See section 5 for more information about HR data requirements. See Section 4 for more information about full HR with OTL. If any project manager is responsible for more than one project. Oracle Enterprise Asset Management. See Section 2 for more information about licensing requirements. For example. if you integrate OTL with Projects or other applications. More integrations are planned for future releases. These rules provide a means to validate entered time. what additional HR data fields do I need to set up to keep my applications running. 7. if you wish to use Oracle HR’s appraisal functionality. 6. you would need to buy the full license. please contact your Oracle account representative to discuss your specific needs for HR data. and why must I add them? OTL requires no additional HR data fields beyond those that you’ve already been using in your HR Foundation environment. Your Oracle account representative will help you determine which license is appropriate for your installation. 2. or you may choose to purchase a full HR license. depending on your configuration.Appendix A – Frequently Asked Questions about OTL with Projects 1. for example. Oracle Purchasing. you can update timecards and resubmit approved and transferred timecards. See Sections 1 and 15 for more information about OTL’s integrations. How can I have my project managers approve only the time entries related to their projects? OTL provides the Project Manager approval method that categorizes the time entries on your timecards by project. 3. When I upgrade from HR Foundation to full HR for OTL.

41 . See Section 7 for more information about time periods in OTL. you must use the HR Supervisor approval method.1. Can I have any time periods of any length for my timecards if I am a Projects user? Yes. and the Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.10 level should refer to Oracle Time & Labor Timecard Configuration. If you choose to have a weekly time period for your timecards that have Projects in their application set. 10. The OTL timecard shows the project and task numbers. 11. 9. OTL will call your code and override the HR supervisor hierarchy with your own. as well as other information or fields that you might find useful for your time entry. then you should start your time period on the same day of the week that your Projects start. can I add the project and task names to the timecard? Yes.1) for more information about migrating your OIT timecards to OTL. customers whose systems are not yet at the 11. you can configure OTL’s timecard and notification layouts to display the project and task names. See OIT to OTL Migration (Metalink Note: 289674.5. See Sections 6 and 15 for more information about preferences and transferring timecard data to other applications. you can have any time period of any length for your timecards. Can I migrate my old OIT timecards to OTL so my users can see them in OTL? All of your old timecards can be migrated to OTL. If you have implemented a client extension to determine whether or not approvals are required.1) for more information about using client extensions in OTL. See Section 13 for more information about approval styles.) for more information about configuring your OTL layouts.10+ (Metalink Note: 304340.Projects. If you have set that approval method on your approval style. Are the same client extensions supported in OIT and OTL? Yes.1. OTL supports and calls OIT’s client extensions. OTL automatically calls your existing code.5. Metalink Note: 227603. your users will be able to see them in OTL just like the ones they will create in OTL. See Oracle Time & Labor Timecard Configuration 11. If your client extension implements a hierarchy of approvers. If you migrate them. 8.

1) Formatting an Exported OTL Template (Metalink Note: 283593.1) Migrating from Shared to Full HR (Metalink Note: 304002. Reporting and System Administration in Oracle HRMS (Metalink Note: 214791. and Confirmation Page (Metalink Note: 294886.1) You can also find further documentation on Metalink about implementing the HR application for your specific localization. Review Page.1) How to Display the Project Name on the Self Service Timecard Entry Page. 42 .Appendix B – Document References & Further Reading Authorizing Delegates for Time Entry (Metalink Note: 344280.1) Configuring.1) Implementing Oracle Self Service Human Resources (Metalink Note: 226088.

1) 43 .1) HXT. Metalink Note: 227603.5.) Supplement for Using the Enter and Maintain Employee Information Template (HR Foundation) (Metalink Note: 284027.10+ (Metalink Note: 304340.1.G (Metalink Note: 258309.OIT to OTL Migration (Metalink.5.1.1) HXT.1) Oracle OTL HXC Time Store Deposit API (Metalink Note: 223987.1) Oracle Time & Labor Mini-Pack About Documents • • • • HXT. Note: 289674.I (Metalink Note: 303755.1) Oracle Time & Labor Implementation and User Guide (Metalink Note: 207333.1) HXT.10 level should refer to Oracle Time & Labor Timecard Configuration. customers whose systems are not yet at the 11.H (Metalink Note: 282087.J (Metalink Note: 344022.1) Oracle Time & Labor Timecard Configuration 11.