Oracle Fusion Cloud Procurement · Implementation guide

How to Enable Responsive Self Service Procurement

A clear implementation guide for enabling Responsive or Redwood Self Service Procurement (RSSP), setting up security and search, and resolving common enablement issues.

Recommended approach: start with a controlled pilot in a nonproduction environment. Keep Classic Self Service Procurement available during testing, then make RSSP the default only after business scenarios, security, catalog search, and support readiness are signed off.

1. Before you begin

RSSP is the responsive requisitioning experience in Oracle Fusion Cloud Procurement. It relies on the same core procurement configuration as Classic Self Service Procurement: business units, requesters, catalog content, suppliers, agreements, approvals, purchasing controls, and accounting.

Confirm that a pilot requester can create and submit a requisition in the current experience.
Confirm that the requisitioning business unit, procurement business unit, procurement agents, document styles, approvals, and purchasing controls are configured.
Confirm that catalog content, smart forms, punchout catalogs, suppliers, supplier sites, agreements, items, UOMs, prices, and effective dates are valid for the pilot business unit.
Confirm that the implementation team can access Setup and Maintenance, Security Console, and Scheduled Processes.

2. Enable RSSP

1Open the Procurement opt-in page

Navigator > My Enterprise > Setup and Maintenance > Manage Features by Offering > Procurement > Opt In Features

Use the Tasks panel search if Manage Features by Offering is not visible.

2Choose the correct parent feature

Feature	Use it when	Result
Procure Goods and Services Using the Responsive or Redwood Self Service Procurement Application	You are running a pilot or phased rollout.	Classic SSP remains available. Pilot users require the RSSP access privilege.
Enable the Responsive or Redwood Version as the Default Self Service Procurement Application	You are ready for a full production cutover.	RSSP becomes the default and Classic Purchase Requisitions navigation is hidden.

Select the feature, choose Enable, then select Save and Close. Do not use the default feature simply to solve a pilot role issue: it affects all users.

3Review optional child opt-ins

Enable only features that have an approved business requirement, such as advanced requisition entry, multiple distributions, view approvers, urgent requisitions, or special handling. Each optional feature can require additional setup or privileges. Record the exact feature name and release in the deployment record.

3. Configure access

Navigator > Tools > Security Console > Roles > Search for Requisition Self Service User

Create a custom role using your organization’s role-design standard. Do not edit Oracle seeded roles.
For a pilot or coexistence rollout, open the custom role and select Edit Role > Function Security Policies.
Add Manage Requisition with the Responsive or Redwood Self Service Procurement Application (POR_MANAGE_REQ_WITH_PWA_PRIV).
If the role is not based on Requisition Self Service User, also review Oracle’s documented baseline privileges for requisitions, enterprise structures, supply sources, location and geography data, catalog access, and the UOM list of values.
Assign the custom role to a pilot user, complete the provisioning process, and test in a fresh user session.

Note: when the default RSSP feature is enabled, Oracle documents that the RSSP-specific privilege is not required for access. The user still needs the underlying requisition, data, and business-unit access required by the process.

4. Configure profile options and Elastic Search

Profile options

Setup and Maintenance > Tasks > Manage Administrator Profile Values > search by profile option code

Profile option	Site value	Purpose
`ORA_FND_SEARCH_EXT_ENABLED`	Yes	Enables the Search Extension Framework.
`ORA_FND_SEARCH_FETCH_COUNT`	100	Row fetch count for initial ingest.
`ORA_FND_RESULT_SET_RESET_MINS`	60	Result-set reset interval in minutes.
`ORA_POR_USE_SUPP_SITE_INVOICE_CURR`	Yes, only if required	Optional supplier-site invoice-currency defaulting for noncatalog, smart-form, and Enter Requisition Line requests.

For each option, add or edit the Site profile level, enter the value, then select Save and Close.

ESS jobs

Navigator > Tools > Scheduled Processes > Schedule New Process

Order	Process name	Parameter and value	When to run
1	Transform Data Post Upgrade	Feature Name = `POPULATE_ELASTIC_INTERMEDIATE_TABLE`	Catalog-search setup. Confirm Succeeded, then wait at least two hours.
2	ESS job to create index definition and perform Initial Ingest to OSCS	Index Name to Reingest = `fa-prc-shoppingcatalog`	Catalog search. Run once during initial setup.
3	ESS job to create index definition and perform Initial Ingest to OSCS	Index Name to Reingest = `fa-prc-por`	Requisition search and My Requisitions. Run once during initial setup.
4	ESS job to create index definition and perform Initial Ingest to OSCS	Index Name to Reingest = `fa-prc-pa`	Agreement list of values. Run when users need agreements.
5	ESS job to run Bulk Ingest to OSCS	Program Name to run Bulk Ingest = `prc_por_downstream`	Schedule periodically to refresh downstream requisition status.

Before submitting catalog processes: the administrator must have Manage Procurement Catalog Content. Without it, the Feature Name parameter may not be available and the Transform Data Post Upgrade request can fail.

5. Validate the pilot

Sign in as a pilot requester and open Purchase Requisitions (New).
If Preferences opens, set valid requester, requisitioning business unit, deliver-to location, destination type, charge account, and project defaults.
Test catalog search and one catalog requisition. Confirm the item is purchasable and that source, UOM, price, supplier, and agreement values are correct.
Test noncatalog, smart form, punchout, internal transfer, project, budgetary-control, and multiple-distribution scenarios only when they are in scope.
Submit the requisition and validate approval, PO creation, receipt, lifecycle status, and My Requisitions results.

6. Common enablement issues and practical resolution

Blank page when a user opens Purchase Requisitions (New)

Resolution sequence:

For coexistence, confirm that POR_MANAGE_REQ_WITH_PWA_PRIV is in the user’s actual custom role.
Compare the role hierarchy, data roles, business-unit access, requester assignment, and location access of one working and one failing user.
Have the affected user complete Preferences and correct every required default.
Retest in a fresh session. If unresolved, raise an Oracle Support request with the role comparison, user details, exact behavior, and release level.

Catalog items, smart forms, or search results are missing

Confirm the content zone is active and assigned to the requester’s requisitioning business unit.
Confirm that the item or smart form is published and that the user is authorized to see it.
Verify the three search profile values.
Review Scheduled Process history for POPULATE_ELASTIC_INTERMEDIATE_TABLE and fa-prc-shoppingcatalog.
For item-level failures, validate purchasability, UOM, category, source, price, supplier site, and effective dates.

My Requisitions is empty or status is not current

Confirm the fa-prc-por initial ingest completed successfully, then verify that the recurring prc_por_downstream bulk ingest request is running and succeeding. Confirm the requester and requisitioning-business-unit access used in the test.

Agreement list of values is empty

Validate the agreement’s status, effective dates, procurement business unit, supplier site, currency, line eligibility, and user access. Then confirm that the fa-prc-pa initial ingest has completed successfully.

UOM invalid, item not purchasable, or price required

Treat these as master-data or sourcing checks first. Validate item purchasing status in the deliver-to organization, UOM and conversions, purchasing category, supplier and supplier item, agreement or BPA line, price, currency, effective dates, and source selection.

Classic fields or actions are missing

Determine whether the function is a documented RSSP difference, requires a separate opt-in, or needs a supported Redwood configuration or extension. Do not assume that Classic Page Composer customizations transfer to RSSP.

Source notes

This guide is based on Oracle Fusion Cloud Procurement implementation guidance, Oracle readiness documentation, and recurring Customer Connect reports about blank screens, role setup, Elastic Search, and My Requisitions visibility. Oracle documentation for the release installed in your pod remains the governing configuration source.