Oracle Value Chain Planning Installation

This chapter covers the following topics:

About this Document

Note: Application Install - Oracle Value Chain Planning 12.2. Information in this document applies to any platform.

This document contains instructions for customers who plan to upgrade an existing Oracle Value Chain Planning system to 12.2.

You should read and understand all the tasks described in these installation instructions before you begin the installation.

Complete the tasks in the following sections in the order listed. Updated versions of the patches and documents listed in this section may be available. Check My Oracle Support or contact Oracle Support Services for the latest versions.

Tasks included in these instructions require use of the AutoPatch, AD Administration, and other AD utilities. Tasks included in these instructions upgrade the following Oracle Value Chain Planning products to Release 12.2 level:

Before Applying the Feature Pack

To purchase this feature pack, contact an Oracle Sales Representative, by calling 1-888-ORACLEi (1-888-672-2534).

You must have already applied the 12.2 EBS upgrade OR performed a fresh install of 12.2 EBS applications.

VCP 12.2.3 is only supported with the following ERP versions: EBS 12.2.3, EBS 12.1.3, and E1 9.1. In the event that the EBS source instance is on 12.2.x, then both the EBS source instance and VCP destination instance must be on matching release version (for example, 12.2.3).

Refer to My Oracle Support Document 1361221.1, Oracle Value Chain Planning Installation Notes, Release 12.2 - FAQ And Latest Patch Information, for information on installation / upgrading to VCP 12.2.

If the source (ERP) system version from which data would be collected is lower than the VCP version being installed, then refer to My Oracle Support Document 1361221.1 for the supported integrations and patches required.


Before performing the upgrade, create backups of the following tables if you are running Demantra, upgrading to VCP 12.2, and have changed the content of any of the following tables:

After the upgrade is complete, check the tables above and reapply any customizations.

Product-Specific Installation Tasks

After you apply E-Business Suite Application Release 12.2 Media Pack, for each product that you intend to use, follow the product-specific installation steps in this document.

Post Installation Tasks

Profile Updates

Set the following profile option:


For customers using Demantra with EBS, perform the following:

Demand Planning

This section is meant for existing Oracle Demand Planning (ODP) customers who are upgrading to 12.2.

The exception granted to Oracle Demand Planning URLs has been removed. This results in an HTTP 400 error while trying to access ODP Plan UI. To correct this issue, manually modify the file security2_conf_FMW.tmp and uncomment the line:

#SecRule REQUEST_FILENAME "!^/oa_html/oowa/aw92/" chain

To do this, perform the following:

  1. Stop all mid-tier services.

  2. Back up the file $FND_TOP/admin/template/security2_conf_FMW.tmp.

  3. Edit $FND_TOP/admin/template/security2_conf_FMW.tmp and uncomment the line:

    #SecRule REQUEST_FILENAME "!^/oa_html/oowa/aw92/" chain


    SecRule REQUEST_FILENAME "!^/oa_html/oowa/aw92/" chain
  4. Run AutoConfig.

  5. Re-start the required mid-tier services.

Refer to My Oracle Support for the latest information.

Oracle Value Chain Planning - Oracle Transportation Management (OTM) Integration

Setting Up Oracle Transportation Management (OTM) v60 to integrate with EBS 12.2

All customers using OTM version 6 in order to integrate with EBS 12.2 need to perform the following on the OTM side:

  1. The following steps need to be performed once on the OTM instance to have the XSL file available for use:

    Get a copy of the "GLogXML v60 to v55 DateTime.xsl" and "GLogXML v60 to v55.xsl" files, the files are shipped with OTM in the {otm_install}/utils/integration/transform directory

    Place the xsl files on the OTM server. There are two options:

    • Manually copy the files to the XSL file location {otm_install}/glog/integration/client/xsl. Note that the actual location is indicated by the following OTM property : glog.integration.stylesheetRoot.

    • Upload the XSL files in the Integration Manager.

      • In OTM, log in as DBA.ADMIN (you can only upload the XSL files as DBA.ADMIN).

      • Navigate to Business Process Automation > Integration >Integration Manager > Upload an XML/CSV Transmission.

      • Upload each of the XSL files.

  2. The following steps need to be performed for the External Systems configured to send to the BPEL flow:

    • In OTM, log in to the domain.

    • Go to the External System you are using to send to BPEL, menu: Business Process Automation > Communication Management > External Systems.

    • In the External System Manager, in the External System Translations section, enter the following:

      • Sequence Number:1 (increase for each entry)

      • Stylesheet Name : GLogXML v60 to v55 DateTime.xsl

      • XML Element ID: Choose the outbound interface or select "*" for all interfaces.

      • Leave the other fields in the grid empty and click Save to save the translation entry.

      • Click Finished at the top of the page to save the External System.