Get Oracle 1Z0-1057-24 Exam Practice Questions - Real and Updated

Answer : B

(Page 2) Flexible Contract-Based Billing

Traditional contract and billing systems enforce a rigid relationship between a project and a funding agreement, which can constrain project setup and execution. Oracle Fusion Project Portfolio Management provides a highly flexible approach to project contract-based billing via a non-exclusive

relationship between multiple projects and tasks with contracts and contract lines. This means that you will have full control over defining contracts, rates and limits, and when and how to recognize revenue and generate invoices while segregating the planning and execution of your projects.

Answer : A, E

To enable a task as a business object for social networking, you need to select the task and the project attributes. These attributes allow you to identify the task and the project it belongs to, and to view the social conversations related to them. Task number and creation date are not available as attributes for social networking. Project number is available, but it is not required to enable a task as a business object. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-tasks.html#OAPFM2355891

Answer : C, D

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapem/define-project-deliverables.html#OAPEM1122079

Associate deliverables with one or many tasks or requirements at any level. Associate existing deliverables to tasks or requirements or create deliverables directly for tasks or requirements. You can delete a deliverable in New status if it is not associated with tasks or requirements.

Can deliverables for projects and tasks be inherited from associated requirements?

No. A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement.

You associate a deliverable with a task, independent of associating a requirement with a task.

Answer : C

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/oapfm/project-foundation-configuration-manage-project-types.html#OAPFM220111

Topic -- Asset Cost Allocation Methods: Explained

The asset cost allocation method determines how indirect or common costs incurred on a project are allocated to multiple assets.

You can specify an asset cost allocation method to enable Oracle Fusion Project Costing to automatically allocate unassigned asset lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned to an asset grouping level.

Projects and project templates inherit a default asset cost allocation method from the associated project type. You can override the default at the project level. If you use capital events to allocate costs, then you can also override the asset cost allocation method at the event level.

The following table describes the available asset cost allocation methods.

Method

Basis of Cost Allocation

Actual Units

Number of units defined for each asset

Current Cost

Construction-in-process (CIP) cost of each asset

Estimated Cost

Estimated cost of each asset

Standard Unit Cost

Combination of the standard unit cost and the number of units defined for each asset

Spread Evenly

Equal allocation of cost to each asset

Answer : B

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-project-financial-management-applications.html#FAPFM969761

Topic - Entering Planning Resource Breakdown Structure Details

Click Navigator > Setup and Maintenance, and search for the Manage Planning and Billing Resource Breakdown Structures task.

Click the Manage Planning and Billing Resource Breakdown Structures link.

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 the Create icon 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 the Allow resource changes at project level check 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 a Job Set as a source of jobs for creating planning resources on your planning resource breakdown structure.

Click Save.