Which statement is true about the business processes that Oracle HCM Cloud Time and Labor provides?

Oracle HCM Cloud Time and Labor provides robust capabilities for tracking time spent on specific activities, including integration with Oracle Project Portfolio Management (PPM). This allows workers to enter their time directly against the projects and tasks they are assigned to. This functionality is a core business process that enables organizations to accurately capture labor costs, manage project budgets, and facilitate client billing. The time card layouts can be configured to include fields for project number, task name, and expenditure type, ensuring that time data is captured with the necessary detail for project costing.

A. While timekeepers can enter time for groups of workers, option D describes a more fundamental business process of cost allocation available to the worker directly.

B. The system is designed for a worker to have only one time card for a specific, defined time period to maintain data integrity and prevent duplicate payroll entries.

C. This describes a system configuration option (defining a repeating period) rather than a transactional business process performed by users like workers or managers.

E. A manager's primary role in Time and Labor is to review, edit, and approve their team's time cards. Creating time cards, especially from templates, is typically a worker or timekeeper function.

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

Chapter 6: Time Entry Setup Components

Section: How Time Card Fields for Project Costing Work Together.

This section explicitly states

"You can configure time card fields to let people report time against projects

and tasks for project costing." It details how time attributes like project name

project number

task name

and expenditure type are used on the time card

confirming the capability described in option D.

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

Chapter 2: Time Entry

Section: How Time Cards Are Created.

This document clarifies the time card creation process

stating

"The application creates one time card for a person for each time card period." This directly contradicts option B.

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

Chapter 3: Time Definition Setup

Section: Repeating Time Periods.

This section describes the setup of time periods

noting that period types can be "Weekly

Biweekly

Monthly

or Semimonthly." This confirms that monthly periods are possible (making statement C factually correct)

but it is a setup task

not a transactional business process itself.

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

Chapter 2: Time Entry

Section: Time Card Entry for Someone Else.

This section details the roles of managers and timekeepers. It highlights that managers "can view

enter

and submit time cards for their direct and indirect reports

" and timekeepers "enter

and submit time for a group of people." While managers can enter time

their primary process is approval

and the concept of "creating from templates" is not a designated manager function

making option E incorrect. The timekeeper's ability to "Manage Batches" is also described

confirming the capability in option A

but as a specific role's task.