Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
‘Transfer Time from OTL to BEE’ is run to split time into Normal and OT hours. This applies all of the policies defined in Time
Management Policies in OTL. The division can then be viewed on the Professional Timecard.
This will populate the Professional Timecard. Here the Time Information can be reviewed for errors.
If any errors are found, they should be rectified in the Timekeeper Entry Window; and the
aforementioned request run again.
Global OTL Application Developer > OTL Time Accounting > Time Accounting>
Entry/Validation/Approval
After reviewing it for possible errors, run this request (from OTL Super Administrator):
This request is run at the End of the Month as Timecards are transferred at the period end date.
After that, run the Transfer to BEE Process request (from OTL Super Administrator):
It is important to note that the process date should be the last date in a period. This request
is run at the End of the Month as Timecards are transferred at the period end date.
Correction of Time Information and Rollback
Time Entry Errors may be discovered at different stages:
Any errors here should simply be rectified and the timecard should be saved and submitted.
Any errors discovered at this stage should not be corrected on the Professional Timecard. The
correction should be made on the Timekeeper Entry form and then the “Transfer time from OTL to
BEE” request should be run again.
3. After time has been transferred to BEE using the Validate and Transfer
Requests
Any errors discovered after transferring the data to BEE should not be corrected on the BEE Form or
the Professional Timecard. First the request “Rollback BEE” should be run from the responsibility
“OTL Super Administrator”. The correction should be made on the Timekeeper Entry form and then
the “Transfer time from OTL to BEE” request should be run again. After this, the following two
requests should be run form OTL Super Administrator:
4. After BEE has been Validated and Transferred to the Payroll Element
Any errors discovered after transferring the data to the Payroll Element should not be corrected on
the BEE Form or the Professional Timecard.
First the “BEE Batch Process (Rollback)” request should be run from the HRMS Responsibility, with
the parameters “Batch, Yes, Yes”.
Then the request “Rollback BEE” should be run from the responsibility “OTL Super Administrator”.
The correction should be made on the Timekeeper Entry form and then the “Transfer time from OTL
to BEE” request should be run again. After this, the following two requests should be run from OTL
Super Administrator:
As per business requirements, create all elements that are to be used to for Time Entry.
Element Definition
Must be Non-Recurring
Must have Allow Multiple Entries flagged to Yes
Input Values
Have one Input Value Called Hours in Format Hours in Decimal format (2 places)
o Flagged as Required
o Flagged as User Enterable
o Flagged as Database Item
Have a second Input Value called Date Claimed in Format Date
Note – It is imperative that the input values are as per the above or else Time Entry will fail with
errors.
Set up Element Links
Navigation: Global HRMS Manager > Total Compensation > Basic > Link
As per business requirements, create links that will be used for Time Entry.
Note – OTL Eligibility can be defined as an alternative or used in conjunction with Element Links, to
specify which group employees it is going to be linked to.
Once the business requirements have identified the basic set of employee rules of what employees
can claim for and see, we can begin to build up the OTL element sets. This is the final grouping of
employee rules.
Enter the Name of the Element Set and include (or Exclude) those elements you want as part of the
set. The Element Set specified here is fed into OTL.
Generate Flexfield and Mapping Information Process
Navigation: Global OTL Application Developer >Process and Reports>Submit Requests>Single
Request>Generate Flexfield and Mapping Information
The Generate Flexfield and Mapping Information process creates context and segments in the OTL
Information Types Flexfield to hold the element and Key Flexfield.
It creates a context for each element and Flexfield, and segment for each element input value and
Flexfield segment.
** You must run this process on initial set up for Each Element Set Created in the previous section,
and run this process later if you change the HR key Flexfields set of elements for which you are
holding information in the time store, or the input values of these elements.
This concurrent process will create Alternate Names sets within OTL which will include the Alternate
Names for the elements created in the element sets in the previous set up.
Parameters:
Delete Definition – Set to No on initial run to create the Alternate Name Mappings.
Set to Yes if you want to delete the Alternate Name Definition and
re-create it again with a new set of elements taken from Element
Sets
Set to Yes if you want to delete this Alternate Name Mappings.
If you set to Yes, you will still have to manually delete the
set from Alternate Names form in OTL.
Element Set – Enter the Element Sets created in the previous section.
Effective Date – Enter Effective Date (usually a date in the past).
Xx Flexfield – Default to Yes for all
Define Alternate Names
Navigation: Global OTL Application Developer > Alternate Names>Alternate Names Definition
The Alternate Names are created once the Generate Flexfield and Mapping Process is run. You can
then go to the form and update the name according to what you want the end-user to see.
Note, that two definitions will be created; Enabled and Disabled. They can both be referenced within
Preferences.
If you want to restrict an element so it is not displayed, uncheck the Enabled flag.
Approval Periods for each application used must be set up. These are generally the same as the
recurring Time Periods.
Define Approval Styles
Navigation: Responsibility: Global OTL> Approval > Define Approval Styles
Different Approval styles can be created for different employees through Preferences.
Approval Rules in the Approval Style Components Region may be used to define the Approval
process for Timesheets.
Optional notifications may be used as per requirements, through the ‘Other Attributes’ tab.
Define Retrieval Rules
Global OTL Application Developer > Deposit / Retrieval Processes > Define Retrieval Rules
Enter the Status for each application, at which it can retrieve OTL data.
Statuses:
• Working - Time has been entered for the application period but not yet
• Submitted - Application period is submitted and all the days in a period have a
submitted status.
One of the structures used to define working patterns is through the Holiday Calendar. This needs to
be defined to determine Paid and Unpaid holidays.
For Paid Holidays, enter the number of standard working hours, e.g. 8.
This table can be maintained at anytime of the year, but holidays must be specified before their
occurrence.
Create Shifts
OTL Super Administrator > OTL Time Accounting > Table Setup and Maintenance > Shift
You can enter Start and Stop timings to signal the start and end of the shift. Also you can define Early
Start time to adjust the time period taken by workers to enter the factory.
The Late Stop column may be used to allow a certain period of time to the employees to exit the
premises.
OTL Super Administrator > OTL Time Accounting > Table Setup and Maintenance > Work Plan
Define Rotation plans
Different Work Plans can be assigned to one employee if he does any shifts other than or in place of
his regular shift.
OTL Super Administrator > OTL Time Accounting > Table Setup and Maintenance > Rotation Plan
You can select different work plans and set appropriate start dates to define when the employee is
rotated.
If you have entered at least two work plans, you can auto generate the pattern you have set. Enter
the next start date and the number of rotations. For example, to repeat the pattern ten more times
starting on 1 March, enter that date in the Next Start Date field, and 10 in the Number of Rotations
field.
Defining Variances:
You can define Variance limits to manage exception reporting.
Global OTL App deleloper > OTL Time Accounting > Table Setup and Maintenance > Variance
Select the element, organization or location you want to monitor, in this case Overtime Hours.
Define Upper and Lower Limits as shown.
Enter Element Time Information
For each element you are going to use for auto generating values using time management structures
and policies, define some additional information using the Element Time Information window. This
information includes the earning category and any applicable premiums and expenditure type.
For example Normal Hours can be classified in the “Regular Earning” Earning Category; whereas
Overtime Hours can be classed as “Overtime Earning”.
It is mandatory to classify at least one Element as “Absence Earning” if the Holiday Calendar is to be
used.
Global OTL App developer > OTL Time Accounting > Policies > Element Time Information
Defining Earning Groups
Earnings groups identify the earnings types (elements) you want to include in the accumulation of
hours for calculating overtime limits (which are defined on the earning policy).
If you do not define elements within the Earning Group, and are using an Earning Policy which says
that first 8 hours should be thrown within Normal Hours element, ALL first 8 hours will be thrown
there, let it be Maternity Leave, Sick Leave, Hajj Leave, Official Work etc
OTL Super Administrator > OTL Time Accounting > Table Setup and Maintenance > Earning Group
In this case, this group will add an employee’s Basic hours, Short Leaves, Official Work etc. to
calculate Overtime limits.
You can create multiple earnings groups for various groups of employees.
Create Shift Differential Policies
These are used to award premiums to those who work certain shifts.
OTL Super Administrator > OTL Time Accounting > Policies > Shift Dfferential
The start and Stop are the start and stop times of the differential shift. Enter the premium earning
type to define how these are to be calculated.
Create Premium Eligibility Policies
A premium eligibility policy lists the authorized premiums associated with hours type. You must
define at least one premium eligibility policy.
OTL Super Administrator > OTL Time Accounting > Policies > Premium Eligibility
In the above example, The Basic Salary Hours have been set as the Base Hours with Overtime Hours
being the Authorised premium.
Create Earning Policies
Here we combine the Holiday Calendar, the Premium Eligibility and Premium Interaction policies,
the Earnings included to meet OVT(Overtime cap), that we previously designed.
Further Rules are also defined as to how all of the elements are to be used in calculating Paid Hours.
1. . Change the effective From date to the appropriate start date for the policy, that predates any
employee hire dates.
2. . Select a Type of earning rule, such as Base, or an overtime rule:
• Use Daily Overtime if you only need to define rules based on a day.
• Use Weekly Overtime if you only need to define rules based on a week.
• Use Special Overtime if you are defining rules that are based on a combination of a day,
and/or week, and/or a consecutive days’ basis.
3. . Select a Holiday Calendar.
4. . In the Earnings included to meet OVT cap field, select the appropriate earning group.
5. . Select the appropriate Premium Eligibility Policy, if applicable.
6. . Select the appropriate Premium Interaction Policy, if applicable.
7. . Enter the appropriate Minimum T/C Interval, if applicable.
For example, if the minimum time card interval is 15, then time entry hours are automatically
rounded up/down to 15 minute increments. The interval begins at the beginning of an hour,
so this example would mean that input and/or generated hours would be 24:00, 24:15, 24:30,
24:45, 01:00, 01:15, etc.
8. . Enter the amount in the Round Up At field, if applicable.
If the minimum timecard interval is 15 and the Round Up At is 8, then time clocked at 24:07
would be rounded down to 24:00, but a time clocked at 24:08 would be rounded up to
24:15.
9. . Enter rules in the Daily/Weekly Base and Overtime Rules region, according to the policy type
you selected in step .
• Daily, you must enter DAY and HOL
• Weekly, you must enter WKL and HOL
• Special, you must enter DAY, WKL, and HOL.
Ensure you enter rules in this sequence: Daily, Weekly, and Special, if all are applicable.
YOU SHOULD USE POINTS TO SET THE ORDER OF PRECEDENTS IF YOU ARE DEFINING SPECIAL
OVERTIME.
OTL Super Administrator > OTL Time Accounting > Policies > Earning
Enter Assignment Time Information
Select Employee from the Assignment Number LOV.
Select the appropriate Rotation Plan, Earning Policy, Shift Differential Policy and Hour Deduction
Policy.
Global OTL > OTL Time Accounting > Policies > Assignment Time Information
Define Preferences (Detail)
By default, all employees receive a set of default preferences. You can create new Preference
hierarchies and assign them to individuals or groups of individuals.
Initial set up requires you to attach the New Alternate Name definition for employees through
Preferences so that an employee can view that list of elements defined in the Alternate Name set.
OTL Eligibility rules can use Employee Assignment criteria enabling eligibility. For example only
certain Grades, Position, Organisation can view a specific alternate name which will decide what
employees can see.
This is a view only tab and no changes can be made at this level. If you wish to make changes to an
individual's preferences, you must use the Eligibility Criteria tab.
Profile Options (To be configured first)
These have been initially configured. These are not to be changed without expert guidance and
research. Doing so may cause EBS to malfunction and any information culled after that may not be
strictly accurate.
This profile option controls the number of past days the retrieval process checks for changes.
If you run the retrieval process on a monthly basis for the same organization (and
workers enter time on a weekly basis), then the OTL application transfers 400 timecards
(100 people with 4 timecards each) in each batch. In this example, the application still
transfers 100 workers' timecards, however the number of timecards increases and each
batch requires 4 times the amount of memory space.