otl fundamentals

8/19/2019 OTL Fundamentals

1/196


2/196

Copyright © 2007, 2012 Oracle. All rights reserved. Disclaimer

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy andprint this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorizationof Oracle.

The information contained in this document is subject to change without notice. If you find any problems in the document, pleasereport them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is notwarranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the UnitedStates Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTSThe U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restrictedby the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respectiveowners.

AuthorGowri Arur

Technical Contributors and ReviewersBob Oganovic, Leanne Wilborn

This book was published using: Oracle Tutor


3/196

Copyright © Oracle 2012. All rights reserved.

R12.x Oracle Time and Labor Fundamentals Table of Contentsi

Table of Contents

R12.x Oracle Time and Labor Fundamentals.................................................................................................1-1 R12.x Oracle Time and Labor Fundamentals ................................................................................................1-3 Objectives ......................................................................................................................................................1-4 Setup for the R12.x Oracle Time and Labor Fundamentals Course...............................................................1-5

Instructor Task - Completing Steps Required for Course Practices ...........................................................1-6 Introduction to Oracle Time and Labor...........................................................................................................1-10

Instructor Demo - Creating and Approving Timecards ...............................................................................1-11 Instructor Demo - Absence Integration with OTL .......................................................................................1-13 Oracle Time and Labor Rules Case Study.................................................................................................1-15

Introducing the Timecard ...............................................................................................................................1-17 Implementation Options .................................................................................................................................1-18 Time Entry and Approval Rules......................................................................................................................1-19

Practice - Defining Recurring Time Periods ...............................................................................................1-20 Solution - Defining Recurring Time Periods ...............................................................................................1-21 Practice - Defining Time Entry Rules and Time Entry Rule Groups ...........................................................1-22

Solution - Defining Time Entry Rules and Time Entry Rule Groups ...........................................................1-23 Approval Periods and Styles ..........................................................................................................................1-24 Practice - Defining Approval Periods..........................................................................................................1-25 Solution - Defining Approval Periods..........................................................................................................1-26 Practice - Defining Approval Styles............................................................................................................1-27 Solution - Defining Approval Styles............................................................................................................1-28

Using Elements in OTL ..................................................................................................................................1-30 Practice - Creating Elements for OTL ........................................................................................................1-31 Solution - Creating Elements for OTL ........................................................................................................1-32 Practice - Entering Element Time Information for OTLR ............................................................................1-35 Solution - Entering Element Time Information for OTLR ............................................................................1-36 Practice - Creating Element Sets ...............................................................................................................1-37 Solution - Creating Element Sets ...............................................................................................................1-38

Mappings and Retrieval Process....................................................................................................................1-39 Practice - Running the Generate Flexfield and Mapping Information Process ...........................................1-40 Solution - Running the Generate Flexfield and Mapping Information Process ...........................................1-41 Instructor Demo - Reviewing Mapping and Mapping Components ............................................................1-42 Instructor Demo - Reviewing Retrieval/Deposit Processes ........................................................................1-43 Instructor Demo - Reviewing Retrieval Rules.............................................................................................1-44

Timecard Layouts and Preferences ...............................................................................................................1-45 Practice - Defining Alternate Names for Warehouse, Retail, and Corporate Employees ...........................1-46 Solution - Defining Alternate Names for Warehouse, Retail, and Corporate Employees ...........................1-47 Practice - Defining Employees ...................................................................................................................1-49

Solution - Defining Employees ...................................................................................................................1-50 Practice - Creating Application Users.........................................................................................................1-53 Solution - Creating Application Users.........................................................................................................1-54 Practice - Defining Preferences for Warehouse, Retail, and Corporate Employees...................................1-56 Solution - Defining Preferences for Warehouse, Retail, and Corporate Employees...................................1-57

Defining OTLR Structures..............................................................................................................................1-64 Practice - Defining Holiday Calendars........................................................................................................1-65 Solution - Defining Holiday Calendars........................................................................................................1-66


4/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsii

Practice - Defining Shifts, Work Plans, and Rotation Plans........................................................................1-68 Solution - Defining Shifts, Work Plans, and Rotation Plans........................................................................1-69

Defining OTLR Policies..................................................................................................................................1-72 Practice - Defining Earning Groups............................................................................................................1-73 Solution - Defining Earnings Groups ..........................................................................................................1-74 Practice - Defining an Hour Deduction Policy.............................................................................................1-75 Solution - Defining an Hour Deduction Policy.............................................................................................1-76 Practice - Defining Shift Differential, Premium Eligibility, and Premium Interaction Policies ......................1-77 Solution - Defining Shift Differential, Premium Eligibility, and Premium Interaction Policies ......................1-78 Practice - Defining Earning Policies ...........................................................................................................1-80 Solution - Defining Earnings Policies .........................................................................................................1-81

Assigning Structures and Policies..................................................................................................................1-83 Practice - Assigning Structures and Policies to an Employee ....................................................................1-84 Solution - Assigning Structures and Policies to an Employee ....................................................................1-85 Practice - Viewing the Employee Assignment Information Folder ..............................................................1-86 Solution - Viewing the Employee Assignment Information Folder ..............................................................1-87 Practice - Using the Automatic Timecard Generation Process...................................................................1-88 Solution - Using the Automatic Timecard Generation Process...................................................................1-89

Transferring Timecards to BEE and Oracle Projects......................................................................................1-95 Practice - Entering Time and Labor on the Timecard Using Self-Service ..................................................1-96 Solution - Entering Time and Labor on the Timecard Using Self-Service ..................................................1-97 Instructor Demo - Running the Workflow Background Process..................................................................1-99 Practice - Approving Timecards .................................................................................................................1-100 Solution - Approving Timecards .................................................................................................................1-101 Practice - Transferring Time from OTL to BEE...........................................................................................1-102 Solution - Transferring Time from OTL to BEE...........................................................................................1-103 Practice - Transferring Time for Corporate Employee................................................................................1-106 Solution - Transferring Time for Corporate Employee................................................................................1-107

Applying Schedule Rules to Timecards..........................................................................................................1-110 Practice - Entering Time Data Exceptions..................................................................................................1-111 Solution - Entering Time Data Exceptions..................................................................................................1-112 Practice - Validating and Transferring Timecard for BEE...........................................................................1-114 Solution - Validating and Transferring Timecard for BEE...........................................................................1-115 Practice - Viewing the Batch Status ...........................................................................................................1-116 Solution - Viewing the Batch Status ...........................................................................................................1-117 Practice - Entering Retro Time Adjustments ..............................................................................................1-118 Solution - Entering Retro Time Adjustments ..............................................................................................1-119 Practice - Using OTL Reports ....................................................................................................................1-120 Solution - Using OTL Reports ....................................................................................................................1-121 Instructor Demo - Running the OTL: Timecard Audit Trail Report ..............................................................1-123

Entry Level Processing ..................................................................................................................................1-124 Instructor Demo - Reviewing Time Categories for Entry Level Processing ................................................1-125 Instructor Demo - Reviewing Time Entry Rules and Rule Groups for Entry Level Processing...................1-126 Practice - Defining an Employee for Entry Level Processing .....................................................................1-128 Solution - Defining an Employee for Entry Level Processing .....................................................................1-129 Practice - Defining Alternate Names for Entry Level Processing................................................................1-131 Solution - Defining Alternate Names for Entry Level Processing................................................................1-132 Practice - Defining Preferences for Entry Level Processing.......................................................................1-133 Solution - Defining Preferences for Entry Level Processing.......................................................................1-134


5/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsiii

Practice - Entering a Timecard for Entry Level Processing Using Self-Service..........................................1-137 Solution - Entering a Timecard for Entry Level Processing Using Self-Service..........................................1-138 Practice - Defining Time Entry Rules Using Mandatory Timecard Fields Formula .....................................1-139 Solution - Defining Time Entry Rules Using Mandatory Timecard Fields Formula .....................................1-140 Practice - Entering a Timecard for Extended Validation for Mandatory Timecard Fields ...........................1-141 Solution - Entering a Timecard for Extended Validation for Mandatory Timecard Fields ...........................1-142 Practice - Defining Time Entry Rules Using Invalid Timecard Field Combination Formula ........................1-143 Solution - Defining Time Entry Rules Using Invalid Timecard Field Combination Formula ........................1-144 Practice - Entering a Timecard for Extended Validation for Invalid Timecard Field Combination...............1-146 Solution - Entering a Timecard for Extended Validation for Invalid Timecard Field Combination...............1-147

Change and Late Audit (CLA) ........................................................................................................................1-148 Practice - Defining Reason Codes for Change and Late Audit...................................................................1-149 Solution - Defining Reason Codes for Change and Late Audit...................................................................1-150 Practice - Defining Time Categories for Change and Late Audit ................................................................1-151 Solution - Defining Time Categories for Change and Late Audit ................................................................1-152 Practice - Defining Time Entry Rules for Change and Late Audit ...............................................................1-153 Solution - Defining Time Entry Rules for Change and Late Audit ...............................................................1-154 Practice - Creating CLA Employee.............................................................................................................1-155

Solution - Creating CLA Employee.............................................................................................................1-156 Practice - Defining Preferences for Change and Late Audit .......................................................................1-158 Solution - Defining Preferences for Change and Late Audit .......................................................................1-159 Practice - Entering a Timecard for Change and Late Audit Using Self-Service..........................................1-162 Solution - Entering a Timecard for Change and Late Audit Using Self-Service..........................................1-163

Timekeeper ....................................................................................................................................................1-164 Practice - Defining an Assignment Set for Timekeeper ..............................................................................1-165 Solution - Defining an Assignment Set for Timekeeper ..............................................................................1-166 Practice - Defining Timekeeper Reporting Group.......................................................................................1-167 Solution - Defining Timekeeper Reporting Group.......................................................................................1-168 Practice - Using the Find Option in Timekeeper.........................................................................................1-169 Solution - Using the Find Option in Timekeeper.........................................................................................1-170 Practice - Transferring Timekeeper Entries from OTL to BEE....................................................................1-171 Solution - Transferring Timekeeper Entries from OTL to BEE....................................................................1-172 Instructor Demo - Using Mass Edits in Timekeeper ...................................................................................1-175

Self-Service Line Manager.............................................................................................................................1-177 Practice - Entering a Timecard as a Self-Service Line Manager ................................................................1-178 Solution - Entering a Timecard as a Self-Service Line Manager ................................................................1-179 Instructor Demo - Using the Timecard Status Dashboard ..........................................................................1-180

Archiving and Restoring Timecards ...............................................................................................................1-181 Instructor Demo - Archiving and Restoring Timecards ...............................................................................1-182


6/196


7/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsv

Preface

Profile

Before You Begin This CourseBefore you begin this course, you should have the following qualifications:

• Thorough knowledge of Oracle Applications

How This Course Is OrganizedR12.x Oracle Time and Labor Fundamentals Ed 1 is an instructor-led course featuring lectureand hands-on exercises. Online demonstrations and written practice sessions reinforce theconcepts and skills introduced.


8/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsvi

Related Publications

Oracle PublicationsTitle Part Number

Oracle Time and Labor Implementation and User Guide E13521-03

Additional Publications• System release bulletins• Installation and user’s guides• Read-me files• International Oracle User’s Group (IOUG) articles• Oracle Magazine


9/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsvii

Typographic Conventions

Typographic Conventions in Text

Convention Element Example

Bold italic Glossary term (ifthere is a glossary)

The algorithm inserts the new key.

Caps andlowercase

Buttons,check boxes,triggers,windows

Click the Executable button.Select the Can’t Delete Card check box.Assign a When-Validate-Item trigger to the ORD block.Open the Master Schedule window.

Courier new,case sensitive(default islowercase)

Code output,directory names,filenames,

passwords, pathnames,URLs,user input,usernames

Code output: debug.set (‘I”, 300); Directory: bin (DOS), $FMHOME (UNIX)Filename: Locate the init.ora file.Password: User tiger as your password.Pathname: Open c:\my_docs\projects URL: Go to http://www.oracle.com

User input: Enter 300 Username: Log on as scott Initial cap Graphics labels

(unless the term is a proper noun)

Customer address ( but Oracle Payables)

Italic Emphasized wordsand phrases,titles of books andcourses,variables

Do not save changes to the database.For further information, see Oracle7 Server SQL Language

Reference Manual. Enter [email protected] , where user_id is thename of the user.

Quotationmarks

Interface elementswith long names

that have onlyinitial caps;lesson and chaptertitles in cross-references

Select “Include a reusable module component” and click Finish.

This subject is covered in Unit II, Lesson 3, “Working withObjects.”

Uppercase SQL columnnames, commands,functions, schemas,table names

Use the SELECT command to view information stored in theLAST_NAMEcolumn of the EMP table.

Arrow Menu paths Select File > Save.Brackets Key names Press [Enter].Commas Key sequences Press and release keys one at a time:

[Alternate], [F], [D]Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

Typographic Conventions in Code

Convention Element Example


10/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsviii

Caps andlowercase

Oracle Formstriggers

When-Validate-Item

Lowercase Column names,table names

SELECT last_nameFROM s_emp;

Passwords DROP USER scottIDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER(OG_GET_LAYER (‘prod_pie_layer’))

Lowercaseitalic

Syntax variables CREATE ROLE role

Uppercase SQL commands andfunctions

SELECT useridFROM emp;

Typographic Conventions in Oracle Application Navigation PathsThis course uses simplified navigation paths, such as the following example, to direct youthrough Oracle Applications.

(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve

This simplified path translates to the following:

1. (N) From the Navigator window, select Invoice then Entry then Invoice BatchesSummary .

2. (M) From the menu, select Query then Find .

3. (B) Click the Approve button.

Notations:(N) = Navigator

(M) = Menu

(T) = Tab

(B) = Button

(I) = Icon

(H) = Hyperlink

(ST) = Sub Tab

Typographical Conventions in Oracle Application Help System PathsThis course uses a “navigation path” convention to represent actions you perform to findpertinent information in the Oracle Applications Help System.

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the General Ledger entry.

2. Under the General Ledger entry, expand Journals.


11/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsix

3. Under Journals, select Enter Journals.

4. Review the Enter Journals topic that appears in the document frame of the help systemwindow.


12/196


R12.x Oracle Time and Labor Fundamentals Table of Contentsx


13/196

Copyright © Oracle, 2012. All rights reserved.

R12.x Oracle Time and Labor FundamentalsChapter 1 - Page 1

R12.x Oracle Time and LaborFundamentalsChapter 1


14/196




15/196



R12.x Oracle Time and Labor Fundamentals


16/196



Objectives


17/196



Setup for the R12.x Oracle Time and Labor Fundamentals Course


18/196



Instructor Task - Completing Steps Required for Course Practices

OverviewBefore students begin working on the practices and demonstrations in this course, instructormust complete the following steps.

Assumptions• You must have access to an Oracle Application Vision database or comparable trainingor test instance at your site on which to complete this practice.

• Replace XX in the Practice with a unique identifier such as your initials or a number (forInstructor Led Training classes, this number will be assigned to you). This isnecessary in order to create unique records within the database when performing thePractice.

Tasks• Attach responsibilities to default Vision users• Verify that the Vision HR Weekly Payroll is available in the year that this course is

taught• Modify the element links for OTL elements• Verify the processing order for OTL elements• Verify that the Cost Reimbursable project is available in the year that this course is

taught

Attach Responsibilities to Default Vision UsersThe OTL Advanced Process Administrator responsibility is required to demonstrate archivingand restoring timecards. By default, this responsibility is not associated with any user in theVision database. Assign this responsibility to the HRMS user. Assign the US Education OTLSelf-Service responsibility to the BPALMER user.

Responsibility = System Administrator1. Log on as HRMS/welcome user.2. Navigate to the Users window.

(N) Security > User > Define3. Query HRMS in the User Name field.4. Select the OTL Advanced Process Administrator responsibility.5. Select Standard as the Security Group and enter 01-JAN-2005 in the Effective Date From

field.6. Save your work.7. Query BPALMER user and attach the US Education OTL Self-Service responsibility to the

user.8. Close the window.9. Switch responsibility and select the US Super HRMS Manager responsibility.


19/196



Verify that the Vision HR Weekly Payroll is Available in the Year that this Courseis Taught

Responsibility = US Super HRMS ManagerPractices and demonstrations in this courseware use the predefined Vision HR Weekly payroll.The start year of this payroll is 1996 and the number of years is 20. If this course is taught after2016, ensure that the payroll is available in the teach year. Otherwise, follow these steps toincrease the number of years so that the payroll period is applicable.10. Navigate to the Payroll window.

Payroll > Description11. Set the effective date to 01-JAN-1996.12. Query Vision HR Weekly payroll.13. Change the number of years from 20 to 30.14. Save your work.15. Close the window.

Modify the Element Links for OTL Predefined ElementsPractices and demos in this courseware use the following predefined OTL elements:

• OTL Regular Pay• OTL Shift Pay• OTL Vacation Pay• OTL Holiday Premium• OTL Jury Duty• OTL Sick Pay

By default, these elements are linked to the US Education organization. For the Earning Policiesto appear in the Assignment Time Information window for employees in the coursewarepractices, these predefined elements must be linked to All Payrolls.Follow these steps to link elements to All Payrolls.16. Navigate to the Element Link window.

(N) Total Compensation > Basic > Link17. Set the effective date to 01-JAN-1990 .18. Query OTL Regular Pay.19. Click Delete.20. Select the Purge option in the choose an option window.21. Save your work.22. Select the OTL Regular Pay as the element name.23. Click the Link To All Payrolls check box.24. Save your work.25. Repeat the steps 17 -23 for the remaining elements:

• OTL Shift Pay• OTL Vacation Pay• OTL Holiday Premium• OTL Jury Duty


20/196



• OTL Sick Pay26. Save your work.27. Switch responsibility and select the US OTL Application Developer responsibility.

Verify the Processing Order for OTL Elements

Responsibility = US OTL Application DeveloperVerify the Processing Order is as follows for the following elements:

• OTL Shift Pay = 20• OTL Holiday Premium = 20

28. Navigate to the Element Time Information window.(N) Element Time Information

29. Set your effective date to 01-JAN-1990.30. Query the OTL Shift Pay element.31. The default processing order is 15. Change it to 20 .32. Choose Correction.

33. Save your work.34. Query OTL Holiday Premium and verify the Processing Order. It must be 20.35. Exit Oracle Applications.36. Click Logout.

Verify that the Cost Reimbursable Project is Available in the Year that this Courseis TaughtThe practices and demonstrations in this courseware use the predefined Cost Reimbursableproject. Ensure that this project is available in the year that this course is taught.

Projects, Vision Services (USA)

37. Log on as SERVICES/welcome user.38. Navigate to the Find Projects window.

(N) Projects39. Select Projects in the Search For field.40. Select Cost Reimbursable in the Name field. This project is assigned to Services-East.41. Click Find. The Projects, Templates Summary window opens.42. Click Open.43. Notice the Trans Duration date, which, by default is 24-FEB-1997 to 31-MAR-2012.44. Change the Trans Finish Date to 2020 or extend it to the teach year.Assign Project Manager45. In the Option Name region, select the Key Members option and click Detail. The Key

Members- Cost Reimbursable window opens.46. Click in an empty row and select Hamilton, Ms.Anne Number 37.47. Select the Project Manager role.

Note : If Anne is assigned as a project manager for different time periods, then verify thelast To Date. When you assign Anne as the project manager for the relevant time period,


21/196



the From date must be the next day after the last To date. For example, if the last Todate is 31-MAR-2012, then the next assigned period starts from 01-APR-2012.

48. In the From Date enter 01-APR-2012 and 31-MAR-2020 or the teach year as the To date.49. Save your work.50. Close the Key Members window.51. Scroll to the Options region.

52. Select Tasks.53. Click Detail. The Tasks window opens.54. Change the Trans Finish Date for the tasks and subtasks to make them available for the

teach year.Note : Click the + sign for 1.0 and 1.1 tasks to change the Trans Finish date for sub taskstoo.

55. Click OK in the Caution window.56. Save your work.


22/196



Introduction to Oracle Time and Labor


23/196



Instructor Demo - Creating and Approving Timecards

Overview

In this demonstration, you learn how to enter and approve timecards. In subsequent practicesand demonstrations in this course, you will:

− Learn to configure OTL− Setup time structure policies for Oracle Time and Labor Rules (OTLR)− Transfer payroll and project timecards

Assumptions• You must have access to an Oracle Application Vision database or comparable training

or test instance at your site on which to complete this practice.• Replace XX in the Practice with a unique identifier such as your initials or a number (for

Instructor Led Training classes, this number will be assigned to you). This isnecessary in order to create unique records within the database when performing thePractice.

Entering Payroll Timecard using Self-Service

Responsibility = Self Service Time and Expenses1. Log on as BPALMER/welcome user.2. Navigate to the Recent Timecards page.

(N) Recent TimecardsYou can view recent timecards in a summary together with their current status. Apreference option governs the number of timecards displayed. This option is useralterable. Click the Preference link on top of the page and then select Oracle Timeand Labor Preferences. Enter the number of timecards to be displayed and numberof empty rows to be shown.You can search for timecards using advance options such as timecard status,timecard submit date, and timecard start date. You can sort timecards on status(Sorting is enabled on all columns). The Transferred To column indicates whether atimecard has been retrieved by recipient applications such as Payroll, Projects,Purchasing, and Enterprise Asset Management. You can also select individualtimecards and delete each of the timecards.

(B) Create Timecard A blank payroll exception timecard is displayed with blank rows. The number of blankrows presented is controlled by an OTL preference option.

3. Select the period for the timecard, for example, the previous week time period. If the periodis marked with a tilde symbol, "~", then a timecard already exists for the period. You cannot

enter another time card for a period where a timecard exists. The OTL set up is such thatchanges and deletions can be made up to the point of approval.

4. Select Regular as the hour type.5. Enter 8 from Monday to Friday. The format on entering hours is governed by OTL

preferences.6. Click Continue and the timecard review page is displayed.7. Submit the timecard.


24/196



8. Log out.9. Log on as BERICKSO/welcome and approve the timecard.

Entering Projects Timecard using Self-Service

Responsibility = OTL, Vision Services (USA)10. Log on as SERVICES/welcome user.11. Navigate to the Recent Timecards page.

(N) Recent TimecardsYou can view all the timecards for this person in various statuses. You can select anexisting timecard to review, edit, or delete. You can also choose create a newtimecard.

(B) Create TimecardThis takes you to a blank time card where you can now begin entering time for thisperson. The period allows you to choose the period you want to enter time. You canenter comments to be submitted with the timecard that will be forwarded to theapprover when the timecard is submitted. The bottom portion of the timecard iswhere you enter the specific time information for each day of the week. There is alsoa section on the page where a person can personalize data and save the data off asa template. This can be reused as often as you like and will help in reduction of theamount of data entry required. You can create as many templates as you require.

12. In the Period field, select the previous week time period.13. Select Cost Reimbursable - Cost Reimbursable as the project, 1.1.1 as the task.14. Select 2320 - Engineering Labor - (Straight Time) as the Type.15. Enter 8 Hours from Monday to Friday.16. Click Continue and then Submit.17. Click Logout.18. Log on as DGRAY/welcome user to approve the timecard.19. Click the Workflow responsibility and then the Notifications link.20. View the timecard notification from Marlin, Amy. Click the Subject to view details.Before you approve the timecard, review the timecard. Scroll down and click the + sign toexpand the timecard. You can view the timecard details that Amy Marlin submitted.21. Approve timecard.22. Click Logout.


25/196



Instructor Demo - Absence Integration with OTL

OverviewIn this demonstration, we will see how Absence Management is integrated with Oracle Time andLabor. The integration:

− Enables seamless integration between Oracle Human Resources absence

management and Oracle Time and Labor.− Provides timecard with details of absences while entering time.− Provides the ability to update absences on the timecard thus eliminating the need to

navigate multiple windows.− Leverages the common applications calendar work schedules.

This demonstration uses the Vision database, where OTL and HR Absence integration is setup.




Submit an Absence in Employee-Self ServiceCreate a vacation absence in Absence Management.

Responsibility = Employee Self-Service1. Log on as RJAMES/welcome user.2. Navigate to the Absence Management Summary page.

(N) Absence Management3. Click Create Absence.You are now on the Absence Management page for Robert James. You can view existingabsence or navigate to see the Entitlement Balances. From here you can create a newabsence. Before creating an absence, review the balances to make sure the employee hasbanked enough time to cover the absence you are entering.4. Click the Absence Type list.This is the page where you will create an absence. The absence integration is configured towork with vacation and sick time. In this scenario, you will create a vacation absence.5. Click the Vacation list item.6. Select Vacation from the LOV.

7. Click the Absence Reason list.8. Click the Vacation list item.You will now enter the dates and times for the start and end of the vacation.9. Enter the start date of the next time period.10. Enter "09:00" as the start time.11. Enter the end date of the next week time period.12. Enter "17:00" as the end time.


26/196



13. Click the Calculate Duration button.This calculates the duration of your absence based on the start date and time and the end dateand time. Ignore any warning that appears.14. Click Next and then Submit.15. Click Logout.Your absence entry is now in the list of absences in a pending approval status. From here we

will approve the absence.

Approve the Absence Created in Self-ServiceYou will log in as Barry Erickson to approve the absence.16. Log in as BERICKSO/welcome user.17. Click the Workflow User Web Applications link.18. Navigate to approve the absence.19. Click the Leave of Absence for James, Robert link.20. Drill into the link.21. Approve the absence.

22. Click Logout.Review the Absence in OTL

Responsibility = Self Service Time and ExpensesWe will now sign back on as Robert James to view the absence on the timecard.23. Log on as RJAMES/welcome user.24. Navigate to the Recent Timecards page.

(N) Recent Timecards25. The Recent Timecards page opens. Note that there is no timecard for the period the

vacation was created in. This does not happen until you create a timecard for the period.

26. Click Create Timecard.27. Select the same period in which the vacation transaction was submitted.Here the integration shows that the absence entered in absence management is now showingin time and labor.28. Click the Show Accrual Balances link.The absence status link displays any absence(s) that were entered in absence management.This helps to identify any discrepancies.29. Click the Continue button.You can also view the balances.30. Click the Submit button.

31. Submit the timecard for approval.32. Click the Logout link. The absence is submitted for approval.


27/196



Oracle Time and Labor Rules Case Study

OverviewThis topic provides you with the general business scenario for AB Shoes that lies behind thedemonstrations and labs for Implementing Oracle Time & Labor. This information helps you seethe individual labs in the context of a complete business operation and helps you to understand

how the labs are designed. While there may not be a true AB Shoes Corporation defined withinOracle Time & Labor, this case study will give you the feel of a real business and the labs areassociated to this corporation as defined in this business scenario.

Business Scenario - Company Profile AB Shoes Corporation is a division of AB Inc. - a diversified multinational corporation withoperations in manufacturing, retail, finance, consulting, and entertainment industries.

AB Shoes has its US Regional Headquarters in New York. AB Shoes Corp. has purchasedOracle Time & Labor and now wants to implement the system to support all of its global andlocal operations.

AB Shoes Corp

AB Shoes maintains a central warehouse and distribution center in Wisconsin that suppliesshoes and leather goods to all other AB locations. All employees at AB Shoes must enter atimecard in order to be paid. Additionally, warehouse inventory is tracked by Oracle Projects.

CompensationWarehouse employees are project based and enter time according to the task or job they aredoing. Project time is entered weekly. If any changes are made to the project number, tasknumber or type after the timecard has been submitted, then the Projects administrator must benotified. All warehouse employees work for the warehouse supervisor, who must approve alltimecards.

Warehouse Employee Requirements:1. The type of approval in the Approval Style must be HR Supervisor.2. You must create alternate names for the Expenditure Element alternative names type if you

use Projects with Payroll layout. Associate these alternative names with the users of thelayouts using the Timecard Alternate Names preference.

3. To use Oracle Projects, you must use the Projects Default Preferences. Create an eligibilityrule for this branch.

4. You must ensure all warehouse employees have a value for the following preferences: Application Set, Retrieval Rule Groups, and Timecard Alternate Names (for workers whouse the predefined Payroll, Exception or Projects with Payroll timecard layouts).

5. Application Set and Retrieval Rule Groups must be assigned the same value.

Retail Employee Requirements:Retail employees enter time in and time out. They work one of two shifts, which rotate every twoweeks. If an employee works over 8 hours per day, the next 2 hours are paid at 1.5 x theirhourly rate, and all remaining hours are paid at double-time. If an entry is made on a timecard inerror, they are required to discuss the issue with their store manager. The shifts are as follows:

• Shift 1 - 9:00am to 6:00pm• Shift 2 - 12:00pm to 9:00pm


28/196



The store manager approves the timecard for the respective store.6. You must create Alternate Names for the Element alternate names type if you use the

Payroll layouts. Associate these alternative names with the users of the layouts using theTimecard Alternative Names preference.

7. To enable workers to use the Work Schedule template, make sure they have:• The Autogen Hours field is set to Yes in the Assignment Time window• The preference OTL Rules Evaluation set to Yes, with HR or Payroll selected in the

Approval Rules for Rules Evaluation segment of this preference.

Corporate Employee Requirements:Corporate employees enter time weekly for payroll purposes and also record vacation or sicktime taken via the Self Service timecard. Corporate employees are scheduled to work 8:00am to5:30pm each Monday to Friday. Corporate employees get a one-hour lunch break but do notclock in and out. Corporate employees are paid for standard public holidays and are notexpected to work on Saturday or Sunday. Their timecard should have the ability for them toeasily enter the normal schedule and then make adjustments for exceptions as necessary.Corporate employee timecards do not need approval.8. You must create Alternate Names for the Element alternate names type if your use the

Exception layouts. Associate these alternative names with the users of the layouts usingthe Timecard Alternative Names preference.

9. To enable workers to use the Work Schedule template, make sure they have:• The Autogen Hours field is set to Yes in the Assignment Time window• The preference OTL Rules Evaluation set to Yes, with HR or Payroll selected in the

Approval Rules for Rules Evaluation segment of this preference.10. Corporate employee is also designated to be the super timekeeper and Line Manager who

has the capability to enter timecards for a group of employeesCLA employees enter time weekly for projects purposes via the Self Service timecard. CLAemployee timecards require one level of approval.

CLA Employee Requirements:To enable workers to use the Late and Audit:

• Usage in Time entry rules must be set to audit• Define Late and Audit lookup codes• Define time entry rules to set the scope of ‘late’ and ‘audit’ criteria• Service Flow preference must be set to Audit.


29/196



Introducing the Timecard

There are no Practices and Demonstrations in this Chapter.


30/196



Implementation Options

There are no Practices and Demonstrations in this Chapter.


31/196



Time Entry and Approval Rules


32/196



Practice - Defining Recurring Time Periods

OverviewIn this practice, you will define Recurring Time Periods. Recurring Time periods are used asapproval periods and to determine time entry periods. You must define your recurring periodsprior to defining your approval periods. All your employees will use the Weekly – Starts Monday

as the recurring period




Tasks

Define Recurring PeriodsRecurring Periods are used as approval periods and to determine time entry periods. You mustdefine your recurring periods prior to defining your approval periods. All your employees willuse the Weekly – Starts Monday as the recurring period.


33/196



Solution - Defining Recurring Time Periods

Defining Recurring Periods

Responsibility = US OTL Application Developer1. Log on as HRMS/welcome user.

2. Navigate to the Recurring Time Periods window:(N) Recurring Periods

3. Set the effective date to 01-JAN-2000.4. Enter XXWeekly – Starts Monday in the Name field.5. Enter Week in the Period Type field.6. Enter 31-DEC-2001 in the Start Date field; 31-DEC-2001 is a Monday.7. Save your work.8. Close the window.


34/196



Practice - Defining Time Entry Rules and Time Entry Rule Groups

OverviewIn this practice, you will define Time Entry Rules using Formulas and Mapping and assign theseTime Entry Rules to a Time Entry Rule Group.



Tasks

Define Time Entry Rule using Period Maximum FormulasWarehouse employees will use a time entry rule using the period maximum formula todetermine if they work over 40 hours in a 2 week period. You need to ensure the time and labordata is validated at the time of submission and resubmission. Warehouse employees will alsohave a recurring time period equal to Weekly starts Monday.

Define Time Entry Rule using MappingsWarehouse employees will also require a time entry rule using mappings at the time ofsubmission/resubmission for projects retrieval processing.

Define Time Entry Rule GroupsOnce you have defined your time entry rules, you will need to group these rules together in atime entry rule group. The rule grouping will produce an error is any of the time entry rules arebroken.


35/196



Solution - Defining Time Entry Rules and Time Entry Rule Groups

Defining Time Entry Rules - Using Period Maximum Formulas


2. Navigate to the Time Entry Rules window.(N) Time Entry Rules > Define Time Entry Rules

3. Set your effective date to 01-Jan-2009.4. Enter XXWarehouse Rule in the Name field5. Enter XX40 hours per week over 2 week period as the description for this rule.6. Select Submission / Resubmission/Delete in the Usage field. This determines approval is

required at the initial submission and when the employee changes the time and labor dataafter approval.

7. Select Seeded Formula for Period Maximum in the Formula field. The OTL Formulaspopup window will display.

8. Select XXWeekly – Starts Monday in the Timecard Period field.9. Enter 40 in the Maximum Hours field.10. Enter 2 in the Reference Period field.11. Choose OK.12. Select the Global check box and save your work.

Defining Time Entry Rules - Using Mappings for Approval Style13. Click in the next row.14. Enter XXWarehouse Mapping in the Name field.15. Enter XX Projects Retrieval Process Mapping as the description for this rule.16. Select Submission / Resubmission in the Usage field. This determines approval is required

at the initial submission and when the employee changes the time and labor data afterapproval.

17. Select Projects Retrieval Process Mapping in the Mapping field.18. Check the Global check box.19. Save your work and close the window.

Defining Time Entry Rule Groups20. Navigate to the Time Entry Rule Groups window.

(N) Time Entry Rules > Define Time Entry Rule Groups.21. Set your effective date to 01-Jan-2009.

22. Enter XXWarehouse Group in the Name field.23. Select XXWarehouse Rule as the Name of the Time Entry Rules. The remaining data field

will populate.24. Select Error in the Outcome field. This will produce an error on the timecard and stop the

submission process until the error is corrected.25. Save your work and close the window.


36/196



Approval Periods and Styles


37/196



Practice - Defining Approval Periods

OverviewIn this practice, you will define approval periods. Approval periods control when timecards aresubmitted for approval by each application.



Tasks

Define Approval PeriodsYour approval period for Oracle Projects (Warehouse employees) and Oracle Payroll (Retailemployees) are defined as Weekly – Starts Monday.


38/196



Solution - Defining Approval Periods

Defining Approval Periods


2. Navigate to the Approval Periods window.(N) Approval > Define Approval Periods

3. Set your effective date to 01-Jan-2009.4. In the Name field, enter XXWeekly Period – Starts Monday.5. Enter the following information:

Application Recurring Period

Projects XXWeekly – Starts Monday

Payroll XXWeekly – Starts Monday

6. Save your work.

7. Close the window.


39/196



Practice - Defining Approval Styles

OverviewIn this practice, you will define approval styles to determine who approves the worker’stimecards for each recipient application. Approvers could be a named individual, supervisor,more than one person in a workflow, or any other rules defined using a formula.




Tasks

Define Approval Styles

Approval Styles are used to alert the approver when timecards are waiting to be approved. Theapproval style defines who approves the timecards for each recipient application. The approvalstyle also defines which data needs to be approved for each application, and which datachanges require resubmission.Warehouse employees will need an approval style to alert the warehouse supervisor whentimecards are waiting to the approved as well as notification of when project, task, and or typeinformation has been changes.Retail employees will need an approval style to alert the store manager that timecards arewaiting to be approved.Corporate employees are not required to have timecards approved. To accomplish this, you willcreate an approval style for auto approve for all corporate employees


40/196



Solution - Defining Approval Styles

Defining an Approval Style for Warehouse Employees


2. Navigate to the Approval Style window.(N) Approval > Define Approval Styles

3. Set your effective date to 01-Jan-2009.4. Enter XXWarehouse Approval in the Name field.5. Enter a short description for this approval style in the Description field.6. Scroll to the Approval Rules region.7. Select XXWarehouse Mapping as the rule.8. Select Projects for the Application.9. Tab to the next row.10. Select Payroll Data Approval Rule.

11. Select Payroll for the Application.12. Scroll to the Approval Style Components region.13. Enter the following information:

Application Type Sequence

Projects HR Supervisor 10

Payroll HR Supervisor 20

14. Save your work.

Defining an Approval Style for Retail Employees

15. With the cursor on the Approval Style Name field, click the New icon to create an approvalstyle for retail employees.16. Enter XXRetail Approval in the Name field.17. Enter a short description for this approval style in the Description field.18. Scroll to the Approval Rules region.19. Select Payroll Data Approval Rule.20. Select Payroll for the Application.21. Tab to the Approval Style Components region, and select Payroll for the Application, HR

Supervisor type, and enter 10 as the sequence.22. Save your work.

Defining an Approval Style for Corporate Employees23. With the cursor on the Approval Style Name field, select the New icon to create an approval

style for corporate employees.24. Enter XXCorporate Approval in the Name field.25. Enter a short description for this approval style in the Description field.26. In the Approval Rules region, select Payroll Data Approval Rule.27. Select Payroll for the Application.


41/196


42/196



Using Elements in OTL


43/196



Practice - Creating Elements for OTL

OverviewIn this practice, you will learn how to create and link elements for time and labor entry. Elementsare essential compensation and benefit components that represent earning types.


• This practice covers only the required steps for performing this task.• Replace XX with your initials or the unique group identifier.

Tasks

Create Elements1. Create and link the following elements for use in OTL:

Overtime Pay

Doubletime Pay


44/196



Solution - Creating Elements for OTL

Creating Overtime Pay Earning

Responsibility = US Super HRMS Manager1. Log on as HRMS/welcome user.

2. Navigate to the Earnings window.(N) Total Compensation > Basic > Earnings

3. Set your effective date to 1 January 2000 .4. In the Name field, enter Overtime PayXX.5. In the Reporting Name field, enter OTXX6. In the Description field, enter XXOvertime Pay.7. In the Classification field, select Earnings.8. In the Category field, choose Overtime.9. Ensure that Processing is Nonrecurring .10. In the Calculation Rule field, select Hours * Rate * Factor and save your work.

Creating Double Time Pay Earning11. With the cursor in the Name field, click New.12. Enter Double Time PayXX as the name.13. In the Reporting Name field, enter DTXX.14. In the Description field, enter XXDoubletime Pay.15. In the Classification field, select Earnings.16. In the Category field, select Overtime.17. Ensure that Processing is Nonrecurring.18. In the Calculation Rule field, select Hours * Rate * Factor and save your work.

19. Close the window.

Modifying the Element20. Navigate to the Element window.

(N) Total Compensation > Basic > Element Description21. Set your effective date to 1 January 2000.22. Enter Query mode and find your earnings element, Overtime PayXX.23. Ensure the Multiple Entries Allowed and Process in Run check boxes are checked.24. Choose the Input Values button.25. Verify that there are Input Values called Hours, Pay Value, Multiple, Rate and Rate Code.

In US, you also require Jurisdiction, Deduction Processing, and Separate Check.Name Units Sequence User Enterable Database Item

Hours Hours in Decimal 1

Pay Value Money 1


45/196



Name Units Sequence User Enterable Database Item

Multiple Number 2

Rate Number 3

Rate Code Character 4

Jurisdiction Character Default default default

DeductionProcessing

Character Default default default

SeparateCheck

Character Default default default

26. Uncheck the Required check box for both ‘Deduction Processing’ and ‘Separate Check’input values if required.

27. Choose the input value and uncheck the Required check box. Save your work as correctionrespectively.

Modifying Double Time Pay Earning28. Query your earnings element, Double Time PayXX.29. Ensure the Multiple Entries Allowed and Process in Run check boxes are checked.30. Choose the Input Values button.31. Verify that there are Input Values called Hours, Pay Value, Multiple, Rate and Rate Code.

In US, you also require Jurisdiction, Deduction Processing, and Separate Check.

Name Units Sequence User Enterable Database Item

Hours Hours in Decimal 1

Pay Value Money 1

Multiple Number 2

Rate Number 3

Rate Code Character 4

Jurisdiction Character default default default

DeductionProcessing

Character default default default

SeparateCheck

Character default default default


46/196



32. Uncheck the Required check box for both Deduction Processing and Separate Check inputvalues if required.

33. Choose the input value, uncheck the Required check box, and save as Correction.34. Save your work as correction respectively and close the window.

Linking your Elements

35. Navigate to the Element Link window.(N) Total Compensation > Basic > Link

36. Set your effective date to 1 January 2000.37. In the Name field, choose Overtime PayXX.38. Check the ‘Link to All Payrolls’ check box.39. Save your work.40. With cursor in the Element Time window, click New.41. In the Name field, choose Double Time PayXX.42. Check the Link to All Payrolls check box.43. Save your work and close the window.


47/196



Practice - Entering Element Time Information for OTLR

OverviewIn this practice, you will enter the element time information necessary to use elements with yourstructures and policies for OTLR . Additional element information entry various based on theearning category assigned to the element. For example, regular pay elements only require an

earning category. Shift elements, and overtime elements require the entry of earning category,premium type, premium amount and processing order.




Tasks

Entering Element Time InformationElement Time Information is required for any elements used with structures and policies. Youneed to specify overtime for the earnings type, and enter the factor/multiple to indicate the rateof pay for overtime, and double time. Processing Order for both overtime and double timeelements should be equal to 15, so you can use these elements in your premium eligibility andinteraction policies.


48/196



Solution - Entering Element Time Information for OTLR

Responsibility = US OTL Application Developer1. Log on as HRMS/welcome user.2. Navigate to the Element Time Information window.

(N) OTL Time Accounting > Element Time Information3. Set your effective date to 01-Jan-2000.4. Select Overtime PayXX in the Element Name field.5. Select Overtime Earning in the Earnings Category field.6. Select Factor/Multiple in the Premium Type field.7. Enter 1.5 in the Premium Amount field.8. Enter 15 in the Processing Order field.9. Save your work.10. Place your cursor on the Element Name field, and choose a New record.11. Select the Double Time PayXX element and enter the following information:

Field Name ValueEarning Category Overtime Earning

Premium Type Factor/Multiple

Premium Amount 2.0

Processing Order 15

12. Save your work.13. Close the window.


49/196



Practice - Creating Element Sets

OverviewIn this practice you will create Element Sets. If you have Oracle HR or Payroll retrieval rules,you define Element Sets to specify the elements to be fed to Oracle Time & Labor. You canselect individually all the elements you require, or select a whole classification.




Tasks

Creating Element Sets

If you have Oracle HR or Payroll retrieval rules, you define Element Sets to specify the elementsto be fed to Oracle Time & Labor. You can select individually all the elements you require.You need to include Overtime Pay and Double Time Pay earning elements in an element set forretail employees.Corporate employees will need to have vacation, sick time and jury duty earning elements intheir element set.


50/196



Solution - Creating Element Sets

Creating an Element Set for Retail Employees

Responsibility = US Super HRMS Manager1. Log on as HRMS/welcome user.

2. Navigate to the Element and Distribution Set window.(N) Payroll > Element Set

3. Set your effective date to 01-Jan- 2000 .4. Enter Retail Element SetXX in the Name field.5. Select Run Set in the Type field.6. Choose Save.7. Click the Elements Name field.8. Choose Include Element button to display elements available for selection.9. Select OTL Regular Pay.10. Choose Include Element button to display elements available for selection.

11. Select Overtime PayXX.12. Choose Include Element button to display elements available for selection.13. Select Double Time PayXX.14. Choose Include Element button to display elements available for selection.15. Select OTL Shift Pay.16. Save your work.

Defining Element Sets for Corporate Employees17. With the cursor in the Name field, click the New icon.18. Enter Corporate Element SetXX in the description field.

19. Select Run Set in the Type field.20. Choose Save.21. Click the Elements Name field.22. Choose Include Element button to display elements available for selection.23. Select OTL Regular Pay.24. Choose Include Element button to display elements available for selection.25. Select OTL Vacation Pay.26. Choose Include Element button to display elements available for selection.27. Select OTL Sick Pay.28. Choose Include Element button to display elements available for selection.

29. Select OTL Jury Duty.30. Choose Save.31. Close the window.


51/196



Mappings and Retrieval Process


52/196



Practice - Running the Generate Flexfield and Mapping InformationProcess

OverviewIn this practice, you run the Generate Flexfield and Mapping Information process. The time storeholds elements, key flexfields, projects, and projects descriptive flexfields in the OTL Information

Types descriptive flexfield (the timecard). The Generate Flexfield and Mapping Informationprocess creates the context and segments in this flexfield to hold the element, key flexfield, andprojects information you want to store. The process creates a context for each element and keyflexfield, and a segment for each element input value and key flexfield segment. You run theGenerate Flexfield and Mapping Information process during implementation and later if youchange the elements, element input values, key flexfield information, or projects information thatyou want to hold in the time store.

After running the Generate Flexfield and Mapping Information process, you must review thesegments that this process has generated in the OTL Information Types flexfield. Thesesegments hold the element input values and flexfield segments in the time store. You canchoose which segments to enable and display.




TasksRun the Generate Flexfield and Mapping Information process and review the segmentsgenerated by this process.


53/196



Solution - Running the Generate Flexfield and Mapping InformationProcess

Responsibility = US OTL Application Developer1. Log on as HRMS/welcome user.2. Navigate to the Submit Request window.

(N) Process and Reports > Submit Requests3. Select Single Request and click OK.4. Select Generate Flexfield and Mapping Information from the list of values.5. Click the Parameters field to open the Parameters window.6. In the Delete Definitions? Field, select ‘No’.7. In the Element Set field, select Corporate Element SetXX.8. In the Effective Date field, enter 01-JAN-2000.9. Choose No for the following fields:

• ‘Include Cost Flexfield?’• ‘Include Group Flexfield?’• ‘Include Job Flexfield?’• ‘Include Position Flexfield?’• ‘Include Expenditure Items Flexfield?’• ‘Include Absence Information?’

10. Press OK when finished entering parameters to close the Parameters window.11. Choose Submit button.12. Write down the Request ID number ____________.13. Choose Yes to submit the same request for the Retail Element SetXX element set.14. Close the window.

15. Navigate to the Find Requests window.(N) View Requests

16. Click Find and view your requests.17. Make sure that your requests have completed without any errors.18. Switch responsibility.19. Select the System Administrator responsibility.

Reviewing the OTL Information Types Segments

Responsibility = System Administrator20. Navigate to the Descriptive Flexfield Segments window.

(N) Application > Flexfield > Descriptive > Segments21. Perform a query enter (F11).22. In the Title field, enter OTL Information Types.23. Execute (CTRL+F11) to run the query.24. In the Context Field Values region, you will see your elements in the Name field.25. With cursor on your structure, choose the Segments button.26. View the Input Values or segments and close the window.


54/196



Instructor Demo - Reviewing Mapping and Mapping Components

OverviewThis demonstration reviews the Mapping and Mapping Components used in Oracle Time &Labor.This demonstration illustrates mapping and mapping components. Each deposit and retrieval

process refers to a mapping. The mapping defines the set of timecard fields that the processdeposits or retrieves, and where these are held in the time store. The fields are defined asmapping components. There are predefined mappings for the predefined processes.Using the AB Shoes business scenario, we do not have a need to define new fields to becaptured by Oracle Time & Labor. Therefore, we will not need to define new contexts andsegments for the OTL Information Types description flexfield.




Reviewing Mapping and Mapping Components

Responsibility: OTL Application Developer1. Log on as HRMS/welcome user.2. Navigate to the Mapping Components window.

(N) Deposit/Retrieval Processes > Define Mapping Components3. Perform an open query on the window to show all mapping components defined.4. Scroll through the mapping components.5. Close this window.6. Navigate to the Mappings window.

(N) Deposit/Retrieval Processes > Define Mappings7. Execute a Blind Query to show all the predefined Mappings for BEE Retrieval Process

Mapping, OTL Deposit Process Mapping, and Projects Retrieval Process Mapping.8. Close the window.


55/196



Instructor Demo - Reviewing Retrieval/Deposit ProcessesThis demonstration reviews the Retrieval and Deposit Processes used within Oracle Time &Labor. This demonstration illustrates the retrieval processes delivered with Oracle Time &Labor. A retrieval process defines the data that a recipient application can retrieve from the timestore. There are predefined retrieval processes for Oracle Human Resources, Oracle Projects,and Oracle Payroll.




Responsibility = US OTL Application Developer1. Log on as HRMS/welcome user.2. Navigate to the Processes window.

(N) Deposit/Retrieval Processes > Define Process3. Perform an open query on the window. Scroll through all the deposit and retrieval

processes.4. Close the window.


56/196



Instructor Demo - Reviewing Retrieval Rules

OverviewThis demonstration illustrates the retrieval rules delivered with Oracle Time & Labor. Retrievalrules determine the approval status that data must achieve before the process can retrieve it.You can review the retrieval rule – Projects and Payroll – Approved. This rule indicates that

Oracle Projects and Oracle Payroll both require data to be approved before it can be retrieved.For retail and corporate employees, you can review the retrieval rule – Payroll. This ruleindicates that Oracle Payroll requires data to be approved before it can be retrieved.




Responsibility = US OTL Application Developer1. Log on as HRMS/welcome user.2. Navigate to the Retrieval Rules window.

(N) Deposit/Retrieval Processes > Define Retrieval Rules3. Perform an open query on the window to view all the Retrieval Rules.4. Close the window.


57/196



Timecard Layouts and Preferences


58/196



Practice - Defining Alternate Names for Warehouse, Retail, andCorporate Employees

OverviewUsing Alternate Names, you can configure lists of values on a timecard layout. You can renamevalues displayed in a list of values, or limit the display of values for a specific field on a timecard.




Tasks

Defining Alternate NamesUsing Alternate Names, you can configure lists of values on timecards. You may wish to changethe name of an element, limit the display of values in a list, or derive the value of a field from thevalue in another field.Warehouse employees will need to use alternate names to derive the expenditure type from theentry of a project.Retail employees do not need to see vacation, sick or jury duty in their list of values becausethey do not get paid for these hour types. However, they will need to have overtime pay anddouble time pay elements in their list of values.Corporate employees should see elements with the name regular pay, sick pay, jury duty andvacation.


59/196



Solution - Defining Alternate Names for Warehouse, Retail, andCorporate Employees

Defining Alternate Names for Warehouse Employees

Responsibility = US OTL Application Developer

1. Log on as HRMS/welcome user.2. Navigate to the Alternate Names window.

(N) Alternate Names > Alternate Name Definition3. Set your effective date to 01-Jan-2009.4. Enter XXWarehouse Employees in the Alternate Name Definition field and enter a short

description.5. Select OTL Alternate Name DFF Context in the Alternate Name Type field.6. Select Elements Expenditure System Linkage Function in the Type Name field.7. Enter XXWarehouse in the Prompt field and save your work.8. Enter Regular Pay in the Alternate Name field in the Alternate Name Type region.

9. Click the Values field to display the OTL Alternate Names popup window.10. Select OTL Regular Pay in the Payroll Elements field and Administrative in the Expenditure

Type field.11. Select ST in the System Linkage Function field and choose OK to close the popup window.12. Select the Enabled check box to display the alternate name in the list of values.13. Save your work.

Defining Alternate Name for Retail Employees14. With cursor on the Alternate Name Definition field, click New.15. Enter XXRetail Employees in the Alternate Name Definition field.16. Enter a short description for this Alternate Name Set in the description field.17. Select OTL Alternate Name DFF Context in the Alternate Name Type field.18. Select Payroll Elements in the Type Name field and enter XXRetail in the Prompt field.19. Save your work.20. Enter Regular Pay in the Alternate Name field in the Alternate Name Type region.21. Click the Values field to display the OTL Alternate Names popup window.22. Select OTL Regular Pay in the Payroll Element field.23. Choose OK to close the popup window.24. Select the Enabled check box to display the alternate name in the list of values.25. Place the cursor on a new record in the Alternate Name Values block and enter the

following information:

Alternate Name Payroll Element Enabled

Overtime Pay Overtime PayXX Checked

Double Time Pay Double Time PayXX Checked

Shift Diff Pay OTL Shift Pay Checked

26. Save your work.


60/196



Defining Alternate Names for Corporate Employees27. With cursor on the Alternate Name Definition field, create a new record.28. Enter XXCorporate Employees in the Alter Name Definition field.29. Enter a short description for this alternate name set in the Description field.30. Select OTL Alternate Name DFF Context in the Alternate Name Type field.31. Select Payroll Elements in the Type Name field.32. Enter XXHours Type in the Prompt field.33. Save your work.34. Scroll to the Alternate Name Type region.35. Enter Regular Pay in the Alternate Name field.36. Click the Values field to display the OTL Alternate Names popup window.37. Select OTL Regular Pay in the Payroll Element field.38. Choose OK to close the popup window.39. Select the Enable check box to display the alternate name in the list of values.40. Place the cursor on a new record in the Alternate Name Values block.41. Enter the following information.

Alternate Name Payroll Element Enabled

Sick Pay OTL Sick Pay Checked

Jury Duty OTL Jury Duty Checked

Vacation Pay OTL Vacation Pay Checked

42. Save your work.43. Close the window.


61/196



Practice - Defining Employees

OverviewYou will create three separate employees to use throughout your remaining labs. You willassign preferences to these employees, and enter time and labor data for each employee.


• Replace XX in the Practice with a unique identifier such as your initials or a number (forInstructor Led Training classes, this number will be assigned to you). This isnecessary in order to create unique records within the database when perfo

otl fundamentals

Documents