Project Change Order Initiation Assistant

Oracle generative AI feature in Oracle Fusion Cloud Project Management that generates a draft change order, including budget and forecast impact, from an existing project issue when a project manager clicks Initiate Change Order. The project manager reviews, optionally regenerates, edits and explicitly saves the change order; Oracle documentation does not establish that the assistant itself submits, approves or implements a change order, or that it updates a project budget.

Recorded characteristics

Function

Oracle documents that a project manager opens a project issue in the Project Management work area and clicks Initiate Change Order, and that the application generates a change order from the information available in the issue. Oracle states the project manager can "refine the generated draft before saving", then reviews the generated change order, updates details as needed, provides additional details and clicks Regenerate until the draft meets requirements, and finally clicks Save. Oracle states that each Regenerate creates a revised version of the entire draft change order rather than updating selected sections. Oracle's 26C release documentation states the feature can "also extract and create detailed budget impacts automatically", and the Change Orders documentation states the generated change order "includes budget and forecast impact, and it can include detailed impacts when a baseline budget version exists". Oracle documentation establishes the highest AI-performed step as generating a draft change order with budget and forecast impact content inside the Initiate Change Order flow; persistence of the change order record follows an explicit user Save. Oracle does not document the assistant submitting the change order for impact assessment, review, approval or implementation, and does not document the assistant approving or implementing anything. In Oracle's documented change order lifecycle, a human owner moves the change order through stages, an Approver provides approval, and an Implementor selects Implement and Mark Complete, which is the action that includes the budget impacts and creates a new baseline budget version (or a new version submitted for approval where the baseline budget version is workflow enabled). Those later steps are deterministic, human-initiated Oracle processes and are not attributed to the AI.

Data access

Oracle documents that the generation uses "the information available in the issue" and details the project manager provides in the Initiate Change Order dialog box. Oracle does not enumerate which specific issue attributes the assistant reads. Oracle separately documents project issue attributes as task, type, priority, status, action items and attachments. Oracle documents that the generated change order includes budget and forecast impact and can include detailed impacts when a baseline budget version exists, and that for rate-based resources amounts are calculated from the rate settings of the current baseline budget version; Oracle does not state precisely which project financial data the assistant itself reads. Broader access to project data beyond these documented points is not established.

Actions

Generative only

External actions

Unknown

Human confirmation

Required

Permission basis

User permissions

Administrative control

Oracle documents the following controls: enablement through the Opt In UI; enabling the Change Order Generation from Project Issue feature through FSM Opt In in the Project Execution Management offering; enabling permission groups in Security Console for each role that will use the feature, including adding the feature-specific duty role and any required runtime duty role to the role hierarchy, and adding the appropriate feature-specific AI assistance duty role to custom roles; the Project Change Order Initiation Assistant (ORA_PRJ_PJE_CHANGE_ORDER_INITIATION_ASSISTANT_TEAM) duty role and Manage Project Work Plan Data (PJT_MANAGE_WORK_PLAN_DATA) data privilege; the Manage Project Changes privilege required to create a change order, perform impact assessment, review and approve a change order; the Manage Project Budget Working Version privilege required to manage change order budget impact; and the Create Project Budget Baseline Version privilege required to automatically implement a change order with budget impacts. Oracle also documents human review, editing and Regenerate before saving, participant and approver assignment, and a change order approval stage that cannot be skipped when an approver is added.

Default state

Disabled

Availability

Documented in Oracle Fusion Cloud Applications 26C readiness documentation for Project Management (What's New page dated 28 AUG 2026) under Offering: Project Execution Management, and in the Oracle Fusion Cloud Project Management 26C Using Project Execution Management guide (page dated 01 JUL 2026). Oracle marks the feature as enabled through the Opt In UI. Oracle does not use GA or preview terminology on this feature page. Oracle's 26C page states the system automatically generates the change order in the user's preferred language; Oracle's earlier 24D page for the predecessor feature stated availability was limited to English, French and Spanish with other languages generated in English. No region restrictions are documented on the 26C page.

Licensing

No specific licensing terms, entitlement or pricing for this feature are established in the Oracle documentation reviewed. Oracle documents the required opt-in, duty role and privileges rather than a licence. Oracle states the feature is now migrated to Fusion AI Agent Studio; any licensing implication of that framework is not established for this feature.

External model or provider

Not established

Limitations and uncertainty

Oracle does not enumerate the specific project issue fields the assistant reads. Oracle does not state whether the generated draft is persisted as a change order record before the user clicks Save; Oracle's wording is that the project manager can refine the generated draft before saving, so the registry records persistence as following the explicit user Save rather than as an AI-performed write. Oracle does not document the assistant submitting, approving or implementing a change order, and does not document the assistant updating a working project budget, creating or submitting a budget version, or baselining a budget. Oracle documents no accounting journal creation, cost posting, revenue recognition, invoice creation, expenditure approval, payment instruction or money movement by this assistant; these are recorded as not established rather than as affirmative negatives. No external-system boundary is established, so external action capability is unknown. Oracle states the feature was previously available in Prompt Lab as the 24D Change Order Generation from Project Issue feature and is now migrated to Fusion AI Agent Studio; the 24D and 26C feature descriptions are materially the same text, so the registry treats this as the same capability migrated and renamed rather than a new or expanded capability, and no separate historical capability record was created. Oracle does not name the underlying model or provider. The primary release-note evidence is pinned to Update 26C and may be superseded by later releases.

Evidence

• Project Change Order Initiation Assistant (Oracle Fusion Cloud Applications 26C What's New, Project Management)

  Supports: General · Function · Actions · Human confirmation · Permission basis · Admin controls · Default state · Availability · Limitations · External model · Licensing · Primary source

  Oracle 26C names the feature Project Change Order Initiation Assistant under Offering: Project Execution Management.

  "Leverage generative AI to create a change order from a project issue... With the ability to also extract and create detailed budget impacts automatically."

  Tips state the Regenerate option "create[s] a revised version of the draft change order", establishing a draft output rather than an approved change.

  Oracle documents generation from the Initiate Change Order dialog box with user-supplied detail and regeneration under user control.

  Access requirements: Project Change Order Initiation Assistant (ORA_PRJ_PJE_CHANGE_ORDER_INITIATION_ASSISTANT_TEAM) duty role and Manage Project Work Plan Data (PJT_MANAGE_WORK_PLAN_DATA) data privilege, included with the seeded Project Manager job role.

  Opt In UI, FSM Opt In of the Change Order Generation from Project Issue feature, and Security Console permission groups per role.

  Feature is not available until opt-in and permission-group enablement are completed.

  26C What's New page dated 28 AUG 2026; generation occurs in the user's preferred language.

  "Previously available in Prompt Lab, the 24D Change Order Generation from Project Issue feature is now migrated to Fusion AI Agent Studio."

  Oracle describes only "generative AI" and Fusion AI Agent Studio; no model or provider is named.

  Oracle documents opt-in, duty role and privilege requirements; no licence terms stated for this feature.

• Generate a Change Order from a Project Issue (Using Project Execution Management 26C)

  Supports: Function · Actions · Human confirmation · Data access · General · Limitations · Primary source

  "You can generate a change order from a project issue using Oracle AI"; the project manager generates it directly from information in the issue.

  Documented steps: open an issue, click Initiate Change Order, review the generated change order, Regenerate, then click Save.

  "the project manager can generate it directly from the information in the issue and refine the generated draft before saving"; the user must click Save.

  Generation uses information available in the issue plus detail provided in the Initiate Change Order dialog box.

  Results: the change order includes budget and forecast impact, and detailed impacts if there's a baseline budget version.

  Each Regenerate creates a revised version of the entire draft change order and does not update only selected sections.

• Change Orders (Using Project Execution Management 26C)

  Supports: Function · Actions · Human confirmation · Admin controls · General · Limitations · Primary source

  "Project managers can generate a change order from an issue using Oracle AI by clicking Initiate Change Order in the issue."

  Change order lifecycle: Create stage has Draft status after the creator initiates the change order; the owner submits for impact assessment, review, approval or implementation.

  Approver responsibilities and the non-skippable Approval stage are assigned to human participants, not to the AI.

  Creator, Owner, Participant, Reviewer, Implementor and Approver responsibilities govern change order progression.

  "The financial project plan is automatically updated when the Implementor selects Implement and Mark Complete" - a human-initiated later step, not an AI action.

  Budget and forecast impact on a generated change order is distinct from the approved project budget, which changes only at implementation.

• Change Order Automation for Project Budget Adjustments (Using Project Execution Management 26C)

  Supports: General · Actions · Permission basis · Admin controls · Data access · Limitations · Primary source

  Budget impacts are recorded through the Add Impact dialog box with Budget and Forecast impact area, task, resource, quantity, currency, raw cost and revenue values.

  Only at implementation does Implement and Mark Complete include the budget impacts and create a new baseline budget version, or submit a new version for approval when the baseline is workflow enabled.

  Manage Project Changes, Manage Project Budget Working Version and Create Project Budget Baseline Version privileges govern change order and budget impact operations.

  Detailed budget impact assessment and automatic implementation require a baseline budget version created from an approved financial plan type; only one change order can be implemented at a time.

  For rate-based resources, impact amounts are calculated from the rate settings of the current baseline budget version.

  Project budget change is an outcome of human implementation and baselining, not of the assistant.

• Create a Change Order and Add Impacts (Using Project Execution Management 26C)

  Supports: General · Actions · Admin controls · Primary source

  Change order impact areas are Project Plan, Resource, Requirement, Budget and Forecast, and Contract.

  Manual creation flow requires naming, saving and assigning participants; impacts are added as separate impact entries on the change order.

  Participants and their responsibilities are assigned by people; change orders with detailed budget impacts sit in approved status pending implementation.

• Project Issues (Using Project Execution Management 26C)

  Supports: Data access · Limitations · Primary source

  Documented project issue attributes are task, type, priority, status, action items and attachments; Oracle does not state which of these the assistant reads.

  Oracle does not enumerate the issue fields consumed by the assistant, so issue data access is recorded conservatively.

• Project Manager (Job Role) (Oracle Fusion Cloud Project Management 26C Security Reference)

  Supports: Permission basis · Admin controls · Primary source

  The seeded Project Manager job role inherits the Project Change Order Initiation Assistant duty role, indicating the feature runs under the invoking user's granted roles.

  Role hierarchy shows the assistant duty role as an administrable component of the Project Manager job role.

• Change Order Generation from Project Issue (Oracle Fusion Cloud Applications 24D What's New, Project Management)

  Supports: Limitations · Availability · Default state · Primary source

  24D predecessor feature Change Order Generation from Project Issue carries materially the same description, supporting a rename/migration rather than a new capability.

  24D documented availability in English, French and Spanish only, with other languages generated in English; 26C states generation in the user's preferred language.

  24D feature was also enabled through the Opt In UI under the Project Execution Management offering.