SoftTech AI Registry
Oracle · Oracle Fusion Cloud Order Management

Purchase Orders to Sales Orders Converter

Oracle documents an Order Management AI agent that converts purchase orders received as PDF documents into Oracle sales orders. Users can upload one or more purchase-order PDFs for a selected business unit and click Create Order, and from release 26C a designated email account can be configured so that purchase orders arriving by email are picked up and converted without user intervention. Oracle states the agent gets the order into draft status rather than failing, optionally invoking the separate Sales Order Correction Assistant to resolve master-data mismatches.

Recorded characteristics

Function
Oracle: "Use an AI agent in Oracle Order Management to automatically convert a purchase order from a PDF file into a sales order." Two intake paths are documented for the same seeded template. Interactive path: Order Management work area, Sales Orders, Create Sales Orders from Purchase Orders; the user selects a business unit, uploads one or more PDF purchase orders and clicks Create Order, then reviews a process ID on the Action Status page and any entries under Issues Needing Your Attention. Email path, added in 26C: an inbound email account, monitored folder, authentication and polling interval are configured in AI Agent Studio, and "purchase orders coming into the designated emails get picked up automatically by the agent and converted to sales orders without user intervention", with an activity trace showing the source email and its attachments.
Data access
Purchase-order PDF documents supplied by upload or as email attachments; for the email path, the monitored mailbox folder and message contents. Oracle states the PDF must contain values for Customer, Ordered Date, Purchase Order Number, Ship-to Address, Item, Quantity and Unit Price, and that any other order attribute may optionally be included. When the Sales Order Correction Assistant is configured, Oracle states smart matching compares purchase-order values with Oracle master and setup data for Customer, Account, Address, Payment Term, Item, Item Description, Salesperson, Currency, FOB, Freight Terms and Shipping Method, and that it can examine a customer's most recent 20 sales orders to find attribute values.
Actions
Can take actions
External actions
Unknown
Human confirmation
Conditional
Permission basis
Not established
Administrative control
Oracle documents an administrator-driven setup: set the profile option Enable VBCS Progressive Web Application User Interface (ORA_HCM_VBCS_PWA_ENABLED) to Y at site level; open Tools, AI Agent Studio and find the Purchase Order to Sales Order Converter template; use Actions, Copy Template with a suffix; publish the copy and confirm its status is Published; note the resulting agent team code, for example PURCHASEORDERTOSALESORDERCONVERTOR_1; and set the convertPOtoSOAgentName attribute on the Sales Orders page through Visual Builder Studio. Optional automatic error fixing requires repeating the same steps with the Sales Order Correction Assistant template and setting salesOrderCorrectionAgentName. The email path additionally requires adding an email account under AI Agent Studio, Credentials, Email Accounts with account name, email address, email folder and authentication details (tenant ID, client ID, secret), plus workflow variables including businessUnitName and an email trigger. Access requirements documented include SCM Intelligent Agent Management Duty (both ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY and ORA_RCS_SCM_AI_AGENT_MANAGEMENT_DUTY_HCM), Fai Genai Agent SCM Administrator Duty, Fai Genai Agent Runtime Duty for interacting with agents in product pages, permission groups enabled in the Security Console, and the View Orders privilege (FOM_VIEW_ORDERS_PRIV).
Default state
Disabled
Availability
Documented for Oracle Fusion Cloud Order Management in the redesigned (Redwood) Order Management pages. Oracle introduced the converter in release 25D, described automatic error fixing and draft-status outcomes in 26A, and added the email intake channel in 26C. A living implementation-guide page maintained outside a single release describes the upload path, template setup and error correction; as fetched it does not yet describe the 26C email channel.
Licensing
Not established. No Oracle primary page reviewed states a licence, entitlement or additional charge for this agent.
External model or provider
Not established. Oracle does not name a model or model provider for this agent in the documentation reviewed.
Limitations and uncertainty
Oracle does not state whose identity the resulting sales-order writes execute under, so permission basis is recorded as not established; the documented duties cover administrator setup and interacting with agents in product pages rather than proving the runtime write identity, although a "Created by Agent" filter indicates some agent attribution exists. Oracle states the order is placed in draft status; no primary text reviewed establishes automatic submission, order import, approval, reservation, release, picking, shipping, invoicing, payment or revenue recognition, and Oracle notes that if the sales order is imported it must be imported through REST API. Oracle describes matching against existing master and setup data with an error displayed when matching fails, and does not establish that the agent creates customer or item master records. Unit price is listed as a required extracted attribute but is not listed among the smart-matched attributes, and no interaction with Oracle pricing rules is documented. Oracle does not establish whether the source PDF remains attached to the created order, whether multiple uploaded PDFs map one-to-one to orders, allowed senders or supported attachment types for the email channel, scanned-image PDF support, or file-size limits. No AI-specific audit store is established beyond the process ID, Action Report, Issues Needing Your Attention and the AI Agent Studio Monitoring and Evaluation activity trace.

Evidence