1. Implementation Guide
  2. Data Loads and Initial Batch Processing
  3. Loading Plans to RI

Loading Plans to RI

If you are implementing a Planning module and need to generate plan-influenced forecasts (such as the AP in-season forecast) then you will need to first integrate your plans into RI (which acts as the singular data warehouse for this data both when the plans come from Oracle Retail solutions and when they come from outside of Oracle).

If you are pushing the plans from MFP or AP directly, then you will enable a set of POM jobs to copy plan outputs directly to RI tables. You may also use an ad hoc process to move the plan data on-demand during the implementation.

Table 3-10 Plan Extracts from MFP and AP

POM Job Name Usage Details

W_RTL_PLAN1_PROD1_LC1_T1_FS_SDE_JOB

Extract the MFP plan output from the MFP_PLAN1_EXP table in the RDX schema.

W_RTL_PLAN2_PROD2_LC2_T2_FS_SDE_JOB

Extract the MFP plan output from the MFP_PLAN2_EXP table in the RDX schema.

W_RTL_PLAN3_PROD3_LC3_T3_FS_SDE_JOB

Extract the MFP plan output from the MFP_PLAN3_EXP table in the RDX schema.

W_RTL_PLAN4_PROD4_LC4_T4_FS_SDE_JOB

Extract the MFP plan output from the MFP_PLAN4_EXP table in the RDX schema.

W_RTL_PLAN5_PROD5_LC5_T5_FS_SDE_JOB

Extract the AP plan output from the AP_PLAN1_EXP table in the RDX schema.

In all of the jobs above, the target table name is in the job name (such as W_RTL_PLAN2_PROD2_LC2_T2_FS as the target for the PLAN2 extract). Once the data is moved to the staging layer in RI, the source-agnostic fact load jobs will import the data (W_RTL_PLAN2_PROD2_LC2_T2_FS is loaded to W_RTL_PLAN2_PROD2_LC2_T2_F, and so on). The fact tables in RI are then available for AI Foundation jobs to import them as needed for forecasting usage.

The plan tables in RI have configurable levels based on your Planning implementation. The default levels are aligned to the standard outputs of MFP and AP if you do not customize or extend them. If you have modified the planning solution to operate at different levels, then you must also reconfigure the RI interfaces to match. This includes the use of flexible alternate hierarchy levels (for example, the PRODUCT_ALT.csv interface) which require custom configuration changes to the PLAN interfaces before you can bring that data back to RI and AIF. These configurations are in C_ODI_PARAM_VW, accessed from the Control & Tactical Center in AI Foundation. For complete details on the plan configurations in RI, refer to the Retail Insights Implementation Guide.