Oracle 11i and R12 Time And Labor (OTL) Timecard Configuration (Doc ID

304340.1)

http://projectsaccounting.com/oracle-projects-otl/oracle-projects-information-in-otl.html

http://ora17hr.blogspot.in/search?q=Time+and+Labour

TIME AND LABOR Part 30 Oracle Time and Labour Setup's

Part 30.Define OTL Responsibilities and User ID

Part 30.2 Security Profile Setup for OTL

Part 30.3 Defining Elements like PTO, Holiday Hours, Sick Time...etc

Part 30.4 Linking the Elements

Part 30.5 Defining the Holiday Calendar

Part 30.6 Defining Shifts, Work Plan, Rotation Plan, Earning Group

Part 30.7 Defining Policies, Premium Eligibility, Shift Differential policy, Earning Policy

Part 30.8 Assign the Time Information to the Employee

Part 30.9 Define the Element set for the OTL

Part 30.10 Defining Recurring Period

Part 30.11 Generate Flexfield Mapping

Part 30.12 Defining Alternative Names, Approval Period, Time Entry Rules, Approval Style,
Retrieval Rules

Part 30.13 Defining Preferences: Self Service, Time Store

Part 30.14 Creating Eligibility Criteria

Part 30.15 Entering Time Sheet from Employee Login

Part 30.16 Time Cards Approval

Part 30.17 Transfer Time from OTL to BEE

Part 30.18 Running the Payroll using Time Sheets

Profile Options in OTL

A system profile is a set of changeable options that determine how (or whether) a
particular function runs.

Profile Options Table and Descriptions

Configurable Value
Profile Level Values (Default value in bold) Required?

HR: OTL Absence Site Yes No

Integration Setup No

HXT: Approver Required Site, Application, Yes, No No

Responsibility,
User

HXT: Adjust Overtime To Site, Application, YesNo, No

Previous Timecard Responsibility,
Within Same Workweek User

HXT: All / Selected Site, All Earning Categories Selected No

Earning Categories Responsibility, Earning Categories
User

HXT: Allow HDP Site, - No

Definition In Minutes Responsibility,
User

HXT: Batch Size Site, Application, 25, positive integers Yes

Responsibility,
User

HXT: Compare Special Site No

Rules Evaluation

HXT: Holiday Hours from Site, Application, Yes, No Yes

Holiday Calendar Responsibility,
 User

HXT: Hours per Year Site, Application, 2050, Positive integers Yes
Responsibility,
User

HXT: Limit Hour Site, Application, Yes, No No

Deduction on Shift Responsibility,
Premium User

HXT: Merge Batch Site, Application, Yes, No Yes

Timecards Responsibility,
User

HXT: Overtime Site

Functionality on Holidays

HXT: Rollup Batch Hours Site, Application, Yes, No Yes

Responsibility,
User

HXT: Include Premium Site, Application, Yes, No Yes

Hours to PA Responsibility

OTL: Allow Additional Site, Application, Yes, No No

Details on Time Entry Responsibility
Page

OTL: Allow Change Responsibility, Yes, No No

Group Timekeeper User

OTL: Allow Creation Responsibility, Yes, No No

Public Templates User

OTL: Allow TK Locking of Site, Application, Yes (at the site level), No Yes (if using
Queried Records Responsibility, TK)
User Note: Ensure that you set this
profile option to Yes if you use
Absence Integration
OTL: Archive Restore Responsibility 100 Yes
Chunk Size

OTL: Consider DayLight Site, Application, Yes, No No

Saving Time Responsibility

OTL: Defer Approval Site, Yes, No Yes

Process on Timecard Responsibility,
Submission User

OTL: Defer Data Site, Yes, No No

Collection for Time Entry Responsibility,
Detail Report User

OTL: Enable Diagnostics Site, Yes, No No

on Time Entry Detail Responsibility,
Report User

OTL: File Separators for Application, , (comma), ; (semicolon) Yes

the Import Export Responsibility,
Functionality User

OTL: Max Errors Application, Positive integers No

Responsibility,
User

OTL: Max Errors in Responsibility 500 Yes

Validate Data Set

OTL: Minimum Age of Responsibility 6 Yes

Data Set for Archiving

OTL: Number of Past Application, 365, Positive integers Yes

Days for Which Retrieval Responsibility
Considers Changes
(days)

OTL: RDB - Default Site, Application, Payroll No

Application Responsibility, Projects
User
OTL: RDB - Run Post Site Yes No
Retrieval Snapshot No
Automatically

OTL: Timecard Operating Site, Application, HR Assignment, MO: Operating No

Unit Source Responsibility Unit (Profile Option)

OTL: Transfer Batch Size Site, Application, Positive integers Yes

Responsibility,
User

OTL: Transfer to OTLR Site BEE only, Both OTLR and BEE, Yes
and/or BEE OTLR only

OTL: Use Upgraded Site Yes No

Retrieval Process No

OTL: Default Approval Responsibility, Approve, Reject, Skip Yes

Action for Mass Timecard User
Approver

7. Integration with OTL

Application: OTL

N: Time - Create TimeCard.

Select Period.

Give Project, Task, Type & Timecards

Click on save and continue and submit. then close the form.

Logout from services/welcome.

Login Dgray/welcome. click on workflow and click on Notifications.

Select the check box and click on open

Click on approve on Right side in the form and Logout.

Login into services/welcome.

Run “PRC: transaction import” source: Oracle Time and Labor

When you run above concurrent program, time sheets come to projects from OTL.

Open expenditure inquiry window & see allocated time slots with amounts.

Click on find.
Click on Item details.

Click on ok
To generate debit accounting entry, run following concurrent program.

“PRC: Distribute Labor Costs”

Click on ok.
To generate credit accounting entry, run following concurrent program.

“PRC: Generate Cost Accounting Events”

In expenditure inquiry window, we can see generated debit and credit account by clicking on item
details button.
If we want to interface labor costs to GL, then we have to Run “PRC: Create Accounting” concurrent
Program and specify parameter as Labor Cost.

If you get any error at the time of running “PRC: Create Accounting”, you can run another concurrent
program. i.e. “Validate Application Accounting Definitions”. and also Check the whether the Periods
are opened are not in related modules.
N: Tools tab - View Accounting.

8. Generation of Revenue and Invoice.

Revenue generation:

Run “PRC: Generate Draft Revenue for a Single Project”

If you want to see how much amount or revenue is generated, you can see it in view output.

Review Revenue.

N: Billing - Revenue Review.

click on open and click on Release.

then the Status is changed from unreleased to released. then close the form.

If we want to Transfer Revenue to the GL, we have to release the revenue. and Run PRC:Generate
Revenue Accounting Events concurrent Program. and also Run PRC:create Accounting concurrent
program .
if we check the Revenue status under Revenue Review window. Revenue Status is Accepted.

To generate invoice, we should run the program

prc: Generate Draft Invoices for single Project.

If we have more projects then we can run PRC: Generate Draft Invoices for Range of Projects.
After this we need to see the invoice review window, and click on Approve and click on Release while
releasing you have to specify the AR Invoice number : specify any number and check the status. Status
is Released.

After this we need to Run PRC: Interface Invoices to Receivables

Note: while running the above Program we have to give parameters which we have copy the Project
Number, otherwise that program will not work.

then we will go to AR.

After this we need to Run the concurrent program in AR i.e Auto Invoice Import program.

Then Open the Transactions workbench and Query the Invoice with GL Date.

Then go to Tools - create Accounting. View Accounting.

Then Check the status in Projects Invoice Review, The Status is Changed to Transferred to Receivables.

Then again Switch to Projects Module and Run the Program PRC: Tieback Invoices from Receivables.

Then Check the status in Projects Invoice Review, The Status is Changed to Accepted in Receivables.

Note: In projects after creating the Invoice the status are Unapproved -> approved -> released ->
Transfers to Receivables -> Accepted in Receivables.