|Oracle Time and Labor Implementation and User Guide|
Part Number E13521-07
A system profile is a set of changeable options that determine how (or whether) a particular function runs.
|Profile||Configurable Level||Values (Default value in bold)||Value Required?|
|HR: OTL Absence Integration Setup||Site||Yes|
|HXT: Approver Required||Site, Application, Responsibility, User||Yes, No||No|
|HXT: All / Selected Earning Categories||Site, Responsibility, User||All Earning Categories Selected Earning Categories||No|
|HXT: Batch Size||Site, Application, Responsibility, User||25, positive integers||Yes|
|HXT: Compare Special Rules Evaluation||Site||No|
|HXT: Holiday Hours from Holiday Calendar||Site, Application, Responsibility, User||Yes, No||Yes|
|HXT: Hours per Year||Site, Application, Responsibility, User||2050, Positive integers||Yes|
|HXT: Merge Batch Timecards||Site, Application, Responsibility, User||Yes, No||Yes|
|HXT: Overtime Functionality on Holidays||Site|
|HXT: Rollup Batch Hours||Site, Application, Responsibility, User||Yes, No||Yes|
|HXT: Include Premium Hours to PA||Site, Application, Responsibility||Yes, No||Yes|
|OTL: Allow Change Group Timekeeper||Responsibility, User||Yes, No||No|
|OTL: Allow Creation Public Templates||Responsibility, User||Yes, No||No|
|OTL: Allow TK Locking of Queried Records||Site, Application, Responsibility, User||Yes (at the site level), No
Note: Ensure that you set this profile option to Yes if you use Absence Integration
|Yes (if using TK)|
|OTL: Archive Restore Chunk Size||Responsibility||100||Yes|
|OTL: Defer Approval Process on Timecard Submission||Site, Responsibility, User||Yes, No||Yes|
|OTL: File Separators for the Import Export Functionality||Application, Responsibility, User||, (comma), ; (semicolon)||Yes|
|OTL: Max Errors||Application, Responsibility, User||Positive integers||No|
|OTL: Max Errors in Validate Data Set||Responsibility||500||Yes|
|OTL: Minimum Age of Data Set for Archiving||Responsibility||6||Yes|
|OTL: Number of Past Days for Which Retrieval Considers Changes (days)||Application, Responsibility||365, Positive integers||Yes|
|OTL: RDB - Default Application||Site, Application, Responsibility, User||Payroll|
|OTL: RDB - Run Post Retrieval Snapshot Automatically||Site||Yes|
|OTL: Transfer Batch Size||Site, Application, Responsibility, User||Positive integers||Yes|
|OTL: Transfer to OTLR and/or BEE||Site||BEE only, Both OTLR and BEE, OTLR only||Yes|
|OTL: Use Upgraded Retrieval Process||Site||Yes|
|OTL: Default Approval Action for Mass Timecard Approver||Responsibility, User||Approve, Reject, Skip||Yes|
This profile option determines whether you integrate absences with OTL.
This profile option determines whether an approver is required to approve the timecard. If this profile is set to Yes, then the timecard requires an approver, otherwise no approver is required
This profile option determines the earnings category to consider for OTLR Time Accounting.
This profile option determines the number of timecards you transfer to BEE in a single batch.
This profile option determines whether you use the combination functionality. If you set this profile to Yes, then the application includes combination points while determining the greatest of the Daily, Weekly and combination points. If all three are of the same points then Combination takes the precedence. The order of precedence in case of EQUAL points is Combination, Weekly, and Daily.
This profile option determines whether the application autogenerates holidays from the work plan or from the holiday calendar.
If you use Oracle Projects, then you can use this profile option to transfer data.
If you set this profile option to Yes, then the application merges batches during the validate for BEE processes (standard and retro). For example, the application copies all timecards in a batch range that pass validation into one batch, copies all timecards that fail validation with a warning to a second batch, and copies all timecards that fail validation with an error into a third batch.
If you enables this profile option, the application calculates and adds the extra hours worked on a holiday towards overtime and not just as hours worked for the holiday. This profile option has the following values:
No Explosion except Holiday Rule - if you select this value, the application would consider Holiday Rule only as defined in the Earning policy for calculating overtime on a holiday.
Normal Explosion and Holiday Rule - if you select this value, then the application triggers a Daily/Weekly/Special explosion to happen on holiday days as per the earning policy. Additionally the holiday rule trigger and explode as defined in your earning policy.
Daily/Weekly/Special Overtime only and Holiday Rule - if you select this value, then the application triggers a normal explosion per Daily/Weekly/Special overtime rules, and only overtime elements are paid. Regular hours will not appear and will not be paid in the timecard. Holiday rules are applicable for the total number of hours.
Daily/Weekly/Special Overtime and Holiday Rule for Regular - if you select this value, then the application triggers a normal explosion per Daily/Weekly/Special overtime rules, and only overtime elements are paid. Holiday rule are applicable only for Regular hours.
For more information, see: HXT: Overtime Functionality On Holidays - Whitepaper, My Oracle Support Note: 1511131.1.
If you set this profile option to Yes, then the application rolls up the elements when transferring them to BEE. If you set this profile option to No, then the application does not roll up the elements when transferring them to BEE.
Note: If you set this profile option to Yes, then the application consolidates all hours, including absence entries such as PTO elements, and uses the payroll period end date.
This profile option determines whether OTL transfers premium hours to Oracle Projects when you run the Transfer to PA process.
Set this profile option to Yes to allow the timekeeper the same privileges as the super timekeeper. With this profile option set to yes, the timekeeper can view all groups and workers in their business group, and can define groups for other timekeepers (if the timekeeper is in the same business group as the people for whom they enter time). Set this profile option to No to allow the timekeeper to define groups and enter timecards for workers for whom they act as timekeeper only.
Set this profile option to Yes to enable the user to create public templates.
If you set this profile option to No, then the application does not lock the timecard unless a change is made to the timecard. If you set this profile option to Yes, then the application locks all the timecards in the timekeeper group.
This profile option controls the amount of data you move to archive tables in the archive process. The amount of data is defined in chunks, and a chunk consists of a number of workers. The default chunk size is 100. The size of the chunk depends on the following factors:
How often you archive timecard data
How often workers access their timecards
If you archive the timecards for March 2004 (with the profile option set to 100), then the application marks each timecard in the date range for archive, and then processes 100 workers' timecards at a time. If your workers enter time on a monthly basis, then the archive process archives 100 timecards.
If your workers change or update their timecards, the application saves the additional data in OTL tables. This additional data increases the size of the timecard, and therefore increases the size of the chunk.
Caution: If you increase the chunk size in the profile option, then you must ensure the server can accommodate the extra data.
This profile option enables you to control the immediate execution of the approval process. If you set this profile option to No, then you no longer need to submit the Workflow Background Process.
This profile option enables you to select a semicolon as a field delimiter instead of a comma.
This profile option controls the number of errors the retrieval process allows. The retrieval process stops when it reaches the maximum number of errors you specify. You can view the errors in the error log file.
This profile option controls the number of errors the Validate Data Set process allows. The process does not stop if it encounters a warning. The process stops running only if it reaches the maximum number of errors you define. This option enables you to fix errors in small groups.
This profile option defines the minimum length of time before a timecard period is available for archiving. For example, to limit the timecards available for archiving to those that are at least one year old, set the minimum age to 12 months. The default value is 6 months.
This profile option controls the number of past days the retrieval process checks for changes.
Use this profile to select a default application if you want to use the dashboard for both payroll and projects recipient applications
This profile affects PRC: Transaction Import process only. Because the recipient application is projects, OTL requires gathering additional information after running the retrieval process. Use the concurrent program OTL: RDB - Post Retrieval Snapshot program for this purpose. If you set this profile to Yes, the snapshot program initiates automatically when running the PRC: Transaction Import process, to run in background and work on the snapshot collection. This has no adverse impact on performance. If you set this profile to No, then you must run the program at a later point of time for each request of the PRC: Transaction Import process to view correct data in the Post Retrieval tab.
This profile option controls the batch size for the number of timecards the OTL application transfers into memory, at one time, during the retrieval process. The size of the batch also depends on the following factors:
How often you run the transfer process.
How often workers enter time (weekly, daily, or monthly).
For example, if you run the retrieval process on a weekly basis (for weekly timecards) for an organization with 1000 workers, with the profile option set to 100, then the OTL application transfers 100 timecards (100 people with 1 timecard each) in each batch. As the application transfers 100 workers' timecards in each batch, a total of 10 batches are transferred.
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.
Caution: Oracle recommends that you set this profile option to no higher than 100. If you set this profile to a higher number, then you may experience errors due to lack of memory space in the OTL application.
This profile option enables you to specify whether you expect to process time entries to BEE or to evaluate and process time using OTLR. If you set the Evaluate Rules preference to Yes for all workers, then set this profile option to OTLR Only. If you set the Evaluate Rules preference to No for all workers, then set this profile option to BEE Only. Otherwise, leave the profile with its default value of both OTLR and BEE.
Use this profile to make OTL retrieval processes to Projects and Payroll use the changed data model. This profile is required to ensure the timecard retrieval dashboard displays correct data.
You must choose the appropriate values from Approve, Reject and Skip in the Approvals page to approve pending timecards.
Copyright © 2003, 2013, Oracle and/or its affiliates. All rights reserved.