Enable and Set Up Redwood Pages

Redwood is Oracle’s next-generation user experience. Redwood brings state-of-the-art, consumer-grade user experiences to the sophisticated enterprise scenarios that Oracle enables.

Many of the application pages and task flows have been re-created in Redwood to improve the user experience and, in some cases, to introduce enhanced capabilities, such as improved search.

Enable Redwood Pages

Most pages are enabled by using a profile option to turn them On or Off. Many, though not all, of the Redwood-related profile options are turned off by default. You can decide whether, and when, to enable those Redwood pages in your enterprise’s implementation. At some point, each Redwood page is turned on by default.

We recommend you review this document, My Oracle Support: SCM Redwood Pages with Profile Options (Doc ID 3037517.1) for every new release. The table in the Profile Options for Redwood Pages section of this document identifies the profile options that control each Redwood page or task flow, and the release in which the Redwood page is enabled by default, if that release has been determined.

Note that not all Redwood pages are controlled by profile options. Some are controlled by opting into features in the Offerings or Setup and Maintenance work areas. But in most cases, if an existing application page is re-created in Redwood, that page is controlled by a profile option. Additional details may be found in the What’s New guides for Maintenance for each release, as well as in additional sections in this guide if specific setup is required.

Redwood pages that include a search and results region may use the Oracle Search Cloud Service (OSCS). Therefore, in addition to enabling the profile and ensuring you have the right privileges, you must perform the initial ingest of the object data into its corresponding index. If this step isn't completed, the pages won't show any data.

When you navigate from a Redwood landing page to other Redwood pages that have an organization drop down or filter chip, the context organization is defaulted on the pages. If you directly navigate to the Redwood pages, your default maintenance organization is shown by default, if defined. You can optionally switch to a different maintenance organization as required. For additional details on how to set the site and user level default maintenance organization profile options, see the How can I define the default maintenance organization topic.

Redwood Pages in Maintenance that Require Additional Setup

Redwood Page or Feature	Link to the Topic
Asset Information Page	Manage your installed base assets using either the legacy Manage Assets page or the Redwood page Asset Information Management. See the How You Use Smart Search to Search For and View Assets in the New Assets UI topic to know more.
Maintenance Supervision	Manage your maintenance work orders using either the existing Manage Maintenance Work Orders page or the Redwood page, Maintenance Supervision. To enable Maintenance Supervision for supervisors, go through the Manage Work Using Maintenance Supervision section in this guide. Also, see the Maintenance Supervision chapter in the Using Maintenance guide to know how supervisors can use this workbench.
My Maintenance Work	Report your maintenance work orders using either the existing Dispatch List page or the Redwood page, My Maintenance Work. To enable My Maintenance Work for technicians, go through the Report Work Using My Maintenance Work section in this guide. See the My Maintenance Work chapter of the Using Maintenance guide to know how technicians can use this workbench.
Maintenance Management and Maintenance Execution Landing Pages	To enable the Maintenance Management and Maintenance Execution landing pages, switch on their respective profile options. Additional setup actions and considerations are covered in the details below.
Manage Maintenance Work Definitions	To enable the Manage Maintenance Work Definitions page, switch on the ORA_MNT_WORK_DEFINITIONS_REDWOOD_ENABLED profile option, then follow the details below to enable the index.
Manage Maintenance Forecasts	To enable the Manage Forecasts page using smart search, enable the opt-in for the feature and then follow the details below to enable the index.
Warranty Claims	To enable the Claims page using smart search, enable the opt-in for the feature and then follow the details below to enable the index.
Maintenance Programs	To enable the Maintenance Programs page, including the Work Requirement, Program and Calendar pattern tabs, enable the opt-in for the feature and then follow the details below to enable the index.

Additionally, you may need to configure settings for these pages using the Asset Maintenance Parameters, as covered in the Set Up Maintenance topic.

Manage Oracle Search Indexes

Oracle Search indexes are used to manage data and provide search services across multiple pages and workbenches in maintenance using the Oracle Search Cloud Service (OSCS). During implementation and later through the enablement of new features, follow instructions in this guide, along with the release What’s New documentation, to enable, use, and manage these indexes:

Object	Index name for initial ingestion	Index name for reingest
Installed Base Assets	fa-alm-asset	IB_ASSET_BULK_INGEST
Work Orders	fa-alm-work-order	MNT_WO_BULK_INGEST
Asset Work Orders	fa-alm-work-order-asset	MNT_WO_BULK_INGEST
Work Definition	fa-alm-work-definition	MNT_WD_BULK_INGEST
Maintenance Forecasts	fa-alm-maintenanceforecasts	MNT_FORECAST_BULK_INGEST
Supplier Warranty Claims	fa-alm-warranty-claim	CSE_CLAIM_BULK_INGEST
Work Requirements	fa-alm-work-requirement	MNT_WR_BULK_INGEST
Saved Searches	fa-hcm-savedsearch	Reingest isn't required.

First, you need to enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.
Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
- Job Name: ESS job to create index definition and perform initial ingest to OSCS.
- Index Name to Reingest: fa-alm-work-order

Note: If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

During the implementation of each object’s pages or workbenches, you see instructions to submit the scheduled process to create the index definition and perform initial ingest to OSCS before using the feature. You can also submit the process if the index is already created, and you want to ingest it again. This process clears the index and reingests all the data:

Program name: ESS job to create index definition and perform initial ingest to OSCS.
Index Name: See the table above by object.

After the index is created, most of them need periodic reingestion because not all modes of data creation or update trigger the near real-time ingest of the index. Examples include File-based import of new and updated data. Therefore, update the index by running a separate scheduled process. This scheduled process doesn't clear the index, but only updates the existing index with the changes from these transactions. We recommend that you ingest these updates at least once a day, or as often as your business requires, to keep the index current.

Program Name to Run Bulk Ingest: ESS job to run Bulk ingest to OSCS.
Index Name to Reingest: See the table above by object.

Maintenance Management and Maintenance Execution Landing Pages

With the new Maintenance Management and Maintenance Execution landing pages, maintenance users have a comprehensive view of all maintenance management and execution activities, highlighting work orders that require immediate attention and enabling quick actions to navigate to additional maintenance activities.

Steps to Enable

To enable the Maintenance Management and Maintenance Execution landing pages, switch on their respective profile options. Here's how you do it:

Navigate to the Setup and Maintenance work area and perform a global search of Manage Administrator Profile Values.
On the Manage Administrator Profile Values page, search for and select the profile option code.
1. Maintenance Execution Profile Options:
  - Enable Maintenance Execution Landing Page (ORA_MNT_EXECUTION_LANDING_PAGE_REDWOOD_ENABLED)
  - Set days used to calculate metrics for My Future Assignments and My Qualified Work (ORA_MNT_LANDING_PAGE_FUTURE_WO_METRICS_HORIZON)
Maintenance Management Profile Options:
- Enable Maintenance Management Landing Page (ORA_MNT_MANAGEMENT_LANDING_PAGE_REDWOOD_ENABLED)
- Set days used to calculate metrics for Future Work Orders (ORA_MNT_LANDING_PAGE_FUTURE_WO_METRICS_HORIZON)
In the Profile Values section, set the Site level to Yes or No. The default value of the Enable Maintenance Execution Landing Page profile option is Yes. The default of the Enable Maintenance Management Landing Page profile option is No.
- Yes = Enables the feature
- No = Disables the feature
Click Save and Close. Changes to the profile value affect users the next time they sign in.

If you enable the Maintenance Execution landing page, users can open the page from the new Maintenance Execution icon under the Supply Chain Execution group. To hide the icon and disable the feature, change the profile option to No.

If you enable the Redwood version of Maintenance Management landing page, the existing Maintenance Management landing page is replaced with the new page.

The following actions aren't available on the Redwood Maintenance Management landing page:

Production Calendar
Work Center Resource Calendar
Report Resource Transactions: You can report resource transactions through the My Maintenance Work action. However, if you need to direct access this page, then consider reverting the profile value to No.
Issue and Return Materials from Inventory: You can issue and return materials through the My Maintenance Work action. However, if you need to direction access to this page, then consider reverting the profile value to No.

To access these features, switch back to the existing Maintenance Management landing page by setting the ORA_MNT_MANAGEMENT_LANDING_PAGE_REDWOOD_ENABLED profile option to No.

Manage Maintenance Work Definitions

Create and manage maintenance processes in your organization more efficiently with the maintenance work definition using Redwood. A maintenance work definition includes operations, operation items, and resources required for a maintenance or repair process. The previous user experience focused on visualizing the data relationships within a work definition, displaying a limited view of the dataset, and utilizing mouse-driven navigation and techniques like drag and drop or expand and collapse. By enabling the Redwood page, you find a user experience that provides quick editing and better information density for work definitions with extensive operational data.

Steps to Enable

To enable the Manage Maintenance Work Definitions page, switch on the ORA_MNT_WORK_DEFINITIONS_REDWOOD_ENABLED profile option to see this Redwood page. Here's how you do it:

Navigate to the Setup and Maintenance work area and perform a global search of Manage Administrator Profile Values.
On the Manage Administrator Profile Values page, search for the ORA_MNT_WORK_DEFINITIONS_REDWOOD_ENABLED profile option.
Set the profile option to Yes at the site level.
Save the changes.

After you enable the profile option, you need to enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes
Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
- Job Name: ESS job to create index definition and perform initial ingest to OSCS.
- Index Name to Reingest: fa-alm-work-definition

Note: If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

After enablement and index ingestion, ensure that users have the existing dispatch list privileges:

Manage Maintenance Work Definitions
- MNT_MANAGE_MAINTENANCE_WORK_DEFINITIONS_PRIV
View Maintenance Work Definitions
- MNT_VIEW_MAINTENANCE_WORK_DEFINITIONS_PRIV

Manage Maintenance Forecasts

Manage maintenance forecasts in your organization more efficiently using Oracle's smart search and filters. Maintenance programs define and generate a preventive maintenance forecast for one or more affected assets in a maintenance-enabled organization. The forecast is then used as the basis for creating preventive maintenance work orders, thus reducing the workload for maintenance planners, and allowing them to focus on maintenance program auditing, optimization, and exception-based events. Enable the opt-in for the updated page to get an improved user experience.

Steps to Enable

To enable the Manage Forecasts page, enable the opt-in for the feature.

After you enable the opt in, you need to enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.
Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
- Job Name: ESS job to create index definition and perform initial ingest to OSCS.
- Index Name to Reingest: fa-alm-maintenanceforecasts

Note:

If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

After enablement and index ingestion, ensure that users have these privileges:

Manage Maintenance Forecasts
- MNT_MANAGE_MAINTENANCE_FORECASTS_PRIV
View Maintenance Forecasts
- MNT_VIEW_MAINTENANCE_FORECASTS_PRIV

Warranty Claims

Search for and manage supplier warranty claims in the new Warranty Claims page using Oracle's smart search and filters. This feature uses Oracle Search Extension Framework to provide a powerful index-based search engine combined with Oracle's next user experience so you can quickly and easily perform full-text searches for claims. If not enabled, the existing Warranty Claims page uses a non-smart search user experience. If you have large volumes of claims it's recommended to enable this feature.

Steps to Enable

To enable the Claims page using smart search, enable the opt-in for the feature.

After you enable the opt-in, enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
Ensure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.
Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
- Job Name: ESS job to create index definition and perform initial ingest to OSCS.
- Index Name to Reingest: fa-alm-warranty-claim

Note: If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

After enablement and index ingestion, ensure that users have these privileges:

Manage Supplier Warranty Claims
- MNT_MANAGE_SUPPLIER_WARRANTY_CLAIMS_PRIV
View Supplier Warranty Claims
- MNT_VIEW_SUPPLIER_WARRANTY_CLAIMS_PRIV
Use REST Service: Workers List of Values
- PER_REST_SERVICE_ACCESS_WORKERS_LOV_PRIV

Manage Maintenance Programs

use Oracle's smart search and filters to manage maintenance programs in your organization. Maintenance programs define and generate a preventive maintenance forecast for one or more affected assets in a maintenance-enabled organization. Enable the opt-in, Redwood: Manage Maintenance Programs, for the updated page to get an improved user experience.

Note: It's recommended that you enable the option in a Test environment before enabling it in your Production environment. After you opt in the feature, the work requirement status, Ready to Forecast, is enabled only on Redwood pages. If you switch back to the existing page, you can see the programs in Ready to Forecast status, but you can't change the status to Active. Therefore, it isn't recommended to switch back to the existing pages after you opt in on your Production environment.

Steps to Enable

After you enable the opt in, enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.
Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
- Job Name: ESS job to create index definition and perform initial ingest to OSCS.
- Index Name to Reingest: fa-alm-work-requirement.
  Note: If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

Data Security Policy

With Redwood, you now have a Data Security Policy (DSP) applied to the Maintenance Program object. DSP governs access to data through the maintenance program REST APIs. Users can view and manage data in the Redwood pages using the program REST APIs based on their DSP privileges. DSP is applicable to integrations and custom pages that use the maintenance program REST APIs. Grant a data security policy (DSP) to your users so that they have all the required privileges to view the pages and search results. Data security features include:

Data security policy: Defines the conditions based on which, data access is granted to a role.
Role: Applies data security policies with conditions to users through role provisioning.

By default, users with the Maintenance Manager role has DSP that enforces access to each organization they can manage the maintenance programs for. This is consistent with the existing user experience in the current pages, where a user can only view and manage programs in organizations for which they have access. Any custom users that inherit this role will automatically get the DSP. There is also an additional DSP that can provide access to all maintenance organizations.

Maintenance users with custom roles need DSP to access the maintenance program REST APIs and associated Redwood pages. Without that, they won't get search results on page searches.

Here's how you manually add DSP for users to let them access an assigned maintenance organization:

Login with a user who has security console access.
Navigate to Tools, Security Console. On the vertical tabs, ensure the Roles tab is viewable.
Search for a custom role and edit it.
In the edit mode of a role, go to the Data Security Policy and give these details to add the grant:
- Policy Name: Grant on Maintenance Program
- Description: Grant on Maintenance Program
- Data Resource: Maintenance Program
- Data Set: Select By Instance Set
- Condition Name: Access the maintenance program for table MNT_PROGRAMS_B for all the maintenance organizations in which they can operate.
- Actions: Read; Update; Delete; Manage Maintenance Program

To let your users access all the maintenance organizations, follow these steps:

Login with a user who has security console access.
Navigate to Tools, Security Console. On the vertical tabs, ensure the Roles tab is viewable.
Search for a custom role and edit it.
In the edit mode of a role, go to the Data Security Policy and give these details to add the grant:
- Policy Name: Grant on Maintenance Program by Org Access
- Description: Maintenance Manager can manage Maintenance Programs for the Maintenance Organizations in which they operate
- Data Resource: Maintenance Program
- Data Set: Select By Instance Set
- Condition Name: Access the maintenance program for table MNT_PROGRAMS_B for all the maintenance organizations in which they can operate.
- Actions: Read; Update; Delete; Manage Maintenance Program

Privileges

After enablement and index ingestion, and assigned of DSP to your roles, ensure that users have these privileges:

Manage Maintenance Programs
- MNT_MANAGE_MAINTENANCE_PROGRAMS_PRIV
View Maintenance Programs
- MNT_VIEW_MAINTENANCE_ PROGRAMS_PRIV
Import Maintenance Programs
- MNT_IMPORT_MAINTENANCE_PROGRAMS_PRIV