SoftTech AI Registry
Oracle · Oracle Fusion Cloud Inventory Management

Goods Return Assistant

Oracle AI Agent Studio agent documented in Update 26C under the Receiving module of Oracle Fusion Cloud Inventory Management. The user enters the item, organization and quantity to return; the assistant searches receipts within a configurable lookup window, automatically creates the return against the single matching receipt, or displays multiple matching receipts for the user to select one, then creates the return and shows a confirmation message with a link to it. A configuration parameter determines whether returns are created in incomplete status (default) or submitted after creation, and an optional parameter emails return details to the user who created the return. Oracle documents no supplier contact, shipping, inventory movement or accounting authority for the agent itself.

Recorded characteristics

Function
Oracle 26C documents the flow as follows. The user enters the item, organization and quantity to return. The AI assistant then searches for matching receipts and creates the return against the appropriate receipt. If there is only one receipt matching the entered item and organization in the receipt lookup date range, the AI assistant automatically creates the return against that receipt. If multiple matching receipts are found, the assistant displays the matching receipts and the user selects the receipt against which the return should be created. After the return is created, the AI assistant displays a confirmation message with a link to the return, which the user can open to view the return details. Oracle positions the agent as providing intelligent prompts and recommendations for less experienced users and a streamlined workflow for inventory and receiving managers. Three documented configuration parameters govern its behaviour: ReceiptLookupDays (how many days of receipt history the assistant searches when looking for matching receipts, default 30 days), SendEmail (whether an email with return details is sent to the user who created the return, default false), and ReturnStatusIncomplete (whether returns are created in incomplete status or submitted immediately, default Yes; when Yes returns are created in incomplete status, when No returns are submitted after creation). The registry attributes to the AI only: receipt search within the lookup window, automatic creation of the return where exactly one receipt matches, presentation of candidate receipts where several match, creation of the return against the selected receipt, the configured submission behaviour and the confirmation message with link. Everything downstream - Oracle Receiving return transaction processing, any Return to Receiving / Return to Supplier / Return to Customer transaction generation, purchase order reopening, debit memo creation, on-hand and received quantity effects, shipping of returned goods and any supplier-side handling - is ordinary Oracle Receiving and downstream processing that Oracle does not attribute to this agent.
Data access
Oracle documents the agent taking the item, organization and quantity entered by the user, and searching receipts within the ReceiptLookupDays window for receipts matching the entered item and organization. Oracle's narrative also frames the problem in terms of not knowing which receipt goods came from and which supplier and purchase order they were tied to, but does not state that the agent reads or returns supplier or purchase order attributes, so supplier and purchase order data access is recorded as not established. Access to any wider inventory, procurement, costing or financial dataset is not established.
Actions
Can take actions
External actions
Conditional
Human confirmation
Conditional
Permission basis
Not established
Administrative control
Oracle documents these controls. AI Agent Studio: administrators use or copy the preconfigured Goods Return Assistant agent template to create agents; Copy Template automatically adds a suffix to all artifacts in the agent team and navigates to the agent team canvas where agent team settings, agents, tools and topics can be edited, while Use Template steps through configuring each artifact. The agent must be published. After publishing, the agent is added to a page by including it in the guided journey of that page, by creating an Agent task of type Workflow Agent for the agent and adding it to the guided journey. Parameters are changed from the Set Default Parameters node via More Options > Edit, updating values and clicking Update: ReceiptLookupDays (default 30 days), SendEmail (default false) and ReturnStatusIncomplete (default Yes). ReturnStatusIncomplete is the key authority control: leaving it at Yes means the agent creates returns in incomplete status, while setting it to No means returns are submitted after creation, so an administrator setting alone changes the agent from create-only to create-and-submit without any change in user interaction. Access requirements: 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, both required) and Fai Genai Agent SCM Administrator Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_SCM_ADMINISTRATOR_DUTY) to manage SCM AI agents; Fai Genai Agent Runtime Duty (ORA_DR_FAI_GENERATIVE_AI_AGENT_RUNTIME_DUTY) to interact with AI agents in product pages; permission groups enabled in the Security Console on those users' configured job roles; privileges allowing access to the pages where AI agents are enabled; and Receiving Transaction Maintenance Duty (ORA_RCV_RECEIVING_TRANSACTION_MAINTENANCE_DUTY) for users who can access this feature.
Default state
Disabled
Availability
Documented in Oracle Fusion Cloud Applications 26C readiness documentation for Supply Chain Management, Inventory Management What's New document, Receiving module. The 26C revision history records the feature as added on 26 JUN 2026 under module Receiving. The 26C feature summary table lists Receiving | AI Agent: Goods Return Assistant with Impact to Existing Processes of None and Action to Enable of Setup Required. Oracle's definitions state that features with Impact of None are not delivered enabled and need steps to use. Oracle uses no GA or preview wording for this feature, and documents no regions, languages or environment restrictions. Use of Oracle AI Agent Studio for Fusion Applications is required to deploy the template.
Licensing
No licensing terms, entitlement or pricing for this feature are established in the Oracle documentation reviewed. Oracle documents AI Agent Studio access duty roles, Receiving duty roles and setup steps rather than a licence.
External model or provider
Not established
Limitations and uncertainty
Transaction object: Oracle says the assistant "creates the return" against a receipt but does not name the underlying Oracle business object, transaction type or status model in the feature page, so the exact persistent object is recorded as not established. Oracle separately documents receipt-referenced returns in Using Receiving (where returning to a supplier causes Oracle Receiving to create both a Return to Receiving and a Return to Supplier transaction and reopen the purchase order for the return quantity) and documents a Receiving Returns REST resource under Inventory Management with create, update, delete and submitForApproval operations, plus a receivingReceiptRequests submitForApproval action for receiving corrections and returns; the registry records these as the surrounding Oracle return model, not as an attribution of any specific object to the agent. Return type: Oracle does not state whether the created return is a return to supplier, to customer or to receiving; the feature page says only that the return is created against the matching receipt. Input fields: only item, organization and quantity are documented as user input, with receipt selection where multiple receipts match; no receipt, supplier, purchase order, location, subinventory, lot, serial, reason, return date or comment input is documented for the agent. Zero matches: Oracle documents the single-match and multiple-match cases only; behaviour when no receipt matches is not established. Matching: Oracle documents matching on item and organization within the receipt lookup date range. No quantity, supplier, purchase order, receipt status or eligibility matching rule is documented for the agent, and no semantic or AI reasoning over receipts is claimed; ReceiptLookupDays is documented only as how many days of receipt history the assistant searches. Submission: Oracle states returns are "submitted after creation" when ReturnStatusIncomplete is No, but does not define in this feature page what submission validates, completes or changes. Quantity effects: Oracle does not state that creating or submitting a return through the agent changes received quantity or on-hand inventory; the inventory effect of the agent's actions is not established. Physical and supplier boundary: no supplier notification, return material authorization, shipping document, outbound shipment, carrier request, supplier debit or supplier record update is attributed to the agent, and no physical movement of goods is attributed to it. Financial boundary: no accounting entry, accrual reversal, receipt accounting change, debit memo, invoice matching change, AP adjustment, refund or payment authority is established for the agent. Email: Oracle documents the SendEmail parameter as determining whether an email with return details is sent to the user who created the return, defaulting to false; Oracle does not name the sending component, does not describe the email content beyond "return details", and does not state whether it is conditional on successful submission, so execution responsibility for the send is only partly established. Permission basis: Oracle documents duty roles and permission groups required to access AI Agent Studio, to interact with agents in product pages and to access this feature, but does not state the identity under which the return is created or submitted, so the runtime permission basis is not established. Invocation: Oracle documents user-initiated interaction on a page where the agent has been added to the guided journey; no scheduled, event-triggered or background operation is documented, so the automatic creation on a single receipt match is automatic action within a user-initiated request, not unattended autonomy. Model and provider are not established. Release pinning: all behaviour recorded here is from Update 26C documentation.

Evidence