Oracle® Retail Price Management

Release Notes

Release 13.2.9

E73281-01

March 2016

Oracle Retail Price Management (RPM) Release 13.2.9 is a patch release for RPM 13.2.�

RPM 13.2.9 includes selected defect fixes and enhancements for RPM 13.2 code.� Oracle Customer Support investigates submitted issues assuming that all released� updates have been applied. It is the customer's decision when to apply a new release;� however, delays in applying updates can complicate the support process.

About Patch Releases

Oracle Retail patch releases are periodic releases that can include new defect fixes and� product enhancements.

Documentation for patch releases includes the following:

New and updated guides (for example, operations and user guides) that apply to the patch release level. See "Related Documentation" for a list of the documents published for RPM 13.2.9.
Defect reports for new fixes and enhancements for the patch release.

See the Oracle Retail Price Management Installation Guide for Release 13.2.9 for instructions about how to apply the defect fixes and enhancements that you have not already installed.

Applying a Patch Release

Before applying the RPM 13.2.9 patch release, be sure that:

RPM 13.2 has been installed.
Patch release RPM 13.2.8 has been applied.

Before applying the release over your files:

Note whether any modules have been customized. If so, the customizations must be reapplied to the new version of the module, or the fix may need to be applied to the custom version of the code.
Copy the original files to a different directory before you copy over them, in case you need to refer to them at a later date.

Back up data before running any script, because the scripts provided do not preserve data. See defect reports for details.

Check with your database administrator to determine whether your database should be analyzed after a script is run. In many cases, analysis of the database is necessary to take advantage of new or modified indexes intended to improve performance of the application.

Hardware and Software Requirements

See the Oracle Retail Price Management Installation Guide, Release 13.2.9 for information about the following:

Hardware and software requirements
Oracle Retail application software compatibility

Technical Enhancements

This section addresses the technical enhancements included in Oracle Retail Price Management Release 13.2.9.

Note:

The list below announces the addition of Oracle Retail support for the technology described. See the Oracle Retail Price Management Installation Guide requirements section for critical information, such as whether the enhancement below replaces previous versions or is supported in addition to already existing versions.

Database Server Support

Oracle Retail Price Management Release 13.2.9 is supported for use with the following database server:

Oracle Database Enterprise Edition 12cR1 (12.1.0.2)

Oracle Fusion Middleware

Oracle Retail Price Management Release 13.2.9 is supported for use with the following Oracle Fusion Middleware:

Oracle Access Manager (OAM) 11.1.2.3
Oracle HTTP Server (OHS) 11.1.1.9
Oracle Internet Directory (OID) 11.1.1.9
Oracle WebGate 11.1.2.3

Browser Support

Oracle Retail Price Management Release 13.2.9 is supported for use with the following browser:

Microsoft Internet Explorer 11
Mozilla Firefox ESR 31+

Java Support

The client of Oracle Retail Price Management Release 13.2.9 is supported for use with the following Java version:

Oracle Java 7 Update 80
Oracle Java 8 Update 65

Defect Fixes and Documentation

A defect fix is a modification to the base Oracle Retail code (for example, a bug fix, a performance enhancement, or a functional enhancement). Each defect fix that is included in this patch has a corresponding defect report titled <defect-number>.PDF (for example, 1234567.PDF) that is posted to My Oracle Support at the following location: Oracle Retail Defect Document Listings (MOS ID:2021275.1).

In the same folder, the file named DEFECT MODULE XREF RPM 13.2.9.XLS lists every defect number and the modules and scripts that are included in the patch. Review each defect report carefully before implementing the defect fixes. Note that scripts do not preserve data. Make sure that all data is backed up before you run any script.

Noteworthy Defect Fixes

The following defect fixes and enhancements are included in RPM 13.2.9. This is not a complete list; see the cross-reference spreadsheet and defect reports for a complete list and full details.

Defect Number	Description
18622630	The PurgeExpiredExecutedOrApprovedClearancesBatch are not purging the records.
21376555	The emergency clearances are not being published.
20633742	The multi buy promotions are not exported correctly when the DEPT CLASS is added in the one buy list and reward list.
20062544	The users with RSM SUBMIT roles are able to approve the Clearance Resets.
20625562	The RPM user interface is slow and crashes with a fatal error - ORA-0403.
19215526	The ORA-14450 error occurs while trying to create a Price Change request from SIM.
22126317	The Maintain Promotion window takes a long time to invoke when searching for a Promotion.
21454575	The RPM displays an exception error 'MAXMESSAGESIZEEXCEEDEDEXCEPTION' when editing a huge Promotion component.
21085589	The simple Promotion conflict check process is hanging.
20317308	Performance improvement is required for the Create from Existing button for Promotions.
21670962	The NIL batch file populates the RPM_FUTURE_RETAIL.MAX_HIER_LEVEL and RPM_PROMO_ITEM_LOC_EXPL.MAX_HIER_LEVEL with a NULL value.
21229280	The Timelines are missing if the NIL batch file is executed multiple times and when the Item /LOC Retail is different than Item/Zone Retail.
20848311	Performance improvement is required for the PromotionArchiveBatch file.
20868502	The REFRESHPOSDATABATCH does not populate the Clearance Payloads for the records that are reset.
21153986	For the RPM instrumentation the Partitioning and Adding an Index on the RPM_BATCH_LOG table is required.
20846446	When creating a complex Promotion with 25k, no message is received for 240 seconds.