1z0-1057-22 Practice Exam Questions with Answers Oracle Project Management Cloud 2022 Implementation Professional Certification

 Project Management is the product offering that enables you to collaboratively plan and deliver projects by leveraging intuitive and integrated scheduling tools. Project Management allows you to create and manage project plans, tasks, deliverables, issues, milestones, gates, etc. using various methods and sources. You can also monitor and control project progress and performance using dashboards and reports. Resource Management is the product offering that enables you to optimize the utilization and allocation of resources for projects and tasks. Resource Management allows you to create and manage resource requests, assignments, pools, calendars, etc. using various criteria and sources. You can also monitor and analyze resource availability and demand using dashboards and reports. Project Control is the product offering that enables you to simplify the planning, budgeting, and forecasting capabilities for projects and tasks. Project Control allows you to create and manage project budgets, forecasts, financial plans, etc. using various methods and sources. You can also monitor and control project costs and variances using dashboards and reports. Project Costing is the product offering that enables you to capture and process project costs from various sources and applications. Project Costing allows you to create and manage project transactions, expenditures, assets, etc. using various rules and options. You can also generate project costing and accounting entries using dashboards and reports. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/overview-project-financial-management.html#OAPFM2356301

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementin g-project-execution-management-applications.html#FAPFM1724547

Topic – Submitting the Process to Maintain Project Resource Search Index: Procedure

Submit the Maintain Project Resource Search Index job set to update the resources that appear on the Search and Evaluate Resources page when a resource manager searches for resources to fulfill project resource requests. The job set consists of a set of processes that facilitate efficient and rapid searches for qualified resources.

Resource managers can't search for resources or view resource details if the search index isn't available for a project resource request with qualifications or keywords. For project resource requests without qualifications and keywords, resource managers can search for and evaluate resources based on resource availability even if the search index isn't current or available.

Caution: The search index isn't available if the Maintain Project Resource Search Index job set process fails, or while the process is running.

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.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/18c/oapfm/project-costing-configuration-define-project-costing-integrations.html#OAPFM174886

How can I validate distribution sets for projects information?

Oracle Fusion Projects performs validations on Oracle Fusion Payables distribution sets for payables invoices at the time you create the actual distribution set lines. It validates the project and task number during the invoice validation.

Distribution sets are typically used on recurring transactions, and the associated project does not have transaction controls. When you create a distribution set in Oracle Fusion Payables, the distribution set line is not validated against the project transaction controls in Oracle Fusion Projects because you do not enter an expenditure item date, which is required for transaction control validation. The expenditure item date is not provided because you use the distribution sets for an indefinite period of time.

The Deploying step within the functional setup manager helps you to move your verified setup data from the test environment to a production environment. This step allows you to export and import setup data across instances using spreadsheets or configuration packages. You can also compare and validate setup data across instances using reports and dashboards. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/implement-project-financial-management-applications.html#OAPFM2356111

Ref: https://docs.oracle.com/cd/E17904_01/doc.1111/e14431/managing.htm#APMAG3333

Fusion Middleware Administrator's Guide for Authorization Policy Manager

Managing Security Artifacts

This chapter describes the procedures an administrator follows to manage application-specific security artifacts, view the external role hierarchy, manage the application role hierarchy, and manage the many-to-many mapping of application roles to external roles from both the application and the external role point of view.

This chapter is divided into the following sections:

• Managing Application Security Artifacts
• Viewing the External Role Hierarchy
• Managing the Application Role Hierarchy
• Mapping Application Roles to an External Role
• Mapping External Roles to an Application Role

Role Mapping Policy

• A Role Mapping Policy is used to determine what external subjects (users, groups or External Roles) are assigned to the applicable Application Role. The Application Role, when referenced in an Authorization Policy, defines the principals affected by the Authorization Policy. Role Mapping Policies may also include conditions

Oracle Identity Manager – Not used for mapping application roles to external roles

How do Users Interact with Oracle Identity Manager?

Oracle Identity Manager provides an end-user interface, called the Identity Self Service console, and a system administrator interface, called the Identity System Administration console. Both end-users and system administrators use the web browser to log on to Oracle Identity Manager. Oracle Identity Manager (OIM)

• OIM provision users, roles, and defines what a user can do in Oracle Cloud
• Duty Roles are mapped to jobs and assigned access privileges (Data Security)

Ref: https://docs.oracle.com/cd /E51367_01/projectop_gs/OAPJB/F1087456AN1006D.htm

What's a bill set?

Transactions originating from different bill plans with the same bill set number on a contract are included on the same invoice. If a contract has multiple bill plans and each have different values for the bill set, Oracle Fusion Project Billing creates a separate invoice for each bill plan

Program management is a capability that allows you to coordinate and track multiple related projects and tasks as part of a strategic program. To configure the program options as part of implementing the program management capability, you need to define three components:

• Calendar: This component allows you to specify the calendar that is used to calculate the dates and durations for the program and its projects and tasks.
• Calculation Methods: This component allows you to specify the methods that are used to calculate the progress, performance, and variance measures for the program and its projects and tasks based on various sources and formulas.
• Derivation Methods: This component allows you to specify the methods that are used to derive the attributes and values for the program and its projects and tasks based on various rules and conditions. Currencies and Accounting Methods are not components that are required to configure the program options. Currencies are used to define the currency conversion rates and rules for the program and its projects and tasks. Accounting Methods are used to define the subledger accounting rules and options for the program and its projects and tasks. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-programs.html#OAPFM2356261

https://docs.oracle.com/applications/farel12/projectop_gs/OAPFM/OAPFM2264569.htm#OAP FM2159921

Configuring Rapid Implementation: Procedure

Project application administrators can use the rapid implementation feature to set up the Project Financial Management offering. Use the Rapid Implementation for Project Financial Management Applications macro-enabled Microsoft Excel spreadsheet to enter setup data and generate the ProjectsWorkbook.zip. Upload this .zip file to the Setup and Maintenance work area. When the upload completes, the offering is configured based on the setup information that you provide.

Perform the following steps to configure rapid implementation for the Project Financial Management offering:

• Prepare setup data.
• Generate CSV files.
• Upload setup data.
• Correct errors, if any, and reload the data.

Shift is one of the key elements in defining project and resource calendars. Two additional key elements that are required to define the project and resource calendars are:

• Schedule Exceptions: These are dates or periods that override the regular workday patterns and shifts of a calendar. They can be used to define holidays, vacations, or other special events that affect the availability of resources or projects.
• Workday Patterns: These are patterns of working and nonworking days that repeat over a period of time. They can be used to define the standard working days and hours for a calendar. Time off, expenditure type, and accounting calendar are not key elements in defining project and resource calendars. Time off is an attribute of a resource assignment that reduces the availability of a resource. Expenditure type is a classification of costs that determines how they are processed and accounted. Accounting calendar is a calendar that defines the accounting periods and dates for transactions. Reference: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/20c/oapfm/manage-project-resources.html#OAPFM2356131

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19a/fapfm/implementing-pr oject-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.

Ref: https://docs.oracle.com/en/cloud/saas/project-portfolio-management/19b/oapfm/p roject-control-configuration-manage-financial-and-project-plan-types.html#OAPFM75315

Financial and Project Plan Setup Options

The following table describes the basic budget, forecast, or project plan setup options that determine how a plan type is used in the context of a project. Except for third-party scheduling, you can't edit these options at the project level.

Option

Location

Description

Planning amounts

Financial plan type

Indicates that the financial plan type supports the creation of versions with the following amounts:

• Cost amounts
• Revenue amounts
• Both cost and revenue amounts
• Either cost or revenue amounts

Approved budget or primary forecast

Financial plan type

Determines whether a financial plan type is used for creating approved budget versions or primary forecast versions that are used for plan comparison or project performance reporting.

Default financial plan type

Financial plan type

Determines whether the financial plan type is the default selection when you create budget or forecast versions.

Workflows

Financial plan type

Enables the use of a workflow for managing budget or forecast status changes.

Third-party scheduling software

Project plan type

Indicates whether project planning is performed in Microsoft Project.

If third-party scheduling is disabled in the project plan type, you can use the associated project or project template to create a project in Microsoft Project. However, you can't export the new project or link it to one created in Oracle Fusion Project Portfolio Management.

Multiple transaction currencies

Financial and project plan type

Enables entry of plan amounts in currencies other than the project currency.

Budgetary control settings

Financial plan type

Manages options for creating control budgets in Oracle Fusion Budgetary Control.