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.