Oracle Retail Merchandising

Upgrade Guide
Version 1
2184520.1

December 2016
Note: The following is intended to outline our general
product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracles products
remains at the sole discretion of Oracle.
 Contents
Contents............................................................................................................................. ii
1 Revision History........................................................................................................... 1
2 Introduction .................................................................................................................. 3
Oracle Retail Merchandising Operations Management Applications ............................. 3
Overview of the Upgrade Utility ................................................................................... 3
Upgrade Recommendations ........................................................................................... 4
Master Controller ............................................................................................................. 4
3 RMS, RPM, ReIM, and Allocation Upgrade ................................................................ 5
Upgrade Overview ................................................................................................................. 5
Supported Releases for the Upgrade............................................................................. 5
Upgrade Assumptions .................................................................................................... 5
Upgrade Prerequisites ..................................................................................................... 6
Upgrade Requirements ................................................................................................... 6
Upgrade Script Distribution Process ............................................................................. 6
RMS Upgrade .......................................................................................................................... 6
Upgrade Process .............................................................................................................. 6
Translate Data Upgrade not Supported by Upgrade Scripts ..................................... 8
Technical Overview ......................................................................................................... 8
Objects Affected by the Upgrade ................................................................................. 16
RPM Upgrade ........................................................................................................................ 16
Overview of the Upgrade Utility ................................................................................. 16
Upgrade Recommendations ......................................................................................... 16
ReIM Upgrade ....................................................................................................................... 17
Overview of the Upgrade Utility ................................................................................. 17
Upgrade Recommendations ......................................................................................... 17
Allocation Upgrade .............................................................................................................. 18
Overview of the Upgrade Process ............................................................................... 18
Upgrade Recommendations ......................................................................................... 18
Pre Upgrade Steps ......................................................................................................... 18
 1
Revision History
Date Revision

December 2016 Initial release for Release 16.0

RMS, RPM, ReIM, and Allocation Upgrade 1

 2
Introduction
Because the upgrade process varies among Oracle Retail applications, the Oracle Retail
Merchandising Upgrade Guide describes the approach taken for each Oracle Retail
Merchandising application, as well as product-specific upgrade assumptions and
considerations. Actual procedures for the upgrade may be included in corresponding
installation guides.
The table below explains how and when the upgrade occurs for each application, as well
as associated resources.

Product How/When Upgrade Occurs Resource for Additional

Information

Oracle Retail Allocation
Oracle Retail Invoice Matching
Oracle Retail Price Management
Oracle Retail Merchandising System
During installation, with
scripts post installation
During installation, with
scripts post installation.
During installation.
During installation, with
scripts post installation
This Upgrade Guide and the
Oracle Retail Allocation
Installation Guide.
This Upgrade Guide and
the Oracle Retail Invoice
Matching Installation Guide.
This Upgrade Guide and the
Oracle Retail Price
Management Installation
Guide.
Oracle Retail Merchandising
System Installation Guide

Oracle Retail Merchandising Operations Management Applications

This section covers the upgrade of the Oracle Retail Merchandising Operations
Management applications.

Overview of the Upgrade Utility

Some Oracle Retail Merchandising Operations Management applications can be
upgraded from 15.0.x to 16.0 by using an upgrade utility. This upgrade utility modifies
the database to accommodate 16.0 functionality.
The utility also installs any system level data required for the new functionality included
with the 16.0 release. All database changes and data installations preserve existing data.
However, if a client has added custom columns to tables affected by the upgrade utility,
those custom modifications are not preserved.
In addition to the database changes and the necessary data added to the database, the
upgrade also installs PL/SQL packages. If there are PL/SQL packages in the 15.0.1
environment with custom modifications in them, this process does not preserve those
custom modifications.
The upgrade utility is utilized only by the database side of the 15.x applications. All Java
files and shell scripts are to be installed separate from this process.

RMS, RPM, ReIM, and Allocation Upgrade 3

Oracle Retail Merchandising Operations Management Applications

Upgrade Recommendations
Before beginning the upgrade process, back up the database and application
files. Oracle highly recommends you back up all your production data prior to
performing the upgrade.
For some applications, the ORPatch upgrade utility upgrades the database
(tables, triggers, control scripts, procedures, and packages) to Version 16.0.
However, all RIB Objects that are part of Version 16.0 must be installed, as with
previous releases.
The list of tables provided in the Functional Impact sections is provided to give
clients an opportunity to verify whether any of their customizations are affected
(potentially overwritten) by the upgrade utility.
Retailers can verify whether any 16.0 code changes (forms, PL/SQL, and reports)
affect customized code by comparing all modules in the 16.0 code base with what
the client currently has. There are numerous tools available to complete this
comparison, or diff.
RIB should be brought down before running the Upgrade Installer or control
scripts manually.
Create an upgrade plan by becoming familiar with the following:
Product dependencies
Changes to the functionality
Other technical impacts
The upgrade process

Master Controller
The Master Controller is used to upgrade some of the applications discussed in this
document (from 15.0.1 to 16.0). The Master Controller contains the following objects.

Object Contents

DATA_SCRIPT Contains transformation Data Scripts

ERROR Contains error files that are generated
FILES Contains all object script file names
LOG Contains log files
PROCESSED Contains all processed DB script files
UTILITY Contains Utility file
<<CONTROLLER SCRIPT FILE>> - The controller shell script file name
CONTROLLER.CFG The configuration file for Controller

4 Oracle Retail Merchandising

 3
RMS, RPM, ReIM, and Allocation Upgrade
Procedures for performing an upgrade are contained in the installation guide of each
product. For additional instructions for performing an upgrade, see Part II of the Oracle
Retail Merchandising System Installation Guide.

Upgrade Overview
The RMS, RPM, and ReIM upgrade is an upgrade to the database and data used by these
products. The upgrade has two main components:
Database upgrade
This component upgrades the tables, packages, scripts, batch, triggers, and views
of the database.
Data upgrade
This component migrates existing data to the new database structure.
Unlike a patch installation that simply replaces the changed portions of the database; the
upgrade makes changes to the database. For example, if a column has been added to a
database table, instead of overwriting the old table, the new column is appended to the
table that already exists in your database.
The database upgrade is achieved by running scripts either automatically (from the RMS
installer) or manually during the RMS installation process. Each product has its own set
of scripts which have all been combined to run during the RMS installation. See the
Oracle Retail Merchandising System Installation Guide for complete instructions for
performing an upgrade. Installation of the application portion of each product is
documented in each products installation guide.
The data upgrade maps the existing data and migrates that data into the new database
schema.
The RMS installer allows you to select the products you want to upgrade. If at a later
date you want to upgrade a product, you can re-run the RMS installer and select the
check box for the product you want to upgrade.

Supported Releases for the Upgrade

Only a clean (non-customized) version of 15.0.1 can be upgraded to release 16.0.

Upgrade Assumptions
The following assumptions are made regarding the upgrade:
The database is already upgraded to 12c.
The upgrade script is responsible for running the dbc scripts. This is to ensure
that tables are not dropped accidentally (costing requirement).
The scripts have the alter statements and database changes for each table to be
upgraded.
Only 15.0.1 tables that are modified in 16.0 will be upgraded.
The translation data in TL_SHADOWS table will not be upgraded to the new
entity specific translation tables. Most of the translation tables will be empty

Upgrade Guide 5
RMS Upgrade

when the system is upgraded and any translation data will need to be seeded to
the new entity specific translation tables.
The DAS schema will not be upgraded. Review the Oracle Retail Data Access
Schema (DAS) Developer's Guide for Oracle's recommended approach of
upgrading the DAS schema based on each client's replication tooling choice.

Upgrade Prerequisites
Drop the Database User RMS_ASYNC_USER
The RMS notification process was designed to send notification alerts to the user when
asynchronous jobs have either finished successfully or failed. This feature was
introduced in RMS 14.0. It involves enqueuing and dequeuing a separate notification AQ
and works with RMS forms. In 16.0, RAF notification framework is utilized to send such
notifications. RMS_ASYNC_USER owns the RMS_NOTIFICATION_QUEUE and the
related DB objects to provide notification. Consequently the RMS notification framework
is no longer needed and all notification queue related modules should be removed from
RMS 16.0 repository. RMS_ASYNC_USER should be explicitly dropped in the
environments by clients upgrading from 15.0.1 to 16.0.
For RMS 16.0, the supplier site indicator will always be Y. For existing customers that
do not use the supplier site functionality, you will need to setup a one to one relation
between a supplier and a supplier site.

Upgrade Requirements
The hardware and software required for upgrading your product can be found in the
Oracle Retail Merchandising System Installation Guide.

Upgrade Script Distribution Process

Updates to the 16.0 upgrade scripts will be distributed through hot fixes (16.0.1, 16.0.2,
and so on). Each hot fix will contain the defect fix as well as the updated, complete 15.0.1
to 16.0 upgrade scripts. The latest complete upgrade scripts for 16.0 will also be included.

Note: If a hot fix is released, it may be necessary for the

upgrade scripts to be changed. Before performing an
upgrade, be sure to check My Oracle Support for updated
upgrade scripts.

RMS Upgrade
The RMS upgrade is the most extensive of the upgrades and affects production data.
Oracle highly recommends that you back up all production data prior to performing the
upgrade.

Upgrade Process
The RMS installer provides the option to run a full install or an upgrade during the
installation process. If you choose to upgrade RMS, the installer launches the ORPatch
utility to upgrade the database schema.
The upgrade is split into two jobs. The first job is to upgrade the database which is
performed using the ORPatch utility. The second job is to upgrade the data for new
tables and new columns manually, using the master controller.
1. Database Upgrade jobs

6 Oracle Retail Merchandising

 RMS Upgrade

Check_if_empty jobs
These are jobs that check if tables are empty. These are tables that are processed
by the nightly batch cycle (for example, the cost_change_trigger_temp table).
The assumption is that these tables are empty before proceeding with the
upgrade.
Database upgrade object jobs
These are jobs that upgrade the database from one version to another. They also
insert seed records for the application to use.
The database upgrade objects are:
DBC scripts
Control scripts
Object scripts
Packages
Procedures
Triggers
Translation scripts
2. Data Upgrade jobs

Note: Data upgrade jobs are used only by RMS and ReIM.

PreValidation script
This script validates the input files the customer will update.
security.dat is required to create the data level security for new application
user used when loging in to the RMS16 application. Since RMS16 will not be
using the database user as a login on the online application, new application
user will need to be created instead. The security.dat file will ensure that the
created application user will have access at the minimum, the same data as
the database user.

Note: The PreValidation script is used only by RMS. See the

Data Migration chapter of the RMS Installation Guide for
additional information on the input files.

Data upgrade
These scripts upgrade the data for new tables and new columns.
The data upgrade scripts upgrade the following tables in RMS:
RTK_ROLE
SEC_USER
SEC_USER_ROLE
SEC_GROUP
SEC_USER_GROUP
FILTER_MERCH
FILTER_ORG
SEC_LOC_MATRIX

Upgrade Guide 7
RMS Upgrade

Translate Data Upgrade not Supported by Upgrade Scripts

The translation table TL_SHADOW has been dropped as part of 16.0 and for every table
which holds description column requiring translation, individual translation _TL tables
have been created in 16.0. The entries in TL_SHADOW were held for strings translation
and did not map that record to the specific entity record. As part of upgrade to 16.0, any
custom entries in TL_SHADOW table will not be copied to individual translation table
for the entities. As a pre-upgrade work, the entries in the TL_SHADOW table should be
extracted and the entries mapped against the entity and post upgrade, the entities
translation table should be loaded with the translation entries.

Technical Overview
Data Input from Client
This is the information the client needs to provide to upgrade the data to 16.0. The files
are located under the files directory of the master controller. For more information, see
the Installation Guide.
Depending on the DATA_LEVEL_SECURITY_IND in SECURITY_CONFIG_OPTIONS,
the configuration on security.dat file will change. The configurations are specified below.
1. DATA_LEVEL_SECURITY_IND = 'N'

If DATA_LEVEL_SECURITY_IND is set to 'N', this would mean the RMS16 application

do not implement data level security. The security.dat file will be configured to only
create and associate the roles and application user as shown below.

|RTK_ROLE|DEVELOPER|10|Y|
|RTK_ROLE|MANAGER|9999999|Y|
|RTK_ROLE|STAFF|1|Y|
|SEC_USER|RMS_ADMIN|Y|N|N|N||
|SEC_USER|RMS_DEVELOPER|Y|N|N|N|RMS_ADMIN|
|SEC_USER|RMS_TESTER|Y|N|N|N||
|SEC_USER_ROLE|RMS_ADMIN|MANAGER|
|SEC_USER_ROLE|RMS_TESTER|DEVELOPER|

1. DATA_LEVEL_SECURITY_IND = 'Y'

If DATA_LEVEL_SECURITY_IND is set to 'Y', this would mean the RMS16 application

will implement data level security. The security.dat file will be configured to create and
associate the roles, application user and groups. Assigining merchandise and
organization levels to the groups can also be configured, but is not mandatory.

|RTK_ROLE|DEVELOPER|10|Y|
|RTK_ROLE|MANAGER|9999999|Y|
|RTK_ROLE|STAFF|1|Y|
|SEC_USER|RMS_ADMIN|Y|N|N|N||
|SEC_USER|RMS_DEVELOPER|Y|N|N|N|RMS_ADMIN|
|SEC_USER|RMS_TESTER|Y|N|N|N||

8 Oracle Retail Merchandising

 RMS Upgrade

|SEC_USER_ROLE|RMS_ADMIN|MANAGER|
|SEC_USER_ROLE|RMS_TESTER|DEVELOPER|
|SEC_GROUP|1||||
|SEC_USER_GROUP|RMS_ADMIN|
|SEC_USER_GROUP|RMS_DEVELOPER|
|SEC_GROUP||SYSTEM LIMITED MERCH||Associated with Certain Merch Levels.|
|SEC_USER_GROUP|RMS_TESTER|
|FILTER_MERCH|D|1111|||
|FILTER_ORG|A|1|
|FILTER_MERCH|S|2101|2|4|
|SEC_LOC_MATRIX|LTXFRM||||10003|Y|Y|
|FILTER_ORG|W|10003|
|SEC_LOC_MATRIX|LTXFRM|15|153|1531||Y|Y|

For DATA_LEVEL_SECURITY_IND set to 'Y', the script will assign application user,
merchandise, organization levels and locations to a security group similar to a header-
detail association. The script first reads for a sec group header. Any succeeding lines will
be assigned to that SEC_GROUP, until it reads another SEC_GROUP header. Note that
for the SEC_GROUP line, you can use an existing group by specifying the GROUP_ID
from SEC_GROUP table.

For the above file template, the associations created will be as follows.

|SEC_GROUP|1|||| - This line will use an existing security group. The RMS_ADMIN
and RMS_DEVELOPER application user will be associated with this group.
|SEC_GROUP||SYSTEM LIMITED MERCH||Associated with Certain Merch
Levels.| - This line will insert a new group in the SEC_GROUP table with the name
SYSTEM LIMITED MERCH. The RMS_TESTER application user will be associated with
this group, and also all the lines below it, until the next SEC_GROUP header.

Upgrade Guide 9
RMS Upgrade

Below is the data model diagram for the security and group associations.

10 Oracle Retail Merchandising

 RMS Upgrade

The upgrade uses only one input file (security.dat). The security file contains headers
(first field) which will determine which action to execute and tables to insert the data.
The following explains in detail the purpose of each header.

RTK_ROLE
This will insert records into the RTK_ROLE_PRIVS table. The user can create any role
here, as long as it is unique. The user will also specify the order approval amount and
transfer approval indicator for the role.

Columns Loaded Table Validations

Loaded

ROLE Alphanumeri UPG_RTK_ User can specify a role whch already

c identifier for ROLE exists in RTK_ROLE. Doing so will update
the role. the role with the specified
ORD_APPR_AMT in the file.
ORD_APPR_AMT Numeric field
which holds
the order
approval
amount.

SEC_USER
This will insert records into the SEC_USER table. It will create new application users
used when logging in to RMS16 online application. It is also used to mark the application
user as either an RMS user, ReSA User, ReIM user or an Allocation User in the
SEC_USER table. Also a manager can be associated to each of the application user.
However, the manager specified should be a valid database user or application user in
the SEC_USER table.

Columns Loaded Table Validations

Loaded

APPLICATION_ Alphanumeric UPG_SEC_ APPLICATION_USER_

USER_ID identifier for the USER ID should be unique. It
application user should also be unused
used for logging as a
in the RMS16 UI. DATABASE_USER_ID
in SEC_USER table.
RMS_USER_IND Alphanumeric
field which holds
the RMS user Manager should be a
indicator. valid
DATABASE_USER_ID
RESA_USER_IN Alphanumeric or
D field which holds APPLICATION_USER_
the RESA user ID in SEC_USER table.
indicator.
REIM_USER_IN Alphanumeric
D field which holds
the REIM user
indicator.
ALLOCATION_ Alphanumeric
USER_IND field which holds
the

Upgrade Guide 11
RMS Upgrade

Columns Loaded Table Validations

Loaded
ALLOCATION
user indicator.
MANAGER Alphanumeric
field which holds
the manager for
the application
user.

SEC_USER_ROLE
This will insert records into the SEC_USER_ROLE table. It will assign the created roles to
the application users. An application user can be associated with multiple roles.

Columns Loaded Table Validations

Loaded

APPLICATION_ Alphanumeric UPG_SEC_ None.

USER_ID identifier for the USER_ROL
application user E
used for logging
in the RMS16 UI.
ROLE Alphanumeric
identifier for the
role..

SEC_GROUP
This will reference records on the SEC_GROUP table. This line will be used to either
create a new group or associate an existing group with data level security. If creating a
new group, then the group id should not be specified as this will be system generated.
Instead, the name for the group id and group role should be specified, with the name
being mandatory.

Columns Loaded Table Validations

Loaded

GROUP_ID Alphanumeric UPG_SEC_ If creating a new group,

identifier for the GROUP do not specify a
group id. GROUP_ID as this will
be system generated.
GROUP_NAME Alphanumeric
field which holds
the group name. For an existing group,
no need to specify the
ROLE Alphanumeric group name.
field which holds
the role.
COMMENTS Alphanumeric
field which holds
the comments.

SEC_USER_GROUP

12 Oracle Retail Merchandising

 RMS Upgrade

This will insert records into the SEC_USER_GROUP table. This will associate an
application user with a group. An application user can exist in multiple groups. (See
Notes above)

Columns Loaded Table Validations

Loaded

APPLICATION_ Alphanumeric UPG_SEC_ none

USER_ID identifier for the USER_GRO
application user. UP

FILTER_MERCH
This will insert records into the FILTER_GROUP_MERCH table. Defined are the
merchandise levels that are accessible to the group. If the group will have no restriction
on merchandise data, then do not insert records here for the group. (See Notes above).

Columns Loaded Table Validations

Loaded

FILTER_MERCH Alphanumeric UPG_FILT Ensure to use valid merch levels and

_LEVEL identifier for the ER_MERC merch id combinations. See below the
filter merch level. H views filtered by the
The merchandise FILTER_GROUP_MERCH table.
levels that can be
used are under
There is no actual validation on the
the code type
script but it is up to the user to ensure
FLTM
data integrity
FILTER_MERCH Alphanumeric
_ID field which holds
the merch id.
FILTER_MERCH Alphanumeric
_ID_CLASS field which holds
the class.
Populated only if
the merch level is
for a class or
siubclass.
FILTER_MERCH Alphanumeric
_ID_SUBCLASS field which holds
the subclass.
Populated only if
the merch level is
for a siubclass.

Upgrade Guide 13
RMS Upgrade

FILTER_ORG
This will insert records into the FILTER_GROUP_ORG table. Defined are the
organization levels that are accessible to the group. If the group will have no restriction
on organization data, then do not insert records here for the group. (See Notes above).

Columns Loaded Table Validations

Loaded

FILTER_ORG_L Alphanumeric UPG_FILT Ensure to use valid org

EVEL identifier for the ER_ORG levels and org id
filter org level. combinations. See
The organization below the views filtered
levels that can be by the
used are under FILTER_GROUP_ORG
the code type table.
FLOW
FILTER_ORG_ID Alphanumeric There is no actual
field which holds validation on the script
the organization but it is up to the user to
id. ensure data integrity

SEC_LOC_MATRIX
This will insert records into the SEC_GROUP_LOC_MATRIX table. This will define
security for a specific organization and group. If the group will have no restriction, then
do not insert records here for the group. The user can apply security at the region,
district, store or warehouse level. (See Notes above).

14 Oracle Retail Merchandising

 RMS Upgrade

Columns Loaded Table Validations

Loaded

COLUMN_COD Alphanumeric UPG_SEC_ Ensure to use valid org

E identifier for the LOC_MAT hierarchies. See below
functional area RIX the views filtered by the
code. The SEC_GROUP_LOC_MA
available TRIX table.
functional areas
are LTXFRM
There is no actual
(Transfers from)
validation on the script
and LTXFTO
but it is up to the user to
(Transfers to).
ensure data integrity.
REGION Alphanumeric
field which holds
the region.
DISTRICT Alphanumeric
field which holds
the district.
STORE Alphanumeric
field which holds
the store.
WH Alphanumeric
field which holds
the wh.
SELECT_IND Alphanumeric
field which holds
the select
indicator.
UPDATE_IND Alphanumeric
field which holds
the update
indicator.

Post Upgrade

CLEANUP
The CLEANUP process drops the temporary tables that are created for upgrade purposes
along with the associated package DATA_MIGRATION_SQL.

PRODUCT_VERS_CONFIG_OPTIONS
Run the ad-hoc script STAGING_DIR/rms/installer
/mom/Cross_Pillar/install_scripts/source/sys_update_prod_vers.sql to update the
PRODUCT_VERS_CONFIG_OPTIONS table.
It updates the patch version of RMS and ReSA to 16.0 and also updates the patch version
of other MOM products installed if any. It accepts six values as user input:
first input as Allocation version
second input as RWMS version
third input as REIM version

Upgrade Guide 15
RPM Upgrade

fourth input as SIM version

fifth input as AIP version
sixth input as RPM version
seventh input as ReSA version

Objects Affected by the Upgrade

The following objects are affected by upgrading from 15.0.1 to 16.0.

Database Change Objects

NA

RPM Upgrade
Before upgrading from Oracle Retail Price Management (RPM) 15.0.1 to RPM 16.0, the
Oracle Retail Merchandising System (RMS) must first be upgraded to Release 16.0.

Overview of the Upgrade Utility

Oracle Retail Price Management (RPM) can be upgraded from 15.0.1 to 16.0 by using an
upgrade utility in the product installer. This upgrade utility modifies the database to
accommodate the 16.0 functionality. For more details, see the Installation Guide.
The utility also installs any system level data required for the new functionality included
with the 16.0 release. All database changes and data installations preserve existing data.
However, if a client has added custom columns to tables affected by the upgrade utility,
then the impact of the upgrade scripts must be analyzed before utilizing them on tables
that are affected.
The upgrade utility is utilized only by the database side of the RPM application. All
application code will be installed separate from this process, using the installer. For
details see the Installation Guide.

Upgrade Recommendations
Before beginning the upgrade process, back up the database and application files.
Oracle highly recommends you back up all of your production data prior to
performing the upgrade.
The upgrade utility upgrades the database (tables, triggers, control scripts,
procedures, and packages) to Version 16.0. However, application code and
dependencies such as RIB Objects that are part of Version 16.0 must be installed, as
with previous releases.
Clients can verify whether any 16.0 code changes (tables, PL/SQL) affect customized
code by comparing all modules in the 16.0 code base with what the client currently
has. There are numerous tools available to complete this comparison, or diff.
Create an upgrade plan by becoming familiar with the following:
Changes to the functionality in 16.0 Review the User Guide, Operations Guide,
and Release notes
Other technical impacts in release 16.0
The upgrade process

16 Oracle Retail Merchandising

 ReIM Upgrade

ReIM Upgrade
The following describes the functional impact of the Oracle Retail Invoice Matching
(ReIM) upgrade.

Overview of the Upgrade Utility

Oracle Retail Invoice Matching (ReIM) can be upgraded from 15.0.1 to 16.0 by using an
upgrade utility in the product installer. This upgrade utility modifies the database to
accommodate 16.0 functionality.
The upgrade utility is utilized only by the database side of the ReIM application. All
application code will be installed separate from this process, using the installer. For
details see the Installation Guide.

Upgrade Recommendations
All processing on the legacy system should be up to date and as complete as possible
before starting the upgrade process.
Before beginning the upgrade process, back up the database and application files.
Oracle highly recommends you back up all your production data prior to performing
the upgrade.
The upgrade utility upgrades the database (tables, triggers, control scripts,
procedures, and packages) to Version 16.0. However, application code and
dependencies that are part of Version 16.0 must be installed, as with previous
releases.
The list of tables provided in the Functional Impact sections are provided to give
clients an opportunity to verify whether any of their customizations are affected
(potentially overwritten) by the upgrade utility.
Clients can verify whether any 16.0 code changes (tables, PL/SQL) affect customized
code by comparing all modules in the 16.0 code base with what the client currently
has. There are numerous tools available to complete this comparison, or diff.
Create an upgrade plan by becoming familiar with the following:
Changes to the functionality in 16.0 please review the User Guide, Operations
Guide, and Release notes
Other technical impacts in release 16.0
The upgrade process
legacy deal related documents have to be handled manually if the customer wants

Upgrade Guide 17
Allocation Upgrade

Allocation Upgrade
This release of Allocation supports an upgrade from version 15.0.1 to 16.0. The following
sections describe the details that you should consider before upgrading your system to
the new version.

Overview of the Upgrade Process

Oracle Allocation can be upgraded from 15.0.1 to 16.0 by using several database scripts.
Allocation can be upgraded from 15.0.1 to 16.0, along with other Merchandising
products. Various products can be selected during the installation process by selecting an
upgrade installation path instead of a full installation.
All database changes to support the upgrade are included in the installer. Most data
transformations, such as populating required new columns with a default value, are also
handled in the installer. There are a few exceptions due to the changes needed for the
Multiple Style FPG requirement. A data transformation script must be run manually after
the upgrade through the installer. There is also a script needed to update the store type.
For more information, see the Oracle Retail Merchandising System Installation Guide and the
Oracle Retail Allocation Installation Guide.
Notifications which were present in the 15.0.1 environment will be removed in the
upgrade. The source table for the notifications will be modified for the 16.0 release, and
any past notifications will be removed at the time of the upgrade.

Upgrade Recommendations
Before beginning the upgrade process, back up the database and application files.
Oracle highly recommends you back up all your production data prior to performing
the upgrade.
As part of the update, you must delete Metadata Services (MDS). Recreate any
previously saved customizations after the upgrade. You may want to make a note of
existing customizations by taking screenshots, to quickly reapply the customizations
after the upgrade. This would include user run-time customizations commonly made
in ADF such as Saved searches, column sorting, column selections, and column
ordering. These customizations will need to be re-created with the 16.0 application.
The reason for purging the MDS layer is that due to significant changes in the
underlying components used by the run time customizations, the customizations
from a 15.0.1 version of the product may have conflicts against the 16.0 code, causing
problematic errors.
All database changes to support the upgrade are included in the installer. Most data
transformations, such as populating required new columns with a default value, are
also handled in the installer. There are a few exceptions due to the changes needed
for the Multiple Style FPG requirement. A data transformation script must be run
manually after the upgrade through the installer. There is also a script needed to
update the store type. For more information, see the Oracle Retail Allocation
Installation Guide and in the Oracle Retail Upgrade Whitepaper.
Any customizations made in the 16.0.x release, such as dashboard configurations, or
embedded BI, will need to be re-implemented using the customization information in
the Oracle Retail Operations Guide.

Pre Upgrade Steps

Prior to upgrading the MDS data for Allocation, 15.0.1 must be removed. The MDS data
includes user runtime customizations, which are created when you take the following

18 Oracle Retail Merchandising

 Allocation Upgrade

types of actions in the application: saved search, re-organizing columns, adding columns
to the default views. To back up the MDS and delete the partition, see the latest Oracle
Fusion Middleware documentation.

Upgrade Guide 19
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright 2016, Oracle. All rights reserved.

All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to
be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by
this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written
permission.

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.