Feature Summary

Features Delivered Disabled: Customer Action Required for Use

This table provides a summary of the features that require customer action before they can be used by end users. These features are delivered in a disabled state, and you can choose if and when to enable them.

Examples of such features include:

  • New or expanded BI subject areas that need to be incorporated into reports
  • Integration required to utilize new web services
  • Features that must be assigned to user roles before they can be accessed

These features are non-disruptive since they remain inactive until you take action. You can selectively enable them, allowing you to set your own testing and rollout schedule.

Supply Chain Orchestration

Feature Action Required
Manage Configure to Order Changes Without Canceling Supply Setup Required
Group Transfer Orders Using Source and Destination Organizations Opt In plus Setup

SCM Common Components

Feature Action Required
Create Guided Journeys for Redwood Pages in the Setup and Maintenance Work Area Visual Builder

Supply Planning

Feature Action Required
Redwood: Manage Demand Priority Rules Using a New User Experience Setup Required

Constraint-Based Planning

Feature Action Required
Consider the Assigned Units of a Resource when Computing Dates of Make Orders Opt In plus Setup
Respect Shipping Calendar When Rescheduling Transfer Orders Opt In

Backlog Management

Feature Action Required
Redwood: Manage Demand Priority Rules Using a New User Experience Opt In plus Setup
Collect and Plan In-Transit Shipments Without Reference to Transfer Orders or Purchase Orders Opt In
Select the Fastest Ship Method to Avoid Delay Opt In

Production Scheduling

Feature Action Required
Enhanced Highlighting in Gantt Chart Opt In
Maximize Schedule Views Opt In
Edit Shift Exceptions for Scenarios Opt In
Improved Manual Scheduling by Firming Operations Opt In

Features Delivered Enabled: Ready for Use by End Users

This table provides a summary of the features included in the document that are ready to be used by end users.

The impact of these features can be categorized as follows:

  • Larger Scale UI or Process-Based: These features have a higher potential impact on users due to their complex designs. Focus your acceptance testing on these features.
  • Small Scale UI or Process-Based: These features have minimal impact on users and typically involve minor changes to fields, validations, or programs.
  • Report: These features have minimal impact on users and include new or modified, Oracle-delivered, ready-to-run reports.

Supply Planning

Feature Impact
Refresh a Plan's Master Data Incrementally Small scale
Queue Overlapping Scheduled Runs of Same Plan Small scale
Release Planned Transfer Orders Grouped by Source and Destination Pairs Small scale
Plan Multiple Outputs in Discrete Work Definitions Small scale
Collect and Plan In-Transit Shipments Without Reference to Transfer Orders or Purchase Orders Small scale