How should you define a new, single attribute time card field with a new data source for the Project Costing Task time attribute that is dependent on…

To create a new time card field that is dependent on another, you must first define the independent field (Project) and the dependent field (Task). The dependency is established by configuring the independent field. On the "Define Time Card Fields" page for the independent "Project Costing – Projects" field, you use the "Dependent Field Definition" section to add the new "Task" field. The data source for the new Task field must be a correctly configured table-based value set. This value set's WHERE clause will reference the value of the independent Project field to filter and display only the relevant tasks for the selected project.

A. This is incorrect because the question explicitly requires a dependent relationship between the Task and Project fields, not an independent one.

B. This is incorrect because the dependency is on the "Project Costing Project" value, not the "Project Costing – Expenditure Type" attribute.

C. The "Generate Time Card Fields" process is run after the fields are defined and configured; it does not define the field's logic or dependencies.

D. This is incorrect. Oracle Cloud Time and Labor is highly configurable and allows for the creation of new time card fields beyond the delivered ones.

1. Oracle Fusion Cloud Human Capital Management: Implementing Time and Labor (Release 22D)

Section: Time Card Fields > Dependent Time Card Fields

Content: The documentation outlines the process: "You can make a time card field dependent on another time card field... On the Define Time Card Fields page

search for and select the independent field... In the Dependent Field Definition section

click Add Row. Select the dependent field." This directly supports the steps described in option E

where the dependency is configured on the independent field's definition page.

2. Oracle Fusion Cloud Human Capital Management: Implementing Time and Labor (Release 22D)

Section: Value Sets in Time and Labor > Table-Defined Value Sets

Content: This section explains how to use table-based value sets for time card fields. For dependent fields

it details using a WHERE clause with a bind variable that references the independent field's value (e.g.

:{PARAMETER.INDEPENDENTFIELDATTRIBUTENAME}). This confirms that a "properly defined table value set" is the correct mechanism for the new data source

as stated in option E.