Oracle 1z0-1057-24 Online Access

According to Oracle sources1, the inheritance between requirements, tasks, and deliverables works as follows:

You can associate a deliverable with a task independent of associating a requirement with a task. You can also associate a deliverable with a requirement independent of associating a task with a requirement1.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. You must manually associate the deliverable with the tasks that produce it1.

Therefore, the correct answer is B and D.

1: Can deliverables for projects and tasks be inherited from associated requirements? - docs.oracle.com (index 1)

In Oracle Project Management, you can define requirements, tasks, and deliverables for your project based on your project methodology and lifecycle. Requirements are statements of needs or expectations that must be met by the project outcome. Tasks are units of work that must be performed to complete the project. Deliverables are products or services that are produced or provided as part of a task or requirement. Two correct statements about how the inheritance between requirements, tasks, and deliverables works are:

You associate a deliverable with a task independent of associating a requirement with a task. This means that you can create a deliverable for a task regardless of whether the task is linked to a requirement or not.

A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement. This means that you have to manually associate a deliverable with a task even if both the deliverable and the task are linked to the same requirement.

Reference

To import and process third-party transactions that are costed and accounted, you need to set the Transaction Source Options for the transaction source that you use to import the transactions. The Transaction Source Options allow you to specify whether the transactions are costed and accounted by the source system or by Oracle Fusion Cost Management. You can also specify whether to validate and transfer costs and accounting entries to projects and general ledger.Reference:

Reference

Settings That Affect Performance Data Summarization

You can summarize performance data for a project unit, business unit, a range of projects, or projects managed by a project manager. When you run the Update Project Performance Data process from the Scheduled Processes page, select one of the summarization methods from the following table:

Summarization Method

Usage

Incremental

Summarizes new transactions that are yet to be summarized

Delete and re-summarize

Correct summary data when the source system data changes outside the regular transaction flow.

Do not use this summarization method when you run the Update Project Performance Data Without Producing Report process unless you are advised to do so.

Resource breakdown structure

Migrate all summary data from one resource breakdown structure version to the next.

If you select this option, you must also specify the resource breakdown structure header.

Ref: oject-financial-management-applications.html#FAPFM969761

Topic - Entering Planning Resource Breakdown Structure Details

ClickNavigator > Setup and Maintenance, and search for theManage Planning and Billing Resource Breakdown Structurestask.

Click theManage Planning and Billing Resource Breakdown Structureslink.

Use the Manage Planning and Billing Resource Breakdown Structures page to create new planning resource breakdown structures and to review existing planning and billing resource breakdown structures.

Click theCreateicon in the Planning Resource Breakdown Structures section.

Use the Create Planning Resource Breakdown Structure: Basic Information page to provide basic resource breakdown structure information including the name, active dates, and project unit.

Enter a planning resource breakdown structure name and select a date from which the resource breakdown structure is available for use.

Optionally, provide a description and a date to which the planning resource breakdown structure is available for use.

Select a project unit. Only projects created for the selected project unit can use this planning resource breakdown structure.

If you want to allow project managers to add planning resources at the project level, then select theAllow resource changes at project levelcheck box.

Tip:Changes at the project level don't move back to the parent planning resource breakdown structure.Deselect this option to ensure all project using the planning resource breakdown structure use the same resources.

Optionally, select aJob Setas a source of jobs for creating planning resources on your planning resource breakdown structure.

ClickSave.