Skip navigation
1 2 3 4 Previous Next

Retail Support Blog

59 posts

Please review Oracle Retail Reference Library (RRL) Information Center and Release Index (Doc ID 2058843.2) for an overview and details on RRL, including how to get started with RRL.



The Premier Support End Date is approaching for certain Oracle Retail Products.


Please review the following Knowledge Note for full details:

Premier Support End Date Approaching For Certain Oracle Retail Product Releases (Doc ID 2530439.1)






Per the Oracle Retail Error Correction Policy (ECP), the grace period for version 16.0.1 is due to expire in August 2019, after which Oracle Retail Development will cease to provide fixes on this version. Retailers must plan their maintenance strategy to move their product version to 16.0.2. If you would like more details on the ECP, refer to the following articles.


Oracle® Retail Error Correction Support Policy (Doc ID 1988031.1)

Oracle® Retail Global Business Unit Terminal Patch and Grace Period on Enterprise Releases (Doc ID 2099142.1)




Ivanti (Wavelink) has released the latest Studio Client for iOS which is used by the Retail Store Inventory Management (RSIM) application for the mobile functionality.  This version contains bug fixes reported to solve customer production issues.


Oracle Retail Development has updated this document with the link for downloading the new release for iOS.

Please reference the following Knowledge Note:

Oracle Retail Store Inventory Management Support for New Wavelink Studio Clients (Mobile SIM) (Doc ID 1669543.1)

Oracle Retail Patch Value Propositions (PVP) are deliverables that provide retailers with a view of fixes and enhancements (functional, technical, integration, and so on) that are scheduled for inclusion in a patch. PVPs are provided at either the product level or the solution unit level, and they are intended to assist partners and retailers in their long-term planning.


PVP documents are now available for version 16.0.2 and can be found in Patch Value Propositions for Oracle Retail Applications Releases 12, 13, 14, 15, and 16 (Doc ID 1996991.1)

RTLOG file is transaction logs comes from Point of Sale(POS) system and process in  Retail Sales Audit(ReSA) system.

RTLOG file format changed  to allow 40 characters in place of  16 characters for coupon numbers.

This field COUPON NUMBER is part of  Discount(IDISC) and Tender(TTEND) record type in RTLOG .


If RTLOG format not changed to increase size in IDISC and TTEND records, RTLOG processing in ReSA will fail with GARBAGE_IN_RECORD.

Please see Note 2223509.1 and Note 2338626.1  for details.

Oracle Retail Merchandising applications (RMS, RTM, ReIM,  ReSA and Allocation) have been modernized using Oracle’s Application Development Framework (ADF) to improve overall user experience, fit retailer needs and simplify business processes, allowing retailers to run leaner and more efficiently. These ADF applications can be customized for retailers to tailor the applications to best suit their business practices.  To customize these applications the System Integrators/Retailers need to have knowledge on the following:


  • ADF Framework
  • Leveraging the seeded customization framework in ADF to extend the Retail applications


Oracle Retail recommends the following documentation and training to enable Partners and Customers to support their ADF customization requirements.


1.       Oracle University (Training) - Oracle Middleware 12c: Build Rich Client Applications with ADF Ed 1

2.       Oracle Retail GA Documentation  Refer to the Oracle Retail Merchandising Operations Guide - Volume 3  (Chapter 6 - Customization of Retail Applications)

3.       My Oracle Support (White Paper) - Oracle Retail Merchandising ADF Customization Guide  (Doc ID 2018356.1)

4.      Oracle University (Training) - Oracle Retail Learning Subscription (RLS) for Merchandising (Channels : Your Resources)



If you are using RWMS 16.0, you will be utilizing Oracle Forms Services 12c ( Ensure that mandatory Forms patch 22184867 is installed to avoid FRM-93652 exception. O_Retail_clr.bmpReview Doc ID 2260556.1: FRM-93652 Exception Raised While Invoking User Class Editor Screen, for additional details.


Also issue has been reported on multiple different forms that throw DMS error with "Invalid user identifier or password. Re-enter. ORA-0000: normal, successful operation..." logged in ERROR_LOG table and after that the user session hangs. This has been reported for below GUI screens:

1. Inventory Management -> Confirm Paper Pick to Belt / Confirm Paper Pick to Pallet / Confirm Paper Unit Pick

2. Processing -> Order Consolidation / Packing / Resolve Trouble / Quality Assurance

3. Receiving -> Container Checking

4. Returns -> Return to Vendor


In order to address this issue, apply Oracle Forms Services 12c ( patch 21534616. For further details regarding this Forms related issue, check Doc ID 2192436.1: Intermittent 12c Crashes with Segfault when Querying, or Saving Records - FRM-93652 - or FRM-40007: Invalid user identifier or password. Re-enter when Logging On


FRM-93652 exception has also been reported in a different application due to Linux OS level updates. Below note is provided for the same, in case if that too is required:

Doc ID 2288127.1: FRM-93652, FRM-93656 Errors After Linux Kernel OS Updates

O_Retail_clr.bmpWhen multiple users tried to access the RMS UI (Retail Merchandising System User Interface) application, severe performance issues were observed.

This was caused by few incorrect entries from the jazn-data.xml saved into the RMS OPSS schema.  This file contained definitions for incorrect

Please follow the instructions as given in  Solution Section of the  Doc ID 2287719.1 to resolve performance issue caused by incorrect policies.

Prior to release 14.0, In Oracle Retail Point of Service , overlapping promotions created in Retail Price Management (RPM) were exported as separate

Price Promotion events in the PricingExtract.xml. In release 14.0 and 14.1, price promotions event has been enhanced to support overlapping promotions

in a single event.


Example of the PricingExtract.xml that is extracted from RPM for an overlapping promotion:


<?xml version="1.0" encoding="UTF-8" ?>
<PricingImport Priority="0" FillType="FullIncremental" Version="1.0" Batch="1" CreationDate="2017-02-08T13:32:03.0Z" xsi:noNamespaceSchemaLocation="PricingImport.xsd" xmlns:xsi="">

<PriceChange ChangeType="ADD" ID="21210840" StartDate="2017-02-08" TemplateType="Default">
<Item ID="4322" TemplateType="Default">

<PricePromotion ChangeType="ADD" ItemPriceCategory="Both" ID="330400" PromoCompID="336882" PromoCompDetlID="32276707" StartDateTime="2017-02-06T00:00:00.0Z" EndDateTime="2017-02-13T23:59:59.0Z" Type="PercentOff" Priority="1" TemplateType="Default">
<Item ID="4322" StartDateTime="2017-02-06T00:00:00.0Z">
<Price CurrencyCode="USD">131.25</Price>

<PricePromotion ChangeType="UPD" ItemPriceCategory="Both" ID="330400" PromoCompID="336882" PromoCompDetlID="32276707" StartDateTime="2017-02-06T00:00:00.0Z" EndDateTime="2017-02-13T23:59:59.0Z" Type="PercentOff" Priority="1" TemplateType="Default">
<Item ID="4322" StartDateTime="2017-02-06T00:00:00.0Z">
<Price CurrencyCode="USD">131.25</Price>
<Item ID="4322" StartDateTime="2017-02-08T00:00:00.0Z">
<Price CurrencyCode="USD">144.37</Price>



Refer the following article which provides the details of the patch that needs to be applied in order for the import to process correctly on the Oracle

Retail Backoffice application so that the items ring up with the correct price on RPOS.


Version 14.1.x
Price Change Overlapping With a Promotion Sent From RPM Is Not Updated Correctly in Back Office (Doc ID 2244492.1)


Version 14.0.x
Import of PricingExtract in Back Office is Partially Processed when an Overlapping Promotion is Sent from RPM (Doc ID 2102011.1)
'UNITRETAIL' and 'IDISC' Amounts Incorrect for Items on Clearance and Simple Promotion in the RTLog (Doc ID 1957229.1)

With 16.0 release, the RMS user-interface has been re-written to use Oracle’s Application Development Framework (ADF). The existing Oracle Forms framework for RMS has been deprecated.


The new technology provides an enhanced user experience through a re-architecting of the application screens, enhanced user experience through the use of business intelligence (BI) driven workflows, user-centric design and the building of role-based dashboards.


Although the look of the new user interface differs significantly from previous versions, the underlying application, including the core data model, Major Calculations, batch processing and integration remains largely the same as in previous releases. The benefits of the modernization of merchandising are many, including a reduced total cost of ownership because RMS, RTM, Allocation, ReIM, and ReSA all reside on the same technology.


Matching of invoices to receipts is the core functionality of Invoice Matching.

Once, invoices are matched to receipts, they need to be posted to the financial system. Posting of invoices may fail for many different reasons.

If an invoice was stuck in Matched status and doesn't get posted, in RelM15.0, technical support team would need to get involved to identify the root cause and fix the issue.


With ReIM 16.0, a new process is introduced that allows the end user to view the posting errors and understand the reasons for those errors.

Depending on the root cause, users with appropriate access may be able to fix the problem in the new screen or determine where additional setup is needed to allow the posting for the specific document to be completed successfully.

Please refer to ReIM 16.0 User Guide for more details on this topic.

cnt2267539.jpgSelecting stock orders and distributing on a wave is the core operation of Oracle Retail Warehouse Management System (RWMS). Highlighted in this blog are two very useful self help documents created in My Oracle Support.


When distribution is taking long time to complete the execution, below note should help with performance improvement in most cases:

What are the Recommendations on Frequency of Analyzing Tables and Rebuilding Indexes in RWMS Application? (Doc ID 362803.1)


Distribution is a complex process that must ensure compliance with numerous rules and business logics in order for the warehouse to be able to fulfill store demands. For troubleshooting purposes, Oracle has compiled a list of points to check against below note when a stock order to a store is not fulfilled as expected by distribution: What to Check When a Stock Order to a Store Does Not Get Distributed? (Doc ID 1410253.1).

Oracle Retail Point of Service  Suite Patches 14.0.4 and 14.1.3 containing a number of bug fixes that were found in versions 14.0.3 and 14.1.2 respectively. Oracle recommends that customers and solution implementers take advantage of all fixes and enhancements included in the patches. If you are currently implementing version 14.0.x or 14.1.x, this is a good time to download the latesSoftwaredownload.pngt installers from My Oracle Support.


For links to the 14.1.3 patches and read me files, visit Recommended Patches for Oracle Retail Point-of-Service Suite: Version 14.1.x (Doc ID 2067812.1).


Both patches are terminal patch releases.  Thus, no new patches will be released on versions 14.0 or 14.1.  Please review the Lifetime Support Policies brochure located on to understand the time lines for the different code lines and the end of Premier Support. Currently versions 14.1.x and 14.0.x have active Premier Support.


Note: Defect reports are now available via the Oracle Retail Applications Defect Report Documents (Doc ID 2021275.1)


If you have any questions about this topic, feel free to comment on this blog post or create a new My Oracle Support Community (MOSC) thread under the Retail Point-of-Service Solutions space.

Oracle Retail 16.0 was released in December 2016. Support has created a community thread in the RMS Community to proactively support our customers implementing RMS v16.  In the RMS 16.0 Installation Assistance thread you will find up to date information on the installation process, known issues and how to resolve them.  This community post will be updated periodically as more RMS 16.0 installation information becomes available.  You can also refer to the Retail Merchandising System Documentation Library for the Installation Guide and other v16 documentation.



Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.