OTL Boot Camp r12
OTL Boot Camp r12
Implementation Planning
and Procedures
Book One
April 2006 Version 1
ORACLE CORPORATION
ALL RIGHTS RESERVED.
Note: The element is of the type Non Recurring with multiple entries allowed checked.
Now Create an Input value for the above element by name Hours. Note: The sequence
of the input value is 0 and the unit is Hours in Decimal format (2 places)
Repeat the same steps to create the other earnings element namely Overtime 1_5
Create an Element Set that includes the above elements defined in Payroll to be available
in OTL.
1. The alternate name defined here would appear in the Hours type LOV in the
Timecard
2. The values defined here are the payroll elements against which the time needs to
be entered. The OTL to BEE transfer process would populate the no. of hours
entered in the timecard to the input value of the corresponding element which is
used to pay the employee
Step-2
Navigate to OTL Application Developer> Application Sets
Define the application to which you wish to transfer the time from OTL. There are seeded
application set already defined. In this case we would use the seeded Payroll application
set.
Step-3
Navigate to OTL Application Developer> Deposit/Retrieval> Define Retrieval Rules.
You define the application & process that would retrieve timecard details from OTL. You
also define the status of the timecard that can be retreived by the application.
E.g. you can have Payroll/BEE reteive timecards that have their status as approved
inorder the pay the employees.
Step-4
Navigate to OTL Application Developer>Recurring Periods
You define the time period here. The time period defined here can be used for
1. Entering the timecad for the above timeperiod e.g. If you define a weekly time
period you can enter timecard for week.
2. You can use the above time period for approval. E.g. If you want the approver
to approve the timecards of employee on a weekly basis. You can also have
the timecard period defined as weekly but the approval period as monthly.
Step-5
Navigate to OTL Application Developer>Approval>Define approval periods
As mentioned in step 4 you can define the time period for approving a timecard. You also
specify different approval periods for different applications.
Payroll timecard can be approved every week whereas a Projects timecard could be
approved every month.
Step-6
Now that we have defined the other setups as mentioned above the timecards entered by
Allan has to be approved by his supervisor Charles.
Lets define the appropriate approval style to implement the above functionality.
Navigate to OTL Application Developer>Approval>Define approval style
You can setup different approval styles for different applications. As per the requirement
in the above fig we have setup the style as HR Supervisor so that the timecard submitted
by Allan should be approved by his supervisor Charles.
Now that we have defined the required setup we need to associate the same with the
employees. Preferences help us to associate the above setup with individual or set of
employees.
Navigate to OTL Application Developer> Preferences
There are certain predefined preferences available in the application. Now we need to
create a new preference tree for our Payroll timecards.
Right click on the root node and create a new preference tree.
Now we need to setup the preferences and preference values for the newly defined tree.
Add the following preferences to the GCI Payroll Tree.
Now that we have defined the basic preference and preferance values that are required to
enter a payroll timecard, we need to link the above preference to employee Allan.
Navigate to OTL Application Developer> Preferences>Eligibility Criteria
In the above fig. We have attached the GCI Payroll Tree individually to Allan. We can
also have the preference tree attached to
1. All emplooyes
2. All employee of a specific organization or Location.
Check the Link by LOV for other values.
Note: Rules with higher precedence have higher priority.
E.g. A rule with precedence 20 would have higher priority compared to a rule that has
the precedence as 10
The application has a Default preferences tree and a Default rule with precedence 1 that
is linked to All employees.
The preference tree that is applicable for a specific employee can be viewed in the People
tab.
Navigate to Submit Request and run the Generate Flexfield and Mapping Information
concurrent request.
Its all set for Paul to enter his timecard through self-service.
Note: Attach the GCI OTL Self Service responsibility to Paul.
The Hours Type against which timecard needs to be entered will appear in the Hours
Type LOV.
The above values are fetched from the Alternate name defintion.
Paul should now click on the submit button for Bill to approve the timecard.
Now Bill would login to the application and select the GCI Timecard Approval
responsibility.
Note: Attach the GCI Timecard Approval responsibility to Bill.
Now click on Approvals function to view the list of Timecards that needs to approved
by Bill.
Bill can now fill his comments and also Approve or Reject the timecards.
After the above process is completed successfully you could view the newly created
batch in payroll.
Navigate to GCI HRMS Manager>Mass Information Exchange>Batch Element Entry
and query for the batch reference supplied in the above request.
Run validate and transfer batch process for the above values to get reflected in Pauls
Element entry screen.
Time Entry rules are used to setup validations while employees enter timecards.
Greeting Card Inc has decided to display a warning message to their employees when the
total of Regular Hours entered for a week exceeds 40.
Step-1 (Define Time Category)
Navigate to GCI OTL Application Developer> Time Category
Time category is grouping of various components, which will be used by the Time Entry
Rules to validate the entry.
Foruma Inputs: Define the parameters that need to be passed to the formula. Also define
the maximum hours allowed for the time category for a specific timecard
Period. In the above scenario the Maximum hours is defined as 40.
The following warning message is displayed in the Timecard if the total time entered by
Paul for the week exceeds 40 hours. The warning message can be turned to Error by
changing the outcome field in Time Entry Rule Groups form.
Define the maximum hour that doesnt need supervisor approval in the formula inputs
field.
Attach the time category that needs approval for any timeentry greater than the maximum
hours specified.
Paul has entered 6 hours of overtime and submitted the time card. In this scenario the
timecard gets auto approved as the total overtime for the period is 6 which is lesser than
14.
The time card for the period starting 30th April 2006 is auto approved.
Paul has now entered 20 hours of overtime and submitted the time card. In this scenario
the timecard is sent to his supervisor (Bill) for approval as the total overtime hours for the
period is greater than 14.
The time card for the period starting 13th May 2006 is sent for supervisor Approval.
Hours Type
Regular Time
8 to 12 hours
Overtime
Comments
Employees are paid for upto
8 hours of regular pay
Employees are paid
overtime for the no of hours
worked beyond 8 and upto
12
Note: Earnings group are used to identify the set of earnings type that can be used for
hours accumalation in the earnings policy. The earnings group defined here is used in
Earnings Policy defintion.
Step-3 (Define Holiday Calendar)
Navigate to GCI OTL Application Developer> Table setup & maintanence> Holiday
Calendar
Set the Timecard Review Layout to Payroll OTLR Details Review Layout
You can see the timecard for Start Time 01-APR-2007 is approved.
Note :-If you have set OTL Rules Evaluation to Yes OTL data first moves from
Timestore to PUI and then to BEE screen.
Screen Shots below will help in understanding this.
Navigate to GCI OTL Application DeveloperOTL Time AccountingTime
Accounting-> Entry/Validation/Approval ->Query in Batch Field as PAUL%
As you can see the Timecard data has moved to PUI after Transfer Time From OTL to
BEE is run.
Step-9 (Run Valiodate For BEE)
Now this Data needs to be validated .Run Validate For BEE.This Concurrent Program
will validate BEE data against Earning Policy you have setup.
You can see above the Timecard Data has been vaidated after the Validate For BEE is
Complete.
Step-10 (Run Transfer to BEE)
Now you can finally move the data to BEE.Inorder to do that you need to run the
Transfer To BEE.
You can see the BATCH STATUS=Transferred To BEE in the above screen shot.
Now Navigate as Follows
OTL Time Accounting->MIX->Batch Element Entry Query as PAUL01%
This Data can be now be Interfaced to Payroll.Below are the steps to do that.
Step-9 (Interface to Payroll)
a) Click on Process and Validate BEE.
You can see the data for Paul in the Element Entry Form
The above is a basic setup for Payroll OTL.It should give you a fair idea as to how OTL
works with payroll.
Note: All the Project related setups e.g Creation of Projects,Transactions Controls on the
Project,Expenditure Type creation are part of Project Setup.Below I will discuss only the
OTL setup for Projects Timecard.
Now we need to setup the preferences and preference values for the newly defined tree.
Add the following preferences to the GCI Projects Preference.
In the below screen shot you can see the Timecard has been Auto Approved.
Now this Timecard needs to be interfaced to Projects.Run the below concurrent program.
Once the Programe completes sucessfully OTL data moves from Timestore
To Projects.
You can see the 8hours against the project Service Center has interfaced to Projects.
The above is a basic setup for Projects OTL.It should give you a fair idea as to how OTL
works with Projects.