Cloud Readiness / Oracle Supply Chain Planning Cloud
What's New
  1. Update 19C
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
    1. Demand Management
        1. Use a Calculated Measure Across Multiple Planning Work Areas
        2. Monitor Planning Processes and Improve Planning Data Quality
    2. Sales and Operations Planning
        1. Use a Calculated Measure Across Multiple Planning Work Areas
    3. Planning Central
        1. Use a Calculated Measure Across Multiple Planning Work Areas
      1. Integrate and Extend Planning Central Using REST Services
        1. Update Planning Supplies Using a REST Service
        2. Update Planning Demands Using a REST Service
        3. Extract Planning Pegging Data Using a REST Service
    4. Supply Planning
        1. Use a Calculated Measure Across Multiple Planning Work Areas
      1. Integrate and Extend Supply Planning Using REST Services
        1. Update Planning Supplies Using a REST Service
        2. Update Planning Demands Using a REST Service
        3. Extract Planning Pegging Data Using a REST Service

Update 19C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
21 JUN 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users in a couple of ways:

Access the Opt In page from the New Features Work Area

  1. Click the Navigator, and then click New Features (under the My Enterprise heading)
  2. On the New Features page, select the offering that includes new features you’d like to review
  3. Click Go to Opt In for any feature you want to opt in
  4. On the Edit Features page, select the Enable option for the feature, and then click Done

or...  Access the Opt In page from the Setup and Maintenance Work Area

  1. Click the Navigator, and then click Setup and Maintenance
  2. On the Setup page, select your offering, and then click Change Feature Opt In
  3. On the Opt In page, click the Edit Features icon for any area that includes features you want to opt in
  4. On the Edit Features page, select the Enable option for any feature you want to opt in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close
  5. Click Done.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may auto enable in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially auto enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

Demand Management

Use a Calculated Measure Across Multiple Planning Work Areas

Monitor Planning Processes and Improve Planning Data Quality

Sales and Operations Planning

Use a Calculated Measure Across Multiple Planning Work Areas

Planning Central

Use a Calculated Measure Across Multiple Planning Work Areas

Integrate and Extend Planning Central Using REST Services

Update Planning Supplies Using a REST Service

Update Planning Demands Using a REST Service

Extract Planning Pegging Data Using a REST Service

Supply Planning

Use a Calculated Measure Across Multiple Planning Work Areas

Integrate and Extend Supply Planning Using REST Services

Update Planning Supplies Using a REST Service

Update Planning Demands Using a REST Service

Extract Planning Pegging Data Using a REST Service

Demand Management

Use a Calculated Measure Across Multiple Planning Work Areas

You may need to create measures that are common to multiple planning work areas when the data is of interest to multiple stakeholders across the enterprise. These measures may be calculated measures that are dependent on other measures, and these other measures must be available in the work areas that this new measure is needed in. Prior to this update, the dependent measures had to be available in the Demand Management, Supply Planning, and Sales and Operations work areas. With this update, the dependent measures need to be available only in the work areas that the new measure is needed in. This change gives you a broader list of measures that can be used in the new measure’s formula. For example, when creating a measure for use in demand planning and supply planning, the new measure’s formula can include a dependent measure that is available in both the Demand Management and Supply Planning work areas, but not in the Sales and Operations Planning work area.

Oracle Supply Chain Planning Cloud will generate messages when the dependent measures aren't available in the target work areas. This validation minimizes errors in the definition of measures by requiring corrective actions to ensure that all relevant measures are available in the target work areas.

Let's say you want to create a new measure called Final Forecast enabled in both the Demand Management and Demand and Supply Planning work areas. The formula you want to use for calculating the Final Forecast measure is 60% of the Final Bookings Forecast measure plus 40% of the Final Shipments Forecast measure. Because both the Final Bookings Forecast measure and the Final Shipments Forecast measure are available in both the Demand Management and Demand and Supply Planning work areas, they can be used in the Final Forecast measure's expression. In prior updates, when creating a common measure, the Final Shipments Forecast and Final Bookings Forecast measures weren't available because these measures aren't available in all planning work areas.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • If you created any measures that had the common measures check box selected in a prior update, those measures are enabled in all work areas after upgrade to update 19C.
  • You can deselect work areas that don't apply to a given user-defined measure. Reducing the number of enabled work areas gives you access to a broader number of other measures that you can use in the user-defined measure's expression. For example, a user-defined measure that's enabled in the Supply Planning, Demand Management, and Sales and Operations Planning work areas has fewer measures that can be used in its expression than a measure that's enabled in only the Demand Management and Demand and Supply Planning work areas.
  • After creating a new measure, or editing an existing measure, regardless of whether it's enabled in more than one work area or not, you must complete steps to use that measure in a plan:
    • Add the measure to a measure catalog.
    • Associate the measure catalog to a plan.
    • Run the plan using the Refresh with current data option.

Key Resources

Monitor Planning Processes and Improve Planning Data Quality

When you launch a plan, the demand planning process generates numerous technical processes on the Oracle Supply Chain Planning Cloud server. If an error occurs, or the plan results are abnormal, the source of error is captured in a log file. Analyzing all the log files can be tedious and time consuming, especially when you can fix the root cause by making minor modifications to the data.

Use the Review Planning Messages page to review important information generated by the demand planning process while running a plan. For example, the forecasting process was unable to generate a forecast due to lack of historical demand. In such a scenario, you can review a message on the page to learn about the issue immediately. Use the information on the Review Planning Messages page to significantly reduce the time required to fix errors. You can use the information provided to act without the need to contact the Oracle technical support team.

In addition, you can still open the plan, even though the demand planning process failed. You can work on the historical data or forecast data of another forecasting profile which ran successfully.

Watch a Demo

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • This feature extends the existing Review Plan Messages functionality by introducing new messages to identify issues related to forecasting profiles.
  • The existing Open Plan functionality changed. With this update, you can open a plan when there is a warning due to a forecasting profile issue.
  • All forecasting profile messages are available on the Review Plan Messages page. In addition, to view more detailed information of each issue, you can open the log files available on the Scheduled Processes page.

Key Resources

Sales and Operations Planning

Use a Calculated Measure Across Multiple Planning Work Areas

You may need to create measures that are common to multiple planning work areas when the data is of interest to multiple stakeholders across the enterprise. These measures may be calculated measures that are dependent on other measures, and these other measures must be available in the work areas that this new measure is needed in. Prior to this update, the dependent measures had to be available in the Demand Management, Supply Planning, and Sales and Operations work areas. With this update, the dependent measures need to be available only in the work areas that the new measure is needed in. This change gives you a broader list of measures that can be used in the new measure’s formula. For example, when creating a measure for use in demand planning and supply planning, the new measure’s formula can include a dependent measure that is available in both the Demand Management and Supply Planning work areas, but not in the Sales and Operations Planning work area.

Oracle Supply Chain Planning Cloud will generate messages when the dependent measures aren't available in the target work areas. This validation minimizes errors in the definition of measures by requiring corrective actions to ensure that all relevant measures are available in the target work areas.

Let's say you want to create a new measure called Final Forecast enabled in both the Demand Management and Demand and Supply Planning work areas. The formula you want to use for calculating the Final Forecast measure is 60% of the Final Bookings Forecast measure plus 40% of the Final Shipments Forecast measure. Because both the Final Bookings Forecast measure and the Final Shipments Forecast measure are available in both the Demand Management and Demand and Supply Planning work areas, they can be used in the Final Forecast measure's expression. In prior updates, when creating a common measure, the Final Shipments Forecast and Final Bookings Forecast measures weren't available because these measures aren't available in all planning work areas.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • If you created any measures that had the common measures check box selected in a prior update, those measures are enabled in all work areas after upgrade to update 19C.
  • You can deselect work areas that don't apply to a given user-defined measure. Reducing the number of enabled work areas gives you access to a broader number of other measures that you can use in the user-defined measure's expression. For example, a user-defined measure that's enabled in the Supply Planning, Demand Management, and Sales and Operations Planning work areas has fewer measures that can be used in its expression than a measure that's enabled in only the Demand Management and Demand and Supply Planning work areas.
  • After creating a new measure, or editing an existing measure, regardless of whether it's enabled in more than one work area or not, you must complete steps to use that measure in a plan:
    • Add the measure to a measure catalog.
    • Associate the measure catalog to a plan.
    • Run the plan using the Refresh with current data option.

Key Resources

Planning Central

Use a Calculated Measure Across Multiple Planning Work Areas

You may need to create measures that are common to multiple planning work areas when the data is of interest to multiple stakeholders across the enterprise. These measures may be calculated measures that are dependent on other measures, and these other measures must be available in the work areas that this new measure is needed in. Prior to this update, the dependent measures had to be available in the Demand Management, Supply Planning, and Sales and Operations work areas. With this update, the dependent measures need to be available only in the work areas that the new measure is needed in. This change gives you a broader list of measures that can be used in the new measure’s formula. For example, when creating a measure for use in demand planning and supply planning, the new measure’s formula can include a dependent measure that is available in both the Demand Management and Supply Planning work areas, but not in the Sales and Operations Planning work area.

Oracle Supply Chain Planning Cloud will generate messages when the dependent measures aren't available in the target work areas. This validation minimizes errors in the definition of measures by requiring corrective actions to ensure that all relevant measures are available in the target work areas.

Let's say you want to create a new measure called Final Forecast enabled in both the Demand Management and Demand and Supply Planning work areas. The formula you want to use for calculating the Final Forecast measure is 60% of the Final Bookings Forecast measure plus 40% of the Final Shipments Forecast measure. Because both the Final Bookings Forecast measure and the Final Shipments Forecast measure are available in both the Demand Management and Demand and Supply Planning work areas, they can be used in the Final Forecast measure's expression. In prior updates, when creating a common measure, the Final Shipments Forecast and Final Bookings Forecast measures weren't available because these measures aren't available in all planning work areas.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • If you created any measures that had the common measures check box selected in a prior update, those measures are enabled in all work areas after upgrade to update 19C.
  • You can deselect work areas that don't apply to a given user-defined measure. Reducing the number of enabled work areas gives you access to a broader number of other measures that you can use in the user-defined measure's expression. For example, a user-defined measure that's enabled in the Supply Planning, Demand Management, and Sales and Operations Planning work areas has fewer measures that can be used in its expression than a measure that's enabled in only the Demand Management and Demand and Supply Planning work areas.
  • After creating a new measure, or editing an existing measure, regardless of whether it's enabled in more than one work area or not, you must complete steps to use that measure in a plan:
    • Add the measure to a measure catalog.
    • Associate the measure catalog to a plan.
    • Run the plan using the Refresh with current data option.

Key Resources

Integrate and Extend Planning Central Using REST Services

Update Planning Supplies Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies, such as file-based data import (FBDI) or REST API, to enable integrations with other applications. You can now update data for all planned supplies, transfer orders, purchase orders, and work orders, and optionally create planned orders specific to a supply plan or an integrated demand and supply plan using the Planning Supplies REST API. This REST service is a child resource of the Supply Plans and Demand and Supply Plans parent resources. For example, you can use this REST API to create firm planned supply orders from another system in your enterprise in a named plan. This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise.

Steps to Enable

Review the REST service definition in the REST API guides (available from the Oracle Help Center > your apps service area of interest > REST API) to leverage this capability.  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or a demand and supply plan you can use the POST method on the Planning Supplies resource to update on hand or supply orders like planned order or other supplies in the plan to simulate changes. This service respects data security and allows updates of only the attributes that can be edited.

Key Resources

  • Watch Update Planning Supplies Using a REST Service Readiness Training
  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation available at Oracle Help Center Cloud Documentation (Select Supply Chain Planning, and then the link for Supply Chain Management under the REST API heading).

Update Planning Demands Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies, such as file-based data import (FBDI) or REST API, to enable integrations with other applications. You can now update data for demand data, such as sales orders, and optionally create manual demands specific to a supply plan or an integrated demand and supply plan using the Planning Demands REST API. This REST API is a child resource of the Supply Plans and Demand and Supply Plans parent resources. For example, you can use this REST API to create manual demands from another system in your enterprise in a named plan. This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise.

Steps to Enable

Review the REST service definition in the REST API guides (available from the Oracle Help Center > your apps service area of interest > REST API) to leverage this capability.  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or any demand and supply plan you can use the POST method on the Planning Demands resource to update any demand data, such as forecast or a manual demand, in the plan to simulate changes. This service respects data security and allows updates of only the attributes that can be edited.

Key Resources

  • Watch Update Planning Demands Using a REST Service Readiness Training.
  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation available at Oracle Help Center Cloud Documentation (Select Supply Chain Planning, and then the link for Supply Chain Management under the REST API heading).

Extract Planning Pegging Data Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies such as file-based data import (FBDI) or REST API to enable integrations with other applications. In this update, you can retrieve supplies and demands, upstream or downstream, for a specified supply or demand order in a named plan. For example, you can use REST APIs to integrate the planned demand orders with a reporting system.

  • To GET the upstream supply information of a given Planning Demand use the resources
    • End Pegged Supplies
    • Pegged Supplies
  • To GET the downstream demand information of a given Planning Supply use the resource
    • Pegged Demands
  • To GET the upstream supply information of a given Planning Supply use the resource
    • Upstream Supplies

These resources are child resources to the Planning Demands and Planning Supplies resources, which are part of the Demand and Supply Plans and Supply Plans root resources.

This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise.

Steps to Enable

Review the REST service definition in the REST API guides (available from the Oracle Help Center > your apps service area of interest > REST API) to leverage this capability.  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or a demand and supply plan you can use the applicable GET method to get all upstream and downstream supply chain data in the plan. However, to limit the amount of data, it is recommended to use appropriate query parameters in the GET request.

Key Resources

  • Watch Extract Planning Pegging Data Using a REST Service Readiness Training
  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation available on the Oracle Help Center (Select Supply Chain Planning, and then the REST API link for Supply Chain Management.)

Supply Planning

Use a Calculated Measure Across Multiple Planning Work Areas

You may need to create measures that are common to multiple planning work areas when the data is of interest to multiple stakeholders across the enterprise. These measures may be calculated measures that are dependent on other measures, and these other measures must be available in the work areas that this new measure is needed in. Prior to this update, the dependent measures had to be available in the Demand Management, Supply Planning, and Sales and Operations work areas. With this update, the dependent measures need to be available only in the work areas that the new measure is needed in. This change gives you a broader list of measures that can be used in the new measure’s formula. For example, when creating a measure for use in demand planning and supply planning, the new measure’s formula can include a dependent measure that is available in both the Demand Management and Supply Planning work areas, but not in the Sales and Operations Planning work area.

Oracle Supply Chain Planning Cloud will generate messages when the dependent measures aren't available in the target work areas. This validation minimizes errors in the definition of measures by requiring corrective actions to ensure that all relevant measures are available in the target work areas.

Let's say you want to create a new measure called Final Forecast enabled in both the Demand Management and Demand and Supply Planning work areas. The formula you want to use for calculating the Final Forecast measure is 60% of the Final Bookings Forecast measure plus 40% of the Final Shipments Forecast measure. Because both the Final Bookings Forecast measure and the Final Shipments Forecast measure are available in both the Demand Management and Demand and Supply Planning work areas, they can be used in the Final Forecast measure's expression. In prior updates, when creating a common measure, the Final Shipments Forecast and Final Bookings Forecast measures weren't available because these measures aren't available in all planning work areas.

Watch a Demo

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • If you created any measures that had the common measures check box selected in a prior update, those measures are enabled in all work areas after upgrade to update 19C.
  • You can deselect work areas that don't apply to a given user-defined measure. Reducing the number of enabled work areas gives you access to a broader number of other measures that you can use in the user-defined measure's expression. For example, a user-defined measure that's enabled in the Supply Planning, Demand Management, and Sales and Operations Planning work areas has fewer measures that can be used in its expression than a measure that's enabled in only the Demand Management and Demand and Supply Planning work areas.
  • After creating a new measure, or editing an existing measure, regardless of whether it's enabled in more than one work area or not, you must complete steps to use that measure in a plan:
    • Add the measure to a measure catalog.
    • Associate the measure catalog to a plan.
    • Run the plan using the Refresh with current data option.

Key Resources

Integrate and Extend Supply Planning Using REST Services

Update Planning Supplies Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies, such as file-based data import (FBDI) or REST API, to enable integrations with other applications. You can now update data for all planned supplies, transfer orders, purchase orders, and work orders, and optionally create planned orders specific to a supply plan or an integrated demand and supply plan using the Planning Supplies REST API. This REST service is a child resource of the Supply Plans and Demand and Supply Plans parent resources. For example, you can use this REST API to create firm planned supply orders from another system in your enterprise in a named plan. This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise. 

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or a demand and supply plan you can use the POST method on the Planning Supplies resource to update on hand or supply orders like planned order or other supplies in the plan to simulate changes. This service respects data security and allows updates of only the attributes that can be edited.

Key Resources

Update Planning Demands Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies, such as file-based data import (FBDI) or REST API, to enable integrations with other applications. You can now update data for demand data, such as sales orders, and optionally create manual demands specific to a supply plan or an integrated demand and supply plan using the Planning Demands REST API. This REST API is a child resource of the Supply Plans and Demand and Supply Plans parent resources. For example, you can use this REST API to create manual demands from another system in your enterprise in a named plan. This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise. 

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or any demand and supply plan you can use the POST method on the Planning Demands resource to update any demand data, such as forecast or a manual demand, in the plan to simulate changes. This service respects data security and allows updates of only the attributes that can be edited.

Key Resources

Extract Planning Pegging Data Using a REST Service

You may need Oracle Supply Chain Planning Cloud applications to coexist with other enterprise applications that you have. You can use technologies such as file-based data import (FBDI) or REST API to enable integrations with other applications. In this update, you can retrieve supplies and demands, upstream or downstream, for a specified supply or demand order in a named plan. For example, you can use REST APIs to integrate the planned demand orders with a reporting system.

  • To GET the upstream supply information of a given Planning Demand use the resources 
    • End Pegged Supplies
    • Pegged Supplies
  • To GET the downstream demand information of a given Planning Supply use the resource
    • Pegged Demands
  • To GET the upstream supply information of a given Planning Supply use the resource
    • Upstream Supplies

These resources are child resources to the Planning Demands and Planning Supplies resources, which are part of the Demand and Supply Plans and Supply Plans root resources.

This new capability enables standards-based interoperability of Oracle Supply Chain Planning Cloud with other applications that you may have in your enterprise.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

For any supply plan or a demand and supply plan you can use the applicable GET method to get all upstream and downstream supply chain data in the plan. However, to limit the amount of data, it is recommended to use appropriate query parameters in the GET request.

Key Resources

  • Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation available on the Oracle Help Center (Select Supply Chain Planning, and then the REST API link for Supply Chain Management.)