The configuration requires defining two separate repeating periods: one with a "Time card" usage for the bi-weekly submission cycle and another with an "Overtime" usage for the weekly calculation. These distinct periods are then associated with a group of workers through the Worker Time Processing Profile. This profile is the central component that links employees to their specific time card submission periods, overtime calculation periods, and the corresponding time calculation rule sets, ensuring that time is processed and overtime is calculated according to the correct frequencies.

A. Layout sets define the appearance and fields on a time card (the user interface), not the processing periods for time submission or overtime calculation.

B. Oracle Time and Labor is designed to handle this common business scenario, allowing the time card submission period to be different from the overtime calculation period.

D. The worker time entry profile governs the time entry method and layout (e.g., which time card layout to use), not the backend processing rules like calculation periods.

1. Oracle Fusion Cloud HCM

Implementing Time and Labor (Release 22D)

Document ID F55031-02

Chapter 6: Define Time and Labor Setup Profiles

Section: Worker Time Processing Profiles.

Page 6-10: "The worker time processing profile links people to the correct time card period

overtime period

time calculation rules

and approval rules." This statement directly confirms that both the time card period and the overtime period are components of the Worker Time Processing Profile.

2. Oracle Fusion Cloud HCM

Implementing Time and Labor (Release 22D)

Document ID F55031-02

Chapter 6: Define Time and Labor Setup Profiles

Section: How Time Entry and Time Processing Profiles Work Together.

Page 6-3: This section clarifies the distinction: "The time entry profile...specifies how they [workers] enter

review

and submit their time." and "The time processing profile...links people to the correct time card period

overtime period

time calculation rules...". This supports that calculation periods belong to the processing profile (C)

not the entry profile (D).

3. Oracle Fusion Cloud HCM

Using Time and Labor (Release 22D)

Document ID F55033-02

Chapter 3: Time Cards

Section: Repeating Time Periods.

Page 3-2: "You create repeating periods with a specific usage. For example

you create a weekly repeating period with the Overtime usage to calculate overtime on a weekly basis. You create a biweekly repeating period with the Time card usage for people to complete and submit their time cards every 2 weeks." This confirms the practice of creating separate repeating periods for different usages.

To configure a time submission rule set for time devices, you use the "Manage Time Submission Rule Sets" task in the Setup and Maintenance work area. This task allows you to create a new rule set and then add existing, individually-defined time submission rules to it. This set is then associated with a time device processing profile to validate time events submitted from physical time clocks.

A. A rule set is not automatically created when you save a single rule. You must explicitly create the set and then add rules to it.

B. The time device import process is used for importing transactional time data (punches), not for configuring validation rule sets.

C. You associate a completed rule set, not an individual rule, with a time device processing profile. This association does not create the rule set; the set must be created beforehand.

1. Oracle Fusion Cloud HCM: Implementing Time and Labor (Release 24B)

Chapter: Time Entry Validation

Processing

and Approval Rules

Section: Time Submission Rule Sets

Content: "You create time submission rule sets on the Manage Time Submission Rule Sets page. You add the appropriate time submission rules to the set." This directly supports option D as the correct procedure.

2. Oracle Fusion Cloud HCM: Implementing Time and Labor (Release 24B)

Chapter: Time Collection Device and Web Clock Setup

Section: Overview of Time Device Setup

Content: The setup steps are listed in order: "1. Create time submission rules... 2. Create time submission rule sets... 3. Create time device processing profiles...". This sequential process confirms that rule sets are created in a dedicated step (supporting D) before being associated with a profile (refuting C).

The standard and integrated process within Oracle Cloud HCM for this scenario is retroactive processing. When a worker or manager corrects and resubmits a time card for a period that has already been paid, the system flags these changes. After approval, the "Load Time Card Batches" process transfers these retroactive changes to Oracle Cloud Payroll. The next scheduled payroll run will then automatically process these changes, calculating any resulting back pay or deductions to correct the employee's pay. This method ensures that the source data in Time and Labor is accurate and remains synchronized with the payroll results.

B. This describes a manual intervention. The best practice is to correct the data at its source (the time card in Time and Labor), not directly in Payroll, to ensure data integrity across modules.

C. This is incorrect for the same reason as B; it bypasses the source system for the correction and also circumvents the standard approval process involving the manager.

D. Time card data is transferred to Payroll via a scheduled batch process ("Load Time Card Batches"), not immediately upon approval.

E. This is incorrect because it omits the mandatory approval step required for all time card changes and incorrectly states the transfer to payroll is immediate.

1. Oracle Fusion Cloud HCM: Using Time and Labor (Release 23D)

Document ID F82489-01

Chapter 6: Time Cards

Calendars

and Schedules

Section: "How You Correct and Resubmit Time Cards". The documentation states

"You can edit and resubmit time cards after they're approved

rejected

or returned for correction... If the time card was already transferred to payroll

your changes are sent as retroactive changes." This directly supports the process described in answer A.

2. Oracle Fusion Cloud HCM: Implementing Payroll for the United States (Release 23D)

Document ID F82478-01

Chapter 13: Retroactive Pay

Section: "Retroactive Pay Processing". This chapter details how the payroll process is designed to handle retroactive changes originating from other applications

such as Time and Labor. It explains that the "Recalculate Payroll for Retroactive Changes" process identifies and processes these changes from a previous

paid period in the current payroll run

which is the receiving end of the process initiated in option A.

The Analyze Rule Processing Details task is the specific diagnostic tool used to troubleshoot and review the sequence of rules and rule sets that the time repository process executed for a specific person and time card action. This administrative function is located within the Time Management work area, which is used for operational time-related tasks. The Time and Labor Administrator role is the appropriate security role that includes the necessary privileges to access and use this troubleshooting tool.

A. The Time and Labor Manager role typically lacks the required privileges for this administrative task, and the task is not in the Setup and Maintenance work area.

B. The Manage Time Repository Rule Sets task is for configuring rule sets, not for analyzing their execution on a specific time card.

C. The Analyze Rule Processing Details task is located in the Time Management work area, not the Setup and Maintenance work area.

E. The Time and Labor Manager role is focused on approvals and team management, not the deep technical troubleshooting provided by this task.

F. The Manage Worker Time Processing Profile task is used to assign profiles that contain rule sets, not to analyze the detailed execution of those rules.

1. Oracle Fusion Cloud HCM

Implementing Time and Labor (23D)

Chapter 6: Time Processing and Rule Configurations

Section: How You Analyze Rule Processing Details.

This section explicitly states

"Use the Analyze Rule Processing Details task in the Time Management work area to review the sequence of rules and rule sets that the time repository process ran for a specific person and time card action." This confirms the task and work area.

2. Oracle Fusion Cloud HCM

Security Reference for HCM (23D)

Chapter: Time and Labor Job Roles

Section: Time and Labor Administrator.

This document details the privileges associated with the Time and Labor Administrator role (ORAHWMTIMEANDLABORADMINISTRATORJOB). It includes the function security privilege Analyze Rule Processing Details (HXTANALYZERULEPROCESSINGDETAILSPRIV)

which grants access to the task. The Time and Labor Manager role does not have this privilege by default.

3. Oracle Fusion Cloud HCM

Using Time and Labor (23D)

Chapter 10: Time and Labor Processes

Section: Troubleshoot Time Card Entries and Processing.

This guide describes troubleshooting procedures and directs administrators to the Analyze Rule Processing Details page to "see which rules and rule sets ran

in what order

and whether they passed or failed." It confirms the task's purpose and its location under the Time Management work area.

In Oracle Time and Labor, the time card period and the approval period are intrinsically linked and governed by a single repeating period definition. A worker's time processing profile is configured with one specific "Time Card Period" (e.g., weekly). This period dictates the frequency for which time is entered, submitted, and subsequently approved. The system's architecture does not support configuring a time entry period with a different frequency from its corresponding approval period. Therefore, a weekly time card must follow a weekly approval cycle.

B. The system does not have separate configurations to assign one repeating period for time cards and another for approvals; they are both driven by the single period defined in the worker's profile.

C. There is no standard functionality to define a weekly time card period and then specify that its corresponding approval should only occur on a bi-weekly basis.

D. This option incorrectly suggests using a bi-weekly period for time cards, which contradicts the customer's primary requirement for a weekly time card.

1. Oracle Fusion Cloud HCM: Implementing Time and Labor

Reference: Chapter: Time Entry Setup

Section: Repeating Time Periods.

Details: This section explains the creation of repeating periods. It states

"You create repeating periods

such as weekly or biweekly

to automatically generate time card periods for your various worker populations." This single generated period is then used for the entire time card cycle.

2. Oracle Fusion Cloud HCM: Implementing Time and Labor

Reference: Chapter: Time Entry Setup

Section: Worker Time Processing Profiles.

Details: This documentation details the components of a worker's time processing profile. A key component is the "Time Card Period

" which is selected from the defined repeating periods. There is no separate field or option to define a different "Approval Period

" confirming that both are governed by the same setting.

3. Oracle Help Center

Fusion Cloud HCM Time and Labor

Reference: Document: "Overview of Time Entry Configuration"

Details: The overview describes the key setup objects. The flow shows that a repeating period is defined and then assigned to a worker's profile as the time card period. The approval rules and processes are then triggered by the submission of the time card for that specific period

reinforcing the one-to-one relationship.

Time Entry Rules (TER) are specifically designed to execute validations when a worker saves or submits time entries. To display a validation message from the calendar entry dialog box upon saving, you must configure a TER. The correct process involves creating a Fast Formula that contains the validation logic, often by calling a delivered subroutine or function that can access worker schedule data. This formula is then linked to a message template within a rule. This rule is added to a TER Rule Set, which is then assigned to the relevant workers through their worker time processing profile. This configuration ensures the validation runs at the point of entry and saving.

B. All of the above: This is incorrect because options C, E, and F propose using rule types that are inappropriate for validation during the save action of a time entry.

C. Define a TSR Rule Set...: Time Submission Rules (TSR) run only when the entire time card is submitted for approval, not when an individual entry is saved.

D. Define a TER formula/template using a delivered workforce management calendar validation function...: While also describing a TER, this option is less precise than A. A function's purpose is to perform a validation check, not directly "to display" a message; the rule framework handles the display. Option A more accurately describes the validation logic.

E. Define a TCR formula/template...: Time Calculation Rules (TCR) are executed by the "Calculate Time" process, which is separate from the interactive saving of a time entry.

F. Define a Time Device formula...: Time Device Rules (TDR) are used to validate time data imported from external time collection hardware (e.g., badge readers), not for entries made directly in the application UI.

1. Oracle Fusion Global Human Resources Cloud Implementing Time and Labor (Release 22D)

Chapter 6: Time Rules

Section: Overview of Time Rules.

This section explicitly states

"Time entry rules validate time entries when workers save or submit their time card... You can also use them to validate entries on a time collection device." This confirms that TER is the correct rule type for validation on save. It also defines the other rule types (TSR

TCR

TDR)

confirming why they are incorrect for this scenario.

2. Oracle Fusion Global Human Resources Cloud Implementing Time and Labor (Release 22D)

Chapter 6: Time Rules

Section: Time Entry Rule Components.

This section details the required components: "A time entry rule has these components: a formula to determine if the time entry is valid

a rule template to create the messages... a rule that links the formula and template

and a rule set that includes the rule." This directly supports the configuration steps outlined in the correct answer (A).

3. Oracle Fusion HCM Cloud Fast Formula Reference Guide (Release 13)

Section: Formulas for Time and Labor.

This guide provides details on creating formulas for Time and Labor. It describes the use of Database Items (DBIs) and functions to retrieve information

such as schedule details

within a formula. The concept of calling a pre-built or custom subroutine/function for specific validation logic

as described in option A

is a standard practice illustrated in this documentation. For example

it lists delivered formulas like WFMSCHEDULEVIOLATIONFORMULA which exemplifies this pattern.

When a user submits a time card that includes both regular hours and an absence, Oracle Fusion HCM initiates two distinct approval transactions. The time entries are processed through the Time and Labor approval workflow, governed by the TimecardApproval BPM task. The absence entry is processed through the Absence Management approval workflow, governed by the AbsencesApprovalsTask.

To meet the requirement, the TimecardApproval task must be configured to route to the Line Manager for the time-related entries. Concurrently, the AbsencesApprovalsTask must be configured to route to the HR admin for the absence portion of the submission. Therefore, modifications in both BPM tasks are necessary to achieve the specified conditional routing.

A. This is not possible.

This is incorrect. Oracle's BPM Worklist provides extensive capabilities to configure complex, conditional approval rules based on transaction attributes.

B. You should use the BPM Worklist and modify the BPM task: AbsencesApprovalsTask.

This is incomplete. This action only configures the approval for the absence portion and does not address the approval routing for the regular hours on the time card.

C. You should use the BPM Worklist and modify the Payroll Time Card Approval – > BPM task: TimecardApproval.

This is also incomplete. While this configures the approval for the time entries, it neglects the separate, standard approval process for the absence entry, which is handled by a different task.

D. You should use the BPM Worklist and modify the Project Time Card Approval – > BPM task: ProjectTimecardApproval.

This is incorrect. The question specifies a "Payroll Layout time card," for which the appropriate BPM task is TimecardApproval, not the task for project-related time cards.

---

1. My Oracle Support

Doc ID 2101584.1. HCM Approvals: How Time Card and Absence Approvals Work Together. This document explicitly states

"When an employee submits a time card which has absence hours entered on it

it will trigger two approval transactions. One for the Time card and one for the Absence. The approval rules for both these transactions are independent of each other." This confirms that two separate tasks (TimecardApproval and AbsencesApprovalsTask) are invoked and must be configured independently.

2. Oracle Fusion Cloud HCM: Implementing Time and Labor

23D. Chapter: Time Entry Approvals > How You Configure Time Card Approvals. This chapter details the configuration of the TimecardApproval task in the BPM Worklist for time entries submitted on a time card. It outlines how to build rules for routing to approvers like line managers.

3. Oracle Fusion Cloud HCM: Implementing Absence Management

23D. Chapter: Absence Approvals > Overview of Absence Approvals. This chapter describes the setup for absence approvals using the AbsencesApprovalsTask in the BPM Worklist

which is triggered when any absence is recorded

including those entered via a time card.

To configure and display an overtime period that is different from the main time card period, a two-step process is required. First, you must define the period itself by creating a new repeating time period and specifying its Period Type as Overtime. This establishes the start and end dates for the overtime calculation, separate from the regular time card period. Second, to make this period visually distinct on the user interface, you must configure the layout. By enabling the Highlight overtime periods option in the time card matrix properties of the relevant layout set, a visual bar will appear on both the calendar and time card matrix, indicating the defined overtime period.

A. Time categories are used to group time card entries for validation or transfer rules, not to define or display time periods.

B. A formula is a method to determine the start date of a repeating period, but it does not define the period's purpose or UI display.

C. The correct configuration involves setting the "Period Type" to Overtime, not selecting a generic "overtime checkbox in period usage."

1. Oracle Fusion Cloud HCM

Implementing Time and Labor (Release 24B)

Chapter: Time and Labor Setup and Maintenance > Define Time and Labor Setup Profile Options

Lookups

and Repeating Time Periods > Repeating Time Periods.

Section: Period Type

Content: This section details the creation of repeating periods and explicitly lists "Overtime period" as a selectable Period Type. It states

"You create repeating periods to define the periods for time cards

overtime

and projects." This supports option E.

2. Oracle Fusion Cloud HCM

Implementing Time and Labor (Release 24B)

Chapter: Time and Labor Setup and Maintenance > Define Time Entry Layouts > Time Entry Layout Components.

Section: Configure the Time Card Matrix Properties

Content: This section describes the layout configuration options. It includes the "Highlight overtime periods" setting

explaining that when enabled

it "displays a bar for the overtime period on the calendar and time card." This directly supports option D.

Oracle Time and Labor formulas access HCM data through Database Items (DBIs). DBIs are predefined shortcuts that retrieve specific information from application database tables. Each formula type (e.g., Time Entry Rule, Time Calculation Rule) has a set of registered DBIs that it can use. These DBIs are not limited to the time card object; they can fetch a wide range of worker data, such as assignment details, grade, location, and payroll information, directly from the HCM database tables. This allows formulas to perform complex validations and calculations based on the worker's broader HCM profile, not just the data entered on the time card.

B: This is incorrect because formulas can directly access HCM data via DBIs. It is not mandatory to first configure and store all external data on the time card layout.

C: This is incorrect. While formulas can call subroutines for reusable logic, this is not the required mechanism for accessing HCM data. The primary method is using Database Items (DBIs).

D: This is incorrect. There is no such mandatory AP suffix naming convention for formulas to enable access to external HCM data. Formula functionality is determined by its type, not its name.

1. Oracle Cloud HCM: Using Fast Formulas (Release 23D)

Chapter 3: Database Items

Section: Database Items in Formulas.

This section explains the fundamental role of DBIs: "A database item is a mechanism for the formula to retrieve a value from a database table... When the formula runs

it replaces the database item with its value from the database." This confirms that formulas access the database directly via DBIs.

2. Oracle Cloud HCM: Implementing Time and Labor (Release 23D)

Chapter 11: Time and Labor Fast Formulas

Section: How You Use Database Items in Time and Labor Formulas.

This section explicitly states

"You can use database items in your time and labor formulas to retrieve information that isn't available from the time card entry

such as a person's bargaining unit

grade

or location." This directly supports answer A and refutes the limitation described in answer B.

3. Oracle Cloud HCM: Implementing Time and Labor (Release 23D)

Chapter 11: Time and Labor Fast Formulas

Section: Formula Performance Best Practices.

This section advises on the efficient use of DBIs

stating

"Use database items that retrieve a set of data rather than single values." This implicitly confirms that direct DBI access to a wide range of data is the standard

intended mechanism.

When creating a user-defined time card field in Oracle Time and Labor, you must specify a data source to populate the list of values for that field. The application supports two primary data source types: Public View Object (PVO) and Value Set. When the Value Set option is selected, the system further supports value sets with a validation type of 'Independent' or 'Table'. Therefore, the complete list of valid data sources comprises PVOs, independent value sets, and table-defined value sets.

A. This option is incorrect because dependent value sets are not supported as a direct data source for a single time card field, as they require a preceding independent value.

B. This option is incorrect because it is an incomplete list. It omits Public View Object (PVO) and table-defined value sets, which are both valid data sources.

D. This option is incorrect because it is an incomplete list. It omits the supported value set types (Independent and Table), which are valid data sources.

1. Oracle Fusion Cloud HCM: Implementing Time and Labor (Release 23D)

Chapter: Time Entry Configuration

Section: How You Create a Time Card Field

Content: "In the Data Source Type field

select Public View Object or Value Set... If you select Value Set

in the Value Set Code field

select the independent or table-validated value set that contains the valid values for the time card field." This text explicitly confirms that PVO

independent value sets

and table-validated (table-defined) value sets are the valid options.

2. Oracle Fusion Cloud HCM: Implementing Time and Labor (Release 23D)

Chapter: Time Entry Configuration

Section: Overview of Time Entry Configuration Components

Content: The section on Time Card Fields states: "You create lists of valid values for the fields using value sets or public view objects (PVOs)." This reinforces that these are the two fundamental categories of data sources.