ORACLE DATA SHEET

ORACLE RETAIL REFERENCE MODEL

HELPING ACHIEVE BUSINESS VALUE
WITH ORACLE RETAIL APPLICATIONS
 Decrease time-to-value
 Reduce total cost of ownership
 Provide a baseline for differentiation
Projects to document an organization's business processes can consume
valuable time and resources, which are better spent on other efforts. The Oracle
Retail Reference Model offers a standard set of processes that correspond to the
Oracle Retail applications' generally available functionality, to help reduce
risk, speed implementations, and focus the retailer's customization efforts on the
specific processes that differentiate them in the marketplace.

Overview
ORACLE RETAIL APPLICATIONS
DESCRIBED The Oracle Retail Reference Model is a comprehensive collection of established, industry
The processes assume that at least one leading business processes which guide retailers and implementers on the use of Oracle
of the following Oracle Retail products will
applications to achieve greater business value. The processes support an implementation of
be implemented.
merchandising, stores, planning, and supply chain products, and act as a guide for both the
 Retail Merchandising System
business and implementation teams. The designs are created for a generic retailer, but with
 Retail Invoice Matching
inherent considerations for Hardlines, Fashion, Grocery, and Telecommunications.
 Retail Sales Audit
Process content is complimentary to customers who have licensed any Oracle Retail
 Retail Price Management
application. Ongoing updates and additions based on feedback, recent Oracle Retail releases,
 Retail Trade Management
and new applications, ensure that the retailer always has updated, comprehensive, field-
 Retail Allocations proven processes for retail operations.
 Retail Demand Forecasting
Assisting Retailers by Providing a Baseline Set of Processes to Customize
 Retail Fiscal Management
Without a set of documented business processes, retailers may lack a standard basis for
 Merchandise Financial Planning educating employees, identifying inefficiencies, or communicating changes. Processes may
 Store Inventory Management vary from store to store, warehouse to warehouse, department to department, or region by
 Point-of-Service region, with each working in different ways, which can counteract organizational efficiency.
 Back Office
Projects to document business processes are expensive and time consuming, with time,
money, and resources better spent on other efforts. The Oracle Retail Reference Model offers
 Central Office
a starting set of processes for the retailer and implementer to review, examine, and tailor for
 Markdown Optimization
the retailer's operations, in conjunction with an Oracle Retail implementation.
 Size Profile Optimization
Enhancing Speed to Value
 Macro Space Management
 The processes help shorten implementation time, by providing a standard,
 In-Store Space Collaboration
customizable starting set from which to work.
 Warehouse Management System
 The retailer can reduce Total Cost of Ownership through fewer modifications due
 Advanced Inventory Planning
to better alignment with Oracle applications.
 Item Planning/Clearance Optimization

 Returns Management
 The processes provide a baseline for differentiation, by enabling focus on process
areas that set the retailer apart from the competition, while taking other processes
 Regular Price Optimization
and features "out-of-the-box."
 Assortment Planning
Written for a Business Process Audience
 Replenishment Optimization
There are four general audiences for whom the processes are written:
 Category Management

 Financial Integration  Retail clients who have purchased and are implementing the Oracle Retail products

 Integrators and implementers who are implementing the Oracle Retail products

 Business analysts who want to understand how the systems can be applied to meet
their business solutions
 ORACLE DATA SHEET

RELATED PRODUCTS  System analysts and system operation personnel who need additional functional
 Oracle Retail Reference Library
understanding of the Oracle Retail products
 Oracle Retail Reference Architecture
 Business process flows are created and maintained in Microsoft Visio
 Oracle Retail Semantic Glossary

 Oracle Business Process Management

Targeting Levels of Detail by Audience
Suite Name Description Target
Audience
Retail Industry A collection of functional areas to describe Executives
Model the retail enterprise as a whole, using Value
(Level 0) Added Chain notation arranged according to
Plan and Market, Make, Buy, Move and
Fulfill, Sell and Service, and Enterprise
Operations.

Business Process Conceptual representation of one major Executives

Area Models business process area, using adaptation of
Directors
(Level 1) Event-driven Process Chain notation. May
be connected in a start-to-finish flow, Senior Managers
organized as unconnected process areas, or
any appropriate combination thereof.

Organizational Representation of logical part of a start-to-

Business Process finish business process, using adaptation of
Flows Event-driven Process Chain notation.
(Level 2)

Business/System Represent the activities and tasks that are Implementers

Process Flows executed by actor and system to complete
Team Leads
(Level 3) the process. Uses adaptation of Business
Process Modeling Notation symbols. Users

Contact Us
For more information about the Retail Reference Model business processes, please send an
email to retailprocess_ww@oracle.com.

2
 ORACLE DATA SHEET

c
SAMPLE PROCESS MODELS
The following process flows represent a sample of the information available, as supported by Oracle Retail applications. Samples from the
Plan and Market, Buy, Move and Fulfill, and Sell and Service areas are included. Refer to the Retail Reference Model detailed postings for
process flows in actual usage sizes and formats.

Level 0 - Retail
The Retail Reference Model level 0
shows the functional areas that describe
the retail enterprise as a whole, using
Value Added Chain notation arranged
according to Plan and Market, Make, Buy,
Move and Fulfill, Sell and Service, and
Enterprise Operations. The RRM Level 0
is based on an Association of Retail
Technology Standards model.

3
 ORACLE DATA SHEET

Level 1 Sample from

Business Planning and
Forecasting
Conceptual representation of the major
business process area:

Create and Adjust Merchandise

Financial Plan

Level 2 Sample from

Business Planning and
Forecasting
Conceptual representation of logical part
of end-to-end business process:

Create Top-Down Merchandise

Financial Targets – Pre-Season

Level 3 Sample from

Business Planning and
Forecasting
Activities and tasks executed by actor and
system to complete the logical part of an
end-to-end business process:

Create Top-Down Merchandise

Financial Targets – Pre-Season

4
 ORACLE DATA SHEET

Level 1 Sample from Vendor

and Deal Management
Conceptual representation of the major
business process area:

Manage Deals and Rebates

Level 2 Sample from Vendor

and Deal Management
Conceptual representation of logical part
of end-to-end business process:

Negotiate Long Term (Annual)

Deals

Level 3 Sample from Vendor

and Deal Management
Activities and tasks executed by actor and
system to complete the logical part of an
end-to-end business process:

Create Deals and Rebates

5
 ORACLE DATA SHEET

Manage Manage Store and

Manage Vendor Warehouse

Level 1 Sample from Plan Inventory Manage Manage Manage Manage Return Inventory Manage Logistics
Supply Chain to Vendors Recalls Adjustment Receiving and
in Advance Allocations Replenishment Transfers
Exceptions Adjustment
Exceptions

Inventory Management Manage

Physical
Finance
Conceptual representation of the major Inventory

business process area:

Manage
Execute Manage Store Manage Store
Manage Store Manage Store Returns to
Physical Receiving and Inventory
Vendor or
Inventory Management Inventory
Cycle Counts Adjustments Transfers Adjustments
Warehouse

Perform
Manage Shelf
Inventory and
Inventory (Pick
Information
to Replenish)
Lookups

In Store
Operations
Request Handle Store Manage Store
Print Labels
Store Price Managed Based Item
and Tickets
Change Inventory (Store Requests
Order Creation)

Manage Item
Unique Capture Item
Identification Basket
Numbers

Warehouse Manage Manage

Manage
Management Execute Physical Warehouse Warehouse Manage Dock and Manage Quality
Warehouse Cycle
Inventory Receiving and Inventory Shelf Inventory Assurance
Counts
Adjustments Adjustments

Manage Item
Order Unique
Merchandising Inventory Identification
Numbers

Level 2 Sample from

Inventory Management
Conceptual representation of logical part
of end-to-end business process:

Create Store Transfer at Store

Level 3 Sample from

Inventory Management
Activities and tasks executed by actor and
system to complete the logical part of an
end-to-end business process:

Create Store Transfer at Store

6
 ORACLE DATA SHEET

Level 1 Sample from

Store Operations
Conceptual representation of the major
business process area:

Store Operations

Level 2 Sample from

Store Operations
Conceptual representation of logical part
of end-to-end business process:

Return Merchandise

Level 3 Sample from

Store Operations
Activities and tasks executed by actor and
system to complete the logical part of an
end-to-end business process:

Return Merchandise

Copyright © 2014, Oracle and/or its affiliates. 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.