Supplier Negotiation Award Assistant

Seeded Oracle AI Agent Studio template that, for closed negotiations meeting a configured sourcing policy, applies sole-source or line-level awards, submits the award for approval where award approvals are enabled, and after approval finalises the award and generates purchasing documents.

Recorded characteristics

Function

Operates on supplier negotiations that have reached a closed status and have received at least the minimum number of supplier responses specified in the configured autonomous sourcing policy document. Oracle states that the assistant "automates award decisions for eligible negotiations by applying sole-source or line-level awards to achieve optimal pricing". Where award approvals are enabled the award is submitted for approval, and Oracle states that "once approved, the agent finalizes the award and generates the purchasing documents". Oracle does not separately describe a bid-comparison, scoring or recommendation step for this assistant, and does not document it producing a recommendation that a sourcing professional then accepts: the documented behaviour is award application rather than award recommendation. Execution is carried out through the scheduled job "Process Closed Negotiations with Autonomous Award Assistant to award eligible negotiations and create purchase documents automatically", which Oracle advises scheduling at regular intervals such as daily or weekly. Oracle separately notes that after an autonomously awarded negotiation is approved, "the subsequent ESS job run finalizes the award and generates the purchasing documents", so award finalisation and purchasing-document creation occur on a later run of that scheduled job rather than immediately at approval.

Data access

Closed supplier negotiations and their supplier responses, including the count of supplier responses received and response pricing, which Oracle describes only to the extent of applying sole-source or line-level awards "to achieve optimal pricing"; and the autonomous sourcing policy document held in the Autonomous Sourcing Policy tool in AI Agent Studio, which defines eligible item categories, negotiation template names, bidding durations, the minimum number of supplier bids and the maximum line amount for each category. Oracle does not document this assistant reading scoring criteria, requirements, non-price evaluation factors, supplier master data or historical sourcing information; the use of historical data is documented for the separate Autonomous Sourcing Assistant when inviting suppliers, not for this assistant.

Actions

Can take actions

External actions

Unknown

Human confirmation

Conditional

Permission basis

Not established

Administrative control

Enablement is entirely administrative: an instance of the seeded Supplier Negotiation Award Assistant agent team must be created from the template and published in AI Agent Studio, a sourcing policy document must be authored per My Oracle Support knowledge article KB858736 and loaded into the Autonomous Sourcing Policy tool and set to Ready to Publish, the profile options PON_AUTONOMOUS_AWARD_AGENT and PON_AUTONOMOUS_AWARD_AGENT_VERSION must be created and set to the published agent team code and version, and the scheduled jobs must be run in order. The award scope is bounded by the policy document (eligible item categories, maximum line amount per category and the minimum supplier bid count that makes a closed negotiation eligible) and by the schedule of the "Process Closed Negotiations with Autonomous Award Assistant" job. Award approval rules are the documented oversight mechanism; Oracle recommends setting the negotiation owner as the first-level approver in both negotiation and award approvals "to ensure a human reviews the autonomously created negotiations and awards". Update 26B added an Autonomous Award approval attribute so that approval rules for autonomously created awards can be routed to a designated user or approval group, an Autonomous Sourcing attribute, an Autonomous filter and column in the Negotiation Workbench, a banner shown on autonomously created negotiations throughout the negotiation lifecycle, and Award Approval notifications that can be conditioned on the Autonomous Sourcing and Autonomous Award attributes. Access to manage the agents requires named duty roles, and scheduling the ESS jobs through REST services requires a separately created integration user with a restricted set of named privileges. Oracle does not document an explicit deactivation control for the assistant.

Default state

Disabled

Availability

Introduced in Oracle Fusion Cloud Procurement update 26A for the Sourcing product family, delivered as one of two seeded AI Agent templates under the feature "AI Agent: Autonomous Sourcing Assistant", which the 26A feature summary lists with an enablement of Setup Required and no opt-in. Update 26B added visibility controls and approval-routing attributes covering autonomously created awards. Requires Oracle AI Agent Studio for Fusion Applications and Oracle Sourcing. Oracle does not state a preview or limited-availability status for this agent, and does not document geographic or deployment restrictions.

Licensing

Oracle does not document separate licensing or entitlement requirements for this agent beyond Oracle Fusion Cloud Procurement (Sourcing) and access to Oracle AI Agent Studio for Fusion Applications.

External model or provider

Not established

Limitations and uncertainty

Analysis versus award: Oracle describes award application, not bid analysis or award recommendation, and does not document how "optimal pricing" is determined for this assistant, whether by lowest response price, composite score or another method; the Redwood Award Negotiation feature describes system-recommended awards based on lowest response price or highest composite score, but Oracle does not state that this assistant uses that logic. Award selection versus approval: where award approvals are enabled a human approval step precedes finalisation, but Oracle states only that the award is submitted for approval when approvals are enabled, so a customer that has not configured award approval rules may see awards applied and finalised without a documented human checkpoint; this is why human confirmation is recorded as conditional rather than required. Purchasing documents: Oracle attributes purchasing-document generation to the agent in one sentence ("the agent finalizes the award and generates the purchasing documents") and to the scheduled ESS job in another ("the subsequent ESS job run finalizes the award and generates the purchasing documents"), and does not identify which purchasing-document types are produced; the boundary between the AI agent and the deterministic scheduled process is therefore not cleanly established, although the ESS job name attributes purchase-document creation to the Autonomous Award Assistant. Runtime authority is not established: Oracle documents an integration user with the Associated Person Type set to None, holding named privileges including Supplier Negotiation Award Using REST Service, Purchase Order Management Using REST and Purchase Agreement Management Using REST, for scheduling the ESS jobs through REST services, but does not state whose privileges the agent's award, submission, finalisation and document-creation actions execute under. Whether the agent performs any state-changing action in a system outside Oracle Fusion is not documented. Oracle does not identify the model or provider used by this agent. The primary documentation is release-pinned What's New material for updates 26A and 26B rather than an evergreen product guide, so future changes may appear on a different release page.

Evidence

• How do I use AI Agent Studio?

  Supports: General · Default state · Admin controls · Primary source

  Background on how AI Agent Studio agent teams, tools and templates are used.

  Seeded agent templates must be instantiated and published in AI Agent Studio before they run.

  AI Agent Studio is the administrative surface where the seeded template is copied, configured, published and versioned.

• Access Requirements for AI Agent Studio

  Supports: General · Admin controls · Permission basis · Primary source

  Background on AI Agent Studio access requirements.

  Access to manage agents in AI Agent Studio is governed by named duty roles and permission groups.

  AI Agent Studio access requirements describe user access to the studio and to agents on product pages; they do not establish the runtime execution identity of a published agent's actions.

• 26B AI Agent: Autonomous Sourcing Assistant Enhancements

  Supports: General · Human confirmation · Admin controls · Availability · Primary source

  26B distinguishes Autonomous Sourcing (created autonomously) from Autonomous Award (both created and awarded autonomously), supporting the separation of the two capabilities in the registry.

  Update 26B: "Approval rules for autonomously created negotiations and awards can be configured to route to a designated user or approval group ensuring proper oversight over autonomous activities."

  26B adds the Autonomous Award attribute ("indicates the negotiation was both created and awarded autonomously"), the Autonomous Sourcing attribute, an Autonomous filter and column in the Negotiation Workbench, a banner shown throughout the negotiation lifecycle, and Award Approval notifications conditioned on those attributes.

  Update 26B documents enhancements covering autonomously created awards, confirming continued availability in the following update.

• 26A AI Agent: Autonomous Sourcing Assistant

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

  Oracle: "Supplier Negotiation Award Assistant - Automates award decisions for eligible negotiations by applying sole-source or line-level awards to achieve optimal pricing. Eligible negotiations are those in a closed status that have received the minimum number of supplier responses specified in the policy document. When approvals are enabled, the award is submitted for approval. Once approved, the agent finalizes the award and generates the purchasing documents." Also: "When the negotiation closes, awards are automatically applied, either sole-source or line-level, and then submitted for approval. After the award is approved, the purchase documents are created." Trigger is the scheduled job "Process Closed Negotiations with Autonomous Award Assistant to award eligible negotiations and create purchase documents automatically", advised to run daily or weekly; and "after an autonomously awarded negotiation is approved, the subsequent ESS job run finalizes the award and generates the purchasing documents."

  Award application, submission for approval, award finalisation and purchasing-document creation are attributed to the agent or to its named scheduled job, establishing creation and modification of persistent business state. Oracle also states of the two templates collectively: "These ready-to-use AI templates process eligible requisition lines into negotiations, select suppliers, award the best supplier response, and generate purchasing documents."

  Eligibility depends on negotiation status (closed) and the number of supplier responses received relative to the policy threshold. The policy document "defines eligible item categories, negotiation template names, bidding durations, minimum number of supplier bids requirement, and maximum line amount for each category" and is read from the Autonomous Sourcing Policy tool. Supplier response pricing is documented only through "applying sole-source or line-level awards to achieve optimal pricing"; no scoring criteria, requirements, non-price factors or supplier master data are documented for this assistant.

  Oracle: "When approvals are enabled, the award is submitted for approval", so the human checkpoint depends on award approval configuration. Oracle recommends but does not require: "Set the negotiation owner as the first-level approver in both negotiation and award approvals to ensure a human reviews the autonomously created negotiations and awards."

  The agent operates only after an instance of the seeded Supplier Negotiation Award Assistant template is created and published in AI Agent Studio, a policy document is loaded and parsed, the PON_AUTONOMOUS_AWARD_AGENT and PON_AUTONOMOUS_AWARD_AGENT_VERSION profile options are created and set, and the ESS jobs are run in order.

  Configuration surface: agent team code and version profile options, the Autonomous Sourcing Policy tool document, and the ordering and scheduling of the Process Agent Documents and Process Closed Negotiations jobs. Policy thresholds (eligible item categories, maximum line amount, minimum supplier bid count) bound which closed negotiations may be awarded autonomously. Oracle documents no explicit deactivation control.

  Oracle documents an integration user "with the Associated Person Type set to None" holding privileges including Supplier Negotiation Award Using REST Service, Purchase Order Management Using REST and Purchase Agreement Management Using REST, for scheduling the ESS jobs through REST services, but does not state whose privileges the agent's award, finalisation and document-creation actions execute under. Human duty roles (PRC Intelligent Agent Management, Fai Genai Agent PRC Administrator, Fai Genai Agent Runtime) govern management and interaction, not runtime execution identity.

  All documented actions — award application, approval submission, award finalisation, purchasing-document creation and an error email to the negotiation owner — occur within Oracle Fusion. No agent-originated state change in a system outside Oracle Fusion is documented, so this is recorded as unknown rather than no.

  Documented in the Oracle Fusion Cloud Procurement update 26A What's New as a new seeded AI Agent template available in AI Agent Studio, alongside the Autonomous Sourcing Assistant.

  Oracle names Oracle AI Agent Studio for Fusion Applications and Oracle Sourcing as prerequisites; no separate licence or entitlement is stated for this agent.

  Oracle attributes purchasing-document generation both to "the agent" and to "the subsequent ESS job run", and does not name the purchasing-document types produced, leaving the AI/deterministic execution boundary unresolved. Oracle also does not document how "optimal pricing" is determined, nor any bid-comparison, scoring or recommendation step preceding the award, and does not establish the runtime execution identity.

  Oracle delivers Supplier Negotiation Award Assistant and Autonomous Sourcing Assistant as two distinct seeded templates under one feature; this record covers the closed-negotiation award stage only, and the separate record for the Autonomous Sourcing Assistant covers requisition-line conversion through negotiation publication.

• Oracle Fusion Cloud Procurement 26A Feature Summary

  Supports: Default state · Availability · Licensing · Primary source

  The 26A Procurement feature summary lists the AI Agent: Autonomous Sourcing Assistant feature, which delivers this agent template, with an enablement of Setup Required and no opt-in.

  The 26A Procurement feature summary records the delivering feature for the Sourcing product family.

  The feature is listed within the Oracle Fusion Cloud Procurement update, with no separate licensing note for this agent.

• Which large language models (LLMs) are currently used or supported for AI agents?

  Supports: External model · Limitations · Primary source

  Oracle's AI Agent Studio documentation on large language models does not identify a model or provider specific to the Supplier Negotiation Award Assistant.

  No per-agent model or provider is established for this assistant, so external model or provider is recorded as not established.