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.
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) 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.
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:
This white paper examines the requirements for 24x7 retailing and the suitability of RMS in specifically supporting 24x7 inventory availability.
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.
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.
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 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.
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:
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.