APCC Standalone and Backport

This appendix covers the following topics:

Overview of APCC Standalone and Backport Capabilities

Oracle Advanced Planning Command Center integration with APS 11.5.10 enables users of 11.5.10 APS (ASCP, IO, or Demantra) to leverage key capabilities, such as:

APCC provides a format for all your analytical and reporting requirements. It incorporates an open interface with which to feed external data into APCC's fact data repository. The integration of APCC with APS 11.5.10 allows legacy systems or third party planning systems, including Oracle Rapid Planning solutions that are deployed on different instances to use a single APCC repository.

This enables an out-of-the-box integration of an 11.5.10 APS instance with an APCC 12.1.2 instance.

The following diagram compares the configurations of APCC 1.0 and 2.0.

the picture is described in the document text

Setups and Processes

When setting up your standalone or backport system, two separate scenarios are possible:

Changed Setup Steps for IO and ASCP

  1. In the Parameters window, turn on the Export to Advanced Planning Command Center plan launch parameter.

  2. Run Archive Plan Summary concurrent program with two variations: All summarized fact data is updated across the database link in a 12.2 instance.

    Note: A parameter, APCC Instance Code, is defaulted from the new profile MSC: APCC Instance. Demantra unpublished data historical facts or other forecast facts are not updated in the 12.2 instance.

  3. On the destination instance, launch the program to re-compute the aggregates based on the archive plan summary.

Changed Setup Steps for Demantra

There is a new publish workflow, which, includes the ability to archive. The default is Yes.

Dependencies and Interactions

The integration of 11.5.10 and the standalone has some limitations. These include:

Backport and Standalone Configuration

To run 11.5.10 and the APCC standalone successfully, your instances must meet some key criteria. They are:

The diagram below provides a high level view of the configuration:

the picture is described in the document text

Profile Options

Profile options for the backport and standalone versions of APCC must be set up as follows:

For additional information about setting up profile options, refer to Setting Up Profile Options in Chapter 4 of this User's Guide.

Setups and Processes

There are two possible scenarios when you are setting up APCC backport or standalone:

Integration with 11.5.10

11.5.10 Out-of-Box

For the 11.5.10 customers, there is a complete, out-of-box integration to a separate, standalone 12.2 APCC instance. The key assumptions and limitations that apply in this case are:

ASCP and IO Integration

For ASCP and IO plans, there is a new plan launch parameter, Export to Advanced Planning Command Center. The available values are Yes and No. The default is No.

Note: If the Set to Display KPI Indicators plan option is set to No, the Export to Advanced Planning Command Center parameter must also be set to No. It cannot be updated.

When the Export to Advanced Planning Command center parameter is set to yes, perform the steps below:

  1. 1. Run Archive Plan Summary concurrent program with two variations.

    a. All summarized fact data will be updated across the data base link in a 12.2 instance. A new parameter, APCC Instance Code, will be defaulted from a new profile option, MSC: APCC Instance.

    b. Demantra unpublished data, such as historical facts or other forecast facts, will not be updated in the 12.2 instance. A new parameter, Publish All Demantra Facts, will be defaulted to No.

  2. On the destination instance, launch the program to recompute the aggregates based on the above archive plan summary.

Demantra and Oracle Demand Planning

The publish workflow for Demantra is not changed. You must manually run the archive plan summary concurrent program, which will have the same new parameters as ASCP and IO by giving the Demand Scenario designator. This applies to ODP as well because the underlying data model is similar. However, in ODP, the parameter used to publish Demantra unpublished data, historical facts, and other forecast streams, must be set to No.

Integration Process

To achieve a successful integration, you must perform the processes and steps below:

  1. Launch the collection from the EBS/Source system.

  2. Set up all the required profiles for the APCC 12.1 integration.

    2a. For Demantra forecast metrics and historical facts, manually launch the Archive Plan Summary program.

    2b. For ASCP and IO metrics, the integration is automated by a plan launch parameter named “Export to APCC.

  3. Optionally, you can clean up a specific version or all versions of a plan using the Purge Plan summary concurrent program. The Purge Plan summary program cleans up your data for that plan or version in both the 11.5.10 and the 12.1 instances.

A summary or the process is shown in the diagram below.

the picture is described in the document text

Note: This integration does not add any additional latency for the plan itself to be available in the APS 11.5.10 planner workbench.

On APS 11.5.10 instance, the ASCP and IO Launch Plan concurrent program has a parameter named Export to APCC. This launches the Archive Plan Summary program internally for the current plan with the following default values:

When set to Yes, it triggers the Archive Plan Summary Program and creates a new archive of the plan on the APCC 12.1.

the picture is described in the document text

You can also launch the Archive Plan Summary program manually for any plan to publish the summary for analysis in APCC on the 12.1 instance. The parameters are:

Integration with 11.5.10 Purge Plan Summary

From APS 11.5.10 instance you can launch the concurrent program Purge Plan Summary to purge the facts of a plan, or a specific version of a plan, from both the APS 11.5.10 and APCC 12.1 instances. There is also a Purge Plan Summary program on 12.1 instance that you can launch independently, as shown below:

the picture is described in the document text

To launch the 11.5.10 launch process:

  1. Launch collection from the EBS/Source system.

    Note: You can automate this process by making the collections in the APS 11.5.10 instance synchronize the data in APCC 12.1 instance. This is accomplished by setting the collections parameter in the APS 11.5.10 with the parameter Synchronize Collected Data in 12.1 Instance. This must be completed before the archive plan summary is launched on the 11.5.10 instance.

  2. Set up all the required profiles for the APCC 12.1 integration.

  3. Create scenarios.

  4. Assign plans to these scenarios to enable comparisons in APCC reports and dashboards.

  5. Optionally, you can clean up a specific version or all versions of a plan using the Purge Plan summary concurrent program. The Purge Plan summary program cleans up your data for that plan or version in both the 11.5.10 and the 12.1 instances.

Integration with 12.1

To launch 12.1 integration, follow the processes below:

  1. Launch collection from the EBS/Source system.

  2. Set up all the required profiles for the APCC 12.1 integration.

  3. Create scenarios.

  4. Assign plans to these scenarios to enable comparisons in APCC reports and dashboards.

A summary of the process is shown in the diagram below.

the picture is described in the document text

12.1 Data Loads To and From APCC Fact Repository

Import User Interface

A new menu entry under the Advanced Planning Scenario Manager, named Load Fact Data From External Systems, accesses the Load Fact Data page. The data you load, using .csv file format, can be from either a legacy planning application or files that are exported from another 12.2 or 11.5.10 planning application.

You also have the option to upload the data using Id's for all entities, subject to the condition that the same source ERP instance. If you choose this option, you must:

the picture is described in the document text

There are three methods available for uploading your data:

In any plan, only one file can be loaded per entity. You do not need to load data for all twelve entities at the same time. When you do upload more than one file at a time, however, the upload method you have chosen applies to all files.

You can identify the plans created by the Load Fact Data page with a flag. Use this flag to ensure that:

The following list of categories is available for bulk upload directly into the APCC fact data repository. The table indicates the metrics that are grouped into each category and the fact table that the stores the data.

Category Fact Table
Supplies MSC_SUPPLIES_F
Demands MSC_DEMANDS_F
Demands (Cum) MSC_DEMANDS_CUM_F
Historical facts MSC_DEMANTRA_ODS_F
Forecasting MSC_DEMANTRA_F
Exceptions MSC_EXCEPTIONS_F
Order Details (due) MSC_ITEM_ORDERS_F
Order Details (start) MSC_ITEM_WIPS_F
Resources MSC_RESOURCES_F
Suppliers MSC_SUPPLIERS_F
Inventory facts MSC_ITEM_INVENTORY_F
Excess & Obsolescence facts MSC_ST_EXCESS_F

In the event that there is an error during your upload, such as invalid master data reference or invalid date range, the error is logged in the concurrent request log file and the data upload process continues to the next row without stopping.

Importing the Plan Summary

A new concurrent program, Import Plan Summary, is available in 12.2 only for users of 12.1 that enables you to import the summarized fact data from other legacy planning systems or from other versions of APS. The concurrent program has the following parameters:

Parameter Valid Values Notes
Plan Name All plans Required
Plan Version Versions of the plan Required
Plan Type

  • Advanced Supply Chain

  • Inventory Optimization

  • Distribution

  • Service Parts

  • Strategic Network Optimization

  • Demand Scenario

  • Rapid Planning

  
File Location   Directory name where the exported files will be written to. The system will expect the file names to be in the standard format of TABLE_NAME.csv (like MSC_ST_ITEM_ORDERS_F.csv)
Organization   Optional. Plan Owning organization
Plan Start Date   Optional
Plan Cut off date   Optional
Supplies – Overwrite after Date Optional
Demands – Overwrite after Date Optional
Demands (cum) – Overwrite after Date Optional
Historical facts – Overwrite after Date Optional
Forecasting – Overwrite after Date Optional
Exceptions – Overwrite after Date Optional
Orders (start) – Overwrite after Date Optional
Orders (due) – Overwrite after Date Optional
Resources – Overwrite after Date Optional
Suppliers – Overwrite after Date Optional
Inventory – Overwrite after Date Optional
Excess – Overwrite after Date Optional

Export Plan Summary

A new concurrent program “Export Plan Summary” will be made available in 12.2 only for users to be able to export the summarized fact data from APCC repository. The concurrent program will have the following parameters:

Parameter Valid Values Default Vault Notes
Plan Name All plans   Required
Plan Version Version of the plan   Required
Plan Type

  • Advanced Supply Chain Plan

  • Inventory Optimization

  • Distribution Plan

  • Service Parts Plan

  • Strategic Network Optimization

  • Demand Scenario

  • Rapid Plan

   Required
Export Complete Demantra Data Yes / No No Will control if all the Demantra facts (historical data, unpublished forecasts) are exported
      Directory name where the exported files will be written to.
File Location      

Other Impacts

In the 12.2 APCC instance, the imported plan summaries (either through UI or the import concurrent programs) will be flagged internally to distinguish them from other plans that are natively created in the APCC instance.

These imported plans and plan-runs will be available for creating new scenarios in APCC and in all plan list of values in all dashboard in APCC. They will not be available for attaching to any BPEL processes in APCC or in any of the individual applications or workbenches in the 12.1 instance.

APCC Integration with Oracle Distribution Planning

Value Chain Planning users who use Oracle Distribution Planning (DRP) are able to analyze their DRP plan outputs in APCC. You can publish your DRP plans to APCC and enable summarization and archival of these plans. You can also build scenarios using these DRP Plans in the Advanced Planning Scenario Manager User Interface of APCC.

Note: DRP plans are not accessible from the seeded Supply Chain Analyst Dashboard or in any of the seeded reports. However, they can be enabled in any new custom report.

The flow of information from DRP to APCC is shown in the diagram below:

the picture is described in the document text

Archiving a Plan Summary

To bring your DRP plan into APCC, you need to manually run the Archive Plan Summary program. This concurrent program accepts the Plan, Keep archived version parameter. Valid values are Y or N. You can launch this program for DRP plans with the same version and archiving capability as plan types ASCP, SNO, IO, and SPP.

Note: There is no plan option that enables launch of archive plan summary after every plan run. You need to manually launch this program or schedule, if appropriate.

You can use the plan option Calculate Key Performance Indicators to determine whether to trigger archival of DRP plan during its plan run. If this is set to Yes, then after the plan run, archive plan summary is launched automatically for that plan. The default is No.

When a DRP plan is launched, you have the option to keep the previous version of the plan archive or overwrite the previous version with the current version. You do this by using the new plan launch parameter Archive Current Version of Plan Summary, similar to ASCP Plans. The default is No.

Once the archive plan summary is completed, you can access the following measures for this DRP plan in Oracle Business Intelligence – Enterprise Edition (OBI-EE). For information on archiving plans and scenarios, see Archiving Plans and Scenarios in Chapter 4 of this document. For information on the archiving procedures, see Archiving Scenarios in Chapter 2 of this document.

Existing Base Measures:

New Base Measures:

Calculated Measures:

Purging a Plan Summary

The Purge Plan Summary program, which lets you purge unused plans and their archives, is enabled for DRP. There are no changes to the standard dimension or hierarchies. The following lists the dimensions that are relevant for the measures supported for DRP plan:

The mapping of the measures to the dimensions they support remains unchanged. For information on the purging plans and scenarios, see Purging Scenarios in Chapter 2 of this document. For information on measures and the dimensions they support, see Chapter 4 of this document, Understanding the Advanced Planning Analytical Framework.

Distribution Planning Profiles

DRP plans support the current APCC profile settings of the following profiles:

These settings control the time dimensions, item dimensions and the measures. For more information about APCC profiles, see Chapter 4 of this document, Understanding the Advanced Planning Analytical Framework.

Exporting and Importing a Plan Summary

You can deploy APCC in a standalone mode where you can integrate third party planning systems into it. In this mode you can use APCC as a central tool for understanding global supply chain planning deployments that include other legacy products. To enable this, you can import/export facts directly into APCC repository

DRP plans are enabled in the two concurrent programs 'Export Plan Summary' and 'Import Plan Summary so that you can download the measures listed above and upload all measures to APCC.

For more information about APCC standalone, refer to sections earlier in this appendix.