Oracle Fusion Cloud Procurement Contracts standardizes, automates, and governs the creation of procurement agreements natively inside the Redwood Procurement work areas, instead of relying on attachments or manual clause entry. At the core is the Contract Terms Library: a central repository of approved clauses, sections, and templates that can be assembled into a contract and attached directly to a Procurement Contract, Purchase Order, Blanket Purchase Agreement, or Contract Purchase Agreement.
What's different in Fusion is
how that library connects to the transaction. The Contract Terms tab lives
directly inside the Procurement Contract, Purchase Order, or agreement itself,
and Contract Expert runs in real time as you author the document, recommending
templates and inserting clauses based on rules you define once, centrally.
In this post I'll walk through a
real working example: building a Contract Terms Library for an IT services
agreement, creating a Contract Expert rule that automatically pulls in a
stronger Liability clause when the contract value crosses a threshold, and then
generating contract terms on a live Procurement Contract — the same way I
worked through it in my own test environment, with screenshots at every step.
1. Core System Setup
Before any clause or template
can be created, a handful of foundational setup tasks need to be completed once
per Business Unit through Setup and Maintenance / Functional Setup Manager
(FSM). These are one-time activities that establish the scope and approval
routing for everything built afterward.
1.1 Enable the Procurement Contracts Feature
Contract Terms authoring has to
be switched on for the Procurement offering before the Contract Terms tab will
even appear on a BPA or PO.
Navigation: Setup
and Maintenance → Procurement offering → Change Feature Opt In
1.
Open the Change Feature Opt In
page for the Procurement offering.
2.
Enable the Procurement
Contracts feature.
3.
Save and close.
Change Feature Opt In page — Procurement Contracts feature
enabled for the Procurement offering.
Procurement Contracts feature detail — Enable Contract Terms,
Enable Electronic Signature, and Automatically Generate Purchasing Change
Orders, all Enabled.
1.2 Configure the Business Unit for Contracts
Fusion scopes nearly everything
in the Terms Library to a Business Unit through this task — the Terms Library
Administrator set here is who receives every clause and template approval
notification, so it's worth getting this right before building anything else.
Navigation: Setup
and Maintenance → Search → "Specify Supplier Contract Management Business
Function Properties”
4.
Select the procurement Business
Unit — in my case, this is the BU I use for IT services procurement.
5.
Set the Contract Terms Library
Administrator — the person who receives clause and template approval
notifications.
6.
Enable content adoption if global
clauses from a parent BU should flow down automatically.
7.
Enable the Contract Expert
checkbox for this Business Unit — without this, rules will never fire
regardless of how they're configured.
8.
Save.
Specify Supplier Contract Management Business Function
Properties — Terms Library Administrator, Enable Contract Expert, Clause Layout
Template, and Deviations Layout Template all set at the Business Unit level.
1.3 Set Up the Contract Type
The Contract Type determines
which documents (Purchase Orders, agreements, and standalone Procurement
Contracts) can use the Terms Library and which BI Publisher layout prints the
contract. Fusion ships several seeded Buy-intent contract types — Buy: Lines,
Buy: No Lines, Buy: Agreement Lines, and others — so in most cases you're
enabling and configuring an existing type rather than creating a new one.
Navigation: Setup
and Maintenance → Search → "Manage Contract Types"
9.
Open the seeded Buy: Lines
contract type — this is the one used for Purchase Orders and agreements with
order lines.
10. Enable contract terms authoring — this is the master
switch for the document type.
11. Assign the BI Publisher layout template that will format the
printed contract.
12. Save and close.
Manage Contract Types — the seeded Buy : Lines type selected,
described as “Buy Contract with Lines.”
Edit Contract Type: Buy : Lines — Intent Buy, Contract Layout
Template SupplierContract, Terms Layout Template
ContractTermsPlusAmendmentsProcurement, automatic line numbering enabled.
2. Structuring the Contract Terms Library
With the foundation in place,
the next step is building the library itself — sections, clauses, and variables
— all from the Terms Library work area.
I have used a sample term and
condition from google, and generating sections and clauses for our test
scenario, you need to work with Contract Administrator or legal team to get the
terms and conditions and defined sections and clauses accordingly.
2.1 Creating Sections
Sections give the printed
contract its headings and structure. For this contract, I used a set tailored
to a services agreement:
• General Terms and
Conditions
• Invoicing and Payment
• Warranty & Liability
• Confidentiality
Navigation: Terms
Library work area → Tasks panel → Create Section
13. Click Create Section.
14. Enter the section name and select the Business Unit.
15. Repeat for all five sections.
16. Save and close.
I created the following five
sections — these will be used directly in the template:
All five sections created
2.2 Creating Variables
Variables are dynamic
placeholders that pull live data from the document into the clause text at
print time. Fusion ships predefined system variables, and I used the standard
ones for this test rather than creating new ones.
For this test scenario I am not
creating any variable.
Navigation: Terms
Library work area → Search for Variables from search pan
2.3 Creating Clauses
With sections and variables
ready, I built five clauses — one per section — using the Create Clause task.
Navigation: Terms
Library work area → Clauses tab → Create Clause
17. Select the Business Unit for the clause.
18. Enter a clause number and title per the naming convention (I
used GEN_01, PRC-01, CNF-01, WLB-01, DSP-01).
19. Select the Intent as Buy, since this is a procurement-side
agreement.
20. Select the Type — Commercial for the Invoicing and
Payment clause, Legal for the others.
21. Select the matching Default Section created in step 2.1.
22. Enter the clause text in the editor.
23. Position the cursor where a dynamic value is needed and click
Insert Variables to add the variable — for example, inserting Supplier Name and
Contract Amount into the Invoicing and Payment clause.
24. Click Submit to send the clause for approval.
Here is the Invoicing and
Payment clause with the Contract Amount and Supplier Name variables inserted
into the text:
I repeated this for General
Terms and Conditions, Delivery of Procurement, Warranty & Liability, and
Confidentiality, then submitted all five for approval. Approval routes
automatically to the Contract Terms Library Administrator configured in step 1.2.
After the administrator approved
the notifications, all five clauses moved to Approved status and became
available for use in a template.
3. Building the Contract Terms Template
The template is the starting
point every contract author sees. I created one template for this agreement and
added all five approved clauses to it.
Navigation: Terms
Library work area → Contract Terms Templates tab → Create
25. Select the Business Unit for the template.
26. Enter a unique name — I used "IT Services BPA Standard
Terms". (BPA is just ta type and added to Template name, please don’t confuse,
it can be IT Services Standard Terms)
27. Select the Intent as Buy.
28. Select the layout template that will be used to preview the
contract terms.
29. Enable Contract Expert for this template — this is
required if any Contract Expert rule should run against contracts using it.
30. Enter the Default Section where Contract Expert will insert any
additional clauses — I pointed this at Warranty & Liability, since that's
where my rule's clause belongs.
31. Click Save.
Edit Terms Template: IT Services BPA Standard Terms — Layout
Template Contract Terms Procurement, Contract Expert enabled, Default Section
Warranty & Liability.
3.1 Setting the Document Type
32. In the Document Types region, click Add.
33. Select Buy : Lines as the Document Type — the same contract type
configured in Section 1.3.
34. Check the Default option so this template applies automatically
to every new contract or agreement of this type.
Document Types region on the template — Buy : Lines added as the
document type this template can be used for.
3.2 Adding Sections and Clauses to
the Template
35. On the Clauses tab, click Add Section from the Actions menu.
36. Add each of the four sections created earlier, in the order they
should appear on the printed contract.
37. For each section, click Add Clause, search for the matching
approved clause, select it, and click OK.
38. Expand each section and click Refresh to confirm the clause text
is showing correctly.
I added all five sections and
their corresponding clauses — General Terms and Conditions, Delivery of
Procurement, Invoicing and Payment, Warranty & Liability, and
Confidentiality — in that sequence:
3.3 Submitting the Template for Approval
39. Click Submit to begin validation.
40. Review any validation warnings — common ones relate to missing
default sections or clauses not yet approved.
41. If validation passes with no errors, click Submit again to send
the template for approval.
Once the Contract Terms Library
Administrator approved it, the template status changed to Published and became
available for contract authoring.
IT Services BPA Standard Terms template after approval — Status
Approved, ready for contract authoring.
4. Configuring a Contract Expert Rule
Fusion's Contract Expert is more
tightly woven into the authoring experience, and I wanted to demonstrate a real
Clause Selection rule rather than just describe the concept.
The business case: if the
Purchase Order total contract amount exceeds AED 200,000, I want the system to
automatically recommend a stronger Liability Cap clause in addition to the
standard Warranty & Liability clause already in the template.
4.1 Creating the Constant
Numeric rule conditions in
Contract Expert can't reference a typed literal directly — they need a Constant
object to compare against.
Navigation: Terms
Library work area → Contract Expert → Tasks panel → Create Constant
42. Enter a name — I used "High Value PO Threshold".
43. Enter a description explaining the business purpose.
44. Select the data type as Number.
45. Enter the value: 200000.
46. Save and close.
4.2 Creating the Additional Liability Clause
Before building the rule, I
created a second clause to be inserted conditionally — a stricter Liability Cap
clause, in the same Warranty & Liability section.
47. Created the clause the same way as the others (Section 2.3),
titled "Liability Cap — High Value Agreements".
48. Submitted it for approval and confirmed it reached Approved
status.
4.3 Creating the Contract Expert Rule
Navigation: Terms
Library work area → Contract Expert → Rules tab → Create Rule
49. Select the rule type as Clause Selection.
50. Select the Business Unit and Intent (Buy).
51. In the IF condition, select the Contract Amount
variable, the operator Greater Than, and the constant High Value PO
Threshold created above.
52. In the Result tab, click Add Clauses and select the Liability
Cap — High Value Agreements clause.
53. Assign the Terms Template under Term Template Assignment
Tab
54. Save the rule.
55. Click Activate Rule — rules don't require approval, but
they do require activation before they take effect.
Here is the completed rule with
the condition and the resulting clause:
Note:
Rules are restricted to the Business
Unit and Intent they're created in, and they don't get copied automatically
when a global template is copied to a local Business Unit — this tripped me up
the first time I tested it, since the rule simply didn't fire after copying a
template across BUs.
5. Applying the Template on a Live Procurement Contract
With the library, template, and
rule all in place, the final step was to create an actual Procurement Contract
and watch the whole configuration work together.
5.1 Creating the new Contract
Navigation: Contract
Management → My Contracts → Create Contract (Redwood)
1.
Created a new contract, named it
“IT Service Procurement,” and set the Intent to Buy with the procurement
Business Unit.
2.
Selected the supplier — Emirates
Steel — and entered the contract Start Date and End Date.
3.
Saved the contract header — Fusion
assigned it contract number 3001, Version 1, in Draft status.
From the home page, Contract
Management is one of the apps on the springboard, alongside Order Management
and Supply Chain Execution. I opened Contracts (New) — the Redwood contract
authoring app, separate from the classic Contracts work area.
Contract Management springboard — Contracts (New) is the Redwood
page used for this walkthrough.
The My Contracts landing page
opened with no existing records for this Business Unit. I clicked Create
Contract.
My Contracts landing page — no records yet, Create Contract
highlighted.
The Create Contract panel asks
for the Business Unit, Legal Entity, contract Type, Primary Party, Name, dates,
Item Master, Authoring Party, and Currency in one form. I filled it in as
follows:
Create Contract panel — Business Unit US1 Business Unit, Type
Buy: Lines, Primary Party Emirates Steel, Name IT Service Procurement,
Authoring Party Internal.
This is also where the Buy:
Lines contract type from Section 1.3 actually surfaces — it's listed directly
in the Type field on this panel, which confirms the contract type setup carries
through to contract creation exactly as configured.
Clicking Create saved the
contract header. Fusion assigned it number 3001, Version 1, in Draft status,
with the $1,000,000 amount picked up from the line I added next.
Contract 3001, Version 1 — Overview tab, Draft status, Amount
$1,000,000.00 USD.
5.2 Adding the Contract Line
On the Lines tab, I added a
single item line representing the IT hardware component of the agreement, to
give the contract an amount Contract Expert could evaluate against the
threshold.
Lines tab — item CM4800145, Miscellaneous category, unit price
5,000.00 and quantity
5.3 Adding Contract Terms
With the header and line saved,
I opened the Contract Terms tab. It was empty by default — contract terms
aren't generated automatically when the contract is created; you have to add
them explicitly, even when a default template exists for the document type.
Contract Terms tab — empty state, Add Contract Terms
highlighted.
Clicking Add Contract Terms
opened a panel asking for the Authoring Party, the Contract Source, and the
Terms Template. I set the Authoring Party to Internal, the Contract Source to
Terms Template, and selected IT Services BPA Standard Terms — the template
built in Section 3.
Add contract terms panel — Authoring Party Internal, Contract
Source Terms Template, Terms Template IT Services BPA Standard Terms.
After clicking Add, the system
generated a primary contract document and listed it on the Contract Terms tab,
tagged with the template it was generated from.
Note
Note:
Contact Expert automatically added
this Lability Cap Clause in the table of contents of terms and conditions. This
is because we have configured the rule if and specified the threshold value. Please
refer to contract expert configuration.
Contract Terms tab — generated document 3001-1.pdf, Terms
Template IT Services BPA Standard Terms, Authoring Party Internal.
5.4 Reviewing the Generated Terms and the Contract Expert Deviation
Opening 3001-1.pdf, the table of
contents showed all five sections from the template, plus a sixth entry —
Liability Cap — High Value Agreements — that Contract Expert inserted
automatically because the $1,000,000 contract amount is well above the AED 200,000
(~USD 54,000) threshold set on the High Value PO Threshold constant in Section
4.1.
Generated contract terms — table of contents showing Liability
Cap — High Value Agreements inserted by Contract Expert.
5.5 Submitting for Approval
Back on the Overview tab, I
clicked Submit for Approval.
Overview tab — Submit for Approval highlighted.
On the Parties tab, the Customer
and Supplier roles were already populated from the values entered at contract
creation — US1 Business Unit as Customer and Emirates Steel as Supplier — along
with the default Ship-to and Bill-to locations.
Parties tab — Customer US1 Business Unit, Supplier Emirates
Steel, with default locations.
Once approved, the contract
status changed to Active and it appeared in the My Contracts list with its
final amount and dates.
My Contracts list — contract 3001 now Active, Buy: Lines,
$1,000,000.
With the contract Active, the
Overview tab now shows a Create Purchasing Document action in place of Submit
for Approval.
This is the link between
Procurement Contracts and the rest of Procurement: from here you can generate a
Purchase Order directly from the contract or create a PO separately and attach
this contract as its source document.
Either way, the released PO
inherits the contract's terms and lines and is validated against it — so the
clause governance built in Sections 1–4 carries all the way through to the
transaction the supplier sees.
6. Integration with Procurement
Once active, the approved
contract terms travel with the Procurement Contract through every Purchase
Order or release created against it. Buyers creating those documents don't need
to remember which clauses apply — the terms are already locked into the agreement
and validated automatically when a purchasing document references the contract
as its source.
7. Amendments and Lifecycle Management
•
Amendments go through a change
order, with contract terms editable again only within the change order context.
•
Any new deviation introduced
during the amendment is captured in a fresh run of the Contract Deviations
Report.
•
Full revision history remains
visible on the Contract Terms tab for audit purposes.
Conclusion
Oracle Fusion Procurement
Contracts brings centralized governance — a controlled clause library, an
approval lifecycle, and rule-driven automation — directly into the transaction
itself, rather than requiring contract terms to be managed as a separate document
or attachment. The real payoff shows up exactly where I tested it in this post:
a buyer creating a routine agreement never has to think about which clause
applies at which contract value. Contract Expert handles that automatically,
and the printed contract terms give auditors and approvers a clean trail of
exactly what was applied and why.
A successful implementation
depends on three things: a well-designed Contract Terms Library, properly
scoped Business Unit and approval setup, and clear alignment with how your
legal and procurement teams actually want contracts structured. Get those right,
and the rest — templates, rules, and authoring — falls into place quickly.
In a follow-up post, I'll cover
electronic signature integration on Fusion Procurement Contracts and how
Contract Expert rules can be chained together using follow-up questions.
Reference
• Implementing Procurement: https://docs.oracle.com/en/cloud/saas/procurement/25d/oapro/implement-procurement.html
• How Contract Terms Library Setups Work Together: https://docs.oracle.com/en/cloud/saas/sales/facec/how-contract-terms-library-setups-work-together.html
• Examples of Using the Oracle Contracts Terms Library: https://docs.oracle.com/en/cloud/saas/sales/fascc/examples-of-using-the-oracle-contracts-terms-library.html
• How Contract Expert Works: https://docs.oracle.com/en/cloud/saas/sales/fascc/how-contract-expert-works.html
• How Contract Expert Rules Work: https://docs.oracle.com/en/cloud/saas/sales/fascc/how-contract-expert-rules-work.html