Free 1Z0-1057-26 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The BPM Worklist is the centralized user interface in Oracle Fusion Applications for managing human tasks generated by business processes. It allows users to view, act upon (e.g., approve, reject, reassign), and track tasks assigned to them or their groups. This component is part of the Oracle SOA Suite's Human Workflow service and provides the necessary interaction layer between the automated business process and the required human intervention, ensuring that approvals, exceptions, and other manual steps are handled efficiently.

A. Security Console: This tool is used for identity and access management, such as creating users, managing roles, and defining security policies, not for workflow tasks.

B. SOA Suite: This is a comprehensive software suite for building, deploying, and managing a service-oriented architecture. The BPM Worklist is a component within the SOA Suite, making it the more specific and correct answer.

C. Subledger Accounting: This is a rule-based accounting engine that creates journal entries from transactional data. It does not manage human workflow tasks.

1. Oracle Fusion Middleware

Developing SOA Applications with Oracle SOA Suite

12c (12.2.1.4.0)

Chapter 41: Getting Started with Oracle BPM

Section: "Introduction to Oracle BPM". The documentation states

"Oracle BPM Worklist provides a web-based user interface that enables end users to access and process tasks...".

2. Oracle Fusion Cloud Applications

Tools and Technology

"An Introduction to Oracle Fusion Applications for Technical Professionals" White Paper

Section: "Business Process Management". This paper describes how Oracle BPM

including the human task component and worklist

is embedded within the applications to orchestrate business processes.

The Project Requirements work area in Oracle Project Management Cloud is designed for defining and managing the project scope before detailed planning. Within this area, users can create and manage a list of backlog items (E), which represent features or user stories. These backlog items can be organized and grouped under specific requirements to provide structure (B). To transition from requirements to a work plan, users can directly create project tasks from these backlog items (D), forming the initial work breakdown structure. These three activities represent the core cycle of defining, organizing, and decomposing project scope within the work area.

A. An implementation project is created in the Setup and Maintenance work area to configure the Oracle application itself, not to manage project requirements.

C. While you can initiate the creation of an execution project from the requirements, managing backlog items and tasks are more granular, core activities within the work area.

Oracle Fusion Cloud Project Management Using Project Execution Management (Release 24B)

Chapter 6: Project Requirements. The chapter introduction states

"Use the Project Requirements work area to capture and manage requirements for a project... Create and manage backlog items... Create project tasks from backlog items."

When the invoice is generated, the balance previously placed in Unbilled Receivables is re-classified to trade Accounts Receivable. Revenue was already recognized, so only the asset account changes; no additional revenue entry is required.

No alternative accounting entries were provided for evaluation.

1. Oracle Fusion Cloud Project Management Using Project Financial Management 23D, section “Generate Invoices from Revenue,” example journal entries (doc ID E97017-12).

2. Oracle Fusion Cloud Receivables Implementation Guide 23D, chap. “Project Contract Invoicing Integration,” exhibit “Invoice vs. revenue accounting flows.”

Project transaction controls are rules that validate transactions against project and task attributes to determine chargeability. These rules often include date-based conditions (e.g., "allow charges only between start and end dates"). A Payables distribution set is a template for creating invoice distributions and does not contain transactional data like a specific date. The validation of transaction controls occurs when the actual invoice is created because only then is the expenditure item date (derived from the invoice date) available to check against any date-effective rules.

A. There is no expenditure type information available on the distribution set line: Expenditure type can be, and often is, included in a distribution set to classify the cost.

B. There is no expenditure organization information available on the distribution set line: The expenditure organization can also be specified within a distribution set template.

D. The account code combination is not available on the distribution set line: The primary purpose of a distribution set is to pre-populate the account code combination.

Oracle Fusion Cloud Project Management Documentation, "Implementing Project Financial Management and Grants Management", Chapter: Project Foundation Configuration, Section: Transaction Controls. (This document explains that transaction controls are evaluated against transaction attributes, including the expenditure item date.)

Oracle Fusion Cloud Financials Documentation, "Implementing Payables Invoice to Pay", Chapter: Payables Configuration, Section: Distribution Sets. (This document describes distribution sets as templates that lack the full context of a live transaction, such as the date.)

The requirement is to cascade only the project start date to its tasks, while leaving the finish date unaffected by project-level changes. In the project template's planning options, the "Cascade Date Changes" setting controls this behavior. Selecting "Cascade change to the start date" ensures that any modification to the project's start date will automatically adjust the start dates of all its tasks, but changes to the project's finish date will not be cascaded. This provides the specific control requested by the customer.

B. This option would prevent any date changes at the project level from cascading to tasks, which contradicts the requirement to cascade the start date.

C. This option would cascade only the finish date, which is the opposite of the customer's requirement.

D. This option would cascade both start and finish date changes, which is explicitly not what the customer wants for the finish date.

1. Oracle Fusion Cloud Project Management Documentation, "Define Project and Task Codes: Explained". In the section "Project Plan Type Planning Options", the "Cascade Date Changes" setting is described with its available values: Do not cascade date changes, Cascade change to start date, Cascade change to finish date, and Cascade change to start and finish dates.

2. Oracle Fusion Cloud Project Management Documentation, "Project Templates: Explained". This document details how settings in a template, including planning options like date cascading, are used to create new projects with predefined configurations.

A work type is a classification of work that is assigned to project tasks and expenditure items. It is a key attribute used to control financial processing. Within the work type definition, you can specify whether the work is billable or non-billable. Additionally, for intercompany or interproject billing, the work type determines the amount type (such as Raw Cost or Burdened Cost) to be used as the basis for calculating the transfer price, which is the internal price for cross-charging work.

B. event type: Event types are used to trigger billing and revenue recognition for specific project milestones or deliverables, not to classify the billability of all expenditure items.

C. cost type: This is not a standard Oracle Projects attribute for this purpose. Costs are classified by expenditure types, and their billability is determined by work types.

D. expenditure type: An expenditure type classifies the nature of a cost (e.g., Labor, Materials) but does not inherently determine its billability or transfer price basis; these are controlled by the work type.

Oracle Fusion Cloud Project Management Documentation, "Implementing Project Financial Management and Grants Management", Chapter: Project Foundation Configuration, Section: Manage Work Types. (This section explicitly states that work types determine if work is billable and the basis for transfer price calculations.)

Oracle Fusion Cloud Project Management Documentation, "Using Project Costing", Chapter: Manage Project Costs, Section: Work Types. (This guide explains how work types are assigned to transactions to drive their financial treatment.)

A project control budget records the total amount that can be spent on the project as a whole, and Resource budgets record the amount that can be charged to specific expenditure categories or resources. Both of these budget types are transferred to Budgetary Control so that funds‐availability checking can occur during commitment and expenditure entry. Other listed attributes are informational only and are not carried into the Budgetary Control ledger.

B. Expenditure item is a transaction, not a budgeting attribute accepted by Budgetary Control.

C. Project classification is a descriptive flexfield; funds are not controlled at this level.

D. Project plan type is a planning construct only; it is never posted to the control budget.

1. Oracle Fusion Project Portfolio Management Cloud

Implementing Project Financial Management and Grants Management

“Enable Budgetary Control for Projects

” Sec. 4.3 (23C

p. 69).

2. Oracle Fusion Financials Cloud

Using Budgetary Control

“Project and Resource Control Levels

” Sec. 3.2 (23C

p. 34).

Oracle Project Portfolio Management Cloud provides several File-Based Data Import (FBDI) templates to facilitate bulk data loading. Among the available options, templates exist for importing core project data such as Project Tasks (as part of the broader Projects and Tasks import), Project Budgets (for financial planning), and Project Billing Events (for contract billing). These templates are essential for data migration and integration with external systems, allowing for efficient creation and updating of key project financial and execution data.

D. Project Templates: While a process exists to import project templates, the question asks for three, and A, B, and C represent more common, transactional data imports for ongoing project management.

E. Capital Rate Schedule: Rate schedules are typically configured directly within the application's setup and maintenance tasks and are not loaded using a standard FBDI template.

- Oracle Help Center

"File-Based Data Import (FBDI) for Project Portfolio Management

" Release 24B

Document ID E95410-26. This guide provides a comprehensive list of available FBDI templates

including "Project and Task Import

" "Project Budget Import

" and "Project Billing Event Import."

For Microsoft Project tasks to be correctly identified and exported as milestones to Oracle Project Financial Management Cloud, they must conform to specific criteria that define them as event markers rather than work items. A milestone must have zero duration, indicating it is an instantaneous event. It must also have a single labor resource assigned with zero effort, signifying no work is consumed. Finally, its completion status must be binary, either 0% (not reached) or 100% (completed), as milestones cannot be partially complete.

A: A milestone represents an event with no work effort; therefore, an effort of 100 is incorrect.

B: A non-zero duration signifies a work task, not a milestone, which is an event marker with zero duration.

Oracle Project Management Cloud Using Project Management

24B

Chapter 6: Manage Project Plan

Section: Microsoft Project Integration

Subsection: "Export Tasks from Microsoft Project to Project Management". The documentation states: "To export a task as a milestone task

ensure that it has: Zero duration. A single labor resource assignment with an effort of 0. A percent work complete value of 0 or 100."

The Resource Availability Capacity Score is a metric used to evaluate a resource's availability. The calculation for this score is not performed for resources with complex calendars. A calendar is considered complex if it does not follow a standard seven-day week pattern or if it contains multiple patterns and shifts. The system excludes these to avoid potential inaccuracies in a standardized scoring model. Resource R fits this exclusion criterion, while resources P, Q, and S meet the prerequisites for the score to be calculated.

A. An active calendar (Resource P) is a prerequisite for the score to be calculated, not a reason for exclusion.

B. Having request dates within the calendar's effective dates (Resource Q) is a necessary condition for the calculation.

D. Having non-zero working days (Resource S) is required for a resource to be considered available and thus have a score calculated.

- Oracle Fusion Cloud Project Management, "Implementing Project Resource Management", Chapter: Set Up Project Resource Management, Section: How Resource Availability Capacity Score Is Calculated. (Doc ID: F68343-03, Release 23C). The documentation states, "The score isn't calculated for resources with complex calendars."

Rapid Implementation for Oracle Project Financial Management Applications provides pre-configured setups to accelerate deployment. The tool specifically includes configuration capabilities for Expenditure Types (defining how costs are categorized), Work Types (classifying different types of project work for billing and costing), and Project Types (establishing different categories of projects with specific attributes and controls). These are fundamental elements that must be configured early in the implementation process and are included in the rapid implementation framework to ensure standardized setup across the organization.

B. Project Templates - Templates are typically created after initial setup, not part of rapid implementation base configurations.

E. Project Class Categories - This is a more granular classification typically configured manually based on specific business requirements.

1. Oracle Project Financial Management Cloud Implementation Guide

Release 23B

Chapter 3: Rapid Implementation Overview

pp. 3-12 to 3-15

2. Oracle Fusion Applications Project Management Implementation Guide

Doc ID 2018.1

Section: "Rapid Implementation Configuration Elements"

3. Oracle Cloud Project Setup and Administration Guide

Release 23A

Chapter 2: Essential Configurations

pp. 2-8 to 2-11

4. Oracle Project Financial Management Cloud Using Rapid Implementation

Doc ID 2547892.1

Section: "Configurable Elements"

5. Oracle Fusion Cloud ERP Implementation Methodology Guide

Release 22D

Chapter 5: Project Management Setup

pp. 5-4 to 5-7

For Percent Spent billing in Oracle Project Contracts, you must configure the Invoice Method (to specify Percent Spent) and a Bill Plan (to define the billing schedule and frequency). The invoice method determines how amounts are calculated based on spent costs versus budget, while the bill plan establishes when invoices are generated. These two components work together to enable automated billing based on project expenditure percentages.

A. Billing events - Used for event-based billing, not required for Percent Spent method.

C. Expenditure items - These are captured automatically; no special setup needed for Percent Spent.

D. Billing controls - Optional controls for billing limits, not mandatory for basic Percent Spent setup.

3. References:

1. Oracle Fusion Project Billing Implementation Guide Release 23A, Chapter 4 "Invoice Methods", pp. 4-12 to 4-15

2. Oracle Fusion Project Contracts User Guide Release 23B, Section "Setting Up Bill Plans", pp. 8-7 to 8-11

3. Oracle Project Billing Configuration Guide 23C, "Percent Spent Invoice Method Setup", Section 3.4.2

4. Oracle Documentation Library - Project Portfolio Management Cloud, "Configure Project Billing" (Doc ID: E96297-01), Chapter 5

5. Oracle Fusion Applications Project Financial Management Implementation Guide 23A, "Invoice Method Configuration", pp. 11-8 to 11-12

1. Oracle Fusion Cloud Project Financial Management 23B

Using Project Contract Billing

chapter “Invoice Methods”

section “Percent Spent”

pp. 129-130.

2. Oracle Fusion Cloud Project Financial Management 23B Implementation Guide

task “Manage Bill Plans”

step 4 “Select Invoice Method”

pp. 312-313.

3. Oracle Help Center topic “Overview of Bill Plans and Invoice Methods” (accessed 26-Apr-2026).

To implement a borrowed and lent scenario where the transfer price equals the raw cost, two key setups are required. First, the transfer price rule must be defined to use a basis of "Raw Cost" and a calculation method of "Basis Only." This ensures the transfer price is a direct pass-through of the cost without any markup. Second, the specific types of costs to be cross-charged, such as labor hours recorded via a "straight time" document entry, must be enabled for cross-charge processing. This is done by checking the "Process Cross-Charge" option in the document entry configuration.

B. Transfer price basis must be Burdened Cost, and calculation method must be Burden Rate Schedule.

This is incorrect as the requirement is for raw cost. Burdened cost includes overhead, and a rate schedule implies applying a rate, not a direct pass-through.

D. Transfer price basis must be Raw Cost and calculation method must be Rate Schedule.

Using a "Rate Schedule" calculation method would apply a rate or markup to the raw cost, which contradicts the requirement for no further adjustments.

Oracle Fusion Cloud Project Management Documentation

Chapter: Project Costing Configuration: Define Borrowed and Lent Accounting. "For borrowed and lent processing

the transfer price is the same as the raw cost of the transaction. To meet this requirement

you must define a transfer price rule with the basis of Raw Cost and the method of Basis Only."

Oracle Fusion Cloud Project Management Documentation

Chapter: Project Costing Configuration: How Cross-Charge Transactions Are Processed. "You must enable the document entry for cross-charge processing."

Reference https://docs.oracle.com/cd/E51367_01/projectop_gs/OAPJC/F1071488AN1004C.htm

In Oracle Project Financial Management Cloud, approval groups are used to define sets of approvers for various transactions and processes. Static approval groups are the standard type supported, where members are explicitly defined and maintained. This allows administrators to create predefined groups of approvers that can be assigned to approval rules for project-related transactions such as budgets, forecasts, and project status changes.

A. Position - Not a valid approval group type in Oracle PFMC; positions are used in HR contexts.

B. Dynamic - Oracle PFMC does not support dynamic approval groups that change membership based on runtime conditions.

D. Flexfield - Flexfields are for data capture and reporting, not for defining approval groups.

E. Job - Jobs are HR classifications, not approval group types in the project management context.

- Oracle Fusion Cloud Project Management Using Project Financial Management (Release 23C), Chapter on Approvals Configuration

- Oracle Fusion Applications Project Financial Management Implementation Guide, Section on Setting Up Approval Management

- Oracle Cloud Managing Approvals documentation, Approval Groups chapter

When you expose Task as a social object, the selectable identifying attributes are limited to Project Number (to show the owning project) and Task Number (the unique task identifier). No other candidate attributes are delivered for the Task object, so only these two can be enabled for posting to Oracle Social Network.

A. Task – The attribute list contains Task Number, not a generic “Task” field.

D. Creation Date – Creation date is not in the delivered attribute list for Task.

E. Project – Only the numeric identifier (Project Number) is available, not the Project name object.

1. Oracle Fusion Cloud Project Management: Using Project Execution Management (24A), ch. “Collaborate on Projects with Oracle Social Network”, sec. “Enable Tasks as Social Objects”, Table “Attributes Available for Task”, p. 95.

2. Oracle Fusion Cloud Applications: Configuring Social Network Objects (23D), sec. “Task Object”, p. 7.

The Enterprise Project Structure (EPS) hierarchy viewer displays summarized data. The "Update Project and Resource Base Summaries" process calculates this data. When the summarization period option is set to 'Annual', the process uses the current system date to determine the calendar year for which to summarize the data. In this scenario, the job running on 15-Dec-2015 uses 2015 as the current year and therefore calculates and displays labor demand for the entire 2015 calendar year, not a rolling 12-month period from the current date.

A. "Current period start date" is vague; the calculation is based on the current calendar year derived from the system date, not an arbitrary period start date.

C. The project start date is irrelevant for calculating the ongoing annual labor demand summary; the current date determines the summarization year.

D. The "Update EPS" summarization job does not typically take a user-entered date as a parameter for the calculation period; it uses the system date.

1. Oracle Fusion Cloud Project Management, "Implementing Project Financial Management and Grants Management," Document ID F53510-07, Chapter: Summarize Project Data, Section: How Project and Resource Data Is Summarized. "For annual summarization, data is summarized for the current year."

2. Oracle Fusion Cloud Project Management, "Using Project Portfolio Management," Document ID F53512-06, Chapter: Monitor Project Performance, Section: Project Performance Data Summarization. "The summarization process uses the current date to determine the period for which it summarizes data."

A period cannot close with status Closed if it still contains expenditure items that require burden summarisation or unaccounted expenditure items that haven’t been swept forward. Either condition produces a “Closed with Error” status, preventing final closure.

A. Payables period status is independent of Project Accounting period closure.

B. Accounted, yet-to-be-imported transactions trigger only a warning, not an error.

D. Unaccounted transactions that are still outside PPM aren’t checked during closure; only items already in PPM matter.

1. Oracle Fusion Cloud Project Costing

Using Project Costing (23C)

“Accounting Period Close Exceptions

” p. 106–107.

2. Oracle Fusion Cloud Project Costing

Using Project Costing (23C)

“Sweep Unaccounted Transactions

” p. 108.

A project schedule in Oracle Project Management Cloud defines the working and non-working times for a project. It is constructed from three main elements. The question already mentions Shifts, which define working hours within a day (e.g., 8 AM to 5 PM). The other two core elements are Workday Patterns, which define a repeating sequence of shifts over a period (e.g., Monday to Friday work), and Exceptions, which are used to override the standard pattern for specific dates, such as public holidays or special non-working days.

B. Accounting Calendar: This is a financial calendar used for defining accounting periods for posting transactions to the general ledger, not for project work time.

D. Time Off: While employee time off affects resource availability, it is typically managed in HCM and reflected as an exception on a calendar, not a fundamental building element of the schedule itself.

E. Expenditure Type: This is a classification for project costs (e.g., Labor, Materials) and is unrelated to defining project schedules or working time.

Oracle Fusion Cloud Project Management Documentation

Chapter: Project Foundation Configuration

Section: "Schedules

Workday Patterns

and Shifts: How They Work Together". This section details that a schedule is composed of a workday pattern

which in turn is composed of shifts

and can be modified by exceptions.

Oracle Fusion Cloud Project Management Documentation

Chapter: Define Project Foundation Configuration

Section: "FAQs for Define Project Calendars and Periods"

Sub-section: "What's a schedule exception?". This explains that exceptions override the base schedule for specific dates.

The "Manage Project Transaction Sources" page is used to define how transactions from various feeder systems are processed in Oracle Project Costing. The core attributes of the source, such as whether transactions can be adjusted or reversed after being imported, are controlled in the main "Transaction Source" section of this page. Enabling the "Allow adjustments" and "Allow reversals" options in this section permits users to perform these actions on transactions originating from that specific source.

A. The "Documents" section defines settings for the transaction document itself, such as whether to import it, not the rules for adjusting individual transaction entries.

C. The "Document Entries" section defines attributes for the document entries, like mapping and validation, but the master control for allowing adjustments resides at the source level.

D. "Transaction Entries" is not a standard section on the "Manage Project Transaction Sources" page; the relevant sections are Transaction Source, Documents, and Document Entries.

1. Oracle Fusion Cloud Project Management

Implementing Project Financial Management and Grants Management (Release 24B)

Chapter 6: Define Project Costing Configuration

Section: "Project Transaction Sources: Explained". This section details the page components

showing that options like "Allow adjustments" are at the header level of the transaction source definition.

2. Oracle Fusion Cloud Project Management

Using Project Costing (Release 24B)

Chapter 2: Integrating with Other Applications

Section: "How Project Unprocessed Transactions Are Imported and Processed". This document describes how transaction source settings impact imported transactions.