The requirement is to calculate overtime on a different frequency (weekly) than the time card submission period (biweekly). In Oracle Time and Labor, this is managed through the Worker Time Processing Setup Profile. This profile contains two distinct period definitions: the "Time Card Period," which governs the time entry schedule, and the "Overtime Period," which specifically defines the repeating period for overtime calculations. By setting the Time Card Period to biweekly and the Overtime Period to weekly in the same profile, the system will process the biweekly time card but apply the overtime rules on a week-by-week basis within that period.

A. A weekly time period would be attached to the Fast Formula used to create the TCR Rule Template: Fast Formulas contain the calculation logic but do not have period definitions attached to them; they inherit the period context from the processing profile.

B. A weekly time period would be attached to the Worker Time Entry Setup Profile in the Overtime Period field: The Worker Time Entry Setup Profile controls the time card layout and user interface for time entry, not the backend calculation periods like the overtime period.

C. A weekly time period would be attached to the TCR Rule Template, the TCR Rule, the TCR Rule Set: Time Calculation Rules (TCRs) and their components use the period defined in the worker's profile; the period definition is not an attribute of the rules themselves.

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

Chapter: Time Processing Profiles

Section: Overview of Time Processing Profiles

Content: "The worker time processing profile links a person to their time and labor setup

including their time entry and calculation rules... It also identifies the repeating periods to use when processing time card entries and calculating overtime." This explicitly states that the processing profile defines both the time card and overtime periods.

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

Chapter: Time Processing Profiles

Section: Time Processing Profile Settings

Content: This section details the attributes of the profile

clearly listing "Time Card Period" and "Overtime Period" as separate

configurable fields. It states for Overtime Period: "Select the repeating period to use to calculate overtime." This directly confirms that the profile is the correct location for this configuration.

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

Chapter: Time Calculation Rules

Section: How Time Calculation Rules Work with Time Processing Profiles

Content: "The time calculation rule set that you associate with the worker time processing profile determines which rules run and in what order... The time processing profile provides the context

such as the overtime period

for the time calculation rules." This confirms that rules use the context from the profile rather than having the period attached to them.

To populate the Supplier Device Event list of values for mappings, a two-step configuration is required. First, you must define the time collection device (TCD) vendor in the TCD Suppliers lookup (ORAHXTTCDSUPPLIERS). After the supplier is defined, you can then define the specific events (e.g., IN, OUT, BREAK) for that supplier in the TCD Supplier Events lookup (ORAHXTTCDSUPPLIEREVENTS). This dependent setup ensures that events are correctly associated with their specific supplier, making them available for selection in the time device event mapping configuration.

A. Value sets are a generic tool for defining lists of values, but the specific configuration for TCD supplier events uses predefined lookups, not custom value sets.

C. Defining only the events in the TCD Supplier Events lookup is insufficient. The system requires the supplier to be defined first to associate the events with a specific vendor.

D. The system does not provide a fixed, non-configurable default list. The purpose of this configuration is to define the unique event codes specific to each third-party device supplier.

1. Oracle Fusion Cloud Human Resources

Implementing Time and Labor (Release 22D)

Chapter 6: Time Device Setup

Section: Lookups for Time and Labor.

TCD Suppliers Lookup: "Use the ORAHXTTCDSUPPLIERS lookup to define the suppliers of your time collection devices. You need to define the supplier before you can define the supplier device events."

TCD Supplier Events Lookup: "Use the ORAHXTTCDSUPPLIEREVENTS lookup to define the device events for each of your time collection device suppliers. The supplier values that you can select from are those that you defined with the ORAHXTTCDSUPPLIERS lookup."

The Planned and Published Schedules feature, which managers use to view team schedules, is designed to display calendar-based events with specific start and end times. A 'duration' work schedule only defines the total number of hours to be worked (e.g., 8 hours) without specifying the exact start and end times. Because this schedule type lacks the specific time-of-day data required by the calendar view, it is not supported and will not be displayed in the Planned and Published Schedules interface.

B. The worker’s work schedule is assigned to his primary assignment.

Assigning a work schedule to a worker's primary assignment is the standard and expected configuration; this action does not cause visibility issues.

C. Shift short name has not been set for the shifts that composed the worker’s work schedule.

A missing shift short name is a display attribute issue that might result in a blank label, but it would not prevent the entire schedule from being rendered.

D. Shift limits have not been set for the shifts that composed the worker’s work schedule.

Shift limits are constraints used for scheduling validation and planning, not for controlling the basic visibility of an already assigned schedule to a manager.

---

1. Oracle Cloud HCM: Implementing Workforce Management (Release 22D)

Chapter: Work Schedules

Section: Considerations for Creating Work Schedules

Content: The documentation explicitly states: "You can't use duration-based work schedules with the planned and published schedules that you manage with the Team Schedule." This directly confirms that duration schedules are incompatible with the view in question.

2. Oracle Cloud HCM: Using Time and Labor (Release 22D)

Chapter: Team Schedule

Section: Overview of Viewing Team Schedules

Content: This section describes how the team schedule displays shifts and absences on a calendar. The functionality relies on objects having defined start and end times to be placed on the calendar grid

a characteristic that 'duration' schedules lack by definition.

To achieve a weekly overtime calculation on a bi-weekly time card, the system configuration must distinguish between the time entry period and the time calculation period. The time entry layout should be configured with a bi-weekly repeating period, as this aligns with the user-facing bi-weekly time card. The time calculation rules, which process the entered time, must be associated with a weekly repeating period. This ensures that overtime thresholds are evaluated and their accumulators are reset on a seven-day cycle, correctly calculating overtime for each distinct week within the larger bi-weekly pay period. Customizing the WFMTHRESHOLDTIMECALCULATIONRULEAP formula is the appropriate method for implementing specific or complex logic within a threshold rule.

A. This is incorrect because it specifies a weekly repeating period for the time entry layout, which contradicts the requirement for a bi-weekly time card.

B. Using a bi-weekly repeating period for the time calculation rules is incorrect. It would cause the overtime accumulator to run for the full 14 days without resetting after the first week.

C. This is incorrect as this is a standard payroll requirement that is fully configurable within Oracle Time and Labor by using different repeating periods for layouts and rules.

---

1. Oracle Global Human Resources Cloud

Implementing Time and Labor (Release 23D)

Chapter: Time Rule Components

Section: Overview of Time Card and Time Calculation Rule Periods.

This document states

"You can define different repeating periods for the time card and time calculation rules. For example

you can have a biweekly time card period and a weekly rule set period to calculate weekly overtime." This directly supports the core logic of using a bi-weekly layout period and a weekly calculation period as described in the correct answer.

2. Oracle Global Human Resources Cloud

Implementing Time and Labor (Release 23D)

Chapter: Time Calculation Rules

Section: Time Calculation Rule Templates.

In the description of the "Threshold" rule template

the documentation explains that these rules "Compare a time event or the sum of hours for a period against a specified number of hours." It further clarifies that the period is determined by the repeating period associated with the rule set

validating the need for a weekly repeating period for the calculation rules.

3. Oracle Global Human Resources Cloud

Using Fast Formula (Release 23D)

Chapter: Time and Labor Formulas

Section: Formula Types.

This chapter details the various formula types. The "Time Calculation Rule" formula type

which includes the WFMTHRESHOLDTIMECALCULATIONRULEAP template

is specified for use with time calculation rules to "add complex logic to a rule." This confirms that customizing this formula is the correct approach for adding specific reset logic if required.

When configuring a time calculation rule template in Oracle Time and Labor, the "Rule Classification" field is used to define the specific purpose or sub-type of the template. This classification determines the template's behavior and available configuration options. According to Oracle's official documentation, the six available rule classifications are Distribution Rule, Meal or Break, Rounding, Shift Premium, Threshold, and Weekly Premium. Option B is the only choice that accurately and completely lists these six classifications.

A: This option incorrectly includes "Work Time Directive" and "Variance" and omits the valid "Meal or Break" and "Rounding" classifications.

C: This option incorrectly includes "Variance" and omits the valid "Rounding" classification. A variance is typically a type of time category, not a rule classification.

D: This option incorrectly includes "Work Time Directive," which is not a valid rule classification for time calculation rule templates.

1. Oracle Fusion Cloud HCM. (2022). Implementing Time and Labor. Chapter: Time Calculation Rules

Section: Time Calculation Rule Templates.

"When you create a time calculation rule template

you select a rule classification to identify the sub-type purpose of the template. The available classifications are Distribution Rule

Meal or Break

Rounding

Shift Premium

Threshold

and Weekly Premium."