SoftTech AI Registry
Oracle · Oracle Fusion Cloud Order Management

Sales Order Correction Assistant

Oracle AI Agent Studio agent for Oracle Fusion Cloud Order Management that runs on a configured schedule, identifies failed sales orders, analyses order header and order line error messages, creates an action request, invokes a Smart Match Service that fuzzy matches error values against master data, updates order interface table values with corrected values, logs corrections as warnings, and triggers the Import Sales Order ESS job to reprocess the corrected order. Oracle documents no fulfillment, shipping, invoicing or payment authority for the agent.

Recorded characteristics

Function
Oracle 26C documents a seven step flow. (1) The agent identifies failed orders based on the Workflow Agent Parameter Schedule, by default going back seven days from the current date. (2) The agent analyzes error messages for the order header and order lines and identifies any errors. (3) The agent creates an action request for the problem orders to enable tracking of corrections, with action type Resolve Import Exceptions. (4) The agent invokes the Smart Match Service, which performs fuzzy matching of the error values against master data such as Customer, Address, Items, Shipment attributes and Billing attributes; if the confidence percentage is over the value specified in the agent (80%) it uses the value found to update the interface table value, otherwise it checks the previous 10 orders for the same customer and checks frequently used values for the error attribute. (5) The agent updates the interface table data with the corrected values, and the corrections are logged as warnings against the action request. (6) The agent triggers the Import Sales Order ESS job to process the corrected order. (7) During reprocessing the order may get imported successfully or new errors may be logged; status is visible against the action request or against the order if it was imported successfully. Oracle states the agent addresses errors related to customer, addresses, item, UOM, description, salesperson, currency, FOB, freight terms, shipping method, shipment priority, warehouse, subinventory, supplier, supplier site, sales channel, demand class, line type, invoicing rule and accounting rule. Oracle states the agent automatically resolves most problems or guides the user to manually fix identified problems. The registry attributes to the AI only: failed-order identification, error analysis, action request creation, smart match invocation, interface table value updates, warning logging and triggering the Import Sales Order scheduled process. The actual import validation and order creation are performed by the deterministic Import Sales Orders scheduled process, a standard Oracle Order Management job requiring the Import Order (FOM_IMPORT_ORDER_PRIV) privilege, and any subsequent orchestration, scheduling, reservation, shipping, invoicing or payment is ordinary Order Management and downstream processing that Oracle does not attribute to this agent.
Data access
Oracle documents the agent working with failed sales orders identified within the schedule lookback window, error messages on the order header and order lines, order import interface table data (the Oracle FBDI Import Sales Orders interface tables such as DOO_ORDER_HEADERS_ALL_INT and DOO_ORDER_LINES_ALL_INT), master data used by the Smart Match Service (Customer, Address, Items, Shipment attributes, Billing attributes and so on), and the previous 10 orders for the same customer used to check frequently used values for the error attribute. Oracle also documents action requests created by the agent for tracking. Access beyond these documented categories, including access to the wider Order Management dataset, fulfillment state or financial records, is not established.
Actions
Can take actions
External actions
Conditional
Human confirmation
Conditional
Permission basis
Not established
Administrative control
Oracle documents the following controls. Setup and Maintenance profile option Enable VBCS Progressive Web Application User Interface (ORA_HCM_VBCS_PWA_ENABLED) must be set to Y at site level. In AI Agent Studio, an administrator searches for the Sales Order Correction Assistant template, uses Actions > Copy Template with a version suffix, clicks Publish and confirms the agent status is Published, then queries the Agent Team and copies the Agent Team Code. Scheduling is performed from the agent Settings icon: the Triggers tab defines a start and end date for the agent to run, and the Variables tab defines email preferences and number of days. The confidence threshold is a value specified in the agent (80% in Oracle's description). Access requires configured job roles containing SCM Intelligent Agent Management Duty (ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY and ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY_HCM), Fai Genai Agent SCM Administrator Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_SCM_ADMINISTRATOR_DUTY), Fai Genai Agent Runtime Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_RUNTIME_DUTY) for interacting with agents in product pages, enabled permission groups in Security Console, and the View Orders (FOM_VIEW_ORDERS_PRIV) privilege. Review surfaces documented by Oracle include the action request with process status (in progress, completed, completed with errors), the Process ID drill-down showing the order number and the corrected errors, warnings displayed on the imported order that are cleared on submit, the Validation Error filter on the Sales Orders page, and an optional list of corrections emailed to specified email IDs.
Default state
Disabled
Availability
Documented in Oracle Fusion Cloud Applications 26C readiness documentation for Supply Chain Management, Order Management module (What's New page dated 10 SEP 2026), and listed as Sales Order Correction Assistant, Update 26C, type AI agent in Oracle's Supply Chain & Manufacturing features with AI list. Oracle's 26C Order Management feature summary table lists the feature with Impact to Existing Processes of Report and Action to Enable of None, while the feature page itself documents a required profile option, AI Agent Studio Copy Template, Publish and scheduling steps; the registry records this as a documentation conflict and classifies the default state from the feature page's enablement steps. Oracle does not use GA or preview terminology on this feature page. No regions, languages or environment restrictions are documented. Oracle notes the redesigned (Redwood) pages must be used for this feature.
Licensing
No licensing terms, entitlement or pricing for this feature are established in the Oracle documentation reviewed. Oracle documents profile option, AI Agent Studio template publication and duty role requirements rather than a licence. Any licensing implication of Oracle AI Agent Studio for Fusion Applications is not established for this feature.
External model or provider
Not established
Limitations and uncertainty
Naming: Oracle uses both Sales Order Correction Assistant (feature title, AI Agent Studio template name, AI features list) and Sales Order Correction Agent (benefits paragraph of the same page, and the 26C Purchase Order to Sales Order Converter via email page). Oracle uses these interchangeably for the same AI Agent Studio agent, so the registry records one capability and notes the naming inconsistency. Eligibility: Oracle states the agent identifies failed orders based on the Workflow Agent Parameter Schedule with a default seven day lookback, and the introduction refers to problems "in your import data and orders submitted to fulfillment". Oracle does not define exact eligible order states, does not distinguish warnings from errors for eligibility, and does not document a maximum record count; eligibility beyond the documented statements is not established, and every documented correction example operates on interface table data. "Learns over time": Oracle's description says the agent "automatically resolves most problems based on what it learns over time", but the only documented mechanisms are fuzzy matching against master data with an 80% confidence threshold and, below that threshold, checking the previous 10 orders for the same customer for frequently used values, with history enhancing the confidence score. No model training, feedback loop or persisted learned mapping store is documented, so the learning mechanism is recorded as not established. Persistence: Oracle documents the agent updating interface table values and logging corrections as warnings against an action request; Oracle does not document the agent editing an already-created sales order record directly, nor changing order status itself. Reprocessing means triggering the Import Sales Order ESS job, not order validation or fulfillment performed by the agent. Fulfillment boundary: Oracle documents no inventory reservation, line scheduling, warehouse release, shipment creation, picking, packing, shipping, invoicing, revenue recognition or payment collection by this agent; these are recorded as not established rather than as affirmative negatives, and any such steps belong to ordinary Order Management orchestration and downstream applications. Financial boundary: Oracle documents no authority for this agent to change prices, discounts or tax, create invoices or accounting entries, capture payments, issue refunds, change credit exposure or recognise revenue; the documented correction list includes invoicing rule and accounting rule attributes on failed import data, which is an import-data correction rather than accounting authority. Runtime identity: the documented duty roles govern managing agents and interacting with agents in product pages; Oracle does not state under which identity the scheduled agent run updates interface tables or submits the ESS job, so permission basis is not_established. External action: correction and reprocessing stay inside Oracle Fusion, but the agent has a documented option to send the list of corrections in a run to specified email IDs, configured when the agent is copied and customised; Oracle attributes this option to the agent without naming a separate sending component, so external action capability is conditional. Human confirmation: automatic corrections and reprocessing occur without documented per-order approval once the agent is scheduled, while Oracle states the agent guides users to manually fix problems it cannot resolve, and review occurs after the fact through the action request and order warnings; confirmation is therefore conditional. Oracle does not name the underlying model or provider. Primary release-note evidence is pinned to Update 26C and may be superseded by later releases.

Evidence