Oracle 1z0-1057-24 Oracle Project Management Cloud 2024 Implementation Professional Exam Practice Test

XML (Extensible Markup Language) is the data format that is supported by SOAP (Simple Object Access Protocol) Web services to establish communication between web services consumers and web services providers. XML is a standard format that allows data to be exchanged across different platforms and applications. SOAP Web services use XML to encode the messages and data that are sent and received between the web services endpoints. Reference:

Ref: ect-foundation-configuration-define-types-and-categorizations.html#OAPFM222700

Topic - Manage Project Class Categories

Setting Up Class Categories: Points to Consider

Available as Accounting Source

This option indicates if theclass category is available as an accounting source so that Oracle Fusion Subledger Accounting can use the category to create mapping sets, account rules, journal line rules, and description rules.

Only one class category at a time is available as an accounting source in Oracle Fusion Subledger Accounting. To change the class category that Oracle Fusion Subledger Accounting uses, deactivate the old class category and create a new one with a different date range.

Ref:

REST API =REpresentationalStateTransfer (REST)ApplicationProgramingInterface (API)

The borrowed and lent cross charge method is a method that allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger. This method does not generate internal invoices or intercompany accounting entries for cross charge transactions. Instead, this method creates accounting entries that move an amount equal to the transfer price between the provider and receiver organizations using borrowed and lent accounts. Two statements that are true about this method are:

Internal Invoice is not generated with this method. This method does not create internal invoices for cross charge transactions, as these transactions are accounted within the same primary ledger using borrowed and lent accounts.

This method allows you to process cross charge transactions across legal entities. This method allows you to process cross charge transactions between provider and receiver organizations that belong to different legal entities within the same primary ledger, as long as they share the same chart of accounts, calendar, currency, and subledger accounting method.

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:

Reference 816855

Spread curves let you distribute quantity, cost, and revenue amounts automaticallyacross accounting or project accounting periods. You assign a spread curve to each resource class. Planning resources (in the planning resource breakdown structure) inherit the spread curve setting from the associated resource class. You can change the spread curve for the planning resource and for any corresponding task assignments, or budget or forecast lines.

The generate public events for project deliverable status changes feature is a feature that allows you to send notifications or trigger actions when the progress status of a deliverable changes from one value to another. For example, when the status of a deliverable is set to Complete, you can send a notification to the owners of the associated tasks or update the status of the tasks accordingly. Two statements that are true about this feature are:

The public event is not generated when a deliverable is created or deleted. This feature only generates events when the progress status of a deliverable changes, not when a deliverable is added or removed from a project or task.

The public event is generated when the progress status for a deliverable changes. This feature generates events when the progress status of a deliverable changes from one value to another, such as from Not Started to In Progress, or from In Progress to Complete. You can define rules and actions for each progress status change using Business Process Management (BPM) Worklist. The public event is also not generated when the priority of a deliverable changes, as this feature only generates events when the progress status of a deliverable changes. Reference:

Ref:

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 anexpenditure 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.

Reference le.com/helpPortal/topic/TopicId_P_8718794B26A7BB93E040D30A688149A3

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:

Ref:

Topic Approval Groups

Each approval group includes a set of users that you configure to act on tasks in a certain pattern. Tasks can be defined to get routed to an approval group instead of an individual user. You can nest approval groups within approval groups.

You have two options for defining the group:

Static: Select the specific users to include in the group.

Dynamic: Provide the logic to use to determine the users in the group.

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:

Ref: 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.

Ref: tor-job-role.html#Project_Administrator_privileges

Project Manager has duty role ‘Project Forecast Approval Duty’ assigned but

Project Administrator has duty role ‘Project Forecast Inquiry Duty’ – no approval authority

Both roles have duty role ‘Project Forecast Management Duty’ which enables them to Allow creation, submission, update, and deletion of working versions of project forecasts. (Cloud _Roles_Duties.xlsx)

Reference 43

Topic - Manage Project Unit Organizations

Ref: ject-costing-configuration-define-project-costing-integrations.html#OAPFM3094605

Topic - Deriving Projects-Related Accounts

The employees and contingent workers will be able to modify their time cards in the Time work area. This work area allows them to enter, review, edit, and submit their time cards for approval. They can also view the status and history of their time cards and make corrections as needed. The Time and Cost work area allows the project managers and cost accountants to review, adjust, and transfer time card transactions to projects and tasks. The Asset work area allows the asset managers and cost accountants to review, adjust, and transfer asset transactions to Oracle Fusion Assets. These work areas are not used by the employees and contingent workers to modify their time cards. Reference:

Some of the main benefits of using the implementation projects within Functional Setup Manager are:

Implementation Project helps in assigning responsibility of managing setup data to a broad group of users. You can assign tasks to different users who are responsible for entering and validating setup data for different functional areas of the offering.

Implementation Project helps you to monitor progress of the setup tasks. You can track the status and completion percentage of each task and view the dependencies and prerequisites among tasks. Implementation Project does not give you the flexibility to set up different functional areas of the offering at different times, as this is determined by the configuration package that you select for your implementation. Implementation Project does not help you to use the manage setup data entry in bulk option, as this is a separate feature that allows you to import and export setup data across instances using spreadsheets. Reference:

Selecting the offering you want to implement and enabling optional functional areas and features by opting in are not part of managing an implementation project. These are part of configuring an implementation project, which is done before managing an implementation project. Configuring an implementation project allows you to define the scope and features of your implementation based on your business needs. Managing an implementation project involves assigning tasks to various users who are responsible for managing setup data, monitoring the progress of completing setup tasks, and generating a list of setup tasks. These are part of executing an implementation project, which is done after configuring an implementation project. Executing an implementation project allows you to perform the setup tasks and validate the setup data for your implementation. Reference:

Reference /implementing-security-in-oracle-fusion-project-portfolio-management.html#FASER1722595

Ref to “Securing Project Financial Management and Grants Management Applications”

Table lists predefined enterprise roles and the type of security that grants the role access to data in a work area or dashboard.

Enterprise Role

Work Area or Dashboard

Data Security Based On

Project Accountant

Asset

Project business unit

Project Accountant

Costs

Project expenditure business unit

Project Accountant

Revenue

Contract business unit

Project Administrator

Project Financial Management

Project business unit

Project organization

Project Billing Specialist

Invoices

Contract business unit

Project Creator

Project Financial Management

Project business unit

Project organization

Project Management Duty

Project Management Infolet Dashboard

Project assignment

Project Management Duty

Project Performance Dashboard

Project assignment

Project Manager

Project Management Infolet Dashboard

Project assignment

Project Manager

Project Performance Dashboard

Project assignment

Project Manager

Project Management

Project assignment

Project Manager

Project Manager Dashboard

Project assignment

Project Team Member

Project Financial Management

Project assignment

Grants Accountant

Invoices

Contract business unit

Grants Accountant

Revenue

Contract business unit

Grants Administrator

Awards

Contract business unit

Grants Administrator

Contracts

Contract business unit

Grants Administrator

Project Financial Management

Project business unit

Principal Investigator

Awards

Award assignment

Principal Investigator

Contracts

Award assignment

Principal Investigator

Project Financial Management

Project assignment

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:

Ref: 19b/oapjf/manage-project-plan-tasks-and-task-assignments.html#OAPJF75076

The Default Capitalized Interest Rate Schedule should be specified on the Manage Project Type page. This option allows you to select a capitalized interest rate schedule that will be used as the default for projects or tasks that use the project type. A capitalized interest rate schedule defines the interest rates and dates that are used to calculate the capitalized interest amount for a project or task. Reference:

Ref: management/19b/oapfm/project-foundation-configuration-define-project-resource-breakdown-structures.html#OAPFM180158_2

Why can't I find persons in the list of resources when I enter team members, planning resources, or person rate schedules?

You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules in the following situations:

The administrator didn't assign adepartmentwhile creating users. Persons must have an active assignment andbe assigned to a departmentin Oracle Fusion Human Capital Management before they can be added as team members or entered as resources on the planning resource breakdown structure or person rate schedule.

The resource isn't active in Oracle Fusion Human Capital Management because the current date is before the effective date of the resource.If you want to include persons who will start in the future, select the Include people with future-dated effective start dates option when you search for the person.

Persons assigned as project managers aren't active as of the project start date.

The assignment of the person is terminated, and an appropriate value isn't set for the number of days to display people with terminated assignments.You can set the profile value appropriately at the site profile level using the Specify Number of Days to Display People with Terminated Assignments task in the Setup and Maintenance work area.

Ref: oracle.com/en/cloud/saas/project-portfolio-management/19a/oapem/execute-project-tasks-and-deliverables.html#OAPEM1122082

Followers are persons who aren't working on the task but have an interest in reviewing the task progress. Only the resources and other followers can add followers to a task. If a resource assigns the task to another team member, the application automatically changes the original resource to a follower.

What's the difference between my tasks and tasks that I follow?

You can edit task details and enter progress for your tasks on the Manage Tasks page. If a task has multiple resources, only the primary resource can edit the task.

When you follow a task, you can view the task details and see the task activity stream. You receive e-mail notifications of changes that team members make to the task.

If a resource reassigns the task to another team member, then the previous resource automatically becomes a follower.

Reference

Topic – Creating Calendars for Projects and Resources: Procedure

Project Schedules are used as a base for project and resource calendars in Project Execution Management applications. The smallest scheduling unit is a day. For example, you can define the number of hours in a day but, you can't schedule work for a specific time of the day.

The following are the elements of a schedule:

Shifts

Workday patterns

Exceptions

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.

The source that can be used while defining the account rule to achieve this requirement is Expenditure Organization Cost Center Segment. This source allows you to retrieve the value of the cost center segment based on the expenditure organization of the transaction. The expenditure organization is an attribute of a transaction that represents the organization that incurs or owns the cost of the transaction.

Ref: o-management/19b/oapjb/manage-project-contract-revenue.html#OAPJB164173

Associated Project Percent Spent Example

The following formula calculates the percent spent revenue for the associated project.

((Sum of ITD Actual Cost for every subtask that is part of the associated task/Sum of Total Budgeted cost for every task that is part of associated task)

xAssociated Project Funded Amount) – Sum of Existing Invoice Event Amounts for the Associated Project

((60/300) x750) – 80 =70

((Actual Cost / Budgeted Cost) x Budgeted Revenue) – Sum of Revenue Event Amount

Ref: ement/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 assetgrouping 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

Reference

Reference Data Sharing Methods

Variations exist in the methods used to share data in reference data sets across different types of objects. The following list identifies the methods:

Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate Conventions are defined and assigned to only one reference data set. This set can be shared across multiple asset books, but all the values are contained only in this one set.

Assignment to one set only, with common values. This method is the most commonly used method of sharing reference data that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are assigned to a common set that is available to all the business units. You need not explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specific set of transaction types. At transaction entry, the list of values for transaction types includes the following:

Transaction types from the set assigned to the business unit.

Transaction types assigned to the common set that is shared across all business units.

Assignment to multiple sets, no common values allowed.The method of sharing reference data that allows a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this method.It means that each payment term can be assigned to one or more than one set.For example,you assign the payment term Net 30 to several sets but assign Net 15 to a set specific only to your business unit. At transaction entry, the list of values for payment terms consists of only the set that is assigned to the transaction's business unit.

Note: Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects your entire enterprise in this set. Also update the data set going forward as you create new reference data items.

The Accounts Member component of performance measures allows you to select the method that is used to measure accounts such as budget, forecast, and actual. The Accounts Member component defines the account dimension member for the performance measure, which represents the financial data that is measured. You can also specify the aggregation rule and calculation method for the account dimension member. Reference:

Project type is a classification that defines the common attributes and processing options for projects. Some of the correct statements about project type are:

Project type can be used as a source in subledger accounting. This allows you to create accounting rules based on the project type attribute.

Summarization options can be specified at project type. This allows you to control how the project transactions are summarized for reporting and performance purposes.

Project type can be associated with multiple project units. This allows you to share the same project type across different business units or organizations. Project type cannot be enabled for both billing and capitalization, as these are mutually exclusive options. Classifications cannot be assigned at project type, but at project or task level. Reference: management/20c/oapfm/set-up-project-financial-management.html#OAPFM2355971

The Cost Collection Flexfield is a descriptive flexfield that captures additional information about project costs. It has three core attributes that are required for every cost transaction:Billable Flag, Expenditure Type, and Capitalizable Flag. These attributes can be derived during import if not explicitly entered in a transaction document, based on various rules and sources such as expenditure type defaults, project type defaults, transaction source defaults, etc. Funding Source and Work Type are not core attributes of the Cost Collection Flexfield, but context-sensitive segments that can be optionally enabled for certain transaction sources or business units. These segments capture additional information about how the costs are funded or what type of work is performed. Reference:

Reference

Project Labor Demand: How It's Calculated

Project executives want to track the labor demand in projects in their organization. The Project Hierarchy Viewer provides project executives a hierarchical view of the enterprise project structure (EPS) along with the labor demand in terms of full-time equivalent (FTE).

Settings That Affect Project Labor Demand

Project application administrators must do the following to set up how project labor demand is calculated:

Organize projects into hierarchical groups on the Manage Enterprise Project Structure page.

Change the quarterly FTE hours for the organization on the Define Project Management Implementation Options page, if different from 520 hours.

Note:You can choose to view labor demand annually instead of quarterly. The Project Hierarchy Viewer uses the current date to determine which year or quarter to display.

How Project Labor Demand Is Calculated

The Project Hierarchy Viewer calculates project labor demand in the following manner:

Spreads the allocation hours from the Manage Project Resources page evenly over the days that the resources are allocated to the project.

Divides the quarterly project allocation hours by the quarterly FTE hours to get the labor demand.

Rolls up the quarterly and annual labor demand up the hierarchy.

Reference gs/OAPEX/F1082603AN23E61.htm

Manage Project Enterprise Labor Resource Maintenance Conditions

Project Enterprise Labor Resources: How They Are Automatically Created and Maintained

Run the Maintain Project Enterprise Labor Resources process to create resources, remove resource availability for staffing, and maintain the resource search index.

Settings That Affect the Maintain Project Enterprise Labor Resources Process

Create and maintain project enterprise labor resources by defining a set of conditions that specify the employees and contingent workers in Oracle Fusion Human Capital Management (HCM) to create as resources in Oracle Fusion Project Portfolio Management. Define the resource attribute values, such as the resource calendar and primary project role, to assign to the new resources.

The following table lists the criteria that you define for selecting HCM persons to create as project enterprise labor resources.

Selection Criteria

Description

Person type

Select the HCM person type for the process to use as criteria when selecting HCM persons to create as resources. Available person types are employees, contingent workers, orboth employees and contingent workers.

Option to select people based on job

Select this option for the process to create resources for HCM persons with specific jobs.

CautionIf you do not select job criteria for this condition, the process will create resources for all eligible people based only on the person type.

Jobs

If you selected the option to select people based on job, then select the jobs for the process to use as HCM person selection criteria.

The following table lists the attributes for which you specify values to assign to resources that are created for the condition.

Resource Attribute

Description

Option to manage resource availability and staffing

Select this option for resource managers to manage the availability and project staffing of resources who are created based on the condition. Resources who are managed in Oracle Fusion Project Resource Management are eligible to fulfill project resource requests.

Calendar

Select the resource calendar for resources that are created based on the condition. The resource calendar defines the work schedule for project enterprise labor resources, and includes working days and hours and any exceptions, such as holidays.

Primary project role

Select the primary project role for resources that are created based on the condition. Project roles are maintained in Oracle Fusion Project Management.

Cost rate and currency

Enter the cost rate and currency for resources that are created based on the condition.

Bill rate and currency

Enter the bill rate and currency for resources that are created based on the condition.

When you use Create Tree or Create Tree Version in the action menu, you create a new organization tree or a new version of an existing tree, respectively. These actions result in an Inactive status for the organization tree, until you activate it. When you use View Tree Version or select the Edit icon or click the name of the tree, you open an existing organization tree that has an Active status.Reference: