Oracle Fusion Supply Chain Planning

Oracle Fusion Supply Chain Planning (FSCP) is a self-service advanced capability in Oracle Fusion Data Intelligence that enables you to extract data from a Oracle Fusion Cloud Supply Chain Planning instance. You can use this data to create data augmentations for various Enterprise Resource Planning and Supply Chain Management use cases.

Load Planning Data from Fusion Supply Chain Planning into Oracle Fusion Data Intelligence Prebuilt Analytics Model (Preview)

As a service administrator or functional administrator, you can use Oracle Fusion Data Intelligence to acquire data from an Oracle Fusion Cloud Supply Chain Planning instance into a prebuilt analytics model.

To use this feature, be sure Supply Chain Planning Analytics is enabled in Preview Features. See Make Preview Features Available.
  1. Create a sample data augmentation to validate the Oracle Fusion Cloud Supply Chain Planning connection is working properly. See Load Data from Fusion Supply Chain Planning into Fusion Data Intelligence (Preview)
    1. In Oracle Fusion Data Intelligence Console, click Data Configuration under Application Administration, and on the Data Configuration page, under Configurations, click Data Augmentation.
    2. Create a sample augmentation for testing the Oracle Fusion Cloud Supply Chain Planning data connection.
    3. Select any one of the facts in the Data Augmentation page and complete the wizard.
    4. In step 6 of the wizard, provide the details and click Finish to save and schedule your data augmentation pipeline job to ensure the job completes successfully.
  2. Activate the dependent Manufacturing, Order Management, and Purchasing functional areas. See Activate a Data Pipeline for a Functional Area
  3. Create the Planning Analytics application.

    In Oracle Fusion Data Intelligence, creating subject areas is dynamic since you have the ability to create subject areas based on the selected plans.

    1. Navigate to the Custom Data configurations and create the planning application by selecting one or more plans.
    2. You can generate the extension metadata (RPD Extension). By default option is disabled.
    3. Depending on the number of plans selected, the dynamic subject areas with different granularities are created.
  4. Publish the Planning Analytics application.
    1. Generate and publish the custom application.
    2. After the custom application is deployed, you can see the subject areas.

Support for Supply Chain Planning Analytics

Oracle Supply Chain Planning Analytics provides data models to support reporting and analytics for the selected plans in the custom data application for Planning Analytics.

After you've published the custom data application , the following warehouse tables are created in Oracle Fusion SCM Analytics.

  • Planning facts: DW_X_SCPA_APP_F_<PLAN_ID>_<Granularity>_F
  • Planning dimensions: DW_X_SCPA_APP_<DIM_CODE>_D
  • Plan as a Dimension: DW_X_SCPA_APP_PLAN_DETAILS
  • Interface / Metadata tables

Planning Facts: DW_X_SCPA_APP_F_<PLAN_ID>_<Granularity>_F

  • There's one fact table that's created in Oracle Fusion SCM Analytics for each granularity of the selected plan. This fact has all the associated dimension identifiers and metrics corresponding to the given granularity (the same as all the exposed columns in the Oracle Fusion Cloud Supply Planning extracts).
  • The grain of this fact is at the dimensions associated to the given granularity.
  • The available Oracle Fusion SCM Analytics dimension keys are denormalized and provided in this fact.

List of common Oracle Fusion SCM Analytics dimensions that are supported:

Planning Dimensions: DW_X_SCPA_APP_<DIM_CODE>_D

  • The dimension tables are provided for each of the dimensions associated with all the granularities of the user selected plans.
  • There are two types of dimensions: those which have a hierarchy, and those dimensions which don't have any hierarchies.
  • Hierarchy Dimension
    • The dimension data is created in Oracle Fusion SCM Analytics only with configured hierarchy levels with functional level names.
    • The dimension data for all hierarchies is pivoted to a single row.
  • Non-Hierarchy Dimension
    • All the columns available in the planning dimension extract are created in Autonomous Data Warehouse (Example: Exception Type, Order Type)

Plan as a Dimension: DW_X_SCPA_APP_PLAN_DETAILS

This dimension provides the details of the selected plans like Plan name, Plan type, and Plan description.

Table 10-1 Interface / Metadata tables

Type Table Name Description
Data model details table DW_X_SCPA_APP_FACT_TABLE_MEASURES_DESCRIPTION This table provides the description of the measures and metrics used in Supply Chain Planning Analytics.
Data model details table DW_X_SCPA_APP_PLAN_TABLES This table provides the list of facts and dimensions generated for each of the user-selected plans.

This table helps you understand the list of data models available for the application and the data models used for semantic model extension.

Granularity measure details DW_X_SCPA_APP_GRANULARITY_DETAILS This table provides the list of granularity with the granularity details.

This metadata provides the Presentation table name for the fact.

Granularity measure details DW_X_SCPA_APP_GRANULARITY_PLAN_MEASURES This table provides the list of measures and metrics available at each granularity of the selected plan.

This metadata helps to build a single logical fact for each granularity across multiple plans by combining the facts of same granularity of different plans.

Hierarchy metadata table DW_X_SCPA_APP_DIM_HIERARCHY_LEVEL_DETAILS This table provides the hierarchy level details for each of the hierarchies associated with the dimensions.

This helps you build the logical hierarchy in the semantic model. In this table ‘Level 1’ is the base level.

Frequently Asked Questions

Review these questions to understand the application:

Why does Supply Chain Planning Analytics have many dynamically created subject areas?

The subject areas for Supply Chain Planning Analytics dynamic are created for each of the granularities in the Planning output of the Supply Chain Plan. For example, granularity 135 is created for Item, Org, Customer, Demand Class, and Time. See Dimensionality Group Codes Used by the Plan Extract Process.

What types of dimensions are supported by Supply Chain Planning Analytics?

Supply Chain Planning Analytics supports both standard Oracle Fusion Data Intelligence dimensions as well as planning dimensions extracted from Oracle Fusion Cloud Supply Chain Planning to Oracle Fusion Data Intelligence. For the planning dimensions, the dimension that's part of the extract dimension catalog (configured in the plan options) is extracted to and supported by Oracle Fusion Cloud Supply Chain Planning.

What types of measures/metrics are supported by Supply Chain Planning Analytics?

Supply Chain Planning Analytics supports both standard seeded measures and custom measures created by users.

In Supply Chain Planning Analytics, is there a limit to the number of measures/metrics extracted to Oracle Fusion Data Intelligence?

Yes. The number of measures is limited by granularity. For example, in granularity 135 you can have up to 250 measures; granularity 125 is limited to 150 measures; granularity 110 is limited to 100 measures, and rest of the granularities can have up to 50 measures.

For additional metrics, you can create calculated metrics in Oracle Analytics Cloud while creating dashboards, or use semantic model extensions if needed.

Does Supply Chain Planning Analytics support private plans, and is it possible to analyze such plans in Oracle Fusion Data Intelligence?

Currently Supply Chain Planning Analytics doesn't support private plans. You should configure your plans as Public plans before extracting the plan data into Oracle Fusion Data Intelligence.

What causes discrepancies between Oracle Fusion Data Intelligence Planning data and Fusion Applications Planning data?

The Planning extracts are generated from Fusion Supply Chain Planning outputs and are regenerated with each Supply Chain Plan run. If the plan is re-run and the updated data aren't loaded into Oracle Fusion Data Intelligence, discrepancies may occur. To resolve this, perform a full reload of the Planning Analytics data in Oracle Fusion Data Intelligence.