Which three Cost Collection Flexfield core attributes can be derived during import if not explicitly entered in a transaction document? (Choose…

When importing project cost transactions, certain attributes can be derived from transaction controls defined at the project or task level if they are not explicitly provided in the source data. The 'Billable Flag' and 'Capitalizable Flag' are commonly derived from the settings of the task to which the cost is charged. Similarly, the 'Work Type' can be defaulted from the task or project. This derivation logic ensures data consistency and reduces the amount of detail required in source transaction documents.

B. Expenditure Type is a fundamental cost classifier that is almost always required in the source transaction and is not typically derived from task settings.

D. Funding Source is specific to sponsored projects (Oracle Grants Management) and is derived from award setup, not from general project/task transaction controls.

1. Oracle Cloud Project Management Implementation Guide (Release 13)

Chapter 11: Define Project Costing

Section: "Transaction Controls: Explained". This section details how transaction controls at the project and task level determine how expenditure items are processed

including their billable and capitalizable status.

2. Oracle Cloud Project Costing User Guide (Release 13)

Chapter 3: Import Costs

Section: "How Transaction Attributes Are Derived". This document explicitly mentions that the capitalizable indicator

billable indicator

and work type for an expenditure item can be derived from the associated project task.