Implementation: Architecture

Step 1: Architecture

You can use a centralized or decentralized deployment. You need to understand the architecture and technical options.

Technical

The first release of Rapid Planning was a patch on top of release 12.1.1. The first official eBusiness Suite release containing Rapid Planning is 12.1.3.

Oracle Rapid Planning works with:

To find out the source and destination releases that work together, see Oracle Rapid Planning Release Notes. Navigate to Oracle E-Business Suite Documentation Web Library, Release 12.1 or Release 12.2. Click tab VCP and navigate to region Value Chain Planning Release Notes.

If the release notes say that certain versions of source and destination systems work together, it means that:

This graphic shows the Rapid Planning engine.

the picture is described in the document text

Oracle WebLogic Server

You deploy Rapid Planning in two domains of the WebLogic Server:

Rapid Planning stores completed plans as binary files in the WebLogic Server. When you close a plan, the binary files remain. When you re-open a plan, Rapid Planning loads the data into the user interface.

You request Rapid Planning to save completed plans to the database. Use the Save Plan action.

When you save the plan, Rapid Planning selectively flushes records into the database. For example, it flushes the records from the Supply/Demand view that display in the view to table msc_supplies. The Cache Manager of the Rapid Planning solver eliminates duplicates in the database.

Database Design

Rapid Planning uses the same base tables as Advanced Supply Chain Planning.

It does not use all of the tables that Advanced Planning uses.

There are Rapid Planning-specific columns in some tables, for example, those that Clear to build and Demand Pull-in use.

Functional

Simulation Data Flow

While you perform Rapid Planning simulations, the plan data is in memory and not available in the base tables.

Updates that you make in the Rapid Planning UI, for example, demand priorities and demand due dates, go into memory as well.

Once you save a plan:

Regenerative Planning

The data flow of regenerative plans or plans run with snapshot is similar to Advanced Supply Chain Planning.

The Plan ID is the reference for which data belongs to which plan. Records have Plan ID after you save the plan.

Architecture and Deployment Configurations

See Oracle Value Chain Planning Collections Implementation Guide, Architecture.

To find patches, installation instructions, and an upgrade matrix, see MyOracleSupport note 746824.1: 12.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling).

Profile Options

This table shows the Oracle Rapid Planning profile options.

Profile Name Default Value Values Description
MSC: Rapid Planning Consume Forecast with No Demand Class Null Within Each Bucket, After Consuming Demand Class Specific Forecast, Null This profile option specifies the order that the forecast consumption process should use to consume forecast entries when some of them have a demand class and some of them do not have a demand class. Valid values are:- Within Each Bucket: Consume forecast entries for the day on the sales order; it consumes entries with matching demand class first, then entries with no demand class. Then, it consumes forecast entries within the backward and forward consumption days; for each day, it uses matching demand class first, then no demand class- After Consuming Demand Class Specific Forecast: The forecast consumption process starts by consuming forecast entries for the day on the sales order with matching demand class only. Then, it consumes forecast entries within the backward and forward consumption days with matching demand class only. If there is a remaining sales order quantity, it repeats the process against forecast entries with no demand class, first on the day on the sales order, then within the backward and forward consumption days.
MSC: Rapid Planning Group Planned Orders None None, Demand Level, Item Level Determines if the planning solver groups planned orders of the same type.
It:

  • Groups buy from and transfer from planned orders if the planned orders have the same start and end dates.

  • Does not group make at planned orders.

  • Respects order modifiers.


Valid values are:

  • None: Planned orders are not combined

  • Demand Level: Combine planned orders for a single item demand

  • Item Level: Combine all planned orders for an item
MSC: Sourcing Variance Tolerance 0.05 Positive number <= 1 Use this profile option to specify the tolerance that you allow between sourcing percentages and the actual percentages in a split sourcing window. If the difference is outside the tolerance, the planning solver issues exception message Sourcing split percentage violated.
MSO: Sourcing Allocation Window 7 Positive integer Use this profile option to divide the planning horizon in to windows. In each window, the planning solver plans to meet the split sourcing percentages.
Rapid Planning Weblogic Server Home Null For example, 
/slot/xyz/abc/WLS/11gNN/WLS_Home
 The path of the Oracle Rapid Planning Weblogic server home.
Released WIP Jobs: Consider in Clear to Build No Yes/No Use this profile option to instruct the planning solver whether to calculate clear to build for released discrete jobs. Valid values are:

  • Yes: Calculate clear to build for released discrete jobs

  • No: Do not calculate clear to build for released discrete jobs
Safety Stock Lead Time Method Safety Stock Percent Do not compute safety stock, Use Safety Stock Percent, Use Safety Stock Quantity Use when you want to calculate safety stock by quantity.

Note: The Safety Stock Method is set to MRP PLANNED PERCENT.

Oracle Rapid Planning uses the MSC: profile options that you set on the Plan Options > Advanced tab. See Plan Options.

The planning solver uses these technical profile options. These are not included in the Plan Options > Advanced tab:

These are other profile options that the planning solver uses. See Oracle Advanced Supply Chain Planning Implementation and User's Guide: