You can integrate Rapid Planning with other Oracle products:
Oracle Advanced Supply Chain Planning
Oracle Demand Planning
Oracle Demantra Demand Management
Oracle Demantra Sales & Operations Planning
Oracle Advanced Planning Command Center
Oracle Inventory Optimization
Oracle Global Order Promising
Rapid Planning integrates with other E-Business Suite Value Chain Planning applications.
It does not integrate with:
Oracle Process Manufacturing
Oracle Project Manufacturing: Project, task, Seibel
Oracle Shop Floor Management
You use Oracle Advanced Supply Chain Planning and Oracle Rapid Planning together to respond to unanticipated events between Advanced Supply Chain Planning runs.
See Simulating Plans from Oracle Advanced Supply Chain Planning.
Use this product to develop consensus forecasts. You can use consensus forecasts to drive the supply plans.
However, you cannot do so if the plan is a baseline Oracle Advanced Supply Chain Planning plan. Use the consensus forecast to drive the Oracle Advanced Supply Chain Planning plan instead.
See also Oracle Demand Planning Implementation and User's Guide.
Use this product to develop consensus forecasts. You can use consensus forecasts to drive the supply plans.
However, you cannot do so if the plan is a baseline Oracle Advanced Supply Chain Planning plan. Use the consensus forecast to drive the Oracle Advanced Supply Chain Planning plan instead.
Global forecasts: You develop forecasts by item in Demantra Demand Management, use them as input to Rapid Planning, and Rapid Planning distributes them to ship-from organizations.
Local forecasts: You develop forecasts by item-organization and use them as input to Rapid Planning.
Forecast spreading: Your forecasts in Demantra Demand Management are in week, month, or quarter buckets. You can pass these forecasts to Rapid Planning and:
Net with the same buckets
Have Rapid Planning spread the bucketed forecasts over daily buckets before it nets
See profile option MSC: Forecast Spreading Calendar.
Forecast consumption: Sales orders reduce forecasts. The planning solver consumes forecasts by:
Item-customer
Item-customer-customer site
Item-zone: Global forecasts only
Item-zone-customer Global forecasts only
Demand class
Item-organization
Use the sales order line date that matches the meaning of your forecast dates:
Schedule Ship Date
Schedule Arrival Date
Request Ship Date
Request Arrival Date
Promise Ship Date
Promise Arrival Date
For consumption by demand class:
If a sales order has a demand class, the solver consumes a forecast that has the same demand class.
If a forecast does not have a demand class, the solver uses its organization demand class.
If a sales order does not have a demand class, the process uses its organization's warehouse demand class.
If you consume by demand class and have forecasts without demand classes, set profile option MSC: Rapid Planning Consume Forecast with No Demand Class.
Forecast explosion: Explode CTO model forecasts to option classes, options, and mandatory components. Either explode them in Demantra Demand Management or Rapid Planning.
Forecast consumption by bucket
Backward and forward consumption days: Use these if:
You do not always have an exact match between the sales order line schedule dates and forecast entry dates.
Your forecast entry quantity is not always sufficient to cover the sales order quantities.
Navigate to the Plan Options view, Organizations tab.
In the Global Demand Schedules region:
Select global forecasts
Select consumption methods
In the Organizations region, select organizations.
In the Demand Schedule region:
Select local forecasts
Select consumption methods
Navigate to the Plan Options view, Main tab.
Select a forecast spreading method.
If you consume by demand class and have forecasts without demand classes, set profile option MSC: Rapid Planning Consume Forecast with No Demand Class.
See also Oracle Demantra Demand Management User Guide and Oracle Demantra Implementation Guide.
Use this product to manage the forecast development and approval process.
Once you have agreed on consensus forecasts, you can upload them to Rapid Planning for additional simulation and planning.
You can use Rapid Planning plans including those that are simulations from baseline Oracle Advanced Supply Chain Planning plans, as Sales and Operations Planning supply scenarios.
Rapid Planning passes this information:
Planned Production
Constrained (Shipment) Forecast
Planned Shipments
Dependent Demand
On-Hand: Usable available on-hand only
Safety Stock
Available Standard (Resource) Capacity
Required (Resource) Capacity
Available Standard Supplier Capacity
Required Supplier Capacity
Repeat this cycle until you have an operational plan.
See Demantra Sales and Operations Planning to Rapid Planning Integration in Oracle Demantra Integration Guide.
Navigate to the Plan Options view, Main tab.
Select Use for Sales and Operations Planning.
See also Oracle Demantra Sales and Operations Planning User Guide.
Use this product to view Oracle Rapid Planning information for supply chain analysis. This includes plans that are simulations from baseline Advanced Supply Chain Planning plans.
You can use it:
As a business intelligence component
As a way to narrow down supply chain problems and drill down for analysis
To develop custom reports and dashboards
This is the sort of information that you can see:
Supply Chain Analyst Dashboard Pages
Supply Demand Plan Drilldowns
Resource Plan Drilldowns
Exceptions Reports Drilldowns
Measures
When you save a plan, set Publish analytics to APCC. See Basic Plan Actions, Save Plan.
See also Oracle Advanced Planning Command Center User's Guide.
Use this product to determine when and where to hold your inventories across the supply chain to achieve the desired customer service levels
You can pass its target safety stock recommendations to Rapid Planning as demand.
Make the start dates and end dates of the Inventory Optimization forecast buckets the same as the start dates and end dates of the Rapid Planning planning buckets.
Navigate to the Plan Options view, Organizations tab.
In the Demand Schedule region, select an Inventory Optimization plan.
See also Oracle Inventory Optimization User's Guide.
Use this product to review projected supplies and suggest promise dates for sales orders.
Use Global Order Promising with a Rapid Planning plan as reference instead of an Advanced Supply Chain Planning plan as reference if you execute from your Rapid Planning plan.
Navigate to the Plan Options view, Main tab.
Select ATP Enabled.
See also Oracle Global Order Promising Implementation and User's Guide.
Use this product to communicate, plan, and optimize supply and demand information with trading partners. See Oracle Collaborative Planning Implementation and User's Guide.
Oracle Collaborative Planning (CP) integrates with Oracle Rapid Planning. On the supplier collaboration side, you can publish order forecast and safety stock targets to suppliers from a Rapid Planning plan and receive supplier supply commits from suppliers. On the customer side, you can publish supply commit information from the RP plan to CP. The integration of these two products allows you to forecast collaboration workflow between and enterprise and its trading partners.
The integration between CP with RP is very similar to the integration of CP with ASCP. The functional workflows are identical.
See the Oracle Advanced Supply Chain Planning Implementation and User's Guide.
Integration makes the following assumptions:
Oracle Rapid Planning and Oracle Collaborative Planning are deployed on the same instance.
Rapid Planning plan has been saved.
Rapid Planning is able to read Supply Commits that are collected from CP to ODS using the Receive Supplier Capacity programs.
The collaboration between RP and CP supports supplier collaboration workflow and enables:
Rapid Planning to publish Order Forecast to Collaboration Planning (Supplier Collaboration).
Rapid Planning to publish Supply Commit to Collaboration Planning (Customer Collaboration).
The first step in a supplier collaboration workflow is to determine the requirements of the enterprise from its suppliers. Typically, you do this by planning for the enterprise demand in a supply plan that is internal capacity constrained, but is supplier capacity unconstrained. When this plan has completed, the requirements on suppliers are published from a supply plan to suppliers through a Collaboration platform.
As part of the publish process, planned buy requirements, which are established by the supply plan, are translated to Order Forecasts and then published to suppliers. Suppliers then evaluate these requirements to determine which ones can be satisfied using internal planning tools. Those that can be satisfied are uploaded into Collaborative Planning by the suppliers, reviewed by the user and modified, if necessary, using Collaborative Planning.
At regular intervals, the enterprise considers the supplier feedback in its next constrained planning run. The commit from suppliers that is uploaded into CP overrides supplier capacity that may have been established through approved supplier lists (ASL). The enterprise locks the resulting plan into for the current cycle. This process is repeated for every planning cycle.
Oracle Rapid Planning supports the customer collaboration workflow and allows Rapid Planning to publish Supply Commit to customers, based on how supply is pegged to forecast or sales order demand. For information on the concurrent programs, refer to the Oracle Collaborative Planning Implementation and User's Guide.
In this collaboration, the order forecast is published from a customer to the enterprise. The order forecast signifies a forecast of the quantity that the customer will order from the enterprise. In the collaboration cycle, an initial order forecast is first received by the enterprise in the collaboration plan. If necessary, the enterprise iterates with the customer to refine the order forecast. The order forecast is read in and planned for in supply planning.
After the order forecast is planned for in the supply planning engine, the enterprise must publish the quantity of forecast that it can satisfy to its customers – this is achieved through the Publish Supply Commit process. Supply pegged to customer forecast as published from the supply plan to CP as “Supply Commit” against the customer.
Data within Rapid Planning exists in memory, and is available in the database (PDS) only when plans are saved through the Save Plan action in the Rapid Planning workbench. When data is published from Rapid Planning to CP, that is Publish Order Forecast to Suppliers, Supply Commit to Customers, the saved data from the Rapid Planning plan is referenced.
It is possible that you may be running simulations in Rapid Planning, and at a particular point of time may want to publish the results to Collaboration Planning. If you launch Publish/Receive Programs without saving the plan data, there will be a message in the log file associated with the concurrent request, which will indicate that you need to save the Plan.
Invoking Concurrent Requests from Advanced Planning Administrator
You can integrate with CP from within the Rapid Planning Workbench or as an Advanced Planning Administrator.
Once any of the programs or functions are selected, the Plan Name field selector must include all Rapid Planning plans and the existing ASCP plans. In addition, Rapid Planning plans must appear as selectable plans in the list of plans, along with other plans.