Oracle EBSOracle Fusion & OCIKatrinaAI & AgentsClientsAboutBlog
Book a call
Back to Blog
Oracle Cloud10 min read

Enabling Oracle Fusion Cloud Redwood for Sourcing / Negotiations — the 5 profile options

A

Ashot Manukyan

July 28, 2026

Objective

This note documents the exact procedure we ran to enable the Redwood experience for Supply Chain Sourcing / Negotiations on an Oracle Fusion Cloud Applications test pod: the 5 profile options involved, the step-by-step in Setup and Maintenance, and — most usefully — how to prove the switch actually happened.

The practical identification rule: in Oracle Fusion, the classic (ADF) experience uses URLs with /fscmUI/faces/... while Redwood uses routes with /fscmUI/redwood/.... If the URL contains /faces/, it is NOT Redwood. Everything else — look and feel, navigator labels — can mislead you; the URL cannot.

Prerequisites

  • A user with the implementation/administrator role (access to Setup and Maintenance).
  • Permission to update profile options at Site level.
  • The Procurement offering enabled in the environment.
  • Oracle Fusion Cloud Applications 25A or later (the Redwood Sourcing pages were released between 25A and 26B).

    • The 5 profile options

    The Redwood experience for Sourcing / Negotiations is activated with five profile options, all at Site level:

  • ORA_PON_SOURCING_REDWOOD_ENABLED = Yes — activates the Sourcing Landing Page and the Manage Negotiations page in Redwood.
  • ORA_PON_CREATE_NEGOTIATION_REDWOOD_ENABLED = Yes — activates the negotiation creation flow (RFQ / RFI / Auction) in Redwood.
  • ORA_PON_AWARD_NEGOTIATION_REDWOOD_ENABLED = Yes — activates negotiation award and result-document creation in Redwood.
  • ORA_FND_SEARCH_EXT_ENABLED = Yes — enables the Search Extension Framework that Redwood searches require.
  • ORA_FND_SEARCH_FETCH_COUNT = 100 — batch size for the search index ingest.

    • The first three are the Sourcing pages themselves; the last two are the search infrastructure they sit on. Skipping the ORA_FND_SEARCH ones is the classic way to end up with a Redwood page whose search returns nothing.

    Step by step

    Setup and Maintenance

  • Log in to the pod with the administrator user.
  • Navigator → My Enterprise → Setup and Maintenance (or the direct URL /setup/faces/TaskListManagerTop).
  • Select the Procurement offering in the top dropdown.

    • Open the Manage Administrator Profile Values task

  • In the right-hand Tasks panel, click Search.
  • On a Spanish-language pod, search the task name with the pattern %valores%perfil% — the real task name is singular («perfil», not «perfiles»), and the wildcard pattern sidesteps the morphology problem entirely.
  • Click Manage Administrator Profile Values (Gestionar valores de perfil de administrador) in the results grid.

    • Enable each profile option

  • Paste the exact profile option code (e.g. ORA_PON_SOURCING_REDWOOD_ENABLED) into the Profile Option Code field and search.
  • Click the result row; the Profile Values block expands below.
  • If there is no Site-level row, add one: Actions → New → Profile Level = Site.
  • Set the Profile Value (Yes for the four booleans, 100 for ORA_FND_SEARCH_FETCH_COUNT).
  • Save (without closing) before moving to the next code; Save and Close after the fifth.

    • Log out, log back in

    Site-level profile option changes may require a full logout/login for the Navigator menu to pick up the new Redwood entry. Do it — the next section explains why.

    Validating the switch — before vs. after

    The conclusive test is the URL the Sourcing landing resolves to when opened from the Navigator.

    Before (classic ADF): Navigator entry Procurement → Negotiations opens the classic infolet Overview page ("My Negotiations", "Messages", award donut charts) at /fscmUI/faces/FndOverview?... — contains /faces/, so it is ADF, not Redwood.

    After (Redwood): a new Navigator entry opens the Sourcing Landing Page — header, recent-negotiations counter, a negotiations table (Negotiation / Status / Title / Supplier responses / Unread messages / Last activity) and an Actions + Quick access side panel — at /fscmUI/redwood/sourcing/landing-page/overview. Contains /redwood/ and no /faces/: this is Redwood.

    The 'Abastecimiento (nuevo)' gotcha

    After enabling the profile options and logging back in, the Navigator grows a new entry — on a Spanish pod it is labeled «Abastecimiento (nuevo)» ("Sourcing (new)") under the Procurement area. That entry, and not the old «Negociaciones», is the one that opens the Redwood page.

    The classic Procurement → Negotiations entry keeps working and keeps resolving to the ADF Overview. That is expected during the coexistence period — nothing is broken. If users report "we enabled Redwood and nothing changed", this navigator split is almost always why.

    Summary

  • 5 profile options enabled at Site level.
  • Logout and re-login to refresh the navigation cache.
  • URL verification: from /fscmUI/faces/FndOverview to /fscmUI/redwood/sourcing/landing-page/overview.
  • Visual verification: the Redwood Sourcing Landing Page with its negotiations table, Actions panel and recent-negotiations counter.

    • References

  • Oracle Fusion Cloud Procurement — What's New 25A..26B (Sourcing Landing Page, Create Negotiation, Award Negotiation in Redwood).
  • Oracle Fusion Cloud Applications — Implementing Procurement (Profile Options).
  • Oracle Help Center — Manage Administrator Profile Values.
    • Back to Blog
    Share: