Oracle Fusion Enterprise Contracts
From Request to Renewal

External Purchase Pricing resolves the price a healthcare organization pays at the point of order, and it is built to update the blanket purchase agreement. An Enterprise Contract can still hold negotiated pricing as contract data — useful for negotiation history, approvals, and reference — but that stored price is not what External Purchase Pricing consults for med-surg and similar healthcare items, so you can't build the BPA from the Contract.

For the hospital’s maintenance agreement, that distinction usually does not matter; a service agreement is not a med-surg purchasing item. But for medical/surgical supplies and similar categories, keep the BPA as the pricing source of truth and treat the contract as the terms-and-negotiation record that sits alongside it.

Outside healthcare, or for non-med-surg items, that constraint disappears. Those categories have more room to let the contract’s fulfillment lines drive pricing into a purchasing document; see Purchasing fulfillment.

A blanket purchase agreement or contract purchase agreement can be associated with a terms template, but it is not where negotiation happens. There is no redline cycle against supplier paper, no structured negotiation workflow, no free-form collaboration notes, no access control by contract header values, and no AI review or key-terms extraction run against its language.

Purchasing agreements do support contract terms deliverables, including recurring commitments where configured. Those capabilities are not exclusive to Enterprise Contracts. The remaining distinctions reflect a record built to price and order, not to carry a legal negotiation. When a purchase needs any of that, the Enterprise Contract is the right record, with the purchasing agreement generated from it where a purchasing outcome is also needed.

For the hospital, I would align these foundations before designing screens. A beautifully configured request form still struggles if nobody knows which supplier entity should sign.

Use Sell for the organization’s sales-side contracting process. Use Buy as the recommended home for the rest of the centrally managed corporate and procurement contract portfolio, including an NDA that supports a supplier evaluation or another non-sales relationship.

For the hospital, putting its supplier NDA and maintenance agreement on the Buy side keeps them with the procurement contract team, its access model, and its reporting. It does not mean the NDA requires a purchase order, financial commitment, or contract lines. It's just an unfortunate quirk that Oracle splits Contracts into either Buy or Sell when not every contract has a PO or SO. Don't over think it: If it doesn't explicitly have a sales order, treat it as a Buy contract.

Choose intent by who owns the relationship and the process that should manage it. Then use contract types to distinguish NDA, maintenance agreement, master agreement, and other document families.

Oracle documentation: Contract creation and reuse · Enterprise Contracts feature overview

A requester should describe the need in business language: “We need a maintenance agreement for these devices.” The contract team should not require the department to understand clause libraries or purchasing fulfillment setup, but you can collect a significant amount of key data that feeds right into the final contract like start and end dates and suggested party details.

In 26D, an intake template can allow a Procurement Contract outcome and control the information collected. The intake creation assistant can help draft the request conversationally. Request approval is followed by the Process Procurement Intake Requests scheduled process, which creates the contract; missing information may need intake-manager intervention.

For the hospital, collect supplier, scope, expected dates, value, business owner, and the supplier’s draft. Define mappings for the downstream contract.

Notice what you don't see here: Attaching a contract to a requisition. This is a struggle for many administrators, but we never recommend this. Force the team to contract before they requisition in order to control spend and risk!

Oracle documentation: 26D procurement contract intake

Manual creation and templates belong in the same authoring path. The specialist creates the contract and can start from an activated contract template, duplicate a suitable agreement, use the Contract Wizard where supported, or enter the details directly.

A contract template reuses the contract starting point. A terms template supplies the organized legal language. You will end up using both!

For our maintenance agreement, the specialist selects the type and supplier, confirms scope and dates, and applies the appropriate terms or attaches the supplier’s paper. When duplicating, challenge every inherited fact: contact, price, end date, notice period, and exceptions.

Oracle documentation: Contract creation and reuse

Where the sourcing award produces a supplier contract, the category manager begins with already-negotiated scope and commercial details. In 26D, the lifecycle is preserved completely: A requisition can become a Negotiation which becomes a Contract which becomes a Purchase Order referencing the original requisition, and the negotiation, and the contract!

For the hospital, the sourcing team might select the maintenance provider through a competitive event, then hand the award into contract preparation. Decide whether requisition demand is fulfilled through the contract or returned to the buyer’s pool, according to the supported contract-class behavior.

Oracle documentation: 26D requisition-backed negotiation awards

The 26D Contract Document Ingestion Analyst workflow accepts PDF, image-based PDF, and Word documents. It scans and classifies documents, extracts header data and key terms, and provides correction and review before creating records.

The business role is document conversion and validation. Someone still reconciles the supplier entity, identifies the signed agreement and amendments, and checks dates and extracted results before sending for approval and signature.

Oracle documentation: 26D AI contract ingestion

Structured terms preserve the relationship between contract sections, clauses, and library content. A supplier-authored document starts from externally prepared language.

The AI powered Word add-in introduced in 26B supports authoring for both flows. It includes clause and section editing, import of external revisions for structured terms, and analysis of third party paper against a reference terms template. AI text suggestions can draw on standards or prior agreements so you know exactly how you handled this the last time that supplier suggested a clause.

For the hospital, “we accepted this clause once” should start a discussion, not end it. A prior agreement may have had a smaller value, narrower scope, or a different risk allocation. The AI tools give you a jumpstart, but you still take this to it's logical conclusion as the human in the loop.

Oracle documentation: 26B AI powered Word add-in

In 26D, Contract Expert supports policy-document-based rules in Redwood and the Word add-in. Rules use the terms template, business unit, and contract values to identify applicable clauses. Required clauses can be added automatically; optional clauses are presented for review with explanations.

Use this to express deliberate legal policy: for example, a maintenance agreement involving remote equipment access may need a security provision. Legal should own the policy and examples that demonstrate when it applies.

Oracle documentation: 26D policy based Contract Expert

The library contains reusable legal clauses, sections, variables, and terms templates. Variables insert changing information into clause text. Contract Expert rules can select language based on answers and contract values. Library setup is a specialist responsibility, supported by Contract Administration leadership and Legal.

Oracle documentation: Terms library components

1. Legal owns the language. Define approved clauses and permitted alternatives.
2. The library administrator assembles the template. Select the business unit and intent, organize sections, add clauses and variables, and configure applicable controls and deliverables.
3. Validate and approve. Resolve validation errors and submit the template and any associated draft clauses for approval.
4. The author uses the approved starting point. Apply the template and complete the agreement-specific information.

The layout template controls presentation for printing and preview; it is different from the legal-content terms template. Test the generated document, not just the clause outline. You've got significant control over formatting, just like Word. Infact, you can import from Word!

Oracle documentation: Terms template setup and approval

For the hospital, one services template may provide the common backbone, with controlled alternatives for equipment access, insurance, and liability. Give Legal an ongoing maintenance process so the next author starts from current policy.

Classify by business purpose. A spreadsheet incorporated into the agreement is different from an internal cost comparison. Contract Documents are editable in Draft or Under Amendment but updating an active contract requires a revision; Supporting Documents can be maintained at any time without requiring a revision.

Remember that the linked document from the PO side is only the Primary Contract Document. While other documents are available for Key Terms Extraction and Summary, they aren't visible to Procurement Agents unless they have access to the Contract and actively go look inside the Contract. The practical implication? When you have an amendment, add it to the Primary Contract Document and replace the Primary Contract Document with the concatenated files! Otherwise, the amendment is effectively invisible to Procurement Agents.

Oracle documentation: Contract attachment types and limits · Signed contract document category

Keep the Excel original or email evidence when useful. For key-term extraction, use the supported PDF source documents; for summarization, use the supported contract terms and searchable PDF documents. The 26D ingestion process has its own PDF, image-based PDF, and Word support.

But, msg and xls files are not included in AI document summaries or key terms extraction, so use caution!

Oracle documentation: Key term extraction guide · AI contract summarization · 26D AI contract ingestion

Administrators define key terms and prompts, test them against sample documents, and activate them. Contract types determine which key terms and prompts apply, including their effective dates. This puts all the data into a structured format that we can query, report against, and use to drive notifications and alerts.

Oracle documentation: Key term prompts and testing · Associate key terms with contract types

For the draft maintenance agreement, useful questions include: How much notice prevents renewal? What limits the annual increase? What insurance must remain in force? What termination charge applies?

A useful prompt asks for the triggering condition as well as the number. “60 days” means little unless the reviewer knows whether it is before expiration, before renewal, or after notice of a breach.

The extraction action selects contract documents, submits the extraction process, and exposes its status and results on Key Term Values.

Oracle documentation: Key term extraction guide

Practically Speaking: Key Terms Extraction puts the data into a set format, easy to search and understand and report on, with no fluff or potential for reordering information from an LLM generated summary paragraph. But, it doesn't plug that data in to the contract header fields, create deliverables, or activities. In other words, if your contract administrator sets the End Date to 4/1, and Key Terms Extraction finds that End Date is actually 5/13, you can report on this discrepancy but it does not automatically fix it.

The Contract Summarization Agent works with searchable PDF contract documents and contract terms. Users select source documents and generate a summary; the prompt can be tailored and you can use different prompts on different contract types. There is no set fee for customization, it only depends on how many tokens are consumed by the agent. You can edit the summary that is generated, and you can automatically attach it to approval notifications.

Oracle documentation: AI contract summarization

For our example, I would ask the summary to explain scope, duration, total commitment, price changes, renewal and termination, significant obligations, and unresolved risks. Then have the owner verify those statements against the final agreement.

Generate an initial summary as soon as draft terms are available so department reviewers can understand the proposed commitment. Refresh the extraction and summary after material changes, and generate the final approval summary from the settled agreement. This can functionally take the place of a cover sheet for sending around with the approval.

Contract Advisor is now AI powered for procurement contracts, related documents, and standard clauses. It uses your Playbook to identify risky clauses and propose replacements.

Oracle documentation: Contracts AI Counsel availability

1. Define the responsibility. For example: departmental reader, departmental author, legal specialist, contract administrator, or signature sender.
2. Build the functional role. Grant the privileges needed for that job, using configured roles rather than relying on a responsibility’s name.
3. Define the data scope. Configure sharing for the relevant business units, ownership, resources, or other supported rule criteria; grant Read or Full as appropriate.
4. Check all inherited grants. Test that broad BU, ownership, or team policies do not unintentionally expose restricted contracts.
5. Publish and process the rules. Run the required access-group jobs and test with representative users.

Oracle documentation: Access groups and functional security

An access group’s reach comes from its object sharing rules. Each rule is a condition built on one or more contract attributes, and it resolves to Read or Full access for the group’s members. Rule conditions can combine:

Oracle also ships predefined rule categories that cover common cases without a custom condition: General Access (all contracts), Contract Owner Based (Read or Full for the owner), Business Unit Based (by sales or procurement business unit), and Resource, Resource Ancestor, and Resource Organization Based rules (by resource, resource hierarchy, or resource organization, each at Read or Full).

Oracle documentation: Control access to contracts using access groups (26A readiness)

The Parties tab identifies party and contact roles; those roles can participate in BPM routing. Contract team membership supports collaboration and access, subject to the user’s privileges and data security. Being an approver or signer is a process responsibility.

Oracle documentation: Party and contact role configuration · Contract team security

SharePoint permissions govern the shared working document separately from Fusion contract access. Plan both when adding or removing a reviewer. IE, if you add or remove them in Sharepoint, it won't impact their access in Oracle, and vice versa. Similarly, a buyer processing fulfillment needs the appropriate procurement-agent access, rather than just membership in the legal review team.

Oracle’s user statuses and transitions are incorporated into an event model. That model defines states, events, actions, and applicable conditions, which can vary by business unit or contract type. Configured actions can also raise business events.

A designed review stage can offer outcomes such as Legal Review Approved, Legal Review Rejected, or More Information Required. These example outcomes can drive subsequent actions when their transitions and any integrations are implemented. And it's all tracked in history along with their comments!

That can function as a departmental signoff. It does not automatically execute the seeded contract approval workflow or place the contract in its system-approved state.

Oracle documentation: User statuses and event models

A review design for the maintenance agreement

For each transition, define who may act, what evidence they must review, where the decision is recorded, and who owns the next step. If notification, assignment, or reminders require an extension, include that work in the design.

Avoid calling every review “approval.” The department’s permission to request work, Legal’s acceptance of wording, the organization’s authorization to commit, and the supplier’s signature answer different questions. But this is the best way to route the contract for review. By the time it goes for official Approval, you want departments to have all reviewed.

There is no requirement to put a human gate at all three layers. A department review can be unnecessary, BPM can auto-approve, and signature can be unnecessary for acceptance under the configured contract type. The contract must still follow the supported application lifecycle and organizational policy. You have significant control over how each contract would be routed: Lets make it as simple as possible, and as complex as required.

Oracle documentation: Automatic contract approval rules · Contract approval lifecycle

For the maintenance agreement, all three may be appropriate. For a repository record of an already executed agreement, repeating all three as new human decisions may add little value. Design the process by agreement type and purpose.

A review model need not be a straight line. The contract owner may send a draft from Legal to Security, back to Legal, then to the department for a commercial decision.

These are design patterns built using configured user statuses, transitions, assignments, and the event model. Conditions can target contract types or business units. A hybrid can preserve flexible consultation while requiring defined exit outcomes before formal approval.

Oracle documentation: User statuses and event models

For example, the NDA might need only Legal Review → Review Complete. The maintenance agreement could require Legal and Security outcomes, allow either team to return it for clarification, and permit Finance Review only when commercial details are ready. Permissions, transition guards, notification actions, and any integration must implement that design.

Design these measures around the department’s service expectations:

For completed visits, duration is exit timestamp minus entry timestamp. For an open visit, age is now minus entry timestamp. Keep repeated visits separate before calculating total time in a status. Agree whether the clock uses calendar or business time and whether time awaiting the supplier is included.

Use a reporting design that actually captures the transition timestamps. Oracle exposes contract status history through REST and BI Publisher.

Oracle documentation: Contract status history REST resource

Use the queue to act: assign an available reviewer, escalate an overdue decision, or move a contract to the right specialist.

Oracle documentation: Contract assignment and workload management

Keep the durable business owner distinct from the person handling the current review. Reassign the current assignee for workload balancing; change the contract owner when accountability changes.

Oracle added SharePoint contract collaboration in 26C. From the Word add-in, the initiator starts collaboration, which creates a contract-specific SharePoint folder and working terms file. Internal contract contacts populate the collaborator list.

Participants can use Word coauthoring, comments, tasks, and tracked changes. SharePoint access can be adjusted independently of their Fusion contract access, so not ever person needs to have an Oracle login!

When review is complete, the lock owner uploads the final reviewed terms through the add-in. This updates the application’s terms. Saving in SharePoint alone does not complete that handoff. Starting collaboration again after upload archives the previous collaboration file.

Setup includes the collaboration opt-in, Microsoft identity and permissions configuration, and the SharePoint location. A contract-type location takes precedence over the business-function location.

An important callout: The redlining history is not imported into Oracle, only the final redlined version. You review and approve the changes in Oracle, but it's comparing original to final, not every single back and forth edit in the middle. If you reject a change, the entire document is rejected and sent back to redline in Word. However, comments do stay visible in the downloaded Word document.

Oracle documentation: 26C SharePoint collaboration

The Word add-in’s upload flow asks whether the upload is final and the lock should be released. Interim uploads can retain the lock. Its structured-terms flow also supports exporting to an external party and importing a revision.

Oracle documentation: 26B AI powered Word add-in

For our example, I would use this completion checklist:

1. Resolve the remaining business and legal questions.
2. Have the designated owner review the tracked changes and prepare the agreed clean execution text.
3. Upload the agreed terms back through the supported Fusion process.
4. Preview the resulting primary contract document and confirm its schedules and exhibits.
5. Refresh extracted key terms and the summary against that final content.

Prepare the primary contract document, applicable schedules, and any deviation justification. Validation identifies errors that must be corrected. The submitter can review the approver hierarchy before submission; submitting moves the contract to Pending Approval.

Remember that you can control which user status values are allowed to submit for approval. If submit is not allowed, check the user status!

Approval history records the outcome. Rejection returns a new contract to Draft or an amended contract to Under Amendment. An approved contract requiring signature moves to Pending Signature; a contract that does not require signature becomes Active.

Oracle documentation: Contract approval lifecycle

For the maintenance agreement, a proposed routing design might ask Finance to authorize the commitment and the delegated business approver to authorize the service. Legal’s earlier review can remain a separate control.

Test the ordinary agreement, a high-value exception, a missing approver, a missing attribute, and an amendment. Positive and negative testing is required because you need to ensure no contracts get stuck without an applicable rule.

Withdraw a pending approval to make corrections and resubmit through the supported lifecycle. The reviewed document, summary, and approval request should all describe the same agreement.

Oracle documentation: Contract approval lifecycle

Use the Track Electronic Signature Status scheduled process to retrieve signature status and the completed signed document. Signature history identifies the envelope and outcome. A declined or voided envelope requires follow-up.

Oracle documentation: Electronic signature lifecycle

Oracle’s signed-document enhancement stores returned executed documents in the Signed Contract Document category, making the executed copy easy to identify. Internal attachments included in the combined signed pack deserve attention before that pack is shared externally.

Oracle documentation: Signed contract document category

For the hospital, confirm the supplier’s signer before sending. Then verify that Fusion has the executed copy and the appropriate lifecycle status. The working Word document, approved unsigned document, and signed document each have a different purpose.

Before execution, a pending-signature contract can require a new version to accommodate requested changes. Once signed and active, use the amendment process.

Oracle documentation: Changes while pending signature

For a material wording change, coordinate the signature envelope, update the contract, and obtain the required approvals for the revised agreement. Correcting an email address and changing negotiated liability are different business events.

Deliverables can be created directly on a contract or inherited from its terms template. Configure the responsible contact, deadline, and notification requirements.

Oracle documentation: Create contract deliverables

Deliverables support one-time and recurring commitments, fixed dates and dates relative to contract events. Contractual deliverables represent obligations; internal deliverables track internal work. Instances can retain attachments and status history.

Notifications depend on activation and the scheduled processes for due dates, overdue items, and escalation.

Oracle documentation: Deliverables and notification processes

Use the Notes tab to preserve context: why the hospital accepted a particular exception, what the supplier clarified, or which question remains open. Notes have security considerations, including private notes and their author’s access.

Oracle documentation: Contract team security

I would use a short convention: date, topic, decision, accountable person, and supporting document. Use deliverables for work that must happen by a deadline, and use the formal approval history for authorization evidence.

Organize documents by their business purpose. A scope exhibit, draft redline, executed agreement, and insurance certificate should be recognizable without opening every attachment. Internal discussion should not accidentally become part of the supplier’s execution package.

Contract team access can support authoring and amendment duties. Redwood visibility also depends on functional privileges and applicable access-group sharing rules.

Oracle documentation: Contract team security · 26C repository contracts and access groups

Party and contact role configuration establishes how people participate; contract contact roles can also be used in BPM approval design.

Oracle documentation: Party and contact role configuration

For our hospital, distinguish the business owner, contract administrator, legal reviewer, supplier service contact, and authorized signers. One person can fill several roles, but those responsibilities should remain explicit.

Include reassignment in the operating model. When the business owner leaves, transfer responsibility for the active agreement, renewal decision, and outstanding obligations. Updating a contact name is only one part of that handover.

The Related Contracts tab can link a master agreement, NDA, statement of work, and other agreements using defined relationship types. The contract type must enable related contracts. Redwood supports reciprocal relationships based on the selected type.

Oracle documentation: 26B Notes and Related Contracts · Related contract access across business units

For the hospital, relate the maintenance agreement to its governing master services agreement and supplier NDA. This helps the next reviewer find the full agreement family rather than relying on a filename or a note.

Contract lines describe the goods or services where line-level detail is useful. Fulfillment lines prepare those commitments for downstream purchasing. They are related records with different purposes; a contract line is not automatically a PO line, but you must have a contract line in order to generate a PO line through Fulfillment.

If you don't have lines on your contract, but you do have a PO, you can still manually link them from the PO by searching for the contract.

Do not invent a token $1 line for an NDA just to make the record resemble a purchase. Use a contract type without lines when the agreement has no meaningful line-level scope or fulfillment requirement. Conversely, line-level quantities, prices, service periods, or separate outcomes may justify lines.

Oracle documentation: Contract fulfillment model

In the Redwood Contract Fulfillments experience, approved enterprise contracts with lines enabled generate fulfillment lines. Buyers review the lines, complete purchasing attributes, select one or more lines, and use Create Purchasing Document.

Oracle documentation: Redwood contract fulfillment processing

For our maintenance agreement, the contract administrator hands over a clear, approved commitment. The buyer validates how that commitment should become operational demand and resolves purchasing creation errors. Purchasing approval remains a separate process from approval of the legal agreement.

Oracle documentation: PO and purchase agreement purposes

A contract purchase agreement in Purchasing is a different object from the Enterprise Contract record. Creating an Enterprise Contract does not automatically create a BPA or CPA for every agreement. Configure a supported fulfillment outcome and ensure the necessary purchasing information is available.

Oracle documentation: Contract fulfillment model · Redwood contract fulfillment processing

The Amend action moves an active contract into Under Amendment. The amendment can change terms and other permitted details, then follow approval. An amendment summary can expose changes to clauses, sections, variables, documents, and deliverables. Revert cancels the current amendment while it remains Under Amendment.

Oracle documentation: Amend and revert contracts

For the new location, document the expanded scope, revised price, effective timing, insurance implications, and required signatures. Refresh the summary and key terms affected by the change.

Yes—buy-side renewal is supported now! Oracle’s 26D Redwood renewal feature covers Buy and Sell repository contracts, plus Buy agreements with Contract Class Agreement and lines enabled. Eligible contracts must be Active or Expired, the latest version, non-evergreen, and have an end date.

Manual renewal creates the new contract in Draft. The Renew Contracts and Lines Using Renewal Settings process handles eligible scheduled renewals. Settings control renewal behavior, duration, internal approval, supplier acceptance, eligible lines, and applicable terms. Approval and acceptance settings determine whether an automatic renewal starts Active, Pending Approval, or Pending Signature.

Fulfillment-line renewal and contract consolidation are not supported by this feature. Review downstream PO/BPA requirements separately. Renewal History connects the source and renewed contract.

Oracle documentation: 26D renewal of buy contracts

For the hospital, decide whether renewal means “create a new draft for a decision” or “automatically extend eligible agreements under approved rules.” Keep the contractual nonrenewal deadline, decision deadline, and scheduled renewal horizon distinct. With 60 days’ notice required, a review beginning 30 days before expiration is already too late.