You can assign timecard layouts to your workers and configure the look and feel of each timecard layout for each individual worker or a group of workers.
Workers use a self-service web page in the format of a timecard. You can create different timecard layouts for each group of workers so that they only see the fields that are relevant to them. You can rearrange the fields on the layouts, edit the list of values, and rewrite the instruction text to make is easy for your workers to fill out their timecard quickly and accurately.
Workers on the move can enter their time and labor data in a spreadsheet and upload it later to the application.
Workers can also use other entry devices such as time clocks, telephones, or legacy entry systems. You can easily enter this data into Oracle Time & Labor using the robust timecard API.
When you save a template as a spreadsheet, you can enter your time for the week into it. You can add or update existing line items. You can also view the valid list of projects and the associated task by scrolling down within the spreadsheet. This allows you to select and enter the correct project and task information on the exported timecard.
You assign timecard layouts to your workers using the Timecard Layout preference. The layout determines the fields that they can enter, how the fields are arranged on the page, and the instruction text that they see. You can define as many layout styles as you require. For each layout style, you need several specific layouts:
Timecard Layout, for time entry
Review and Confirmation Layout, for reviewing entries before submission and confirming the entries after submission.
For employees with the OTL Rules Evaluation preference set to Yes, the Review and Confirmation layout can display the details of overtime, double time, and so on, calculated by applying the OTLR rules from time management structures and policies.
Confirmation Layout, which displays entries after submission
As a supervisor, you can directly access the time sheet dashboard for post timecard submission details. You can check the online status of submitted timecards; track the percentage or number of employees who have and have not submitted timecards. You can view timecard details in a report format, and a chart displaying the distribution of data from the dashboard. You can also drill down to an employee's timecard.
Detail Layout (optional), which you can provide for Projects users or any other layout that requires a Detail page (accessed from the Detail button on the Timecard page). On the predefined Projects layout, the Detail page is for entering comments and other information against each row displayed on the timecard.
Export Layout (optional), for exporting data to a spreadsheet. If you do not specify an Export layout, the Timecard layout is used for export. There is a predefined Export layout for Projects, which displays a Comment column for recording comments against each day of the week.
Several layout styles are predefined. You can use these as supplied, or copy and modify them. For example, you might modify a layout to remove a field that you don't use.
For instructions on modifying layouts, refer to the technical briefOracle Time & Labor Timecard Configuration, which is available on My Oracle Support Note 304340.1.
Important: Do not use Web Application Dictionary or the OA Configuration Framework to configure the layouts.
The predefined layout styles are:
Projects layout
Using this layout, workers can enter their time against a selected project, task, and type. Workers can click on a Details button to enter comments against each project, task, and type combination.
Payroll Layout
Using this layout workers can enter a start and stop time, or a number of hours, for each day of the week for the selected hours type. This layout is suitable for workers who are submitting their time to Oracle HR or Payroll.
Projects with Payroll Layout
This layout is similar to the Projects layout except that the list of values for the Type field comes from the alternate name you have assigned to the worker (using preferences) for the Expenditure Elements alternate name type. So when a worker selects a type for a time entry, an element name is also recorded in the time store.
Work based Projects and Payroll Layout
Using this layout, workers can enter their time against a selected project, task, task and cost code type, job, location, and work type. Workers can click on a Details button to enter comments against each project, task, and type combination.
See: Collecting and Processing Project-Related Timecards, Oracle Projects User Guide
Exception Layout
This layout displays one row where the worker can select an hours type and cost center, then enter the number of hours for each day of the week. Use this layout for workers who only need to submit timecards for exception reporting (such as time absent for sickness or vacation).
If you want workers to be able to review OTLR time details--such as hours of overtime, derived from their earnings policy--on their Self-Service timecard, you must ensure you complete the following setup:
Set the value of the OTL Rules Evaluation preference to Yes for these workers
Assign them to time management structures and policies, including a rotation plan and earnings policy
Set Autogen to Yes on the Assignment Time Information window
In the Timecard Layout preference, assign a Review layout--and optionally a Confirmation layout--that includes an OTLR Details section. For example, you could use the predefined layouts Exception OTLR Details Review Layout or Payroll OTLR Details Review Layout. There is no predefined layout for confirmation. If you define your own layout, follow the instructions in the technical briefOracle Time & Labor Timecard Configuration, which is available on My Oracle Support Note 304340.1.
Note: If you set the OTL Rules Evaluation preference to Yes, then you must use one of the following layouts to ensure the details display: Projects and Payroll Review Layout; Exception OTLR Details Review Layout; or Payroll OTLS Details Review Layout.
There are two situations where the OTLR Details displayed in self-service may be misleading. Consider whether these circumstances apply to your implementation. If they do, you might prefer not to show OTLR Details in self-service, which you can do by using a review layout that does not include OTLR Details. The circumstances are:
If the worker's OTL self-service timecard period (set by a preference) is not the same as their payroll period, and their assigned earnings policy is weekly or special, the OTLR Details displayed in self-service may not show what the user expects. The rules are applied on a payroll period basis.
For example, suppose the timecard period is weekly, starts Sunday, and the payroll period is weekly, starts Thursday. The earnings policy includes the special policy that all hours worked on the seventh consecutive work day are paid as overtime. If employees enter seven consecutive work days (Sunday through Monday), they may expect to see the seventh day showing as overtime on the Details section of the OTLR Review page. However, the application counts seven days from the beginning of the payroll period (Thursday) and therefore does not display Monday as overtime.
If time entries have been transferred to the professional forms Timecard window using the Transfer Time from OTL to BEE process and then the user changes the timecard in self-service, the OTLR Details displayed in self-service will be the old transferred details. They will not reflect the changes the user has made.
You can make a number of changes to the appearance of a timecard using preferences:
Set the Enter Override Approver preference to Yes to display the Override Approver field.
Set the Date Formats preference to determine the format of the date fields for period list, table day header, and detail page header on the timecard.
Use the Number of Empty Rows on the Timecard preference to determine the number of rows displayed by default (the worker can always add more rows as required)
Set the Self Service Template Functionality for a Worker preference to Yes to display a Template field on the timecard, where workers can select an existing template to use.
Set Save as Template on Timecard to Yes to display the Save As A Template button and the Template Name field.
Note: You must also set Self Service Template Functionality for a Worker to Yes.
Set the Timecard Period preference to define which day of the week appears first on the timecard (for example, Sunday or Monday).
You can configure the lists of values that display on fields of the timecard by defining alternate names. Use this feature to provide more user-friendly names, or to restrict the values in a list, or to derive the value of another field from the value a user selects on a field displayed on the timecard.
See: Alternate Names
If you use any of the predefined layouts (except the Projects Layout), you must define alternate names and select values for the Timecard Alternate Names preference.
To configure lists of values for project, task, type, and overriding approver on the Projects layout.
See: Oracle Projects Integration Notes
On the timecard summary and approval summary pages, you can displays totals for categories of time (such as all time for a particular project, or all regular time). To help you do this, there are several predefined time categories (Total1 through Total10). These categories are supplied empty so that you can select the mapping components and subcategories you want to sum to provide totals.
On the predefined timecard layouts, Total1 and Total2 are displayed on the timecard summary page, and Total2 and Total3 are displayed on the approval summary page. The field labels used on these layouts are shown in the table below. To change the field labels to describe the totals you want to display, update the attributes listed in this table.
For example, if you want Total1 to display the total hours worked on Project X and Project Y, you would:
Update the Total1 time category to include the mapping component PA Project Id set to the appropriate values for these projects.
Update the HXC_HOURSTYPE_REGULAR_LABEL attribute in the HXC_CUI_TIMECARD region to be Projects X and Y instead of Regular.
| Field | Time Category | Seeded Prompt | AK Region | Attribute Code | Attribute Name |
|---|---|---|---|---|---|
| TS - First Column | Total1 | Regular | HXC_CUI_TIMECARD | HXC_HOURS_TYPE_REGULAR_LABEL | Timecard Hours Type Regular Label |
| TS - Second Column | Total2 | Premium | HXC_CUI_TIMECARD | OVERTIME_HOURS_TYPE_LABEL | Timecard Hours Type Overtime Label |
| Field | Time Category | Seeded Prompt | AK Region | Attribute Code | Attribute Name |
|---|---|---|---|---|---|
| AS - First Column | [none] | Total Hours | -- | -- | -- |
| AS - Second Column | Total2 | Premium | HXCSEARCH- RESULTSLIST | HXCPREMIUMHRS | Hxc Premium Hours |
| AS - Third Column | Total3 | Non worked hours | HXCSEARCH- RESULTSLIST | HXCNONWRKHRS | Hxc Non Worked Hours |
The Recent Timecards page displays the Absence Duration for both hour based absences and day based absences in the Hours and Days columns to enable you to easily segregate and identify information.
Note: The column Absence days and hours are visible in the recent timecards page when HR: OTL Absence Integration profile and the preference Absence Integration enabled is set to Yes.
In the Timecard Create, Review, Confirmation, Notification, and other pages, the Total in the Timecard matrix displays the total number of hours in the timecard by row. The columns do not differentiate between Hours and Day based absence types with Absence Integration.
Note: To use this feature, you need to set the preference Exclude Absences from Timecard Totals in the Time Store Absence Integration Setup for Worker to Yes. You can use this preference only for Self-Service Timecards.
A template stores timecard data for reuse. For example, you might define a holiday template for a weekly timecard that records zero hours worked and 40 hours taken as vacation. Each template is associated with a timecard layout.
By using a template, users avoid repetitive and error-prone data entry. They can focus on exception entry of any time that is different from their expected working pattern, by simply correcting any entries that need to change, and adding new entries.
Using preferences, you can control users' access to templates and their ability to create templates. For example, you can remove all access to templates by setting the Self Service Template Functionality for a Worker preference to No.
Oracle Time & Labor offers three types of template:
Dynamic
Private
Public
Dynamic templates are predefined and delivered with the product. The data they contain is dynamically drawn from another source when the user selects the template. However, to the user, they appear the same as public templates. Like other templates, a dynamic template can be selected by the user or can appear automatically if it is the user's default template (specified using preferences).
The dynamic templates are:
Project Assignments - This template generates time and labor entries from the project, type, and hours information held in Oracle Project Resource Management for the worker's assignments.
You can only use this template if you have licensed and implemented Oracle Project Resource Management.
See: Introduction to Oracle Project Resource Management, Oracle Project Resource Management Implementation and Administration Guide
Work Schedule - This template generates time and labor entries from the worker's assignment to a rotation plan, holiday calendar, and earning policy.
To enable workers to use this template, you must:
Set the Autogen Hours field to Yes in the Assignment Time Information window for their assignments.
Set the OTL Rules Evaluation preference to Yes, select either HR or Payroll in the Approval Rules for the Rules Evaluation segment of this preference.
Last Period Timecard - This template uses the previous time entry data. You typically use this template when an employee is working on the same projects week after week, eliminating the need for repetitive entry of project and task numbers.
You can use preferences to specify which template appears as a default using the Self Service Default Template Assigned by Sys Admin preference. Users can select a new default using the Self Service Default Template Selected by User preference.
You can grant some or all of your users the ability to create their own templates, using preferences. There are two ways to create a template:
Once you enter and submit a timecard, you can save that timecard as a template. To do this, choose the option to Create a Template from Timecard. This opens the template form where you name the template and choose the desired timecard period from previously submitted timecards.
Create a new template from scratch. To do this, you choose Create New Template. This will open the template form where you name the template and enter the details for each of the seven days of the week.
You enable a user to create templates on the Template page by setting the preference Self Service Create Template Functionality to Yes, and you can display the Save As A Template button on a user's timecard by setting the preference Self Service Save As Template Functionality on Timecard to Yes. You can enable a user to append one template to another by setting the Self Service Functionality to Append Template on the Timecard preference to Yes. A worker with this functionality can use data from two templates on one timecard: the rows from the second template are appended to the rows from the first. For example, if workers end a project mid-week, they can use their project template for the first part of the week and their unassigned to project template for the rest of the week.
Note: The preferences described above only works if you also set the Self Service Template Functionality for a Worker preference to Yes.
Public templates are templates you create for self-service users to enable them to enter time and populate their timecards quickly. You can create groups of public templates and assign them to a specific worker, a group of workers, or all workers in a single business group.
Note: You can create, update, and assign public templates in the current business group only.
You assign public template groups to one or more individuals using the Self Service Timecard Template Group preference. OTL provides a default group of dynamic templates that you can use as public templates. Alternatively, you can select your own defaults in the Self Service Timecard Template Group preference.
You can create a group of public templates and assign them to workers using preferences. This feature provides flexibility for the worker, and enables them to save a public template as a private template. The difference between a private template and a public template is that the user creates a private template, whereas OTL Administrator creates the public templates and assigns them to users.
You can also create a template group with no templates and assign it to a worker using preferences. This empty template group removes the dynamic templates from the worker's choice list.
Using alternate names you can configure lists of values on a timecard layout. You then associate alternate names with a person or a group of people using preferences.
There are two ways to configure lists of values on a timecard:
You can rename the values displayed in a list of values. For example, you may wish to change the element name Regular_Earnings_PKW to display on the timecard as Regular Pay.
You can limit the display of values in a list of values for a specific field on a specific timecard. This makes it easier for users to complete their timecards accurately since they only see the locations, projects, tasks, elements, and expenditure types that are relevant to their work. For example, you might wish to display all elements to timecard users at location A but restrict the element list of values to regular pay and vacation at location B.
If the only configuration you require is to replace element names with element reporting names, you do not need to define alternate names manually. Instead, you can run the Generate Flexfield and Mapping Information process for an element set to create two alternate name definitions-one where all the alternate names are enabled and the other with the names disabled.
To configure lists of values for project, task, type, and overriding approver on the Projects layout.
See: Oracle Projects Integration Notes
You can also use alternate names to derive the value of a field from the value a user selects in another field. For example, you can derive the expenditure type from the element (Hours Type) that the user selects on the Timecard. In this way, expenditure type is held in the time store and can be passed to other applications, but it is not displayed on the Timecard.
Another example would be to derive the appropriate costing account from the Hours Type. You could create alternate names to associate the element Regular to the Cost Allocation key flexfield value GL Acc1 and Vacation to GL Acc2. Then time entries are automatically sent to the appropriate cost center without workers entering this information manually.
For each field on a timecard, you can select and rename the valid values using one of the following predefined context values:
ELEMENTS_EXPENDITURE_SLF
EXPENDITURE_ELEMENTS
EXPENDITURE_TYPES
LOCATIONS
PAYROLL_ELEMENTS
PROJECTS
TASKS
You can create additional context values by configuring the OTL Alternate Names descriptive flexfield. The reason you might want to do this is to configure lists of values for any new fields you have created for the timecard.
Use the Self-Service Timecard Alternate Name Set Defined for a User preference to assign up to ten alternate names to a worker or group of workers. If you update the preference in the middle of a timecard period, or if workers' assignments change mid-period so they become eligible for a different set of alternate names, then they see both sets of alternate names (old and new) for that timecard period only.
If you use any of the predefined timecard layouts (except the Projects layout), then you must define alternate names and select them in the Timecard Alternate Names preference for the workers who use these layouts.
You can define an alternate name for a specific value in the list of values for any field on the timecard. You can use this feature to restrict a list of values to the entries that are applicable to a user or group of users and to name the entries in the way most meaningful to this user group. You can also use this feature to define combinations of two or more fields where the user selects a value in one field and the application automatically derives the values for the other fields. When defining Alternate Names, use caution to ensure you do not include elements within the alternate names that may not be linked to the person or group of people you are assigning the set. For example, an worker may have the element vacation pay in his alternate name set, but if that element is only linked to a payroll other than the one the worker is a member of, the worker will not see vacation pay in the list of values on the timecard.
If you do not define any alternate names for a field's list of values, the full list of elements from the element set used in the Generate FlexField Mapping process displays by default. The Alternate Name set created is named {Element Set Name} - Enabled.
If you want to restrict the list, you must create an alternate name for every value you want to display in the list. The alternate name can be the same as the existing name, or a new name that is more meaningful to the users of the timecard you are configuring.
Use the Alternate Names window.
To define alternate names
Enter a unique Alternate Name Definition.
Enter a description of the name definition.
Select the Alternate Name Type to determine which list of values to display. For example, select Payroll Elements to configure the list of elements displayed, or select Expenditure Elements to also derive expenditure type from the element field.
Note: The Alternate Name Types are the context field values for the OTL Alternate Names descriptive flexfield. Some contexts are predefined. You can create a new context for this flexfield if you add a new field to the timecard and you want to configure the list of values for this field. You can also create a new context to create new field combinations where one or more fields are derived from the value a user selects in another field.
Save your work before continuing to the Alternate Name Values region.
Enter the Alternate Name. This is the name you wish to see in the list of values for the specified field and timecard. For example, if you are configuring the element context, this is the value to display in the Hours Type field.
Enter the From and To dates to define the period of validity of the Alternate Name.
Move to the Values field. The OTL Alternate Names window opens and displays the segments for the alternate name type.
Click on the list of values icon to see the default list of values for a segment. For example, if you are configuring payroll elements, you can see the elements in your element set.
Select the value you want to store in the time store using your new alternate name and choose OK.
If the alternate name type you selected supports deriving the value of other fields from the field you are configuring, select the values to be derived. For example, if you selected Expenditure Elements as the alternate name type, you could select the element Time Entry Wages and associate it with the expenditure type Regular Billable. This means that when a timecard user selects Time Entry Wages, Oracle Time & Labor automatically stores Regular Billable as the expenditure type.
Select the Enabled check box to display the alternate name in the List of Values.
If you do not wish the alternate name to be seen, do not select the Enabled check box. For example, if you wish to create an alternate name to be used at a later date, do not select the Enabled check box until you are ready to use this alternate name.
Repeat steps 5-11 until all alternate names are defined for this list of values.
Save your work.
Remember to select your new alternate name definition in the preference Timecard Alternate Names to link it with the workers who should see these names.
Using the predefined Projects layout style, you can display a Details button on the timecard layout. This button opens a Details page for entering comments and other information against each row displayed on the timecard.
The fields displayed on the Details page are determined by the segments you have created in the Projects Expenditure Items descriptive flexfield.
To display a Details page for projects
In the Descriptive Flexfield Segments window, query the Expenditure Items flexfield. Set up this flexfield, making sure you enter either SYSTEM_LINKAGE_FUNCTION (used for Expenditure Type Class) or EXPENDITURE_TYPE in the Reference Field.
In the Context Field Values area, enter a line for each Expenditure Type Class or Expenditure Type for which you want to display a context-sensitive field on the Details page.
In the Segments Summary window, define the segments for the global data element context (these fields appear for every expenditure type) and each context field value.
Run the Generate Flexfield and Mapping Information process, making sure you select Yes in the Include Expenditure Items Flexfield field.
See: Running the Generate Flexfield and Mapping Information Process.
Review the contexts and segments that the process generated in the OTL Information Types flexfield. (Notice that the system inserts a prefix before the names that you defined in the Expenditure Items flexfield.) Make sure that the contexts you want to use in Oracle Time & Labor are enabled, and that there is at least one enabled segment for each context.
Note: Consider making all the segments to appear on the Details page optional, even if they are required in the Expenditure Items flexfield. If the segments are required in the OTL Information Types flexfield, you must enter values for all the instances of the required field on the Details page (each day of the week). You cannot close the page until all the values are entered. If you make these segments optional, there is no validation until the user completes their entry and submits the timecard. Then the entries on the Details page are validated against the Expenditure Items flexfield.
Recompile the OTL Information Types flexfield.
Select a Details page layout in the Details Page segment of the Timecard Layout preference for your Projects workers.
The calendar view of timecards enables you to see all the time entries recorded in the time store on the respective dates in terms of start time and stop time, or hours recorded for each entry. Existing timecards time entries are indicated by a band on the days covered by that timecard period along with the total hours recorded in that timecard. This helps in easy identification of timecards that have been entered. The calendar view also helps you to see what timecard periods or days do not have time entered and also the gaps in time entries on any specific day. The timecard and time entries are represented on the calendar using different color coding. You can change this color coding using the new profile option OTL: Calendar View Colors.
This calendar view also provides weekly view, daily view or list view of the time entries recorded.
The Timecard Summary region displays the information of latest selected timecard on the calendar. This information includes the timecard period, recorded hours in the timecard, timecard submitted date, timecard approval status, timecard transfer status, and so on.
The calendar's week start day is based on the user's timecard recurring period preference.
Click any empty space on the calendar to navigate to the Create Timecard page.
If an Authorized Delegate has the OTL Self-Service Resource Time Menu attached, then the Authorized Delegate can see only their own timecards on the calendar – they cannot see the timecards of others for whom they delegate.
For further information, see: Calendar View for Timecards MOS Note ID 2157555.1
Entry Level Processing allows you to capture data for multiple applications in one timecard. You use rules to specify which data is optional and which data is required by each recipient application. For instance Oracle Projects always requires that a timecard includes project, task, and type information. Without enabling Entry Level Processing, even if workers did not work on a project for 4 hours that day, they must enter a project, task, and type information because Oracle Projects validation requires it for project and thus for the timecard. Using Entry Level Processing enabled, you do not have to do that.
With Entry Level Processing enabled, you can specify that if a project is entered, then task and type are also mandatory. But, if only an hours type is entered, project, task, and type are not needed.
Entry level processing allows you to define time categories and time entry rules, to determine which recipient application validates time and labor data entered on the timecard. You may also use the predefined time entry rules and time categories as supplied by Oracle Time & Labor.
You can define time categories to identify which components on a timecard belong to which recipient application. Predefined categories include: Projects Processing Fields, Payroll Processing Fields, and HR Processing Fields. Time categories work in conjunction with time entry rules to control which time and labor data on the timecard is validated by which recipient application.
For example, the projects processing fields time category includes PA Task ID, PA Project, and PA expenditure, and are all linked by the “OR" operator. If a worker enters hours and task on the timecard, the projects validation is activated, and a message is returned to the worker indicating a project and expenditure type are also required.
Note: If you define a time category that does not include any one of the fields/entry required by a recipient application, there is a chance the time and labor data will not be retrieved by the appropriate application.
Time entry rules use formulas to determine whether a rule has been broken by the current timecard. The predefined formula, Entry Level Processing, is used to control what time entry on a timecard belongs to which recipient application. The formula inputs on the entry level processing formula determine what time to associate with a recipient application. The two formula inputs are Time Recipient, and Time Category.
Two predefined field combination formulas allow workers to enter mandatory fields, or mutually exclusive fields further validating the time entry on the timecard. The predefined combination formulas are, Mandatory Timecard Fields (Seeded Formula), and Invalid Timecard Field Combination (Seeded Formula).
To ensure proper validation, the applications defined within the Time Entry Rules must also match the applications defined within the Application Set. For example, if you define time entry rules for payroll and projects, and group these rules into one Entry Level Processing Rule Group, your Application Set must also include payroll and projects.
Note: The two field combination formulas are for general time entry rule validation and are added to the Time Entry Rule Group and not the Entry Level Processing Rule Groups.
Once you have defined time entry rules, you define an Entry Level Processing Rule Groups and assign a group to a person or group of people via preferences. To associate time and labor data on a timecard with more than one application, you group your time entry rules to one Entry Level Processing Rule Groups.
You can define time categories to identify what components on a timecard belong to which recipient application. For example, the projects processing fields time category includes PA Task ID, PA Project, and PA expenditure, and are all linked by the “OR" operator. The time category rule is satisfied when a line on the timecard includes a project, or task, or an expenditure type.
The following categories are predefined for entry level processing: Projects Processing Fields, Payroll Processing Fields, and HR Processing Fields
Use the Time Categories window.
To define time categories
Enter a unique name for the category.
Select the operator for this category.
Select either an existing time category or a mapping component to define the category.
Note: You cannot use components that use a table-validated value set containing the $PROFILES$ or $FLEX$ nomenclature. The application will issue a message if you select components that cannot be used.
If you selected a mapping component, select the value of the component that belongs to this category.
Continue selecting categories or mapping components (or both) to complete your definition of the category.
Save your work.
Entry level processing time entry rules are defined to determine the recipient application and the time category for validation on the timecard. You can choose the point of validation to be at the time of submission, resubmission, save, or submission/resubmission.
Use the Time Entry Rules window.
To define time entry rules
Name the rule.
Enter a description for the rule.
Select the Usage:
Submission is when the completed timecard is submitted for approval.
Resubmission is when the timecard has been approved and the employees changes the time or labor data.
Submission/Resubmission determines validation is required at the initial submission and when the employee changes the time and labor data after approval.
Save determines validation is required at the time the timecard is saved.
Select a formula and enter the formula inputs for the recipient application and the time category.
Enter the desired From date to indicate when this rule becomes effective. You are not required to enter a To date until the rule is no longer needed.
If you want to restrict the rule to your current business group, uncheck the Global check box.
Save your work.
Once you have defined time entry rules for entry level processing, you can group the rules together and assign a group to a person or a group of people via preferences. Use the Time Entry PTE Rule Groups window.
To define entry level time entry rule groups
Enter the name of the Rule Group.
Select the name of the first time entry rule.
The remaining data fields will populate, including the outcome of Process Time Entry.
Repeat step 2 to continue entering time entry rules for this grouping.
Save your work.