Oracle Cloud Purchasing in Redwood: Modernizing Purchase Orders, Agreements, Requisitions and Procurement Operations

Oracle Cloud Purchasing is moving toward a more modern procurement experience through the Redwood user interface, with new capabilities focused on usability, extensibility, intelligent assistance, stronger search and faster purchasing workflows. Oracle describes Redwood Purchasing as the next generation of procurement in the cloud, built on the Oracle Redwood design system and supported by extensibility through Visual Builder Studio Business Rules. The experience also introduces generative AI, guided journeys, AI agents, unified search, saved searches and mass actions. For procurement teams, this is more than a visual refresh. Redwood Purchasing changes how buyers work with purchase orders, agreements, requisitions, contracts, exceptions and supplier-related activity while creating a foundation for future AI-driven capabilities. 

A More Modern Oracle Purchasing Experience 

The Redwood Purchasing experience is designed around two broad themes: 

Modern and extensible user experience 

Oracle highlights: 

• A next-generation user interface 
• Redwood design-system components 
• Extensibility through VB Studio Business Rules 

Intelligent and powerful procurement 

Oracle also highlights: 

• Generative AI insights 
• Guided Journeys 
• AI agents 
• Unified search 
• Keyword and filter search 
• Saved searches 
• Mass actions 

These capabilities address a common procurement challenge: buyers often spend a significant amount of time navigating transactions, searching for documents and processing repetitive updates. A more integrated Redwood experience can help reduce that administrative effort. 

Faster Search and Navigation for Buyers 

Search is central to day-to-day procurement work. Buyers need to find purchase orders, requisitions, agreements and supporting information quickly. 

Oracle’s Redwood Purchasing enhancements include: 

• Fast and efficient search 
• Enhanced navigation 
• Quick access to tasks 
• Keyword search 
• Filtering 
• Extensible KPIs 

This improves the buyer experience because users can locate relevant purchasing documents using broader search criteria rather than relying only on rigid navigation paths. Saved searches can also help buyers repeatedly access the same operational views. 

For example, a buyer could maintain searches around: 

• Open purchase orders 
• Orders on hold 
• Agreements nearing action 
• Specific suppliers 
• Requisition backlogs 
• Exception transactions 

This makes procurement work more operationally focused. 

Redwood Alerts and Exceptions 

Oracle’s Redwood Purchasing enhancements also include modern alerts and exception handling. Exception-based work is increasingly important in procurement. Buyers should not need to spend time reviewing every transaction manually. Instead, the system should help surface the transactions requiring attention. 

Alerts and exceptions can help users focus on: 

• Orders requiring action 
• Schedule issues 
• Supplier-related problems 
• Invoice holds 
• Agreement changes 
• Procurement exceptions 

This supports a more proactive purchasing model. 

Review and Resolve Invoice Holds 

Oracle includes the ability to review and resolve invoice holds as part of Redwood Purchasing enhancements. Invoice holds can delay payment and increase coordination between procurement, accounts payable and suppliers. Making these holds visible within the buyer’s experience can help teams understand why a document is blocked and take action faster. This is especially valuable for organizations where procurement teams are frequently involved in investigating invoice or purchase-order mismatches. 

Mass Actions Across Orders and Schedules 

Mass actions are another important Redwood Purchasing capability. 

Oracle identifies mass actions across orders and schedules for actions such as: 

• Cancel 
• Close 
• Hold 
• Freeze 

This can significantly reduce repetitive transaction work. Instead of opening multiple purchase orders individually, buyers can process groups of documents together when the same action applies. 

Potential scenarios include: 

• Closing old purchase orders 
• Placing several orders on hold 
• Cancelling obsolete schedules 
• Freezing groups of purchasing documents 

For high-volume procurement environments, bulk processing can create meaningful productivity improvements. 

Purchase Order Capabilities Available Through 25D 

Oracle’s Redwood roadmap presentation lists several Purchase Order capabilities available through Update 25D. 

These include: 

• Direct Procurement Orders 
• Create, edit and view Requester Change Orders 
• Inclusive and exclusive taxes 
• Recoverable and non-recoverable taxes 
• Tax-line visibility 
• Revision history 
• Change history 
• Buyer review of requester-initiated changes 
• Extensible KPIs in Buyer’s Workbench 
• Additional extensibility capabilities 

These capabilities expand Redwood beyond simple document viewing and into full purchasing execution. 

Direct Procurement Orders 

Direct Procurement Orders are available within the Redwood Purchase Order experience through 25D. Direct procurement is particularly important for organizations purchasing materials directly tied to production, fulfillment or operational demand. 

The buyer must often work with: 

• Item information 
• Supplier details 
• Delivery schedules 
• Taxes 
• Change orders 
• Manufacturing or inventory requirements 

Supporting these processes in Redwood allows procurement teams to work within the new interface for more complex purchasing scenarios. 

Requester Change Orders 

Oracle also supports creating, editing and viewing Requester Change Orders in Redwood. Requester-driven changes are common after a purchase order has already been created. 

Examples could include: 

• Quantity changes 
• Delivery-date changes 
• Distribution updates 
• Line modifications 

Buyers need visibility into these changes so they can review and determine whether the requested modification should be accepted. Oracle also allows buyers to edit or reject requester-initiated changes. This strengthens buyer control while maintaining collaboration with requesters. 

Purchase Order Revision and Change History 

Redwood also includes revision and change history for purchase orders and change orders. Change history is critical in procurement because purchase orders often evolve throughout their lifecycle. 

Buyers may need to understand: 

• What changed 
• When the change occurred 
• Which revision introduced it 
• Whether the document was already approved 
• How the change affects supplier commitments 

Having this history available through Redwood helps support auditability and operational transparency. 

Tax Visibility in Purchase Orders 

Oracle includes tax capabilities for inclusive and exclusive tax as well as recoverable and non-recoverable tax, along with tax-line visibility. This is particularly important for organizations operating across multiple tax jurisdictions. Procurement teams often need to understand how tax treatment affects total purchase cost. Improved tax visibility allows buyers to work with more complete purchasing information without relying on separate financial analysis. 

Extensible KPIs in Buyer’s Workbench 

Oracle also includes extensible KPIs in the Buyer’s Workbench. Procurement teams do not all manage the same priorities. One organization may focus on overdue orders. Another may prioritize supplier delays. Another may want visibility into agreement usage or change-order volume. Extensible KPIs allow organizations to bring more relevant metrics into the purchasing experience. This can help buyers work from a more focused operational dashboard. 

Purchase Agreement Workbench 

Redwood Purchasing also expands agreement management. 

Capabilities available through 25D include: 

• Purchase Agreement Workbench actions and alerts for buyers 
• Purchase Agreement Workbench for suppliers 
• Create and edit Blanket Purchase Agreements 
• Create and edit Contract Purchase Agreements 
• View Purchase Agreements as buyer and supplier 

Purchase agreements are central to strategic procurement. They define negotiated commercial terms that may later be consumed by purchase orders and requisitions. Making agreement management more accessible in Redwood helps procurement teams maintain closer control over supplier commitments. 

Buyer and Supplier Agreement Collaboration 

The availability of agreement views for both buyers and suppliers is especially important. Procurement processes are collaborative by nature. Suppliers may need to review agreement terms, while buyers need to monitor changes and actions. A shared Redwood-based agreement experience can make this collaboration more consistent. Oracle’s roadmap also continues this direction with future agreement change-order capabilities and supplier acknowledgment functionality. 

Process Requisitions in Redwood 

Oracle’s Redwood capabilities also extend to requisition processing. 

Available capabilities include: 

• Requisition-line grouping options 
• Manual grouping 
• Search across processed and unprocessed requisition lines 

These functions help buyers manage demand before it becomes a purchase order. Large procurement teams often receive many requisition lines from different requesters, departments or business units. Grouping and searching those lines efficiently can help buyers consolidate demand and create more effective purchasing documents. 

Requisition-Line Grouping 

Grouping requisition lines allows buyers to determine how individual demand lines should be combined for purchasing. 

This can help improve: 

• Supplier consolidation 
• Purchase-order efficiency 
• Delivery management 
• Administrative workload 

Manual grouping gives buyers more control where automated grouping does not match the desired procurement strategy. 

Search Across Processed and Unprocessed Requisitions 

Oracle also allows users to search both processed and unprocessed requisition lines. This provides broader visibility into requisition demand. Instead of reviewing only lines waiting for action, buyers can also investigate already processed demand when researching historical or current purchasing activity. 

Quick Access from the Redwood Landing Page 

Oracle’s Redwood landing-page capabilities provide quick access to: 

• Requisitions 
• Purchase Orders 
• Agreements 

through Recent Orders and Recent Agreements. This can reduce navigation time. Buyers often return repeatedly to recently handled documents. Providing immediate access from the landing page makes routine procurement work faster. 

Contract Management in Redwood Purchasing 

Oracle also includes contract-related purchasing capabilities through 25D. 

These include: 

• Add or remove structured contract terms 
• Attach or remove primary contract documents 
• Attach or remove contract and supporting documents 
• Change contract source 
• Check for clause updates 
• Copy terms when duplicating purchase orders 
• Use Contract Expert rules to default terms templates and add clauses 

This is significant because procurement and contract management are often closely connected. A purchase order may inherit or reference contract terms, and buyers need visibility into the supporting legal framework. Bringing contract-related actions into Redwood helps reduce fragmentation between purchasing and contract administration. 

Structured Contract Terms and Supporting Documents 

Procurement documents frequently depend on more than commercial data. 

They may require: 

• Legal clauses 
• Primary contracts 
• Supporting documents 
• Negotiated terms 
• Supplier documentation 

Redwood support for attaching and managing these documents creates a more complete purchasing workspace. It can also help ensure that the buyer is working with the right contractual context. 

Contract Expert Rules 

Oracle also supports Contract Expert Rules for defaulting terms templates and adding clauses without user variables. This introduces more automation into contract-term handling. Instead of manually selecting every term or clause, business rules can help determine what should apply. This can improve consistency in purchasing documents. 

Oracle Purchasing Redwood Roadmap for 26A 

Oracle’s roadmap identifies several Purchase Order capabilities targeted for 26A. 

These include: 

• Complex Work Procurement 
• Supplier discounts and credit-line capture 
• Special handling 
• DFFs in search results 
• Applying contract amendments as change orders 
• Consuming requisition demand from purchase orders released from contracts 

These roadmap items expand Redwood into more complex enterprise purchasing scenarios. Because they are roadmap items, organizations should treat them as product direction rather than guaranteed functionality or timing. Oracle explicitly notes that development and release plans may change. 

Complex Work Procurement 

Complex Work Procurement is shown as targeted for 26A. This can be important for procurement involving services, milestones or work-based deliverables rather than simple goods purchasing. 

Complex procurement typically requires additional controls around: 

• Work progress 
• Deliverables 
• Payment milestones 
• Supplier performance 
• Contract terms 

Expanding Redwood to these scenarios would allow more advanced procurement activity to move into the new user experience. 

Supplier Discounts and Credit Lines 

Oracle also identifies supplier discounts and credit lines on purchase orders as part of the 26A roadmap. Capturing supplier discounts directly in purchasing can improve financial accuracy. Procurement teams can better understand actual commercial value rather than relying only on base purchase prices. 

Special Handling 

Special Handling is another roadmap capability. 

Some purchase orders require nonstandard treatment because of: 

• Delivery requirements 
• Product characteristics 
• Compliance needs 
• Packaging rules 
• Internal business policies 

Supporting special handling directly in Redwood can reduce the need for manual notes or off-system processes. 

DFFs in Search Results 

Oracle’s roadmap also includes Descriptive Flex fields in search results. DFFs are commonly used by customers to capture business-specific information. Making DFFs searchable and visible in Redwood is important for organizations that depend heavily on custom attributes. Future roadmap capabilities also include using DFFs as filters and keyword-search criteria. 

Purchase Order Enhancements for 26B and Beyond 

For 26B and later, Oracle shows additional capabilities including: 

• Add Lines from Catalog 
• Supply Chain Financial Orchestration 
• Federal Financial DFFs 
• Search Lines, Schedules and Distributions 
• Edit Multiple Lines, Schedules and Distributions 
• Duplicate Purchase Order Lines 
• Purchase Order Checklists 
• DFFs as filters and keyword-search fields 

These capabilities indicate Oracle’s continued focus on bringing deeper purchasing functionality into Redwood. 

Purchase Agreement Roadmap 

The agreement roadmap is also substantial. 

Capabilities targeted for 26A include: 

• Create, edit and view Change Orders on agreements 
• Buyer and supplier agreement changes 
• Purchase Agreement acknowledgments 
• DFFs in search results 
• Contract amendments applied as change orders 

For 26B and beyond, Oracle lists: 

• Revision and change history 
• Agreement checklists 
• Collaborative catalog authoring 
• Agreement-line uploads 
• Purchase Agreements for catalog administrators 
• Agreement renegotiation 
• Add Lines from Catalog 
• DFF-based filtering and search 

These enhancements show a broader move toward end-to-end supplier agreement management in Redwood. 

Supplier Acknowledgment of Agreements 

Oracle’s roadmap includes supplier acknowledgment of Purchase Agreements and agreement changes. Acknowledgment helps create clearer agreement between buyer and supplier. It can reduce uncertainty about whether the supplier has reviewed and accepted changes. This is especially useful when agreements affect large or ongoing procurement relationships. 

Agreement Change Orders 

Change Orders for agreements are another important roadmap capability. Long-term supplier agreements often evolve over time. Pricing, quantities, terms or validity periods may change. A structured change-order process helps preserve history and governance instead of overwriting existing agreement data. 

Generative AI Supplier Suggestions 

One of the most notable future capabilities appears in Process Requisitions. Oracle’s roadmap includes Gen AI Based Supplier Suggestions for 26B and beyond. This shows how AI may become increasingly embedded into purchasing decisions. Rather than requiring buyers to manually research every supplier option, AI could help surface potential suppliers based on relevant procurement context. However, supplier selection remains a business decision that should be reviewed by the responsible procurement team. 

AI Is Available Only Through Redwood 

Oracle explicitly states that AI features are available only through the Redwood UI in Fusion Applications. This is a major strategic consideration. Organizations interested in Oracle’s future procurement AI capabilities will increasingly need to plan for Redwood adoption. Redwood is therefore becoming not just a UI choice, but an access point for newer intelligent capabilities. 

Is Redwood Purchasing Mandatory? 

Oracle states that transitioning to Redwood Purchasing is not currently mandatory. However, Oracle advises customers to begin planning because future development and new functionality will be centered on Redwood. Oracle also states that an adoption deadline is expected to be announced in the future. For procurement leaders, this means migration planning should not be postponed indefinitely. Even where the classic interface still meets current needs, newer functionality will increasingly appear in Redwood. 

When Should Organizations Start? 

Oracle’s guidance is clear: Get started now. Organizations are encouraged to evaluate Redwood Purchasing, assess AI capabilities and develop a migration plan. A phased approach can reduce migration risk. 

Teams can begin by identifying: 

• Current purchasing processes 
• High-volume buyer activities 
• Customizations 
• DFF usage 
• Search requirements 
• Approval dependencies 
• Contract requirements 
• Supplier collaboration processes 
• AI use cases 

This provides a clearer picture of what needs to be tested before production adoption. 

Is Redwood a Like-for-Like Replacement for Classic ADF? 

Oracle explains that Redwood will generally support the same business functions buyers perform in Classic ADF, but not necessarily in the same way. Some flows have been redesigned to improve efficiency. Any functionality Oracle chooses to exclude will be documented in the relevant What’s New material. This distinction matters. Organizations should not evaluate Redwood purely by asking whether each screen looks identical to Classic. Instead, they should validate whether each business process can still be completed effectively. 

No Single Master List of Classic vs Redwood Differences 

Oracle also confirms that there is no single comprehensive document listing every difference between Classic ADF and Redwood Purchasing. Differences are documented by functional area and page within feature-release documentation. This means migration assessment should be process driven. Organizations should review the features they actually use and compare them with the corresponding Redwood capabilities. 

Extensibility in Redwood Purchasing 

Extensibility is another important migration consideration. Oracle states that most tables in Redwood Purchasing support Business Rules, although some form-layout scenarios have exceptions. Oracle also notes that extensibility is continuing to expand and recommends reviewing feature-release documentation for create, edit and view scenarios across purchase orders and agreements. Customers with extensive Classic customizations should therefore perform a detailed extensibility review. Not every customization should automatically be recreated. Some may no longer be necessary because Redwood workflows operate differently. 

VB Studio Business Rules 

Oracle identifies VB Studio Business Rules as the core mechanism for Redwood Purchasing extensibility. This enables organizations to tailor aspects of the user experience based on business requirements. 

Potential scenarios include: 

• Conditional field behavior 
• Role-based UI behavior 
• Defaulting 
• Validation 
• Business-specific guidance 

Extensibility should be approached carefully so that custom requirements do not unnecessarily complicate the standard Redwood experience. 

Why Redwood Purchasing Matters 

Oracle Redwood Purchasing brings together several themes that matter to modern procurement teams. 

Faster execution 

Search, saved searches, quick actions and mass actions help reduce buyer workload. 

Better exception management 

Modern alerts, invoice-hold review and procurement exceptions help users focus on what needs attention. 

Improved purchasing visibility 

Revision history, change history, tax data and KPIs provide greater transaction context. 

Stronger agreement management 

Buyers and suppliers gain richer Purchase Agreement capabilities. 

Integrated contract information 

Structured terms, supporting documents and clause management become part of the purchasing experience. 

AI readiness 

Future procurement AI capabilities are tied directly to Redwood. 

Taken together, these capabilities make Redwood an increasingly important part of Oracle’s procurement roadmap. 

Preparing for Oracle Redwood Purchasing 

A successful migration should evaluate both functionality and user behavior. 

Organizations should review: 

• Purchase-order processes 
• Requester change orders 
• Requisition processing 
• Purchase Agreements 
• Contract terms 
• Invoice-hold handling 
• Supplier collaboration 
• Search requirements 
• Mass-action opportunities 
• DFF usage 
• Extensibility 
• KPIs 
• Security roles 
• AI adoption priorities 

Testing should focus on complete business scenarios rather than simply validating individual pages. This helps ensure the procurement process still works end to end. 

How NexInfo Helps with Oracle Redwood Purchasing 

NexInfo helps organizations assess, plan and execute Oracle Fusion Cloud Procurement and Purchasing transformation. 

For Redwood Purchasing, NexInfo can support: 

• Redwood Purchasing readiness assessment 
• Classic ADF-to-Redwood process analysis 
• Purchase Order process review 
• Purchase Agreement assessment 
• Requisition-processing review 
• Change-order workflow analysis 
• Contract integration review 
• Search and KPI design 
• DFF and extensibility assessment 
• VB Studio Business Rules 
• Buyer-role and security review 
• AI use-case assessment 
• Regression testing 
• User-acceptance testing 
• Buyer training 
• Migration planning 
• Production rollout 
• Managed services 

The goal should be to use the Redwood transition as an opportunity to simplify procurement processes rather than simply recreate older workflows in a new interface. 

Conclusion 

Oracle Cloud Purchasing in Redwood represents a significant evolution of the Oracle procurement user experience. Through 25D, Oracle has expanded Redwood capabilities across Purchase Orders, Agreements, Process Requisitions, Contract Terms and buyer landing pages. At the same time, the roadmap extends further into complex procurement, agreement change orders, catalog integration, Descriptive Flex fields, bulk editing and AI-based supplier suggestions. Oracle is also making Redwood increasingly important by focusing new development and AI functionality there rather than in Classic ADF. 

For procurement organizations, the practical message is clear: 

Redwood migration should be treated as a business-process modernization initiative, not simply a UI conversion. Organizations that begin planning early can evaluate process changes, remove unnecessary customizations and prepare for the next generation of intelligent Oracle Procurement functionality. 

FAQs 

Is Oracle Redwood Purchasing mandatory? 

Not currently. Oracle states that Redwood migration is not mandatory yet, but future functionality will be centered on Redwood, and customers are advised to begin planning. 

What capabilities are available in Redwood Purchasing through 25D? 

Capabilities include Purchase Orders, requester change orders, tax handling, revision history, Purchase Agreements, requisition processing, landing-page quick access, contract-term management, AI capabilities, search, mass actions and extensible KPIs. 

What mass actions are supported in Redwood Purchasing? 

Oracle lists mass actions including cancel, close, hold and freeze across orders and schedules. 

Does Redwood Purchasing Support Purchase Agreements? 

Yes. Through 25D, Oracle supports Purchase Agreement Workbench capabilities, buyer and supplier agreement views, and create/edit functionality for BPA and CPA agreements. 

Are AI features available in Classic ADF Purchasing? 

No. Oracle states that AI capabilities are available only through the Redwood UI in Fusion Applications. 

Does Redwood provide everything available in Classic ADF? 

Oracle states that Redwood generally supports the same business functions, but some processes are redesigned and may not work exactly the same way as Classic ADF. 

Is there one document listing all differences between Classic and Redwood? 

No. Oracle says differences are documented by individual functional area and page within the corresponding feature-release documentation. 

Does Redwood Purchasing support extensibility? 

Yes. Oracle states that most tables support Business Rules, with some exceptions for form layouts, and that extensibility capabilities continue to expand. 

What Purchase Order functionality is planned for 26A? 

Oracle’s roadmap includes Complex Work Procurement, supplier discounts and credit lines, Special Handling, DFFs in search results, contract amendments as change orders and requisition-demand consumption from contract-released purchase orders. 

Is Oracle planning AI-based supplier suggestions? 

Yes. Oracle’s roadmap lists Generative AI-based supplier suggestions under Process Requisitions for 26B and beyond.