Oracle® Value Chain Planning: Installation Guide Release 12.2

Oracle® Value Chain Planning
Installation Guide
Release 12.2
Part No. E48790-02
November 2013
Oracle Value Chain Planning Installation Guide, Release 12.2
Part No. E48790-02
Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved.
Primary Author: Gary O'Hara, Greg Watkins
Contributing Author: Ganesh Iyer, Christine Chen
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.

Contents
Send Us Your Comments
Preface
1 Oracle Value Chain Planning Installation

About this Document................................................................................................................ 1-1
Before Applying the Feature Pack............................................................................................ 1-2
Product-Specific Installation Tasks.......................................................................................... 1-3
Post Installation Tasks.............................................................................................................. 1-3
Oracle Value Chain Planning - Oracle Transportation Management (OTM) Integration...... 1-4
2 Advanced Planning Command Center

Setting Up Advanced Planning Command Center Reports and Dashboards......................... 2-1
Configuring Single Sign-on...................................................................................................... 2-9
Troubleshooting...................................................................................................................... 2-11
Using WebCenter for APCC....................................................................................................2-12
3 Advanced Supply Chain Planning

Performing Pre-Configuration Setup....................................................................................... 3-1
Performing Configuration ........................................................................................................ 3-2
Upgrading ASCP..................................................................................................................... 3-26
Troubleshooting...................................................................................................................... 3-28
4 Production Scheduling
Standalone, Non-Integrated Production Scheduling Installations..........................................4-1
Production Scheduling Implementation.................................................................................. 4-1
iii
Mandatory Prerequisite Patches............................................................................................... 4-1
Post Installation ........................................................................................................................ 4-2
Post Installation Settings.......................................................................................................... 4-2
Special Instructions................................................................................................................... 4-3
5 Strategic Network Optimization

Standalone, Non-Integrated Strategic Network Optimization Installations.......................... 5-1
Strategic Network Optimization Integration........................................................................... 5-1
Mandatory Prerequisite Patches for Oracle Process Manufacturing (OPM) Users................. 5-1
Post Installation......................................................................................................................... 5-2
Post Installation Settings.......................................................................................................... 5-2
Special Instructions................................................................................................................... 5-3
6 Service Parts Planning

Service Parts Planning Installation Updates............................................................................ 6-1
7 Demand Signal Repository

Demand Signal Repository (DSR) Implementation.................................................................7-2
Prerequisites.............................................................................................................................. 7-2
Setting Up Oracle Data Integrator (ODI)..................................................................................7-2
Configuring the Physical Architecture in Topology Manager.................................................7-5
Configuring the Context and Logical Architecture in Topology Manager..............................7-7
Executing Scenarios................................................................................................................... 7-8
Setting Up Oracle Business Intelligence Enterprise Edition (OBIEE)..................................... 7-8
Setting Up Oracle Business Intelligence Enterprise Translations......................................... 7-10
Setting Up the Exception Management Dashboard Feature.................................................. 7-11
Configuring a Web Service in OBIEE..................................................................................... 7-14
Setting Up Web Services......................................................................................................... 7-19
Setting Up Demand Signal Repository - Demantra Integration............................................ 7-20
Setting up Demand Signal Repository - Retail Merchandise System (RMS) Integration.... 7-21
Configuring the User Parameters in DSR Lookups............................................................... 7-23
Creating the Directories Defined in the DDR_R_LKUP_MST Table....................................7-24
Copying the Class and DTD Files .......................................................................................... 7-24
Importing the DSR - RMS Project Objects in the ODI Designer.......................................... 7-25
Configuring the Physical Architecture in Topology Manager...............................................7-27
Configuring the Context and Logical Architecture in Topology Manager............................7-27
Copying the EDIDLPRD.dat File............................................................................................ 7-28
Executing the Scenario............................................................................................................ 7-28
iv
8 Rapid Planning
Rapid Planning Installation...................................................................................................... 8-1
9 Other Useful Information

Troubleshooting........................................................................................................................ 9-1
Index
v

Send Us Your Comments
Oracle Value Chain Planning Installation Guide, Release 12.2

Part No. E48790-02
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii

Preface
Intended Audience
Welcome to Release 12.2 of the Oracle Value Chain Planning Installation Guide.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Structure
1 Oracle Value Chain Planning Installation
2 Advanced Planning Command Center
3 Advanced Supply Chain Planning
4 Production Scheduling
5 Strategic Network Optimization
6 Service Parts Planning
7 Demand Signal Repository
8 Rapid Planning
9 Other Useful Information
ix
Related Information Sources
Open Source Disclosure
The Advanced Planning applications have embedded within them a variety of third
party software components, each of which has its own copyright and licensing terms.
The Advanced Planning applications containing third party components from the
development organizations identified below are identified in the parenthetical
following the name of the organization.
Apache Software Foundation
Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include
the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (
http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "Apache" and "Apache Software Foundation" must not be used to
endorse or promote products derived from this software without prior written
permission. For written permission, please contact apache@apache.org.
Products derived from this software may not be called "Apache", nor may "Apache"
appear in their name, without prior written permission of the Apache Software
Foundation.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
x
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf
of the Apache Software Foundation. For more information on the Apache Software
Foundation, please see <http://www.apache.org/>.
Portions of this software are based upon public domain software originally written at
the National Center for Supercomputing Applications, University of Illinois,
Urbana-Champaign.
ptmalloc
Copyright (c) 1999 Wolfram Gloger
Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that (i) the
above copyright notices and this permission notice appear in all copies of the software
and related documentation, and (ii) the name of Wolfram Gloger may not be used in
any advertising or publicity relating to the software.
THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY
KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION,
ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. IN NO EVENT SHALL WOLFRAM GLOGER BE LIABLE FOR ANY
SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY
KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF
DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Sleepycat Software
Copyright (c) 1990, 1993, 1994 The Regents of the University of California. All rights
reserved.
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
• Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
• All advertising materials mentioning features or use of this software must display
the following acknowledgement:
This product includes software developed by the University of California, Berkeley
and its contributors.
xi
Neither the name of the University nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS"

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Tool Command Language (TCL)
This software is copyrighted by the Regents of the University of California, Sun
Microsystems, Inc., Scriptics Corporation, ActiveState Corporation and other parties.
The following terms apply to all files associated with the software unless explicitly
disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this
software and its documentation for any purpose, provided that existing copyright
notices are retained in all copies and that this notice is included verbatim in any
distributions. No written agreement, license, or royalty fee is required for any of the
authorized uses. Modifications to this software may be copyrighted by their authors
and need not follow the licensing terms described here, provided that the new terms are
clearly indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY
PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND
NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND
THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE
MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S.
government, the Government shall have only "Restricted Rights" in the software and
related documentation as defined in the Federal Acquisition Regulations (FARs) in
Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of
Defense, the software shall be classified as "Commercial Computer Software" and the
xii
Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1)
of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and
others acting in its behalf permission to use and distribute the software in accordance
with the terms specified in this license.
Independent JPEG Group
This product includes software developed by the Independent JPEG Group. Copyright
(c) 1991-1998 The authors make NO WARRANTY or representation, either express or
implied, with respect to this software, its quality, accuracy, merchantability, or fitness
for a particular purpose. This software is provided "AS IS", and you, its user, assume
the entire risk as to its quality and accuracy.
Henry Spencer's Regular Expression Library (REGEX)
This product includes software developed by Henry Spencer. Copyright (c) 1992, 1993,
1994, 1997 This software is not subject to any license of the American Telephone and
Telegraph Company or of the Regents of the University of California. Permission is
granted to anyone to use this software for any purpose on any computer system, and to
alter it and redistribute it, subject to the following restrictions:
• The author is not responsible for the consequences of use of this software, no matter
how awful, even if they arise from flaws in it.
• The origin of this software must not be misrepresented, either by explicit claim or
by omission. Since few users ever read sources, credits must appear in the
documentation.
• Altered versions must be plainly marked as such, and must not be misrepresented
as being the original software. Since few users ever read sources, credits must
appear in the documentation.
• This notice may not be removed or altered.
XBAE
Copyright (c) 1991, 1992 Bell Communications Research, Inc. (Bellcore)
Copyright (c) 1995-99 Andrew Lister
All Rights Reserved.
Permission to use, copy, modify and distribute this material for any purpose and
without fee is hereby granted, provided that the above copyright notices and this
permission notice appear in all copies, and that the name of any author not be used in
advertising or publicity pertaining to this material without the specific, prior written
permission of an authorized representative of Bellcore and current maintainer.
BELLCORE AND OTHER CONTRIBUTORS MAKE NO REPRESENTATIONS AND
EXTEND NO WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE
INFORMATION, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ANY PARTICULAR
xiii
PURPOSE, AND THE WARRANTY AGAINST INFRINGEMENT OF PATENTS OR
OTHER INTELLECTUAL PROPERTY RIGHTS. THE SOFTWARE IS PROVIDED "AS
IS", AND IN NO EVENT SHALL ANY AUTHOR OR ANY OF THEIR AFFILIATES BE
LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS OR OTHER
INCIDENTAL OR CONSEQUENTIAL DAMAGES RELATING TO THE
INFORMATION.
Oracle
Oracle takes no responsibility for its use or distribution of any open source or
shareware software or documentation and disclaims any and all liability or damages
resulting from use of said software or documentation.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
You can navigate to the Oracle Integration Repository through Oracle E-Business Suite
Integrated SOA Gateway.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
xiv
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xv
1
Oracle Value Chain Planning Installation
This chapter covers the following topics:

• About this Document
• Before Applying the Feature Pack
• Product-Specific Installation Tasks
• Post Installation Tasks
• Oracle Value Chain Planning - Oracle Transportation Management (OTM)
Integration
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:
• Advanced Planning Command Center (APCC)
• Advanced Supply Chain Planning (ASCP)
Oracle Value Chain Planning Installation 1-1

• Demand Planning (DP)
• Demantra Demand Management
• Inventory Optimization (IO)
• Global Order Promising (GOP)
• Collaborative Planning (CP)
• Production Scheduling (PS)
• Strategic Network Optimization (SNO)
• Service Parts Planning (SPP)
• Demand Signal Repository (DSR)
• Rapid Planning (RP)
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.
Demantra
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:
• MSD_DEM_QUERIES
• MSD_DEM_SERIES
1-2 Oracle Value Chain Planning Installation Guide

• MSD_DEM_ENTITY_QUERIES
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

Create the $APPLCSF/out Subdirectory
If you set "AppsLog Distribution = product" during release 12.2 installation process,
manually create the $APPLCSF/out subdirectory.
Profile Updates
Set the following profile option:
• MSC: Share Plan Partitions = No
Demantra
For customers using Demantra with EBS, perform the following:
• After Demantra is installed on the VCP database, run concurrent program 'Update
Synonyms'. (Navigation: Demand Management System Administrator > Other >
Requests > Submit a New Request > Single Request)
Refer to My Oracle Support, Document 1061331.1, for more details.
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

to
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.

2
Advanced Planning Command Center

• Setting Up Advanced Planning Command Center Reports and Dashboards
• Configuring Single Sign-on
• Troubleshooting
• Using WebCenter for APCC
Setting Up Advanced Planning Command Center Reports and Dashboards

This section provides information on setting up Advanced Planning Command Center
(APCC) reports and dashboards.
Installation Prerequisites
Before performing Advanced Planning Command Center Planning (APCC) installation
and setup procedures in this document, verify the following application prerequisites:
• If you are planning to integrate Oracle Business Intelligence Enterprise Edition
(OBIEE) with Oracle E-Business Suite (EBS) using Single Sign-on (SSO), make sure
your EBS and OBIEE servers are in the same domain and use the same security
protocol.
• Oracle Business Intelligence Enterprise Edition 11 (OBIEE 11.1.1.7.0) must be

installed. APCC is certified with OBIEE 11.1.1.7.0. Refer to My Oracle Support,
Document 1542578.1, OBIEE 11.1.1.7.0 is Available for BI Enterprise, for information
on applying patch set updates.
• Copy mscrpd.zip and mscwebcat.zip files, which will be placed in

$MSC_TOP/patch/115/obiee directory, to a temporary directory.
• Refer to Using WebCenter for APCC, page 2-12 for WebCenter and SOA BPEL
flows.
Advanced Planning Command Center 2-1

Configuring the tnsnames.ora File
Configure the tnsnames.ora file so the BI Server can connect to the database.
In OBIEE 11g, the software itself contains database client. When you connect to the
database through the Repository or BI Server, it locates the tnsnames.ora entry in the
Oracle Client of OBIEE 11g instead of your database.
The tnsname.ora file is in the following location:
MW_HOME/Oracle_BI1/network/admin/tnsnames.ora
Note: If file does not exist, create a new one.
The file entry format is not fixed, but follows standard Oracle
tnsnames.ora format.
Sample File Format:

<addressname>=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)HOST=<hostname>)(P
ORT=<port>))(CONNECT_DATA=(SID=<sid>)))
Example:
mz1dv220=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rws60147rems.us.or
acle.com)(PORT=1524))(CONNECT_DATA=(SID= mz1dv220)))
Configuring and Deploying RPD and Webcat Files

Performing the procedure below to configure and deploy RPD and Webcat files.
1. Download the mscrpd.zip, mscwebcat.zip, and the language file you need to set up
(for example, apcc-obiee-ja.zip for Japanese) from $APPL_TOP to a temporary
directory.
The table below provides the names of the available language files.
File Name Language File Name Language
apcc-obiee-ar.zip Arabic apcc-obiee-ko.zip Korean
apcc-obiee-cs.zip Czech apcc-obiee-nl.zip Dutch
apcc-obiee-da.zip Danish apcc-obiee-no.zip Norwegian
apcc-obiee-de.zip German apcc-obiee-pl.zip Polish

File Name Language File Name Language
apcc-obiee-el.zip Greek apcc-obiee-pt.zip Portuguese
apcc-obiee-en.zip English apcc-obiee-pt_BR.zip Brazilian Portuguese
apcc-obiee-es_ES.zip Spanish apcc-obiee-ro.zip Romanian
apcc-obiee-fi.zip Finnish apcc-obiee-ru.zip Russian
apcc-obiee-fr.zip French apcc-obiee-sk.zip Slovak
apcc-obiee-he.zip Hebrew apcc-obiee-sv.zip Swedish
apcc-obiee-hr.zip Croatian apcc-obiee-th.zip Thai
apcc-obiee-hu.zip Hungarian apcc-obiee-tr.zip Turkish
apcc-obiee-it.zip Italian apcc-obiee-zh_CN.zip Simplified Chinese
apcc-obiee-ja.zip Japanese apcc-obiee-zh_TW.zip Traditional Chinese
2. Unzip mscwebcat.zip to OBIEE server ORACLE_INSTANCE

/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/.
3. Unzip mscrpd.zip and place the AdvancedPlanning.rpd file in a temporary

location.
4. Open Fusion Middleware control using following URL:

http://hostname.domain:port/em
1. Log in with WebLogic user and password.
2. In left tree structure, select Business Intelligence > coreapplication > Overview
tab.
3. Click Stop. All services are stopped.


2. In left tree structure, select Business Intelligence > coreapplication >
Deployment tab > Repository tab.
3. In Presentation Service Repository, verify the absolute path for the

PlanningAnalytics directory.
Example:
<CatalogPath>/slot/ems1395/fmw/instances/instance1/bifound
ation/OracleBIPresentationServicesComponent/coreapplicatio
n_obips1/catalog/PlanningAnalytics</CatalogPath>
4. If the path needs to be changed, then click Lock & Edit Configuration at top of
page. Change catalog path, click Apply, and then click Activate Changes at the
top of the page.
6. Open AdvancedPlanning.rpd in the Oracle Business Administration Tool (from

Windows client), and change the database connection information in MSC_Conn,
MSC_INIT_Conn under Planning Analytics in the Physical.
If you are setting up a Single Sign-On environment (most common setup), perform
the following:
1. Enable Connection Scripts for MSC_Conn and MSC_INIT_Conn.
2. Set the translations initialization variables as follows:

• Navigate to Manage > Variables > Session > Initialization Blocks.
• Enable Manage Translation and Set Translation.
• Disable Set Translations without SSO.
3. Save changes.
If you are not setting up a Single Sign-On environment, perform the following:
1. Disable Connection Scripts for MSC_Conn and MSC_INIT_Conn.
2. Set the translations initialization variables as follows:

• Navigate to Manage > Variables > Session > Initialization Blocks.
• Disable Manage Translation and Set Translation.
• Enable Set Translations without SSO.
3. Save changes.

2. In left tree structure, select Business Intelligence > coreapplication >

Deployment tab > Repository tab.
3. Navigate to upload BI Server Repository section.
4. Use the Browse button to select AdvancedPlanning.rpd from temporary

location.
5. Enter password.
6. Click Apply.
7. Click Activate Changes at top of page.
8. Perform the following procedure to refresh GUIDs.

This information is also available from the following URL:
http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10543/privileges.htm#BIES
C721
If you change the directory server used as the identity store for the authentication
provider, then you must refresh the user GUIDs as described below. If you do not
refresh the GUIDs and the same user name exists in both directory servers (original
and new), then the original user GUID might conflict with the user GUID contained
in new directory server, resulting in authentication errors.
To Refresh the User GUIDs:
This task requires that you manually edit the configuration files to instruct the
Oracle BI Server and Oracle BI Presentation Server to refresh the GUIDs on restart.
Once completed, you will edit these files again to remove the modification. For
information about where to locate Oracle Business Intelligence configuration files,
see "Where Configuration Files are Located" in Oracle Fusion Middleware System
Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
1. Update the FMW_UPDATE_ROLE_AND_USER_REF_GUIDS parameter in the file
NQSConfig.ini:
1. Open the file NQSConfig.ini located at:
ORACLE_INSTANCE/config/OracleBIServerComponent/coreappl
ication_obisn
2. Locate the FMW_UPDATE_ROLE_AND_USER_REF_GUIDS parameter and set

it to YES, as shown below.

FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = YES;
3. Save and close the file.
2. Update the Catalog element in the file instanceconfig.xml.

1. Open the file instanceconfig.xml located at ORACLE_INSTANCE
/config/OracleBIPresentationServicesComponent/coreapplication_obipsn
2. Locate the Catalog element and add UpdateAccountGUIDs line as

shown below:
<Catalog>
<UpdateAndExit>false </UpgradeAndExit>
<UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
</Catalog>
3. In the Enterprise Manager Overview tab, click Start to start all services.
4. Set the FMW_UPDATE_ROLE_AND_USER_REF_GUIDS in the file NQSConfig.ini

back to NO.
Important: You must perform this step to ensure that your

system is secure.
5. Update the Catalog element in instanceconfig.xml to remove the

<UpdateAccountGUIDs> entry.
6. In the Enterprise Manager Overview tab, click Restart to restart all services.
9. Unzip the language file, such as apcc-obiee-ja.zip, to temp directory. This generates
the apcc directory.
10. Make sure your environment setting is correct to use the TransX utility.
The following link provides more information about Java technologies, tips for
developing in the Java programming language, and various ways you can leverage
the Java platform.
http://www.oracle.com/technetwork/topics/newtojava/documentation/index.html
You can perform the following option from your database machine with XDK
installed or Windows client.
Option #1 (from database):
1. Set ORACLE_HOME to the database ORACLE_HOME.

2. Set CLASSPATH and export as mentioned below:
CLASSPATH=$ORACLE_HOME/lib/xmlparserv2.jar:
$ORACLE_HOME/lib/xschema.jar:
$ORACLE_HOME/lib/xsu12.jar:
$ORACLE_HOME/lib/oraclexsql.jar:
$ORACLE_HOME/lib/classgen.jar:
$ORACLE_HOME/lib/transx.zip:
$ORACLE_HOME/jdbc/lib/ojdbc6dms.jar:
$ORACLE_HOME/jdbc/lib/ojdbc6.jar:
$ORACLE_HOME/rdbms/jlib/servlet.jar:
$ORACLE_HOME/rdbms/jlib/xdb.jar:
$ORACLE_HOME/oc4j/lib/dms.jar
export CLASSPATH
3. Set CLASSPATHJ and export as mentioned below:

CLASSPATHJ=$ORACLE_HOME/jdbc/lib/ojdbc6_g.jar
export CLASSPATHJ
4. Set JAVA_HOME and export as mentioned below:

JAVA_HOME=$ORACLE_HOME/jdk
export JAVA_HOME
Option #2 (from Windows client):

1. On Windows and Windows XP clients, right-click My Computer and select
Properties. On Windows 7 clients, right-click Computer and select Properties.
2. On Windows and Windows XP clients, select the Advanced tab in System

Properties. On Windows 7 clients, select Advanced System Settings.
3. Click Environment Variables to set CLASSPATH, CLASSPATHJ,

JAVA_HOME, ORACLE_HOME, and other variables.
4. Set ORACLE_HOME.
set ORACLE_HOME=D:\Oracle\Database\Client\product\11.2.0\client_2
5. Set CLASSPATH.
set CLASSPATH=%ORACLE_HOME%\LIB\xmlparserv2.jar;
%ORACLE_HOME%\LIB\xsu12.jar;
%ORACLE_HOME%\LIB\oraclexsql.jar;
%ORACLE_HOME%\LIB\transx.zip;
%ORACLE_HOME%\jdbc\lib\classes12dms.jar;
%ORACLE_HOME%\jdbc\lib\ojdbc5.jar;
%ORACLE_HOME%\LIB\servlet.jar;
%ORACLE_HOME%\RDBMS\jlib\xdb.jar;
%CLASSPATH%
6. Set CLASSPATHJ.
set
CLASSPATHJ=C:\Apps\db\oracle102\jdbc\lib\classes12.zip;C:\Apps\db
\oracle102\jdbc\lib\nls_charset12.jar

7. Set JAVA_HOME.
set JAVA_HOME=D:\jdk1.5.0_09
Note: The path value setting will be different due to different

installation path.
Make sure that all jar files mentioned are located in appropriate
directories, otherwise you will receive errors while running the
TransX utility.
Make sure that the path values are on one line so that all the
directories referenced will be added to environment variable
properly.
11. Use TransX to upload the dlf file such as apcc_ja.dlf in apcc\OracleBI\repository
directory by providing username/password and DB connection SID.
transx "hostname:port:sid" username password filename
Example:
transx "rws60147rems:1524:mz1dv220" apps apps
d:\apcc\OracleBI\repository\apcc_ja.dlf
12. Verify the seeding data is uploaded correctly in MSC_TRANSLATED_MESSAGE

using the following query:
select lang_id, count(*)
from msc_translated_message
group by lang_id;
13. SKIP THIS STEP FOR ENGLISH. Copy the files sopcaptions.xml, sppcaptions.xml,
scacaptions.xml and scrmcaptions.xml from your temp directory into
ORACLE_HOME
\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\core
application_obips1\msgdb\l_ja\captions on OBIEE machine if the directory has
been created; if directory has not been created, create first subdirectory
l_ja\captions under coreapplication_obips1\msgdb directory.
Note: Make sure the captions folder uses a lower case "c".
Also, inside the XML files, make sure the text tag is all upper case
<TEXT>. If it is not (for example, it appears as <Text>), then replace
all occurrences to upper case <TEXT>.
14. Restart OBIEE services.


tab.
4. Click Restart to restart all services.
Configuring Single Sign-on

Perform the subsequent procedures to configure Single Sign-On (SSO) for your APCC
installation.
Note: Make sure your EBS and OBIEE servers are in the same domain
and use the same security protocol.
Setting Up the OBIEE Profile

Set the URL for "FND: Oracle Business Intelligence Suite EE base URL" profile. The URL
uses the following format:
http://machine:port
Add Session Cookie for Single Sign-On

Perform the following procedure to add a session cookie for Single Sign-On
deployments.
1. Stop all OBIEE services using Fusion Middleware control.
1. Open Fusion Middleware control using following URL format:
3. In left tree structure select Business Intelligence > coreapplication > Overview
tab.
4. Click Stop.
2. Run the SQL statement below to get cookie_name. This will be the cookie_name for
nameInSource param.
select app_session.GET_ICX_COOKIE_NAME from dual
3. Add the following to the file authenticationschemas.xml in the

ORACLE_INSTANCE/bifoundation/web/display directory:

For more information, refer to "Integrating with Oracle E-Business Suite Security"
from the Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence
Enterprise Edition 11g Release 1 (11.1.1) in the link below:
http://fmwdocs.us.oracle.com/doclibs/fmw/E15295_01/bi.1111/e16364/ebs_actions.ht
m
Example:
1. Find the following element:
<AuthenticationSchema name="EBS-ICX"
2. Locate the subelement RequestVariable source="cookie" and change

the value of the nameInSource attribute from ICX_SESSION to the name of
the EBS ICX authentication cookie prefix.
Example:
<RequestVariable source="cookie" type="auth" nameInSource="VIS"
biVariableName="NQ_SESSION.ICX_SESSION_COOKIE" />
3. Do not update the RequestVariable source="url" sub-element.
4. In the same entry (RequestVariable source="cookie"), ensure that the

value of the biVariableName attribute is the same as the value you entered as
part of the connection script when you created the connection pool for the
Oracle E-Business Suite database.
See step 13 of Section 5.1, "Creating a Database Object and Connection Pool for
the Oracle E-Business Suite Database
[http://fmwdocs.us.oracle.com/doclibs/fmw/E15295_01/bi.1111/e16364/ebs_actio
ns.htm#CJAGCIEC#CJAGCIEC]" for more information.
5. Find the following element:

<SchemaKeyVariable source="cookie"
6. Change the value of the nameInSource attribute from ICX_SESSION to the

name of the EBS ICX authentication cookie prefix (often VIS).
Example:
<SchemaKeyVariable source="cookie" nameInSource="VIS"
forceValue="EBS-ICX" />
4. Perform the following to instanceconfig.xml file in ORACLE_INSTANCE

/config/OracleBIPresentationServicesComponent/coreapplication_obipsn directory:
Example:
1. Locate the Authentication element.

2. Include EBS-ICX in the list of enabled schemas as shown below:
<EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate
-soap,EBS-ICX</EnabledSchemas>
Note: Ignore the comment in instanceconfig.xml that says this

setting is centrally managed. EBS-ICX must be manually added
to the EnabledSchemas element.
3. Save and close file.
For more information, refer to "Updating instanceconfig.xml

[http://fmwdocs.us.oracle.com/doclibs/fmw/E15295_01/bi.1111/e16364/ebs_actions.h
tm#CIHGHEFE]" from the Oracle Fusion Middleware Integrator's Guide for Oracle
Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).
5. Start all OBIEE services.

tab.
4. Click Start to start all services.
Troubleshooting
If TransX does not run due to missing classes, it is most likely that classpath is not set
properly. Following sample shows setting CLASSPATH variable for Windows 11g
client with XDK option:
Example
set ORACLE_HOME=D:\Oracle\Database\Client\product\11.2.0\client_2
set CLASSPATH=%ORACLE_HOME%\LIB\xmlparserv2.jar;
%ORACLE_HOME%\LIB\xsu12.jar;
%ORACLE_HOME%\LIB\oraclexsql.jar;
%ORACLE_HOME%\LIB\transx.zip;
%ORACLE_HOME%\jdbc\lib\classes12dms.jar;
%ORACLE_HOME%\jdbc\lib\ojdbc5.jar;
%ORACLE_HOME%\LIB\servlet.jar;
%ORACLE_HOME%\RDBMS\jlib\xdb.jar;
%CLASSPATH%
For more XDK information, refer to Oracle XDK documentation.

Using WebCenter for APCC
This topic provides information about using WebCenter with APCC.
Prerequisites
Verify the information below.
1. Verify that WebLogic/WebCenter/SOA components are installed properly. Refer to
My Oracle Support note 1074345.1.
2. Verify UCM is installed and configured properly [optional].
Configuring WebCenter
To configure WebCenter for Oracle Advanced Planning Command Center perform the
following:
1. Deploy and configure the spaces servlet, page 2-12.
2. Deploy and configure the BPM Tasklist, page 2-14.
3. Deploy and configure the group space Template, page 2-17.
4. Deploy and configure the application links [Optional], page 2-19.
5. Deploy and configure the SOA BPEL flows, page 2-23.
6. Set up profile options, page 2-23.
7. Compile MscWCRedirect.jsp, page 2-25.
8. Run the Planning Process Activities concurrent process, page 2-26.
9. Change the WebCenter application name, page 2-26.
Deploy and Configure the Spaces Servlet

Perform the procedures below to deploy and configure the spaces servlet.
1. Obtain file mscspacesservlet.ear from
$MSC_TOP/patch/115/ear/mscspacesservlet.ear.
2. Copy it to your local directory in Linux Session.
3. Open the WebCenter Console for the WebCenter domain.

4. Log in to the WebCenter Console.
5. Click Lock & Edit.
6. From the Domain Structure region, click Deployments.
7. Click Install.
8. Click link upload your file(s).
9. Search for your EAR file in the deployment archive and select the EAR file to
deploy.
10. Click Next, select Managed Server WLS_Spaces, deploy .ear file, and click Finish.
11. When deployment to the managed server is complete, click the Release
Configuration.
12. If the state of deployment of mscspacesservlet is "Prepared", click Lock & Edit >
Deployments, select deployment mscspacesservlet, click Start, click Servicing all
requests, and then click Release Configuration. Verify that the deployment status
of mscspacesservlet changes to Active.
13. To generate Java keystore in the WebCenter instance, go to JDK_HOME/jdk/bin and

open a command prompt.
14. Execute the following keytool run commands to generate keystore producer.jks:
keytool -genkeypair -keyalg RSA -dname
"cn=producer,dc=example,dc=com" -alias producer -keypass welcome1
-keystore /scratch/dumakant/keystore/samedomain/producer.jks
-storepass welcome1 -validity 365
keytool -exportcert -v -alias producer -keystore
/scratch/dumakant/keystore/samedomain/producer.jks -storepass
welcome1 -rfc -file producer.cert
keytool -importcert -alias webcenter_spaces_ws -file producer.cert
-keystore /scratch/dumakant/keystore/samedomain/producer.jks
-storepass welcome1
/scratch/dumakant/keystore/samedomain/ can be your local Linux home path.

Set the value of recipient key alias in profile option "MSC: APCC Webcenter Spaces
Recipient Key Alias".
15. Connect to the WebCenter server using telnet.
16. Execute the following command:

cd /slot/ems2995/appmgr/Oracle/Middleware/user_projects/
domains/wc_domain/config/fmwconfig/
17. Copy producer.jks to this location.

18. Open jps-config.xml.
19. Change serviceInstance as follows:

serviceInstance name="keystore" provider="keystore.provider"
location="./default-keystore.jks" to location="./producer.jks"
20. Run command wlst.
21. Connect to the WebCenter using the following command line:

connect('weblogic','welcome1', 'Webcenter host:port')
For example, for WebCenter host:port, use dadvmi0029.us.oracle.com:7060.
22. Back up cwallet.sso.
23. Execute the following:

createCred(map="oracle.wsm.security",key="enc-csf-key",user="produce
r",password="welcome1",desc="Enc Password")
createCred(map="oracle.wsm.security",key="sign-csf-key",user="produc
er",password="welcome1",desc="Enc Password")
createCred(map="oracle.wsm.security",key="keystore-csf-key",user="ke
ystore-csf-key",password="welcome1",desc="Keystore password")
24. Restart the WebCenter servers.
Deploy and Configure the BPM Tasklist

Perform the following procedures to deploy and configure the BPM Tasklist.
Create a Directory and Set a Path
1. Create directory /tmp/tasklist and set path as follows:
/Oracle/Middleware/jdk160_11/bin/:$PATH
Update and Copy the WAR File to the WebCenter Home

1. Get file msc_custom_spaces.zip from ARU and unzip it to obtain
custom.webcenter.spaces.war. Then, unjar it. Execute the following:
cd /tmp/tasklist;
unzip msc_custom_spaces.zip
cd /tmp/tasklist;
jar xvf custom.webcenter.spaces.war;
2. Go to WEB-INF/lib/ and unjar wf_client_custom.jar. Execute the following:

cd /tmp/tasklist/WEB-INF/lib;
mkdir temp;
cp wf_client_custom.jar temp/
cd temp;
jar xvf wf_client_custom.jar

3. Open wf_client_config.xml and provide your soa server URL for tagsserverURL
and rootEndPointURL.
4. Update wf_client_custom.jar with the updated wf_client_config.xml. Execute the

following:
cd /tmp/tasklist/WEB-INF/lib/temp;
jar uvf wf_client_custom.jar wf_client_config.xml
5. Copy file wf_client_custom.jar to WEB-INF/lib/. Execute the following:

cp /tmp/tasklist/WEB-INF/lib/temp/wf_client_custom.jar ../
cd /tmp/tasklist/WEB-INF/lib/;
rm -rf temp;
6. Update custom.webcenter.spaces.war with updated file

WEB-INF/lib/wf_client_custom.jar and all other files that were part of
custom.webcenter.spaces.war. After executing these commands, there is updated
custom.webcenter.spaces.war at /tmp/:
cd /tmp/tasklist;
jar uvf custom.webcenter.spaces.war WEB-INF/lib/wf_client_custom.jar
7. To back up, execute the following:

/slot/ems4372/appmgr/oracle/middleware/Oracle_WC1/webcenter/
modules/oracle.webcenter.spaces_11.1.1/
custom.webcenter.spaces.war
cd /slot/ems4372/appmgr/oracle/middleware/Oracle_WC1/
webcenter/modules/oracle.webcenter.spaces_11.1.1/
cp custom.webcenter.spaces.war custom.webcenter.spaces.war.orig
8. Copy custom.webcenter.spaces.war. Execute the following:

/slot/ems4372/appmgr/oracle/middleware/Oracle_WC1/webcenter/
cd /slot/ems4372/appmgr/oracle/middleware/Oracle_WC1/webcenter/
cp /tmp/custom.webcenter.spaces.war
Update Deployments
1. Navigate to http://rws60212rems:7004/console/using weblogic/welcome1 and click
Lock & Edit.
2. Click Deployments, select webcenter, click Stop, select option Force Stop Now,
and answer Yes to the confirmation question.
3. Reselect webcenter, click Delete, and answer Yes to the confirmation question.
4. Select custom.webcenter.spaces, click Update, click Next, click Next, and click
Finish.
5. Click Install. Select path as follows:

/slot/ems4372/appmgr/oracle/middleware/Oracle_WC1/archives/applications, and

file as webcenter.ear
Deploy it on managed server WLS_Spaces.
6. Click Deployments, select webcenter, click Start, select option Start servicing all
requests, and answer Yes to the confirmation question.
Set extendApp to true in setDomain.sh.

1. Open
/slot/ems4372/appmgr/oracle/middleware/user_projects/domains/wc_domain/bin/s
etDomainEnv.sh and add the following:
EXTRA_JAVA_PROPERTIES="-Doracle.webcenter.spaces.extendApp=true
${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
2. Restart Managed Server WLS_Spaces.
Create a New View in Oracle BPM Worklist

1. Navigate to the BPM worklist [http://rws60212rems:8880/integration/worklistapp]
and log in using admin credentials.
2. Click Add [+] icon from section Worklist Views.
3. Select Create View, select name APCC Shared View, select Add to Standard
Views. Navigate to Add Condition drilldown and select State. Click Add [+] icon,
and select Assignees who can share this view.
4. Select Display tab, then select these columns in the left side of the window:
• Title: BPEL process name that you created in the Scenario Manager
• Due Date
• Application Context: BPEL Activity Name
• Identifier: Plan name
• State: Worklist task state--Assigned, Deleted, Suspended
• Category: BPEL Activity Status - In progress, Not Started, Error or Completed
• Created: Date
• Creator: User
5. Click OK.
Test the Tasklist

1. Navigate to WebCenter (for example, http://rws60212rems:8877/webcenter/) and

log in.
2. Create a blank group space, edit page, and click add content. The Catalog opens.
3. Click open on APCC Custom Folder, move to Task List, and click Add.
4. Verify that it is added to the Tasklist.
Deploy and Configure the Group Space Template

1. Get file msc_apcc_gs_template.ear from ARU.
2. Copy it to your local directory.
3. Open the WebCenter Spaces URL.

Example
http://rws60212rems.us.oracle.com:8877/webcenter
4. Log in to the WebCenter Spaces URL.
5. Navigate to the WebCenter Administrator.
6. Click the Manage Group Spaces and Group Space Templates. Manage Group
Spaces opens.
7. Click the Templates subtab. The Manage Group Space Templates window opens.
8. Click the Import option. The Import Archive Name window opens.
9. Select Option Archive Located on Local File System, specify local directory as the
EAR file location, and click Import. This completes the group space template
import.
10. Log in to the WebCenter Spaces URL.
11. Click Group Spaces.
12. Click Create Group Space.
13. Enter Group Space Name, enter Description, and select group space template name.
14. Click Create. This creates a group space with group space name given.
15. Click Group Space Name tab.
16. Navigate to Setting > Custom Attributes.

17. Select custom attribute FND_OBIEE_URL.
18. Navigate to Actions, and select Edit Attribute.
19. Enter your OBIEE URL.
Example:
http://adc60069fems.us.oracle.com:9799/
20. Click OK.
21. Select custom attribute APPS_SERVLET_AGENT.
23. Enter Apps Servlet URL.
Example:
http://rws60147rems.us.oracle.com:8034/OA_HTML
24. Click OK.
25. Select custom attribute MSC_SCN_SERVICE_ENDPOINT.
27. Enter the BPM Worklist URL.
Example:
http://rws60018rems.us.oracle.com:8880
28. Click OK.
29. Navigate to the home page, click Edit Page, delete the worklist component from top
of the page, and place APCC Custom Folder > Tasklist at the same location. This
replaces a worklist component with a tasklist component.
30. Navigate to the Setting tab, and then navigate to the General tab.
31. Click Save as Group Space Template. The Save as Group Space Template window
opens.
32. Enter Template Name, enter Description, and check Publish.
33. Click Save. This creates the template.
34. Enter the template name in MSC: APCC Webcenter Group Space Template Profile.

Deploy and Configure Application Links [Optional]
This configures E-Business Suite functions as external applications in the WebCenter
Personal Sidebar; the user can navigate to E-Business Suite from WebCenter.
Group space also contains application links with context-like group space names, but
application Links defined in WebCenter Personal Sidebar do not pass context
information to E-Business Suite applications.
1. Open enterprise manager [http://host:port/em] and log in as administrator
[weblogic/welcome1].
2. Expand Webcenter, expand Webcenter spaces, select webcenter (WLS Spaces),

right-click Settings, and click Service Configuration.
3. Select External Applications.
4. Click the Add icon, input values for these entities, and click OK.
Some of these are sample values:
• Application Name: Scenarios
• Display Name: Scenarios
• Enable Automatic Login: Selected
• Login URL:
http://host:port/OA_HTML/MscObieeSrvlt?ParamType=Name&FROM_NODE=W
C&TO_NODE=SCN
• Find the values for the host and port from the value of profile option Apps
Servlet Agent.
• HTML User ID Field Name: usernameField
• HTML User Password Field Name: passwordField
• Authentication Method: Post
• Enable Shared Credentials: Selected
• User Name: TEST
• Password: TEST

• Application Name: Supply Chain Analyst Dashboard
• Display Name: Supply Chain Analyst Dashboard
• Login URL:
C&TO_NODE=SCA
Find the values for the host and port from the value of profile option Apps
Servlet Agent.
• User Name: TEST
• Password: TEST
• Application Name: Sales and Operations Planning Analyst Dashboard
• Display Name: Sales and Operations Planning Analyst Dashboard
• Login URL:
C&TO_NODE=SOP
Servlet Agent.

• User Name: TEST
• Password: TEST
• Application Name: Simulation Planner Workbench
• Display Name: Simulation Planner Workbench
• Login URL:
C&TO_NODE=rp
Servlet Agent.
• User Name: TEST
• Password: TEST
• Application Name: Demand Management Workbench
• Display Name: Demand Management Workbench
• Login URL:
C&TO_NODE=DEMANTRA
Servlet Agent.

• User Name: TEST
• Password: TEST
• Application Name: BPM Worklist
• Display Name: BPM Worklist
• Login URL:
http://host:port/integration/worklistapp
Find the values for the host and port from the value of profile option MSC: Scn
Service End Point.
• User Name: TEST
• Password: TEST
10. Open WebCenter spaces [http://host:port/webcenter] and log in as administrator

[weblogic/welcome1].
11. Navigate to the top menu, select the Administration, and click Integrate Existing
Applications.
12. Expand Applications Node, select Scenarios, and click Edit. For each application,
change Open Behavior to the Webcenter tab, and click OK.

Deploy and Configure SOA BPEL Flows
To deploy and configure SOA BPEL flows, refer to My Oracle Support Document
1070257.1.
Set Up Profile Options

Perform the procedure below to set up your profile options.
1. Navigate to your E-Business Suite environment.
2. Select responsibility System Administrator.
3. Navigate to Profiles > System.
4. Verify or set values for the profile options as displayed in the table below.
Profile Options
Number / System Profile User Profile Valid Values / Comments

Owner Name Name Set To
1 MSC_WC_ENA MSC: APCC Yes/No -

BLED Webcenter
Enabled
2 MSC_WC_SPA MSC: APCC Viewer Or Members added

CES_MEMBER Webcenter Participant to the
ROLE Spaces Member webcenter
Role group space can
be either
viewers or
participants.
3 MSC_WC_SPA MSC: APCC Webcenter Example

CES_TEMPLAT Webcenter Group Space
Basic
E Group Space Template Name
Template
4 MSC_WC_SPA MSC: APCC Recipient Key Example

CES_RECIPIEN Webcenter Alias
Producer
TKEYALIAS Spaces
Recipient Key
Alias

5 MSC_WC_SPA MSC: APCC Saml issuer Example

CES_SAMLISS Webcenter name of
www.oracle.co
UERNAME Spaces Saml Webcenter
m
Issuer Name
6 MSC_WC_SPA MSC: APCC Webcenter Example

CES_PORT Webcenter Spaces
8877
Spaces Port managed server
Port
7 MSC_WC_URL MSC: APCC Webcenter URL Example

Webcenter URL http://rws60
018rems.us.o
racle.com/we
bcenter/wcAu
thentication
/?login=true
&success_url
=/spaces
Replace your
host and keep
the other things
same. Then, you
skip the
Webcenter
welcome/login
screen when
navigating from
e-Business Suite
to Webcenter.
8 MSC_SCN_SER MSC: BPEL End WebLogic Soa Example

VICE_ENDPOI Point URI server url http://rws60
NT 212resm.us.o
racle.com:88
80
8880 is the
soa_server1
port number.
9 MSC_SCN_BPE MSC: BPEL soa-infra For example,

L_DOMAIN Domain Name soa-infra.

10 MSC_WS_WEB MSC: APCC Oracle BPM Example

LOGIC_USERN WebLogic worklist admin
weblogic_admi
AME Username user
n
This user
should be
admin for OID
and Webcenter.
11 MSC_WS_WEB MSC: APCC Oracle BPM Example

LOGIC_PASSW WebLogic worklist admin
welcome1
ORD Password password.
12 MSC_WC_WEB MSC: APCC WebLogic Example

LOGIC_USERN WebLogic admin user
weblogic
AME Console
Username This user
should be the
admin user for
Weblogic.
13 MSC_WC_WEB MSC: APCC Set it to Example

LOGIC_PASSW WebLogic WebLogic
welcome1
ORD Console admin
Password password.
Compile MscWCRedirect.jsp
Perform the procedure below to compile the MscWCRedirect.jsp file.
1. Log in to the middle tier where $APPL_TOP resides as an appmgr user
2. Execute the following command:

cd $FND_TOP/patch/115/bin;
3. Compile and flush as follows:

perl ojspCompile.pl --compile -s 'MscWCRedirect.jsp' –flush
4. Restart the middle tier as follows:

cd $ADMIN_SCRIPTS_HOME;
adoacorectl.sh stop;
adoacorectl.sh start;
adoacorectl.sh status;
Run the Planning Process Activities Concurrent Process

Perform the procedure below to run the Planning Process Activities concurrent process.
1. Click Deployed Composite. Verify that there is a green dot before each flow name
and that there is a green up arrow in each status. If there is not, undeploy the flow,
restart the server, deploy the flow, and check it again.
2. Select responsibility Advanced Planning Scenario Manager.
3. Run concurrent process Planning Process Activities concurrent process. This

populates the Oracle 11g BPEL flows into the MSC tables.
Change the WebCenter Application Name

Perform the procedure below to change the WebCenter application name.
1. Log in to WebCenter using administrator.
2. Click the Administration link at the top of the page.
3. Select the General tab.
4. Change Application Name to 'Value Chain Planning".
5. Click Apply.

3
Advanced Supply Chain Planning

• Performing Pre-Configuration Setup
• Performing Configuration
• Upgrading ASCP
• Troubleshooting
Performing Pre-Configuration Setup

This section describes pre-configuration requirements for Oracle ASCP Usability
enhancements. The tasks mentioned below need to be completed after applying the
patch and before starting the installation.
1. Ensure that WebLogic 11gR1 (WebLogic Server 10.3.6 with ADF 11.1.1.6.0 libraries)
is installed.
2. Following profiles should be set up in EBS at site level (the EBS instance which the
data source points to):
User Profile Name: MSC: ASCP Planning URL
<Internal Profile Name>: MSC_ASCP_WEBLOGIC_URL
Example:
http://domain_name:port_number
Note: The port number provided in the profile value should be

same as the port number for the ASCP domain, managed server
that is defined in Creating the ASCP Managed Server, page 3-11.
Example:
http://rws60144rems.us.oracle.com:6087
Advanced Supply Chain Planning 3-1

3. After applying the patch, copy $MSC_TOP/patch/115/ear/PlanningUIEar.zip file
from the EBS server to a directory on the WebLogic server.
4. Create a folder named "applications" on the host machine where WebLogic is

installed. This folder is referenced only as "applications" in this document.
Example:
/slot/ems1392/oracle/mwhome/user_projects/domain/fmw_domain/applications
5. Copy the ZIP file to the folder applications.
6. Extract the ZIP file in the same folder. The unzipped file contains PlanningUI.ear
file.
The .ear files will be selected from this location during deployment.
For information on configuration and deployment, refer to the following:
• Creating the JDBC Data Source, page 3-15
• Deploying and Starting the Planning Application, page 3-23
Performing Configuration
This section includes information about the following ASCP configuration tasks:
1. Creating the ASCP Domain and Admin Server, page 3-2
2. Creating the ASCP Managed Server, page 3-11
3. Creating the JDBC Data Source, page 3-15
4. Setting Up MDS Repository, page 3-21
5. Starting the Admin Server and Managed Server, page 3-23
6. Deploying and Starting the Planning Application, page 3-23
Creating the ASCP Domain and Admin Server

Note: If you currently have a working WebLogic Server (WLS) and
domain, this step is optional. You can proceed to Creating the ASCP
Managed Server, page 3-11.
Install WebLogic Server (WLS) 10.3.6, and configure the domain with the Oracle JRF
option.

On the installed WLS, create a new WLS domain (for example, ascpdomain), and a new
admin server (for example, AdminServer) in this domain.
Perform the following procedure to create the ASCP domain.
1. Go to <WLS_HOME>/common/bin folder.
Example:
cd <installation path>/wlserver_10.3/common/bin
2. Run config.sh script.

Example:
./config.sh
The Welcome screen for the Oracle WebLogic Configuration Wizard appears. This
wizard guides you through the steps to generate a new domain or extend an
existing domain.
3. Select Create a new WebLogic domain and click Next. The Select Domain Source
screen appears.

4. Perform the following:
1. Select Generate a domain configured automatically to support the following
products.
Keep the default settings.
2. Click Next.
The Specify Domain Name and Location screen appears.

5. Provide the Domain name and Domain location, and then click Next.
The domain location is <WLS_HOME>/user_projects/domains where <WLS_HOME> is
the installation path for your WebLogic server.
The Configure Administrator User name and Password screen appears.

6. Enter the User name, User password and Confirm user password of your choice,
and then click Next.
The Configure Server Start Mode and JDK screen appears.

1. Select Production Mode.
2. In JDK Selection region, select Available JDKs and select JRockit SDK 1.6.0_05.
3. Click Next.
The Select Optional Configuration screen appears.

8. Select the Administrative Server option only and click Next.
The Configure the Administration Server screen appears.

1. Input the fields in the following table.
Field Description
Name Enter the name of the admin server.
Listen address The admin server listen port address.

Leave default option of All Local
Addresses.
Listen port Enter the server listen port number.

Check the availability of the number
before entering a value.
SSL listen port Enter the SSL listen port number. Check
the availability of the number before
entering a value.
2. Select the SSL enabled option.
3. Click Next.

The Configuration Summary screen appears.
10. Review the details. If you want to modify any settings, use the Previous button to
return to the appropriate screen. If no changes are required, click Create.
The Creating Domain screen appears and displays the system progress.

11. When the domain is complete, click Done.
The wizard closes.
12. Go to the ASCP domain directory.
Example:
$ cd
/slot/ems3424/appmgr/WLS/user_projects/domains/ascpdomain/
13. In the ASCP domain directory (for example, ascpdomain), create the output/ and
log/ directories as follows:
$ mkdir - m 777 output/
$ mkdir -m 777 log/
Creating the ASCP Managed Server

This section provides procedures for creating the managed server and applying JRF.
1. Open a Web browser and type in the URL/address in the following format:
http://<Machine_Name>:<Port_No>/console
<Machine_Name> represents the host name of the machine on which the WebLogic
server is running (for example, rws3220163.us.oracle.com) and <Port_No>is the
Admin server Listen port number specified when the ASCP domain was created.

Example:
http://rws3220163.us.oracle.com:7901/console
The Oracle WebLogic Administration Console appears.
2. Navigate to Servers in the Domain Structure region.

Example Navigation Path:
base_domain > Environment > Servers
3. Click New to create a new server.

Field Description
Server Name Enter the name of the ASCP managed

server (for example,
ASCPManagedServer).

Field Description
Server Listen address Enter the listen address for manager

server.
Server Listen port Enter the server listen port number.
2. Define the server cluster options as needed.
3. Click Next.
4. Select the SSL Enabled option to enter the SSL port number.
5. Enter the Secured Socket Listen port in the SSL Port field.
6. Click Finish.
The Configuration tab displays the new managed server.
5. Apply JRF on Managed Server using Enterprise Manger (EM).

1. Open a Web browser and type in the URL/address in the following format:
http://<Machine_Name>:<Port_No>/em
<Machine_Name> represents the host name of the machine on which the
WebLogic server is running (for example, rws3220163.us.oracle.com) and
<Port_No>is the Admin server Listen port number specified when the ASCP
domain was created.
Example:

http:// rws3220163.us.oracle.com:7901/em
2. Navigate to WebLogic domain, your domain name, and select the Managed
Server.
The managed server information appears on the right side of the page.
3. Click Apply JRF Template.

When successfully applied, a confirmation message appears at the top of the
page.
The JRF Template can also be applied from the command line using the
following procedure:
Note: Skip the command line procedures if JRF was already

applied using Enterprise Manger (EM).
1. Run wlst.sh from Middleware bin directory.

cd $MIDDLEWARE_HOME\oracle_common\common\bin
./wlst.sh
2. Authenticate the connection.

Example:
connect('weblogic','welcome1',
'rws3220040.us.oracle.com:7004')
Substitute your WLS username and password in the example above.
Provide the host and port where the WLS Admin Server is running for the
ASCP domain.
3. Apply JRF.
Example:
applyJRF('ASCPManagedServer',
'/slot/ems6479/appmgr/Oracle111160/Middleware/user_proj
ects/domains/base_domain', true)
Use your Managed Server name and the path for the ASCP domain
directory example above.
Creating the JDBC Data Source

Perform the procedure below to create the JDBC data source (for example,
ApplicationDB).
1. Log in to the WebLogic administration console, as described in Creating the ASCP
Managed Servers, page 3-11.
2. Click Lock & Edit from the Change Center region, located on the top left of the
page, if applicable.
3. Navigate to Data Sources under the Domain Structure region.

Example Navigation:
base_domain > Services > JDBC > Data Sources
4. Click New.
The Create a New JDBC Data Source page appears.

Field Description
Name Enter the name of the JDBC data source

(for example, ApplicationDB).
JNDI Name Enter the name you want to assign to

your new JDBC Data Source (for example,
jdbc/ApplicationDBDS).
2. Select Oracle from the Database Type list.
3. Click Next.
The JDBC Data Source Properties page appears.

4. Select the Oracle's Driver (Thin) for instance connections, Version 9.0.1 and
later from the Database Driver list.
5. Click Next.
The Transaction Options page appears.
6. Click Next to accept the default settings displayed.

The Connection Properties page appears.

7. Input the database connection detail fields in the following table.
Field Description
Database Name Enter the database name (for example,

ma1yd213).
Host Name Enter the host name or IP address of the

database server (for example,
rws60052rems.us.oracle.com).
Port Enter the port on the database server used

to connect to the database (for example,
1572).
Database User Name Enter the database account user name

you want to use to create database
connections (for example, apps).
Password Enter the database account password you

want to use to create the database
connections.

Field Description
Confirm Password Retype your password.
8. Click Next.
The Tests Database Connection page appears.
9. Click Test Configuration.

If the JDBC is set up correctly, then the following message appears at the top of
the page:
Connection test succeeded.
10. Click Next.
The Select Targets page appears.

11. Select the ASCP managed server you created (for example,
ASCPManagedServer), and click Finish.
12. Select the new JDBC data source (for example, ApplicationDB), and click the
Configuration tab.
13. Select Connection Pool subtab and set Maximum Capacity field to 150. The
default value for the field is 15.

14. Scroll down the page, and click the Advanced link. The Advanced options
appear.
15. Select Test Connections on Reserve and click Save.
16. Click Activate Changes from the Change Center region, located on the top left
of the page. This screen only appears if you were in Lock & Edit mode, which
you selected at the beginning of this procedure.
At this point, you have successfully set up the JDBC Resource.
Setting Up MDS Repository

Performing the following procedure to set up the MDS repository.

1. Return to the UNIX console and go to the ASCP domain home (the path where
ASCP domain is installed).
2. Create a new directory "mds": (<ASCP_Domain_Home>/servers/

<ASCPManagedServer>/mds).
Example:
<installation_path>
/user_projects/domains/uitestdomain/servers/AdminServer/mds
Creating a File Persistence Store

To create a file persistence store in WebLogic Server Administration Console, perform
the following procedure:
1. Click Lock & Edit button from the Change Center region to change the domain
configuration, if applicable.
2. Click Persistent Stores from the Domain Structure region (or you can navigate to
Services >Persistent Stores from the Domain Structure region).
The Summary of Persistent Store page appears.
3. Click New, and select Create File Store.

1. Enter mds-ascp-repos in the Name field.
2. Select ASCPManagedServer from the Target list.
3. Enter <ASCP_Domain_Home>/servers/<ASCPManagedServer>/mds in the

Directory path field.
4. Click OK.
5. Click Activate Changes from the Change Center region, located in top left of the
page.

Starting the Admin Server and Managed Server
Perform the command line procedure below to start the ASCP Admin Server and ASCP
Managed Server.
1. Change directories to the <DOMAIN_HOME>/bin location.
Syntax:
cd $<DOMAIN_HOME>/bin
Example:
/slot/ems6479/appmgr/Oracle111160/Middleware/user_projects/domains/base_dom
ain/bin
2. Start the AdminServer.

Example Syntax:
nohup ./startWebLogic.sh
-Dweblogic.management.username=weblogic
-Dweblogic.management.password=welcome1> weblogic.out &
Substitute your Hostname, Managed server post, Username and Password in the
example command above.
3. Start the ASCPManagedServer.

Example Syntax:
nohup ./startManagedWebLogic.sh "ASCPManagedServer"
"http://rws3220163.us.oracle.com:7001"
-Dweblogic.management.username=weblogic
-Dweblogic.management.password=welcome1
>ASCPManagedServer.out &
Substitute your Hostname, Managed server post, Username and Password in the
example command above.
Deploying and Starting the Planning Application

This procedure consists of the following tasks:
1. Copying and extracting the ZIP files.
2. Deploying the Planning Application.
Copying and Extracting the ZIP Files

Perform the following procedure to copy and extract the ZIP files.
After applying the VCP patch, the PlanningUIEar zip file has to be copied from EBS
APPL_TOP to a directory where WebLogic is installed. The new application will have
to be deployed to the ASCPManaged server.

1. Create a folder with name "applications" in a directory on the host machine where
WebLogic is installed. This folder is referred to as "applications".
Example:
2. Copy the following ZIP files to the folder "applications".

Example:
cp $MSC_TOP/patch/115/ear/PlanningUIEar.zip <applications>
3. Extract the ZIP files to the same folder.

The PlanningUI.ear file is selected from this location for deployment.
Deploying the Planning Application

Perform the following procedure to deploy the Planning Application:
1. In order to deploy the Planning Application, open the WebLogic UI for ASCP
Domain according to the procedure mentioned in Starting the Admin Server and
2. Select Deployments in the Domain Structure region.

The Summary of Deployments - Control tab appears.
3. Select Install to install the new Planning Application.

The Install Application Assistant - Locate deployment to install and prepare for
deployment page appears.
4. In the Path field, enter the <applications> directory path.

Example:
5. Select PlanningUI.ear and click Next.

The Select deployment targets page appears.
6. From the list of Available targets for PlanningUI, select ASCPManagedServer and
click Finish.
When the deployment is complete, the "PlanningUI" deployment is visible.
7. Verify your deployment.

Select Deployments from the Domain Structure region, locate PlanningUI in
Deployments table. PlanningUI deployment should be in "Active" state.

Upgrading ASCP
Performing an upgrade consists of the following tasks:
1. Copying and extracting the ZIP files.
2. Redeploying the planning application.
Copying and Extracting the ZIP Files

Perform the Copying and Extracting the ZIP Files procedure in Deploying and Starting
the Planning Application, page 3-23.
Redeploying the Planning Application

To redeploy, you must first delete the existing PlanningUI application. Perform the
procedure below to delete the PlanningUI application, then refer to Deploying and
Starting the Planning Application, page 3-23 for instructions on deploying your new
Planning Application.
1. In order to redeploy the Planning application, open the WebLogic UI for the ASCP
Domain according to the procedure mentioned in Starting the Admin Server and
2. Select Deployments in the Domain Structure region.

3. Select the PlanningUI application you want to redeploy and click Stop. Select Force
Stop Now.
4. Click Yes to stop the application.

5. Select the PlanningUI application you want to redeploy and click Delete.
6. Deploy your new Planning Application. Refer to Deploying and Starting the
Planning Application, page 3-23 for instructions.
Troubleshooting
The table below contains information or possible solutions about potential issues or
errors that may occur while attempting to upgrade to the ASCP Usability Enhancement.
Issue Solution
The PlanningUI deployment does not appear Please stop and delete the deployment. Follow
in Active state. steps in Redeploying the Planning
Application, page 3-26.
Deployment errors indicate ADF related error Ensure that the managed server was created
or libraries missing. in a domain which is JRF enabled.

Issue Solution
An error occurs while running applyJRF from Type help('all') and make sure applyJRF is
command line wlst.sh. available.
Use the following:
$MIDDLEWARE_HOME\oracle_common\co
mmon\bin\wlst.sh

4
Production Scheduling

• Standalone, Non-Integrated Production Scheduling Installations
• Production Scheduling Implementation
• Mandatory Prerequisite Patches
• Post Installation
• Post Installation Settings
• Special Instructions
Standalone, Non-Integrated Production Scheduling Installations

For information on installing Production Scheduling on Microsoft Windows in a
standalone environment that is not integrated with E-Business Suite (EBS), refer to the
Oracle Production Scheduling Installation Guide.
Production Scheduling Implementation

The procedures described in this section are only required if you implement Production
Scheduling with E-Business Suite.
Mandatory Prerequisite Patches

Source Side:
Apply the following patches only if you are using Production Scheduler integrated with
Complex Maintenance Repair Overhaul (cMRO):
• 9413058:R12.EAM.B - EAM patch
• 9138126:R12.EAM.B - EAM patch
Production Scheduling 4-1

Post Installation
In release 12.2, there are two files systems (FS1 and FS2) due to the new online patching
tech stack. If you upgraded Value Chain Planning to 12.2.0 using 12.2.0 Rapid Install,
perform the following procedure after the upgrade is complete:
Note: If you continue upgrade to 12.2.1, these actions are no longer

needed. They are required to upgrade to 12.2.0, but not to 12.2.1 and
higher.
1. Source to the FS2 file system on apps tier, and change directories to $MSC_TOP/bin.
2. Run the following commands:

$perl install_PS.pl
$perl install_SNO.pl
Post Installation Settings

Set the following profile option settings after Production Scheduling is installed:
• Set "MSC: PS/SNO API Version" to 3.7 at Site Level.
• Set "MSC: PS/SNO Data Store Path" to the value of $APPLCSF environment
variable at Site Level. This variable is defined in "APPLSYS.env".
• If Concurrent Tier and Web Tier are on different machines, set "MSC: PS/SNO Use
DB for Integration Data" to "YES".
• If users want to download the xml files to the client machine for debugging
purpose, set "MSC: PS/SNO Download XML Files" to "YES". The default value is
"NO".
• To enable the collection of CMRO Work Order demands when running the VCP
collections process, set "MSC: Collect CMRO Work Order Demand for PS" to "YES".
If you are using a Windows server for Production Scheduling integration, set the system
variables below. This is a one-time mandatory step.
• Set SCP_ROOT_DRIVE to the drive where the Oracle product is installed (for
example, C:).
• Set SCP_MSC_TOP with the MSC_TOP value using forward slash (/).
Example
C:/oracle/VIS/apps/apps_st/appl/msc/12.0.0

• Restart the server to apply your environment variable changes.
• Set "MSC: PS/SNO Data Store Path" using the forward slash (/).
Example
C:/u01/oracle/viscomn/admin
Special Instructions
Review the following when implementing Production Scheduling:
• If Oracle Repetitive Manufacturing Optimization (RMO) option is licensed along
with Production Scheduling application, then the profile option "MSC: PS Enable
CRO Scheduling" must be set to "YES". RMO and CRO are synonymous.
• Uninstall Production Scheduling application from your client machine and reinstall
again through the Workbench. This step ensures that the latest version of
Production Scheduling is applied to client machines.
• Production Scheduling is English only. The client application is deployed with

translations available. Select Tools from the menu bar, select Language, and choose
a language.
• As part of your setup, ensure the Production Scheduler responsibility is assigned to

the appropriate user.
• Ensure that Organization security is enabled for Production Scheduler

responsibility.
• After applying software patch, restart the application server.
Production Scheduling 4-3

5
Strategic Network Optimization

• Standalone, Non-Integrated Strategic Network Optimization Installations
• Strategic Network Optimization Integration
• Mandatory Prerequisite Patches for Oracle Process Manufacturing (OPM) Users
• Post Installation
• Post Installation Settings
• Special Instructions
Standalone, Non-Integrated Strategic Network Optimization Installations

For information on installing Strategic Network Optimization on Microsoft Windows
and UNIX, in a standalone environment that is not integrated with E-Business Suite
(EBS), refer to the Oracle Strategic Network Optimization Installation Guide.
Strategic Network Optimization Integration

The procedures in this section are only required if you implement Strategic Network
Optimization (SNO) with E-Business Suite.
Mandatory Prerequisite Patches for Oracle Process Manufacturing (OPM)

Users
The following patches are required for Oracle Process Manufacturing (OPM) users
when implementing Strategic Network Optimization:
• 9319734:R12.GMP.B (with the following prerequisites)
• 8486861:R12.GMA.B (with the following prerequisites)
Strategic Network Optimization 5-1

• 7587155:R12.INV.B
• 7627262:R12.INV.B
• 7015717:R12.GMP.B
Post Installation
In release 12.2, there are two files systems (FS1 and FS2) due to the new online patching
tech stack. If you upgraded Value Chain Planning to 12.2.0 using 12.2.0 Rapid Install,
perform the following procedure after the upgrade is complete:
Note: If you continue upgrade to 12.2.1, these actions are no longer

needed. They are required to upgrade to 12.2.0, but not to 12.2.1 and
higher.
1. Source to the FS2 file system on apps tier, and change directories to $MSC_TOP/bin.
2. Run the following commands:

$perl install_PS.pl
$perl install_SNO.pl
Post Installation Settings

Set the following Profile option settings after Strategic Network Optimization is
installed:
• Set "MSC: PS/SNO API Version" to 3.7 at Site Level.
• Set "MSC: PS/SNO Data Store Path" to the value of $APPLCSF environment
variable at Site Level. This variable is defined in "APPLSYS.env".
• If Concurrent Tier and Web Tier are on different machines, set "MSC: PS/SNO Use
DB for Integration Data" to "YES" .
• If users want to download the xml files to the client machine for debugging
purpose, set "MSC: PS/SNO Download XML Files" to "YES". The default value is
"NO".
• If users want to publish the output xml files from SNO to the client under
data_store/plan_id path, set "MSC: SNO Publish on Client" to "YES". Setting the
profile option to "NO" helps to improve SNO publish performance. The default
value is "NO".
If you are using a Windows server for SNO integration, set the server system variables

below. This is a one-time mandatory step.
• Set SCP_ROOT_DRIVE to the drive where the Oracle product is installed (for
example, C:).
• Set SCP_MSC_TOP to the MSC_TOP value using forward slash (/).

Example
C:/oracle/VIS/apps/apps_st/appl/msc/12.0.0
• Restart the server to apply your environment variable changes.
• Set "MSC: PS/SNO Data Store Path" using forward slash (/).
Example
C:/u01/oracle/viscomn/admin
Special Instructions
Review the following when implementing Strategic Network Optimization:
• Uninstall Strategic Network Optimization application from your client machine and
reinstall again through the Workbench. This step ensures that the latest version of
Strategic Network Optimization is applied to client machines.
• Strategic Network Optimization is English only. The EBS translations can be

downloaded from My Oracle Support as they become available.
• As part of your setup, ensure the Strategic Planner responsibility is assigned to the
appropriate user.
• Ensure that Organization security is enabled for Strategic Planner responsibility.
• After applying software patch, restart the application server.
Strategic Network Optimization 5-3

6
Service Parts Planning

• Service Parts Planning Installation Updates
Service Parts Planning Installation Updates

There are no Service Parts Planning installation updates for Release 12.2.
Service Parts Planning 6-1

7
Demand Signal Repository

• Demand Signal Repository (DSR) Implementation
• Prerequisites
• Setting Up Oracle Data Integrator (ODI)
• Configuring the Physical Architecture in Topology Manager
• Configuring the Context and Logical Architecture in Topology Manager
• Executing Scenarios
• Setting Up Oracle Business Intelligence Enterprise Edition (OBIEE)
• Setting Up Oracle Business Intelligence Enterprise Translations
• Setting Up the Exception Management Dashboard Feature
• Configuring a Web Service in OBIEE
• Setting Up Web Services
• Setting Up Demand Signal Repository - Demantra Integration
• Setting up Demand Signal Repository - Retail Merchandise System (RMS)
Integration
• Configuring the User Parameters in DSR Lookups
• Creating the Directories Defined in the DDR_R_LKUP_MST Table
• Copying the Class and DTD Files
• Importing the DSR - RMS Project Objects in the ODI Designer
• Configuring the Physical Architecture in Topology Manager
• Configuring the Context and Logical Architecture in Topology Manager
• Copying the EDIDLPRD.dat File
• Executing the Scenario
Demand Signal Repository 7-1

Demand Signal Repository (DSR) Implementation
The following install instructions apply to installing Demand Signal Repository as part
of an E-Business Suite implementation or for upgrading DSR from an earlier release.
Prerequisites
Make sure the following prerequisites are met before installing Demand Signal
Repository:
• Oracle Database 11.2.0.3 must be installed. Please refer to Oracle Database
installation documents.
http://www.oracle.com/pls/db112/portal.portal_db?selected=11&frame=
• Oracle Data Integrator 11.1.1.6 must be installed with both master and work
repositories ID's greater than 300. Please refer to Oracle Data Integrator installation
documents.
http://docs.oracle.com/cd/E23943_01/core.1111/e16453/toc.htm
• Oracle Business Intelligence Enterprise Edition 11.1.1.6 must be installed. Please

refer to Oracle Business Intelligence Enterprise Edition installation documents.
http://docs.oracle.com/cd/E23943_01/bi.1111/e10539/toc.htm
• To use Demand Signal Repository and Retail Merchandising System (RMS)

integration you must have Retail Merchandising System (RMS) version 10.0 or
higher.
• If you are planning to use Demand Signal Repository and Demantra integration,
you must have Demantra version 7.2 or higher.
Setting Up Oracle Data Integrator (ODI)

This section contains the activities required to set up ODI.
Copy the DSR ODI XML Files to a Temporary Folder

Copy the DSR ODI XML files from the APPL_TOP of your environment to a folder that
will be used to import the ODI objects. This folder must be accessible from the ODI
client you will use to perform the import.
DSR ODI XML files are located in the APPL_TOP folders:
• ddr/patch/115/odi/US/master

• ddr/patch/115/odi/US/model
• ddr/patch/115/odi/US/project/DDR
Import the DSR Project Objects in the ODI Designer

Import all XML files with prefixes of FOLD_% from the ODI Studio.
Importing the Folders
1. Select the Designer tab.
2. From the Connect Manager button, select Import > Smart Import.
3. In the file selection box, click the search button, navigate to the folder where the
XML files from ddr/patch/115/odi/US/project/DDR were downloaded, and select
the file to import in the list above.
Leave the response file empty.
4. Click Next.
5. Accept all defaults on the Import Actions screen, and click Next.
6. On the Summary screen, click Finish to import the object.
7. Verify that the folders were imported correctly.
Import all XML files with the prefix of KM_% from the ODI Studio.
Importing the Knowledge Modules
2. From the Connect Manager button, select Import >Smart Import.
4. Click Next.
7. Verify that the knowledge modules were imported correctly.
Import all XML files with the prefix of VAR_% from the ODI Studio.

Importing the Variables
4. Click Next.
7. Verify that the variables were imported correctly.
Importing the DSR Model in the Designer

Perform the following procedure from ODI Studio to import the DSR Model.
XML files from ddr/patch/115/odi/US/project/model were downloaded, and select
the MFOL_DDR.xml.
4. Click Next.
7. Verify that the model was imported correctly.
Importing the Topology Objects

Import the topology objects in the following order:
1. LSC_DDR_RMS_XML_RETLDLPRD.xml
2. LSC_DDR_TDLINX_FILE.xml

3. LSC_DDR_ORACLE_DDR.xml
4. LSC_DDR_ORACLE_APPS.xml
5. CONN_DDR_RMS_XML_DATASERVER.xml
6. CONN_DDR_TDLINX_FILE.xml
7. CONN_DDR_ORACLE_DATASERVER.xml
8. CONT_DDR_CONTEXT.xml
Perform the following procedure from ODI Studio to import the topology objects.
1. Select the Topology tab.
XML files from ddr/patch/115/odi/US/master were downloaded, and select the file
to import in the order above.
4. Click Next.
7. Verify that all the objects were imported correctly.
Configuring the Physical Architecture in Topology Manager

This section provides procedures for configuring the Oracle dataserver and TDLINX.
Configuring the Oracle Dataserver

Perform the following procedure to configure Oracle dataserver.
1. On the Physical Architecture tab under Oracle, open the "
DDR_ORACLE_DATASERVER" object.
2. On the JDBC subtab, change the JDBC URL to point to the DSR database.
3. On the Definition subtab, change the password for the apps user.
4. Save the changes.

5. Click Test Connection and make sure the connection is successful.
Configuring TDLINX
Perform the following procedure to configure TDLINX.
1. On the Physical Architecture tab under File, expand the "DDR_TDLINX_FILE"
object and open the DDR_TDLINX_FILE.<FILE DIRECTORY> object.
2. On the Definition subtab, change the Directory (Schema) and Directory (Work
Schema) to point to the location where the TDLINX file will reside on the server.
Only provide the directory path; do not include the file name in the path.
3. Save the changes.

Configuring the Context and Logical Architecture in Topology Manager
Perform the following procedure to configure the context and logical architecture in
Topology Manager.
On the Contexts tab, verify the following on the Schemas subtab for the "
"DDR_CONTEXT":
• Logical Schema "DDR_ORACLE_APPS" = "DDR_ORACLE_DATASERVER.APPS"
Physical Schema
• Logical Schema "DDR_ORACLE_DDR" = "DDR_ORACLE_DATASERVER.DDR"

Physical Schema
• Logical Schema "DDR_TDLINX_FILE" = "DDR_TDLINX_FILE.<FILE DIRECTORY>

Physical Schema

Executing Scenarios
Perform the following procedure to execute scenarios.
1. Right-click the scenario object and select Execute.
2. For any execution parameter you wish to change, uncheck the "Last Value" check
box, and then enter a new value in the Value box. You must exit this text field for
the value to save your change.
3. Click OK.
4. Monitor the execution on the Operator tab.
Setting Up Oracle Business Intelligence Enterprise Edition (OBIEE)

This section provides the following instructions:
• Setting Up the Oracle Business Intelligence Enterprise Edition Server
• Setting Up the Oracle Business Intelligence Enterprise Edition Presentation Services
• Configuring the Oracle Business Intelligence Enterprise Edition Infrastructure
Setting Up the Oracle Business Intelligence Enterprise Edition Server

Files ddrpd.zip and ddrwebcat.zip contain the following files for use with the Oracle

Business Intelligence Suite Enterprise Edition 11.1.1.6:
• DSR_Reports.rpd - This is the Oracle Demand Signal Repository product repository
file; this file is contained in ddrrpd.zip.
• DSR_Reports - This directory is the Oracle Demand Signal Repository product Web
catalog; this file is contained in ddrwebcat.zip.
1. Copy these ZIP files (ddrrpd.zip, ddrwebcat.zip) from the obiee

(APPL_TOP/ddr/patch/115/obiee) directory.
2. Unzip ddrrpd.zip to display DSR_Reports.rpd.
3. Open the DSR_Reports.rpd file in Oracle Business Administration Tool using

Administrator1 as the password.
4. In the physical layer, change the username/password for the database connection in
DDR connection Pool.
5. Add entry for the database in the correct TNSNAMES.ora file.
Setting Up the Oracle Business Intelligence Enterprise Edition Presentation Services

Perform the following procedure to set up the Oracle Business Intelligence Enterprise
Edition Presentation Services.
1. Change the directory to the catalog directory for the Oracle Business Intelligence
Enterprise Edition Presentation server. Typically
$OBIEE_HOME/instances/instance1/bifoundation/OracleBIPresentationServicesCo
mponent/coreapplication_obips1.
2. Rename or delete the existing catalog directory.
3. Unzip ddrwebcat.zip to get DSR_Reports catalog directory.
Configuring the Oracle Business Intelligence Enterprise Edition Infrastructure

Perform the following procedure to configure the Oracle Business Intelligence
Enterprise Edition Infrastructure.
1. Open the Enterprise Manager. The default URL is http://localhost:7001/em.
2. Expand the Business Intelligence Node and select the application setup in the obiee
installation. The default is coreapplication.
3. Open the Deployment Tab and then select the Repository subtab.
4. Click the Lock and Edit Configuration button.

5. In the Upload BI Server Repository section, click the browse button.
6. Select the DSR_Reports.rpd that you configured with the Administrator tool to
connect to your database.
7. Enter Administrator1 in both password fields.
8. In the BI Presentation Catalog section, edit the path to include the DSR_Reports
directory that was created by unzipping the ddrwebcat.zip.
The path appears similar to the example below:
$ORACLE_INSTANCE/bifoundation/OracleBIPresentationServicesComponent/$C
OMPONENT_NAME/catalog/DSR_Reports
9. Click the Apply button.
10. Click the Activate Changes button.
11. Click the Restart Services to Activate Changes button. The Overview tab appears.
12. On the Overview tab, click the Restart button to restart the services to complete the
configuration.
Setting Up Oracle Business Intelligence Enterprise Translations

Perform this setup only if you are planning to use translated OBIEE UI. This process
uses the "transx" utility that is part of the Oracle DB install.
1. Configure Transx using the instructions provided in the links below:
• http://docs.oracle.com/cd/E11882_01/appdev.112/e23582/adx_j_transx.htm#AD
XDK1200
• http://docs.oracle.com/cd/E11882_01/appdev.112/e23582/adx_j_gs.htm#CHDD
HEIJ
The OBIEE translated files are shipped under APPL_TOP/ddr/patch/115/obiee

directory and are named as ddr_obiee_<language id>.zip. For example,
ddr_obiee_fr.zip.
2. Unzip the language ZIP file to be used to a local drive (for example c:\ drive). The
DLF files are extracted into the C:\ddr\OracleBI\Repository directory.
3. Import the files into the DB by executing the following transx command:
transx "hostname:port:sid" username password filename
For example, to load the Spanish translation version you use the following:

c:\transx rws60147rems:1524:mz1dv220 apps apps ddr_es.dlf
4. Verify that the seed data is uploaded correctly in DDR_TRANSLATED_MESSAGE

by using the following query:
SELECT Count(*)
FROM DDR_TRANSLATED_MESSAGE
GROUP BY lang_id='<language id>'
5. Copy the file sharedcaptions.xml from ddr\OracleBIData\l_<language id>\ into

$OBIEE_HOME\instances/obieedb/bifoundation/OracleBIPresentationServicesCom
ponent/coreapplication_obips1/msgdb/l_<language id>\captions. If the directory
"l_<language id> is not there, first create subdirectory l_<language id>\captions
under
$OBIEE_HOME\instances/obieedb/bifoundation/OracleBIPresentationServicesCom
ponent/coreapplication_obips1/msgdb directory.
6. Restart the BI servers to verify the translation.
7. To use the translated UI, select an appropriate language and then enter user
id/password when you log in to Presentation Service.
Setting Up the Exception Management Dashboard Feature

Perform the set up described in this section only if you plan to use the exception
management dashboard feature. Setup steps assume the use of bundled WebLogic
server.
1. Get the following EAR file:
APPL_TOP/ddr/patch/115/ear/DDRExceptionHandler.ear
2. Log in to Admin Console.
3. After logging in, navigate to Services > Data Sources.

4. Click Lock & Edit and New > Generic Data Source.
5. Enter the following information:

• Name: DDRDS
• JNDI Name: jdbc/DDRDS
Enter the other connection details.
6. Select the targets for this connection.

7. Click Finish to create the connection, and then click the Activate Changes button.
8. Navigate to Deployments > Install.
9. Next, either pick up the EAR file from the server file location, or if you have saved
the EAR file in your local, click "Upload your file" and choose the EAR file.
10. Assign the Targeting style of "Install as an Application" and choose the target server
to deploy. A default name appears.
11. Click Finish.
12. Click Activate Changes.
13. Expand the deployed app and click the Web Service Name.
14. In this settings page, click the expand icon next to the Web Service Name.
15. Right-click on the WSDL link and copy it. This is required in the next step.

Configuring a Web Service in OBIEE
This section contains information on the followings procedures:
• Adding an action
• Adding a new agent
Adding an Action
Perform the following to add an action.
1. Select the New button and click Action.
2. Select Invoke a Web Service.

The Web Service Operation dialog appears

3. Paste WSDL link copied from the last step of "Setting Up the Exception
Management Dashboard Feature", select the HandleExceptions, and click OK.
The parameter configuration screen appears.
4. Enter the following Prompt values:

• Arg0 = Report
• Arg1 = Exception Type
• Arg2 = Exception Source Code
• Arg3 = Date Offset
• Arg4 = User
Select Session Variable and Enter USER. Select Hidden and Fixed options.
• Arg5 = Debug On
Select Hidden and Fixed options.
• Arg6 = Debug File Location

• Arg7 = Debug Log Level

5. Click Save Action, and select the location and Name for the action
Adding a New Agent

Perform the following procedure to add a new agent.
1. Select the New button and click Agent.

2. Navigate to the Delivery Content tab and select the Analysis (Report) that the
Agent will run.
3. On the Actions tab, in the Agent Condition True or No Condition Exists box, select
the Add existing action button, and select the action you just added to configure it
for this agent.

4. Enter the following values:
• Report - Select XML from drop down and select Delivery Content.
• Exception Type - Select the Exception type that you are running with this agent.
• Exception Source Code - Select the Exception source code that you are running
with this agent.
• Date Offset - Select or enter number of days to go back and delete previous
Exceptions.
5. Click OK and save the agent.
Setting Up Web Services

Demand Signal Repository provides a set of Web services that can be optionally

deployed. Implementers can use these Web services to automate their processes or
perform integration with third party systems.
The following procedure assume you are using the bundled WebLogic server.
1. Get the following EAR file:
APPL_TOP/ddr/patch/115/ear/ddrwsfal.ear
2. Log in to Admin Console.
3. After logging in, navigate to Services > Data Sources.
4. Click Lock & Edit, and select New > Generic Data Source.
5. Enter the following:

• Name: DDRDS
• JNDI Name: jdbc/DDRDS
Enter other connection details.
6. Select the targets for this connection.
7. Click Finish to create the connection, and then click the Activate Changes button.
8. Navigate to Deployments > Install.
9. Next, either pick up the EAR file from the server file location, or if you have saved
the EAR file in your local, click "Upload your file" and choose the EAR file.
10. Select "Install as an Application" as the targeting style, and choose the target server
to deploy. A default name appears.
11. Click Finish.
12. Click the Activate Changes button.
Setting Up Demand Signal Repository - Demantra Integration

If you want to use Oracle Demantra Release 7.2 with DSR, apply the script
msddemcrwf3.sql to create the series, integration profiles and workflows required for
the integration.
The SQL file is not executed during patch application. It must be applied manually.
The SQL file location is: $MSD_TOP/patch/115/sql/msddemcrwf3.sql.
Case 1: DSR (APS) and Demantra are on the same database instance.

1. Make sure that the profile 'MSD_DEM: Schema' is set to the correct Demantra
Schema name.
2. Make sure the Demantra installation is not in use for any activity.
3. Apply the SQL File msddemcrwf3.sql in the APPS schema.
4. Restart the Demantra Application Web Server.
5. Create a synonym named 'BIIO_DSR_SALES_DATA' in the APPS schema of the

instance where DSR is installed.
This synonym should point to the table 'BIIO_DSR_SALES_DATA' in the Demantra
Schema. For example, if the Demantra schema name is 'DMTRA_TEMPLATE', then
create the synonym by running the following command in the APPS schema:
CREATE OR REPLACE SYNONYM BIIO_DSR_SALES_DATA FOR
DMTRA_TEMPLATE.BIIO_DSR_SALES_DATA
Case 2: Demantra is on separate database instance.

1. Create the package MSD_DEM_DEMANTRA_UTILITIES in the Demantra schema
by applying the following files:
• $MSD_TOP/patch/115/sql/msddemdus.pls - Package Specification
• $MSD_TOP/patch/115/sql/msddemdub.pls - Package Body
2. Make sure the Demantra installation is not in use for any activity.
3. Apply the SQL File msddemcrwf3.sql in the Demantra schema.
4. Restart the Demantra Application Web Server.
5. Create a synonym named 'BIIO_DSR_SALES_DATA' in the APPS schema of the

instance where DSR is installed. This synonym should point to the table
'BIIO_DSR_SALES_DATA' in the Demantra Schema.
Setting up Demand Signal Repository - Retail Merchandise System (RMS)

Integration
Follow instructions in this section only if you are planning to implement Demand
Signal Repository integration with Retail Merchandising System (RMS).
Copy the DSR RMS Integration XML Files to a Temporary Folder

This topic provides information about copying ODI files and the class and DTD files.
Copying ODI Files

Copy the DSR RMS Integration ODI XML files from the APPL_TOP of your
environment to a folder that will be used to import the ODI objects. This folder must be
accessible from the ODI client you plan to use to perform the import.
DSR RMS Integration ODI XML files are in the following APPL_TOP folders:
• ddr/patch/115/odi/US/master
• ddr/patch/115/odi/US/model
• ddr/patch/115/odi/US/project/DDR_RMS
Copying Class and DTD Files

Copy the ddrrms.zip file from the APPL_TOP of your environment to a temporary
folder and unzip. Location of this zip is ddr/patch/115/odi/US/project/DDR_RMS
The following files are extracted:
• DLPRDFileToXmlConverter.class
• RETLDLPRD.dtd
Using ODI Objects in the RMS Integration

The following ODI objects are used in the RMS integration:
• Topology Objects - These objects are exported from the Topology Manager.
• CONN_DDR_RMS_XML_DATASERVER.xml - Establishes the physical
connection to the .dtd file for the XML format.
• LSC_DDR_RMS_XML_RETLDLPRD.xml - Establishes the logical connection

for the XML file which ties the physical connection and the context together.
• Designer Objects - These objects have scenarios generated then exported from the
Designer.
• FOLD_RETL_to_DSR.xml
• KM_CKM_Oracle.xml
• KM_IKM_SQL_Control_Append.xml
• KM_LKM_SQL_to_Oracle.xml
• VAR_V_DDR_RETL_CLASS_DIR.xml
• VAR_V_DDR_RETL_FAILED_DIR.xml

• VAR_V_DDR_RETL_FM_ADDR.xml
• VAR_V_DDR_RETL_MAIL_SERVER.xml
• VAR_V_DDR_RETL_ORG_CD.xml
• VAR_V_DDR_RETL_SRC_DIR.xml
• VAR_V_DDR_RETL_SRC_FILENAME.xml
• VAR_V_DDR_RETL_SUCCESS_DIR.xml
• VAR_V_DDR_RETL_TO_ADDR.xml
Configuring the User Parameters in DSR Lookups

Configure the following parameters in the DSR Lookup table DDR_R_LKUP_MST.
DDR_R_LKUP_MST Table
The parameters specified below in the LKUP_CD column need to be configured and set
up by the user. Sample values appear in the table below.
MFG_ORG_CD LKUP_TYP_CD LKUP_CD LKUP_NAME LKUP_DESC
-1 SYS_PARAM RETL_DSR_SRC ODI_HOME/retl The directory

_DIR dsr/source where the RMS
EDIDLPRD File
should be kept
for upload to
DSR.
-1 SYS_PARAM RETL_DSR_SRC EDIDLPRD.dat The RMS

_FILENAME EDIDLPRD File
name that needs
to be loaded into
Oracle DSR.
-1 SYS_PARAM RETL_DSR_SUC ODI_HOME/retl The directory

CESS_DIR dsr/sucess where the RMS
EDIDLPRD file
should be
moved after the
successful
upload.

MFG_ORG_CD LKUP_TYP_CD LKUP_CD LKUP_NAME LKUP_DESC
-1 SYS_PARAM RETL_DSR_FAI ODI_HOME/retl The directory

LED_DIR dsr/failed where the RMS
EDIDLPRD File
should be
moved after the
upload fails.
-1 SYS_PARAM RETL_DSR_TO_ nimit.mankodi@ The admin

ADDR oracle.com e-mail address
where the error
or success
notification
should be sent.
-1 SYS_PARAM RETL_DSR_FM_ retl-dsr@integrat The Integrator

ADDR or.com admin e-mail
from which the
error or success
notification
should be sent.
-1 SYS_PARAM RETL_DSR_MAI Mail.oracle.com Mail Server that

L_SERVER will send the
ODI email
notifications.
-1 SYS_PARAM RETL_DSR_CLA ODI_HOME/retl The directory

SS_DIR dsr/source where the
DLPRDFileToX
MLConverter.cla
ss File is located.
Creating the Directories Defined in the DDR_R_LKUP_MST Table

Create the directories that were defined to be the source, success, and failure directories.
Copying the Class and DTD Files

Perform the following procedure to copy the class and DTD files to the appropriate
folders.
1. Copy the class file DLPRDFileToXMLConverter.class from the folder where the ZIP
file was originally downloaded to the directory specified in the

DDR_R_LKUP_MST table.
2. Copy the DTD file RETLDLPRD.dtd from the folder where the ZIP file was
downloaded to the source directory specified in the DDR_R_LKUP_MST table.
Importing the DSR - RMS Project Objects in the ODI Designer

This section provides procedures for importing DSR - RMS project objects using ODI
Designer.
Import the DSR - RMS Project Objects in the ODI Designer

Import all XML files with prefixes of FOLD_% from the ODI Studio.
Importing the Folders
2. From the Connect Manager button, select Import > Smart Import.
3. In the file selection box, click the search button and navigate to the folder where the
XML files from ddr/patch/115/odi/US/project/DDR_RMS were downloaded and
select the file to import in the list above.
4. Click Next.
5. Accept all defaults on the Import Actions screen and click Next.
7. Verify that the folders were imported correctly.
Import all XML files with the prefix of KM_%. from the ODI Studio
Importing the Knowledge Modules
2. From the Connect Manager button select Import >Smart Import.
4. Click Next.

7. Verify that the knowledge modules were imported correctly.
Import all XML files with the prefix of VAR_% from the ODI Studio.
Importing the Variables
4. Click Next.
7. Verify that the Variables were imported correctly.
Importing the Topology Objects

Import the topology objects in the following order:
1. LSC_DDR_RMS_XML_RETLDLPRD.xml
2. CONN_DDR_RMS_XML_DATASERVER.xml
Perform the following procedures from the ODI Studio.

1. Select the Topology tab.
XML files from ddr/patch/115/odi/US/master were downloaded and select the file
to import in the order above.
4. Click Next.

7. Verify that all the objects were imported correctly.
Configuring the Physical Architecture in Topology Manager

Use the following procedure to configure the RMS XML Dataserver.
Configuring the RMS XML Datasever
1. On the Physical Architecture tab under XML, open the "
DDR_RMS_XML_DATASERVER" object.
2. On the JDBC subtab, change the JDBC URL to point to the file RETLDLPRD.dtd in
the source directory created.
3. Save your changes.
4. Click Test Connection and make sure the connection is successful.

Example:
jdbc:snps:xml?d=\\server\rms\source\RETLDLPRD.dtd&s=RETLDLPRD
Configuring the Context and Logical Architecture in Topology Manager

Use the following procedure to configure the context and logical architecture for a
DSR-RMS integration in the Topology Manager.
On the Contexts tab, verify the Schemas tab for the "DDR_CONTEXT".
Logical Schema "DDR_RMS_XML_RETLDLPRD" =

"DDR_RMS_XML_DATASERVER.RETLDLPRD" Physical Schema
Copying the EDIDLPRD.dat File

Copy the EDIDLPRD.dat file to the location as specified in RETL_DSR_SRC_DIR
lookup.
Executing the Scenario

Perform the following procedure to execute the scenario for a DSR-RMS integration.
1. Right-click the LOAD_RETL_ITEMS_TO_DSR_PKG object from the Operator on
the Scenario tab and select Execute.

2. Uncheck the "Last Value" check box and then enter a value for RTL_ORG_CD in the
Value box. You must exit this text field for the value to be saved.
3. Click OK.
4. Select the Sessions List tab to check the status of the execution.

8
Rapid Planning

• Rapid Planning Installation
Rapid Planning Installation

For information on Rapid Planning installation, refer to the following documentation:
• Oracle Rapid Planning Installation Guide
• Oracle Rapid Planning Release Notes on My Oracle Support
Rapid Planning 8-1

9
Other Useful Information

• Troubleshooting
Troubleshooting
This section contains information that may be helpful when installing or
troubleshooting Value Chain Planning.
Issue Description
11g RDBMS Bug Customers using 11g DB, "glibc error" appears
when launching collection. Apply RDBMS
patch 7330434 to resolve this issue.
11g RDBMS Bug Customers using 11g database on their source

instance may experience Drop materialized
view statement error ORA-00060 when profile
"MSC: Source Setup Required" is set to "Yes".
Customers are recommended to apply
RDBMS patch 7175822 to resolve this issue.
Other Useful Information 9-1

Index
creating directories, 7-24

A demand signal repository (DSR)
implementation, 7-2
Advanced Planning Command Center (APCC)
Demand Signal Repository (DSR)
configuring and deploying rpd and webcat
configuring the physical architecture in
file, 2-2
topology manager, 7-5
configuring single sign-on (SSO), 2-9
DDR_R_LKUP_MST table, 7-24
setting up reports and dashboards, 2-1
demantra integration , 7-20
troubleshooting, 2-11
DSR - RMS project objects, 7-25
using Webcenter for APCC, 2-12
EDIDLPRD.dat, 7-28
using WebCenter for APCC
integration with Retail Merchandise System
configuring WebCenter, 2-12
(RMS), 7-21
prerequisites, 2-12
prerequisites, 7-2
Advanced Supply Chain Planning (ASCP)
setting up exception management dashboard,
performing configuration, 3-2
7-11
performing pre-configuration setup, 3-1
Setting Up ODI, 7-2
troubleshooting, 3-28
Demand Signal Repository (DSR)
upgrading, 3-26
configure the context and logical architecture
in topology manager, 7-7
B
configuring a web service in OBIEE, 7-14
before applying the feature pack, 1-2 setting up Oracle Business Intelligence
Enterprise Edition, 7-8
C demantra
configuring the physical architecture in topology integration with Demand Signal Repository
manager with Demand Signal Repository (DSR), (DSR), 7-20
7-5 post installation tasks, 1-3
context architecture DSR - RMS project objects
configure the context and logical architecture importing, 7-25
in topology manager, 7-7
E
D EDIDLPRD.dat, 7-28
DDR_R_LKUP_MST table executing scenarios, 7-8
Index-1
server variables settings, 4-2
I special instructions, 4-3
standalone, non-integrated Production
installation
Scheduling installations, 4-1
VCP post installation tasks, 1-3
project objects
Installation
importing DSR - RMS project objects, 7-25
Rapid Planning, 8-1
L R
Rapid Planning
logical architecture
Installation, 8-1
in topology manager with Demand Signal
Repository (DSR) , 7-7 S
scenarios
O executing, 7-8
Service Parts Planning (SPP)
OBIEE
installation updates, 6-1
configuring a web service in OBIEE for
setting up ODI, 7-2
Demand Signal Repository (DSR), 7-14
setting up the exception management dashboard
ODI
feature, 7-11
setting up with Demand Signal Repository
Strategic Network Optimization (SNO)
(DSR), 7-2
integration, 5-1
Oracle Business Intelligence Enterprise Edition
mandatory prerequisite patches for Oracle
setting up with Demand Signal Repository
Process Manufacturing (OPM) users, 5-1
(DSR), 7-8
post installation , 5-2
oracle dataserver
post installation settings
configuring with Demand Signal Repository
profile settings, 5-2
(DSR), 7-5
server variables settings, 5-2
Oracle Process Manufacturing (OPM)
special instructions, 5-3
Strategic Network Optimization (SNO)
standalone, non-integrated Strategic Network
mandatory prerequisite patches for
Optimization installations, 5-1
Oracle Process Manufacturing (OPM)
users, 5-1
Oracle Value Chain Planning Installation Guide T
about this document, 1-1 TDLINX
product-specific installation tasks, 1-3 configuring, 7-6
Oracle Value Chain Planning - Oracle tnsnames.ora
Transportation Management (OTM) Integration , configuring the tnsnames.ora file, 2-2
1-4 topology manager
P in topology manager with Demand Signal
Repository (DSR), 7-7
Production Scheduling (PS)
configuring physical architecture with
implementation, 4-1
mandatory prerequisite patches, 4-1
troubleshooting
post installation, 4-2
Advanced Planning Command Center
post installation settings
(APCC), 2-11
profile settings, 4-2
Index-2
Troubleshooting, 9-1
W
Webcenter
using Webcenter for APCC, 2-12
WebCenter
configuring, 2-12
prerequisites, 2-12
web service
adding an action, 7-14
adding a new agent, 7-17
configuring a web service in OBIEE for
web services
setting up, 7-19
Index-3

Oracle® Value Chain Planning: Installation Guide Release 12.2

Uploaded by

Copyright:

Available Formats

Oracle® Value Chain Planning: Installation Guide Release 12.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle® Value Chain Planning: Installation Guide Release 12.2

Uploaded by

Copyright:

Available Formats

Oracle® Value Chain Planning

Part No. E48790-02

Primary Author: Gary O'Hara, Greg Watkins

Contributing Author: Ganesh Iyer, Christine Chen

Send Us Your Comments

1 Oracle Value Chain Planning Installation

2 Advanced Planning Command Center

3 Advanced Supply Chain Planning

5 Strategic Network Optimization

6 Service Parts Planning

7 Demand Signal Repository

9 Other Useful Information

Oracle Value Chain Planning Installation Guide, Release 12.2

Access to Oracle Support

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS"

• This notice may not be removed or altered.

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

This chapter covers the following topics:

About this Document

• Advanced Supply Chain Planning (ASCP)

Oracle Value Chain Planning Installation 1-1

• Demantra Demand Management

• Inventory Optimization (IO)

• Global Order Promising (GOP)

• Collaborative Planning (CP)

• Production Scheduling (PS)

• Strategic Network Optimization (SNO)

• Service Parts Planning (SPP)

• Demand Signal Repository (DSR)

• Rapid Planning (RP)

Before Applying the Feature Pack

1-2 Oracle Value Chain Planning Installation Guide

Product-Specific Installation Tasks

Post Installation Tasks

To do this, perform the following:

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

Oracle Value Chain Planning Installation 1-3

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)

• Upload the XSL files in the Integration Manager.

• Navigate to Business Process Automation > Integration >Integration

• Upload each of the XSL files.

1-4 Oracle Value Chain Planning Installation Guide

• Stylesheet Name : GLogXML v60 to v55 DateTime.xsl

Oracle Value Chain Planning Installation 1-5

This chapter covers the following topics:

Setting Up Advanced Planning Command Center Reports and Dashboards

• Oracle Business Intelligence Enterprise Edition 11 (OBIEE 11.1.1.7.0) must be

• Copy mscrpd.zip and mscwebcat.zip files, which will be placed in

Advanced Planning Command Center 2-1

Note: If file does not exist, create a new one.

Sample File Format:

Configuring and Deploying RPD and Webcat Files

File Name Language File Name Language

apcc-obiee-ar.zip Arabic apcc-obiee-ko.zip Korean

apcc-obiee-cs.zip Czech apcc-obiee-nl.zip Dutch

apcc-obiee-da.zip Danish apcc-obiee-no.zip Norwegian