SoftTech AI Registry
Oracle · Oracle Fusion Cloud Manufacturing

Work Order Completion Assistant

An Oracle-documented AI agent, introduced in Update 26B, that a production supervisor invokes from the Manage Work Orders page to check manufacturing work orders in Awaiting Review for Completion status for anomalies related to issued materials, reported resources, completed outputs and open exceptions, and that then completes the work orders that have no anomalies. The physical manufacturing has already occurred on the factory floor; the agent reviews recorded execution data and changes work order completion status. It is unavailable where electronic signatures and electronic records are enabled for Manufacturing Work Order Completion Approval.

Recorded characteristics

Function
Oracle documents the Work Order Completion Assistant as an AI agent of Agent Type "Workflow" that "streamlines the manufacturing work order completion process by validating the material, resource, output requirements, and open exceptions". A production supervisor invokes it from the Manage Work Orders page using the "Use Completion Assistant" menu option. Oracle's agent description states: "This agent checks for anomalies in work orders that are awaiting review before completion. The agent checks for anomalies related to issued materials, reported resources, completed outputs, and any open exceptions. The agent then proceeds to complete the work orders that have no anomalies." Eligible work orders are those "completed on the factory floor" and "currently in an 'Awaiting Review for Completion' status", a status Oracle defines (Update 26A) as meaning "the last operation of the work order has been completed, and the work order is under review and awaiting submission for completion approval". For work orders without discrepancies Oracle states "you can use the assistant to approve and bulk update their status to 'Completed.'" For work orders with discrepancies Oracle states "you can manually resolve any pending transactions before attempting to complete the work orders again". The manufacturing activity itself occurred on the factory floor before the agent runs; Oracle does not establish that the agent manufactures goods, operates machinery, physically consumes materials, performs labour, performs inspections or controls factory equipment. Oracle documents the feature for discrete and process manufacturing work orders.
Data access
Oracle establishes that the agent examines work orders in Awaiting Review for Completion status and checks anomalies related to issued materials, reported resources, completed outputs and open exceptions, and that it validates material, resource and output requirements. Oracle does not publish a field-level inventory of the data the agent reads, does not state whether it evaluates all eligible work orders in the plant or only work orders selected or displayed on the Manage Work Orders page, and does not enumerate which material, resource, output or exception attributes (for example shortages, over-issue, lot or serial data, pending transactions, scrap, co-products, by-products, or specific exception types) are compared. Broader Manufacturing or SCM data access beyond the documented work order completion review is not established.
Actions
Can take actions
External actions
Unknown
Human confirmation
Not established
Permission basis
Not established
Administrative control
Oracle documents these administrative controls: the plant parameter "Enable manual completion of work orders" must be enabled under Setup and Maintenance > Manage Plant Parameters (Work Execution tab, Execute Production); the agent team must be created and published in Oracle AI Agent Studio using the preconfigured template (Use Template or Copy Template); and the Agent Team Code must be added in Visual Builder to the manage-work-orders page of the Production Supervisor Workbench and/or the Work Orders page and the changes published. Oracle further states the feature "is available only if electronic signatures and electronic records are not enabled for 'Manufacturing Work Order Completion Approval'". Administration of SCM AI agents requires the SCM Intelligent Agent Management Duty (ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY and ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY_HCM) and Fai Genai Agent SCM Administrator Duty roles.
Default state
Disabled
Availability
Oracle introduced the feature in Update 26B. The 26B Manufacturing Feature Summary lists "AI Agent: Work Order Completion Assistant" with Impact to Existing Processes "None" and Action to Enable "Setup Required". Oracle's current Redwood feature catalogue for Supply Chain & Manufacturing continues to list "AI Agent: Work Order Completion Assistant", Update 26B, Setup Required, "Does not expire". Oracle documents applicability to discrete and process manufacturing work orders and states the feature is available only where electronic signatures and electronic records are not enabled for Manufacturing Work Order Completion Approval. Oracle does not publish explicit general-availability or preview wording, region, language or environment restrictions for this agent in the reviewed documentation.
Licensing
Oracle does not publish separate licensing terms for this agent in the reviewed documentation. It is documented as a feature of Oracle Fusion Cloud Manufacturing that requires Oracle AI Agent Studio for Fusion Applications for agent creation and publication. Whether additional licensing applies is not established.
External model or provider
Not established
Limitations and uncertainty
Oracle does not state the mechanism behind the anomaly checks: whether they are deterministic validations, predefined business rules, generative reasoning, an anomaly model or configurable thresholds is not established; the agent is only labelled Agent Type "Workflow". Oracle's wording is not fully resolved on human confirmation: the narrative says "you can use the assistant to approve and bulk update their status", while the agent description says "the agent then proceeds to complete the work orders that have no anomalies"; no explicit per-work-order approval click is documented, so human confirmation is recorded as not established. Oracle does not document the exact completion mechanism (whether the agent calls a completion tool or API, or triggers Oracle's deterministic status-transition processing), whether operation statuses also change, whether completion transactions or completed quantities are created or changed by the agent, or any inventory effect caused by the agent. Oracle does not establish the runtime identity under which the completion occurs; the documented privileges (Manage Work Execution Work Area, Manage Work Order Headers, View Work Orders, Fai Genai Agent Runtime Duty) establish access eligibility, not execution identity. Oracle does not state whether the agent explains discrepancies, recommends fixes, creates correction transactions or modifies discrepant work orders in any way, nor whether a maximum batch size applies or whether bulk completion is one transaction or per-work-order actions. Oracle does not state whether the agent can be invoked on a schedule, in the background or by an event; the documented invocation is a supervisor selecting "Use Completion Assistant". Downstream Oracle processing after status Completed - including closure, costing, variance calculation, accounting and general ledger posting - is not attributed to the agent, and Oracle does not document any such effect performed by the agent. Oracle documents Completed and Closed as distinct work order statuses; the agent is documented only in relation to reaching Completed. No external notification, external MES interaction, equipment control or write outside Oracle Fusion Manufacturing is documented, and no affirmative statement excluding such behaviour was found, so external action capability is recorded as unknown. Oracle does not name a model or provider for this agent.

Evidence