Monday Feb 17, 2014

Announcing Significant Functional White Papers for Merchandising

In conjunction with Release 14, Oracle Retail has published to My Oracle Support a collection of in-depth White Papers addressing the functional details of various business operations within the  Merchandising Operations Management suite of applications. Retailers and partners should consider these key reference documents as essential supplements to the Oracle Retail end user documentation suite.

Oracle Retail Merchandising Functional Library (Doc ID 1585843.1)

Oracle Retail Merchandising System (RMS) Catch Weight Overview v14

Catch Weight functionality allows for the ordering and management of items that vary by weight from one instance of an item to the next. Examples of this are primarily in the grocery industry, where items such as fresh produce, deli, butchery and prepackaged cheese and meat, are often purchased by weight and may be sold by weight or as individual products (eaches). Catch weight items can have a varying cost by unit of measure (UOM) and have an average weight maintained for the items, which is used by any transactions involving the items where a weight is not captured. From an ordering perspective, Oracle Retail Merchandising System (RMS) was built primarily to support the ordering of catch weight items using simple packs. However, the ordering of catch weight items without using simple packs is also supported. RMS supports four different types of catch weight items, which are outlined in more detail in this document, including how the setup for these items differs from other items in RMS, as well as the various ways that catch weight items impact inventory functions, such as purchasing, receiving and, cost maintenance.

Oracle Retail Trade Management (RTM) v14

Oracle Retail Trade Management (RTM) is used to manage the import process, including automating the steps necessary to import goods, managing file exchanges with trading partners, and providing a central database of critical import order information. This document provides an overview of the primary functions and features of the RTM system, as well as information regarding implementation, data setup, and troubleshooting.

RMS 24x7 Inventory Availability v14

Large retailers today have operations and operating models that extend across different continents and time-zones. 24x7 Retailing refers to an amalgamated retail model that offers customers retailing experience and information across various channels, time zones, formats and geographies on an uninterrupted basis, that is, 24 hours a day, 7 days a week. The need for 24x7 retailing has been driven by several emerging retailing models, including:

  • Store Operations
  • Distribution Center (DC) Operations
  • Commerce Anywhere Operations
  • Geographically Dispersed Business Process Models

This white paper examines the requirements for 24x7 retailing and the suitability of RMS in specifically supporting 24x7 inventory availability.

RMS Franchise Management v14

To scale up business operations and market presence, particularly in new markets, retailers may choose to utilize business partners to manage branded or co-branded stores while retaining the retailer’s business processes and value proposition. Businesses who partner with a retailer to expand the retailer’s presence are known as franchisees. Franchisees may operate one or more stores under the retailer’s banner. This white paper addresses the management of Franchise functionality within RMS and describes the several system parameters that are used to configure RMS related to Franchise management functionality.

RMS Deals Overview v14

A deal is a set of one or more agreements that take place between the retailer and a vendor. A vendor can be a supplier, wholesaler, distributor or manufacturer, and from the vendor, the retailer is entitled to receive discounts or rebates for goods that are either purchased or sold. A deal consists of a set of discounts and/or rebates that are negotiated with the supplier and share a common start and end date. This functional white paper holistically addresses Deals functionality in the Oracle Retail Merchandising System.

RMS Stock Counts Overview v14

Inventory accuracy is a critical and highly sensitive area affecting retailers. Inventory record accuracy has a significant impact on increasing levels of customer service, reducing costs, and increasing productivity. Stock counts verify the inventory figures kept within the merchandise management system, which makes reporting, planning, and ordering more accurate. In order to reconcile theoretical inventory levels to actual inventory on-hand, retailers perform physical inventory stock counts, which also serve to make stock ledger adjustments. These stock counts assist retailers in budgeting and accounting for shrinkage. This document provides an overview of the primary functions and features of the Stock Count module in RMS as well as an overview of the integration of this module with the Store Inventory Management (SIM) and Warehouse Management System (RWMS).

Oracle Retail Allocation v14

Oracle Retail Allocation helps retailers determine the inventory requirements at the item and location level, resulting in an inventory allocation that optimizes your supply across all locations. Using real-time inventory information, the system calculates need based on parameters you set, whether it is the characteristics of the product or the store. The result is an allocation tailored to each store's unique need. Oracle Retail Allocation allows you to allocate either in advance of the order's arrival or at the last minute to leverage real-time sales and inventory information. The primary objective of this document is to highlight lesser-known capabilities within the Allocation product, provide more detail on commonly asked questions, call out product facts, clarify specific capability/features, and provide additional information on how to use the Allocation product more effectively.

RMS Stock Ledger v13.2

This document provides an overview of the primary features of Oracle Retail Stock Ledger functionality. In addition, this document addresses the integration of this module with the financial packages. Use this document to get a detailed overview of the following:

  • Stock ledger attributes
  • Accounting methods
  • Budgeted shrink
  • Transaction data
  • What impacts the stock ledger
  • Stock ledger processes

RMS Managing Multiple Company Operations v13

Generally, large multi-national retailers have complex organization structures with multiple business groups, legal entities, operating units, and inventory organizations. Such enterprises have the business need to be able to separate financial transactions along with business groups, legal entities, operating units, and inventory organizations. When retailers operate with multiple legal companies or entities, they may use different physical instances of their accounting systems to support the segregation of financial records, or they may use a single physical instance of their accounting system. When operating with multiple legal companies or entities in a single installation, a company needs the ability to partition their general ledger along certain criteria, so that each set has its own chart of accounts and other identifying characteristics, such as the primary currency, accounting calendar, and balancing segment. RMS was extended to support multiple company operations in a single instance with the inclusion of multiple sets of books (MSOB) functionality, described in this white paper.

Monday Sep 23, 2013

Announcing Two White Papers and a Checklist for Oracle Retail Analytics

Oracle Retail has published to My Oracle Support two White Papers and a Checklist addressing Oracle Retail Analytics, an analytical application that provides multiple modules for analysis and reporting on different areas of retail management and operations.

Oracle Retail Analytics Merge Whitepapers (ID 1576449.1)

Oracle Retail Analytics Merge Whitepaper, Release 13.2.x and 13.3.x 

The combination of Oracle’s Retail Analytics modules with Oracle’s Business Intelligence Applications modules provides significant out-of-the-box value in creating an enterprise data warehouse, with deep content that is focused on each module’s applicable source applications. Because Retail Analytics was created as a new application, in part to better resemble Oracle's Business Intelligence Applications, it shares architectural alignment, and its dimensions were conformed on the initial build.

Merging Retail Analytics and Oracle Business Intelligence Applications Whitepaper

Because these two application families are packaged separately, and because Oracle Business Intelligence Enterprise Edition (BI EE) currently only allows one metadata file per server, this document has been created to help in the merge decision-making process.

Retail Analytics Implementation Checklist (ID 1573976.1)

Retailers should use this document early in the Retail Analytics implementation planning phase. It allows retailers to ask key questions when selecting a skilled Retail Analytics integrator. It assists integrators when posing key questions to retailers during requirements definition. Lastly, it provides considerations for implementation planning. This checklist should be used to set expectations among all partners and should be considered a longterm reference.

Friday Apr 12, 2013

Announcing Functional White Papers Addressing Stock Counts for RMS and SIM

Inventory accuracy is a critical and highly sensitive area affecting retailers, and it has a significant impact on increasing levels of customer service, reducing costs, and enhancing productivity. Stock counts are one of the main tools retailers have to ensure their perpetual inventory is accurate. Oracle Retail has published two new documents on My Oracle Support ( that provide partners and retailers with deeper functional information about stock counts in Oracle Retail Merchandising System (RMS) and in Oracle Retail Store Inventory Management (SIM).

Oracle Retail Merchandising System Stock Counts Overview (1536804.1)

This document provides an overview of the primary functions and features of the Stock Count module in Oracle Retail Management System (RMS) as well as an overview of the integration of this module with Oracle Retail Store Inventory Management (SIM) and Oracle Retail Warehouse Management System (RWMS). This white paper covers numerous topics around stock counts including:

  • Scheduling stock counts
  • Creating stock count requests
  • Inventory snapshots
  • Uploading count results
  • Reviewing, updating, and accepting count results
  • Updating and reviewing the value of a count
  • Processing value results
  • Reviewing the month end process
  • Batch processes related to stock counts
  • System level settings related to stock counts

Oracle Retail Store Inventory Management Stock Counts Overview (ID 1541449.1)

All stock counts in SIM follow a similar process flow. The general process of taking a stock count begins with the setting up of a product group (with the exception of Ad Hoc stock counts). When a product group is created, it can be named in any way that is meaningful to the user. A group can be a way to logically group the items, such as by department or a specific section of a store. After the product group is set up, the user must schedule the stock count. When the schedule date is reached, the stock count appears on the Stock Count List screen. The user can then perform the stock count.

Topics in this White Paper include the following:

  • Stock count functional overview
  • Types of stock counts
  • Stock count configuration
  • Creating, scheduling, generating, and starting stock counts
  • Counting and recounting
  • Processing third party results
  • Viewing and updating rejected items
  • Authorizing a stock count
  • Updating stock on hand (SOH)
  • Stock-count related process flows
  • Tables and batches used for 'unit and amount' stock counts
  • Glossary

Friday Nov 30, 2012

Announcing Key Functional White Papers for SIM and ReIM

Oracle Retail has published two new documents on My Oracle Support (  that provide partners and retailers with deeper functional information about two products: Oracle Retail Store Inventory Management (SIM) and Oracle Retail Invoice Matching.

Oracle Retail Store Inventory Management Item Configuration White Paper (Doc ID 1507221.1)

There is functionality within the Store Inventory Management system related to item configuration that spans across multiple concepts that apply to the application as a whole rather than to a specific area. This white paper covers numerous topics around item configuration including:

  • Item Transaction Levels
  • Item Long Description
  • Pack Size
  • Standard Unit of Measure
  • Standard Unit of Measure Conversion
  • Pack Items
  • Simple Pack Conversion Items (Notional Packs)
  • Ranging Items
  • Item Status
  • Non-Sellable Items
  • Type-2 Item Recognition
  • UPC-E Barcodes
  • Non-Inventory Items
  • Consignment and Concession Items
  • Quick Response Codes

Oracle Retail Invoice Matching Financial Transactions (Doc ID 1500209.1)

This document explains the financial transactions that are posted by Oracle Retail Invoice Matching (ReIM). The scope of the document is limited to ReIM transactions only, and does not explain Retail Merchandising System (RMS), Finance, or Account Receivable transactions.

ReIM follows the double-entry accounting standard, which works by recording the debit and credit of each financial transaction belonging to each party involved. Each transaction means a profit to one account (debit) and a loss to another account (credit).

Full invoice match processing is completed in ReIM with payment recommendations communicated to Oracle Accounts Payable. ReIM matches merchandise orders and receipts against merchandise invoices, performing automated and manual matching, as well as discrepancy-resolution processing. Matched invoices are posted to interface staging tables specifying the amount and date to pay, vendor, site ID, General Ledger Chart of Accounts (GL CoA) information, and payment terms. Other payables documents, including debit memos, credit memos and credit notes are also interfaced to Accounts Payable through the ReIM staging tables (IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL). For information about how ReIM engages in this processing, see the latest Oracle Retail Invoice Matching Operations Guide. Certain ReIM transactions are not interfaced to Oracle Payables, but instead are interfaced to Oracle General Ledger through the IM_FINANCIAL_STAGE table. When analyzing transactions posted through the staging tables, retailers should note the transaction type, Standard/Credit, as well as the sign in the amount field. Technically, a negative sign on a credit transaction changes the transaction to a debit entry, and vice versa. This document is concerned about the financial meaning of the transactions, and will avoid a discussion of negative numbers in T-charts.


The blog is designed to help retailers and partners receive regular updates about documentation releases at Oracle Retail.

Click here to subscribe RSS

Send your comments to us using the electronic mail address:


« April 2014