How many features has Oracle shipped for Planning Data & Collections?

9 features across releases 24B to 26B, counted from Oracle’s own release readiness books for Fusion SCM.

When did Redwood reach Planning Data & Collections in Oracle Fusion?

The first Redwood feature for Planning Data & Collections appears in release 25C. 8 of the 9 features on this screen are Redwood.

Home / Releases / Feature Timeline / Planning Data & Collections

🗄️ Planning · every release, 24A to 26D

Oracle Fusion Planning Data & Collections: every change Oracle shipped

The data planning runs on, and the collection jobs that keep it current. Nobody looks at this screen until a plan comes out wrong. Below is every feature Oracle published for this screen from 24B to 26B, newest release first. Each one shows the enablement Oracle recorded and links straight to Oracle’s own page for it.

9 features5 releases with changes8 RedwoodRedwood since 25C

← All 30 screens

26B4 features

REDWOODRedwood: Collect Planning Data Using a New User Experience

Demand ManagementAuto

REDWOODRedwood: Load Planning Data from Flat Files Using a New User Experience

Demand ManagementAuto

REDWOODRedwood: Manage Planning Data Security Using a New User Experience

Demand ManagementAuto

REDWOODRedwood: Manage Planning Source Systems Using a New User Experience

Demand ManagementAuto

26A1 feature

REDWOODRedwood: Extract Application Data from a Read-Optimized Data Store Using a Redwood Page

SCM Common ComponentsOpt In plus Setup

25D1 feature

REDWOODRedwood: Search for Planning Data More Efficiently Using Advanced Capabilities

Demand ManagementAuto

25C2 features

REDWOODRedwood: Analyze Planning Data Quality Issues

Demand ManagementAuto

REDWOODRedwood: Search for Planning Data More Efficiently with a Streamlined Experience

Demand ManagementAuto

24B1 feature

Increase Performance of the Aggregate Collected Planning Data Scheduled Process When Run in Net Change Mode

See doc

What the badges mean

Auto means the feature is on the day you take the update. Nobody has to do anything.
Opt In means somebody has to switch it on first. Opt-ins expire in a later release, so they do not stay optional forever.
Setup Required means it is there but does nothing until it is configured.
REDWOOD marks a feature Oracle shipped as part of the new Redwood interface for this screen.
Journey appears when the same feature came back in more than one release, usually because the enablement changed.

Feature titles, enablement and links come straight from Oracle’s release readiness documents on docs.oracle.com, releases 24A to 26D. The grouping into screens is ours, and a feature can belong to more than one screen. Oracle has not published the Order Management book for 26D yet. Next: every 26D change in plain English, or browse all 30 screens.

Oracle Fusion Planning Data & Collections: every change Oracle shipped

What the badges mean

Other Planning screens

Demand Management

Supply Planning