Oracle Retail Reference Model: User Guide Release 14.1.1 June 2015

Oracle® Retail Reference
Model
User Guide
Release 14.1.1
June 2015
Note: The following is intended to outline our general
product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Contents
Contents ............................................................................................................................. ii
Preface .............................................................................................................................. iv
Audience ................................................................................................................................ iv
Related Documents ............................................................................................................... iv
Conventions ........................................................................................................................... iv
1 Introduction .................................................................................................................... 1
Web Browser Requirement ....................................................................................................1
Web Browser Support .....................................................................................................2
Index to Business Processes ............................................................................................ 2
Vertical Process ................................................................................................................2
2 Process Modeling Standards ........................................................................................ 3
Process Groups ........................................................................................................................4
Standards Used .......................................................................................................................4
Symbols Used ..........................................................................................................................5
Retail Industry (Level 0)..................................................................................................5
Business Process Areas (Level 1) ...................................................................................5
Organizational Business Process Flows (Level 2) ........................................................5
Symbols for Levels 1 and 2 ............................................................................................. 5
Business/System Process Flows (Level 3) ....................................................................7
Examples of Processes .......................................................................................................... 11
Retail Industry Model (Level 0) .......................................................................................... 11
Business Area Process Models (Level 1) ............................................................................ 12
Multiple Groups ............................................................................................................. 14
Other Alternative Drawings ......................................................................................... 14
Level 1 for Business Area Models ................................................................................ 17
Organizational Business Process Flow (Level 2) .............................................................. 17
Business/System Process Flows (Level 3) ......................................................................... 17
Business/System Process Flow .................................................................................... 18
Business/System Process Flow (Level 2.5/3) ................................................................... 18
Relationship of Level 2s to Level 3s .................................................................................... 18
Example 1: 1:1 Higher/Lower Level ........................................................................... 18
Receive Inventory from Warehouse or Finisher (Level 2) ........................................ 19
Receive Inventory from Warehouse (Level 3) ............................................................ 19
Example 2: Supporting/Complimentary/Day in the Life ....................................... 20
3 Process Modeling Styles ............................................................................................. 23
Visio Templates and Shape Stencils ................................................................................... 23
Templates ........................................................................................................................ 23
Stencils ............................................................................................................................. 24
General Drawing Shapes ..................................................................................................... 24
Drawing Models ............................................................................................................ 24
Preferred Shape of Models ........................................................................................... 26
Appropriate Levels of Information .................................................................................... 27
Appropriate Information for Level 2 Functions ........................................................ 27
Organizational Units on a Level 2 Swimlane ............................................................. 28
Avoid Gateways on Level 2s ........................................................................................ 28
Appropriate Level of Information for Level 3 Functions ......................................... 28
Checklist for Appropriate Level of Detail .................................................................. 29
Sending Information to Other Applications ...................................................................... 29
Indicating Custom Integrations ................................................................................... 30
Labeling Applications Outside the Immediate Application ........................................... 30
Naming Functions................................................................................................................. 31
Connecting from One Flow to Another ............................................................................. 32
Appropriate Function Shapes for Assignments ........................................................ 32
Connecting from One Level 1 or Level 2 Flow to Another ...................................... 34
Connecting a Level 1 to Its Level 2s and 3s ................................................................ 35
Connecting a Level 2 to its Level 3 .............................................................................. 36
Sending Information from One Store to Another Store ................................................... 37
Depicting Two Versions of One Application .................................................................... 38
Drawing a Gateway .............................................................................................................. 39
Labeling Connections ........................................................................................................... 39
Drawing the End Event ........................................................................................................ 39
Information to Appear at the Top of Level 1s, 2s, and 3s ................................................ 40
Left Align All Text Box text ................................................................................................. 41
Create Flows for Administration Data/Parameters/Security ........................................ 41
Numbering and Naming Conventions .............................................................................. 42
Notes on Unique Folder Numbering .......................................................................... 43
Process Flow and Folder Naming Conventions ........................................................ 44
Communication When Crossing Lanes ............................................................................. 44
Separating Creation Versus Maintenance Processes ........................................................ 45
Copyright Notice in Template............................................................................................. 45
A Appendix: Additional Information ............................................................................. 47
Development of the Models ......................................................................................... 47
Maintenance of RRM ..................................................................................................... 47
Inaccuracies or Suggestions .......................................................................................... 47
Business Process Models ............................................................................................... 47
Modeling Notations used RRM ................................................................................... 48
Standard Retail Industry Process Models .................................................................. 48
Release of an Application ............................................................................................. 48
Contact ............................................................................................................................ 48
Oracle Applications Outside the Retail Global Business Unit ................................. 48
iii
Preface
This document provides information on the Oracle Retail Reference Model (RRM)
process modeling standards and style.
Audience
The intended audience is C-level decision makers (such as Chief Executive Officer/Chief
Information Officer/Chief Technology Officer) through system users, depending on the
level of the model.
For more information on the intended audiences of the Level 0 through Level 3 models,
see Process Modeling Standards.
Related Documents
For more information, see the following documents in the Oracle Retail Reference
Library Release 14.1.1 documentation set:
 Oracle Retail Reference Library Release Notes
 Oracle Retail Reference Model Installation Guide
The following documentation is available in the My Oracle Support Knowledge Base
(https://support.oracle.com). To download the documentation, use the following
Knowledge Base article numbers:
 1617507.1 for the 14.x Retail Reference Library files
 1564821.1 for the 13.x Retail Reference Library files
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated with
an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code in
examples, text that appears on the screen, or text that you enter.
iv
1
Introduction
The Retail Reference Model is one component of the Retail Reference Library. It is a
comprehensive collection of established, industry-leading business processes that guide
the retailers and implementers on the use of Oracle Retail solutions. The Retail Reference
Model is based on the input and experience that Oracle Retail and its partners have
gained in working with a wide range of retail customers. The processes align with Oracle
solutions, leverage industry standards, and help business units communicate with IT.
Process flows are created using Microsoft Visio. This enables retailer-specific business
processes to be managed and maintained.
Retailers can use process models as a starting point for implementations, to understand
the context and value that the business is trying to achieve during the implementation of
the software, and to understand and tailor the baseline process that will be used going
forward. Processes are the setup to understanding further levels of detail. They can also
be used to identify and prioritize scenarios or paths for testing and user training.
There are many challenges to business process modeling. While there are industry
standards to use common symbols, there are still challenges on how to model a process
to meet the defined objectives. This guide explains the methods in which the Retail
process models are depicted. It describes the design patterns and ensures consistency of
modeling in the Retail Reference Model. This guide is divided into the following
chapters:
 Process Modeling Standards
 Process Modeling Styles
Web Browser Requirement

The Oracle Retail Reference Model navigator tree points to the Microsoft Visio source
versions of models. The navigator and Visio source work best with Internet Explorer 8.0.
The source is built using Microsoft Visio 2007 and Microsoft Visio 2010 software.
Note: The source files have not been tested with older or
newer versions of Visio.
A Visio plug-in Viewer is available from Microsoft for use with Internet Explorer. If you
do not have either Microsoft Visio 2007 or 2010 software, you can download the Visio
Viewer from http://www.microsoft.com/en-us/download/details.aspx?id=21701.
You cannot either read or update the models without Microsoft Visio, Visio Viewer, or
any another tool that can read .vsd files.
The other modeling tool used to read .vsd files is OmniGraffle Pro version 5.4.3 on the
Macintosh Operating System.
Note: You cannot read .vsd files if Visio or the Visio Viewer
is not installed on your computer.
Introduction 1
Web Browser Requirement
Web Browser Support

The following sections explain the browser support functionality for Microsoft Visio.
Note: The navigator works differently with different

browsers.
Microsoft Internet Explorer

With Microsoft Visio 2007 or 2010 installed, Internet Explorer has the options to
Open, Save, or Cancel the files. If either Microsoft Visio 2007 or 2010 is not installed
and with only Visio Viewer installed, Internet Explorer navigates to the view-only
version of the Visio file.
Google Chrome
With Microsoft Visio 2007 or 2010 installed, Chrome has the options to either Keep or
Discard the Visio file. Without Microsoft Visio 2007 or 2010, Chrome navigates to the
file location folder.
Mozilla Firefox
With Microsoft Visio 2007 or 2010 installed, Firefox has the options to either Save File
or Cancel access to the Visio file. Without Microsoft Visio 2007 or 2010, Firefox
navigates to the file location folder.
Safari
The Safari installed on MAC OS navigates to the file location folder.
To read, view, and edit .vsd files, you must have OmnigrafflePro installed on your
computer.
Note: OmnigrafflePro does not support the hyperlinks

within the Visio source files..
Index to Business Processes

The Index to Business Processes in Retail Reference Model N.N.xls, or Excel Index.xlsx in
the collection, lists all offered models. Use Excel’s Filter functionality to locate models by
application or group (folder), or the Find functionality to look for specific words or
phrases in the names of models. The Index to Business Processes is located under the
Link section of the RRM user interface.
Vertical Process
In the Index to Business Processes in Retail Reference Model N.N.xls or Excel Index.xlsx
in the collection, see the Applicable to Verticals columns on the far right. Fashion,
Hardlines, Grocery, and Telco indicators are included in the index
2 Oracle Retail Reference Model

2
Process Modeling Standards
The process modeling standards explain the methods in which the Retail Reference
Models are depicted. The following are the three goals of process modeling:
 Adds business value:
– Significant to business to have impact (breadth and depth)
– Additional value not usually obtained through standard software package
 Improves return on investment:
– Lower total cost of ownership
– Lower implementation cost
– Speed implementation
– Speed organizational adoption
– Standardize most business processes
 Actionable:
– Target right people
– Target different groups
– Be used at right time
– Have correct breadth and depth
Process Modeling Standards 3

Process Groups
Process Groups
This table explains the different models and uses for the primary audience.
Name Description Primary Audience When to Use
Retail Industry A collection of  Executives Sales Cycle:

Models (L0) functional areas to  Support Insight Driven
describe the retail and Value sales
enterprise as a engagements.
whole.
 Show value and best
Business Process Conceptual  Executives practices that Oracle
Areas Models representation of  Directors supports.
(L1) one major business  Support the pre-sales
 Senior Managers
process area. demo, by first showing
process and then
Organizational Representation of  Directors
executing in the system.
Business Process logical part of an  Senior Managers
Flows (L2) end-to-end Implementation (Analysis and
 Managers Design Phase):
business.
 To understand the context
and value that the
business is trying to
achieve during the
implementation of the
software.
 Processes are the setup to
understanding the next
level of detail.
Business/System Represent the  Implementers Sales Cycle:
Process Flows activities and tasks  To show the additional
 Team Leads
(L2.5/L3) that are executed by value and details that
actor and system to  Users Oracle brings to the table.
complete the
 A detailed process
process.
evaluation workshop is
not appropriate during the
sales cycle. (That is an
Implementation task).
Implementation (Analysis and
Design Phase):
 To understand the
baseline process that will
be used going forward.
Standards Used
Two standards are used for depicting process designs. The right standards and symbols
are used to complete the business goals. Event-driven Process Chains (EPC) symbols are
leveraged for the Business Process Area Models (L1) and Business Process Flows (L2).
Object Management Group: Business Process Model and Notation (BPMN) is used to
describe the Business/System Process Flows (L2.5/L3).
The Symbols Used section explains the symbols that are used. This is by choice to
simplify the design patterns and to make them more widely actionable to the many
different business process skill levels across retailers.

Symbols Used
For more information on BPMN, see the following web site: www.bpmn.org.
Symbols Used
The Oracle Retail Reference Model uses the following types of models and symbols.
Retail Industry (Level 0)

In this level, a collection of functional areas are used to describe the retail enterprise as a
whole.
Symbol for Level 0

A single symbol is used for each area on the Level 0.
Symbol Description Used in Process

Groups
0 1 2 3
The Value-added chain denotes the 
Value-added chain business process grouping and value
area.
Business Process Areas (Level 1)

In this level, one major business process is represented in a conceptual way.
Organizational Business Process Flows (Level 2)

This level represents
Organizational elementsthe logical part of an end-to-end business process.
& Appl...
Symbols for Levels 1 and 2

Carries out & Supports
A subset of Event-driven Process Chains (EPC) symbols are leveraged at Level 1 and
Level 2.
Symbol Description
Organizational elements & Appl... Used in Process
Groups
0 1 2 3
The group within the business that is  

responsible for carrying out the task.
Organizational unit
Some examples include: Merchandising,
type Warehouse Operations, In Store
Operations, and Pricing.
The person is represented through the  

Organizational elements & Appl... Role role responsible for carrying out the task.
Some examples include: Allocator,
Planner, Buyer, and Store Manager.
The conceptual process step.  

Textbox of free-form text may be placed
Function underneath and grouped to functions, to

add clarification.
ries out & Supports

orts
Symbols Used

Groups
0 1 2 3
The conceptual process step that is  
important to the process but not
Process interface categorized within the current context of
the design (that is, within the immediate
folder/value-added chain structure). For
example, Replenishment processes create
orders. When speaking of replenishment,
the create order processes will be process
interfaces because they are stored under
the Purchasing Management area.
The Link to Visio shape used within the    

flow represents a hyperlink to another
process model within the collection.
The Link to Visio shape at the upper right
hand corner of the flow represents a
hyperlink to the Visio version of this flow
itself, when Visio is installed but the user
is browsing in the HTML version.
In some cases, a manual step is used to 1 1 
denote that the conceptual step is always
Manual task performed outside of any application
software.

Symbols Used
Business/System Process Flows (Level 3)

This level represents the activities and tasks that are executed by a person/role and
system to complete the process.
Symbols for Level 3

A subset of Business Process Modeling Notation (BPMN) symbols is used for Level 3.

Groups
0 1 2 3
User
Business process steps could be one of 1 1 
the following types:
Interaction
Function  Activity where the user must
interact with the system to continue
the process.
 Manual activity performed outside
Manual task the system.
o Manual may also be
used on Level 1 and 2
to indicate tasks that
are completely
Notification manual, such as a
Function human decision,
discussion, or
agreement step, which
would never be
performed in a system
Automated
(Oracle or otherwise).
Function
 Activity where the user must notify
others of a request or outcome.
 Automated activity executed by the
system.
A Pool represents a Participant in a 
Process. Also acts as a swim lane and a
Pool graphical container for partitioning a set
of activities from other Pools, usually in
the context of B2B situations. Examples
of pools include: Vendor, Enterprise (for
example, a retail enterprise), and
Customer.
A Lane is a sub-partition within a Pool 
Lane and extends the entire length of the Pool,
either vertically or horizontally. Lanes
are used to organize and categorize
activities. The Lane name is the Actor
who carries out the activities.

Symbols Used

Groups
0 1 2 3
Application system is the product. Thus, 
Application with the lane name, a lane is specific by
system the actor and the product in which the
activities are performed. One application
system is usually applied to a lane, but
exceptions may exist, such as where
multiple applications use the output of
another lane (for example, a demand
forecast may be used by multiple
applications).
A Gateway is used to control the  

divergence and convergence of multiple
sequence flows. Thus, it determines
branching, forking, merging, and joining
Gateway of paths. Gateways need not be
questions, but can be OR, AND/OR, or
AND too.
OR– One path can be taken
AND/OR– One or multiple paths can be
taken. One need not be taken before
another.
AND– Both paths must be taken. One
path need not be taken before another.
While there are different BPMN

accepted gateway symbols for OR,
AND/OR, and AND. The Retail
Reference Model uses the generic
symbol and text to denote the type of
gateway. It does not expect every end
user to know the BPMN standards.
An event is something that happens 
during the course of a business process.
Start event These events affect the flow of the
process and usually have a cause
(trigger) or an impact (result). There are
three types of Events, based on when
they affect the flow:
Timer (start event)
 Start
 Intermediate
 End

Symbols Used

Groups
0 1 2 3
While there are several variations on 
start, intermediate, and end events for
Intermediate event BPMN, not all symbols are used. The
generic start, intermediate, and end
events (no middle symbol) can always
be used with a description. Some symbol
Timer (intermediate event) events are allowed to give visual
representation to some of the events as
well as to take advantage of some active
BI modeling.
Start Timer and Intermediate Timer are 

used to precede steps that must be
End event periodic or that involve a wait, such as
for a periodic/timed update of inventory
positions, a nightly upload of sales data,
or a wait to count stock until all
receiving tasks have finished.
[The other sub-shapes are removed
although the edit does not show clearly.]
Grouping of activities is done to provide 
Group
additional information about the specific
group.
Text Annotations are a mechanism for a 

modeler to provide additional
Annotation
information for the reader.
A Textbox of free-form text may also be
placed underneath and grouped to
functions, to add clarification.
This is used either to reference an 
Subprocess outside process held in another drawing
(collapsed) or it can reference an expanded
subprocess within the same drawing. It
will usually be the former.
The LinktoVisio hyperlink shape is used
to enter the link to the other process.

Symbols Used

Groups
0 1 2 3
For a process that is repeated several 
Subprocess times within the same process, an
(expanded) expanded subprocess can be used. The
expanded process will have an entire
process located within itself. Expanded
processes are located on the same
drawing (but in a reference area, like a
key) as the collapsed process.
The LinktoVisio hyperlink is not used, to
distinguish that the detail is found
within this flow.
Place a Group around the subprocess
expanded steps, and use a Start and End
as appropriate for the subprocess.
Data Objects are considered Artifacts 

because they do not have any direct
Data
objec t effect on the Sequence Flow or Message
Flow of the Process, but they do provide
information about what activities require
to be performed and/or what they
produce. Some examples include a
report, a paper Purchase Order, Bill Of
Lading, or invoice.
The Link to Visio shape used within the    
flow represents a hyperlink to another
process model within the collection.
The Link to Visio shape at the upper
right hand corner of the flow represents
a hyperlink to the Visio version of this
flow itself, when Visio is installed but
the user is browsing in the HTML
version.
Client-specific Denotes a customization that must be   
implementation examined with the retailer.
APP
01
An out-of-the-box integration that can be 
enabled in the field by an implementer,
from or to a Retail Global Business Unit
(RGBU) application. Appears in the
Integration Layer swimlane, and
hyperlinks to an integration solution
catalog entry.
APP An integration that must be enabled or 
01
customized in the field by an
implementer. Appears in the Integration
Layer swimlane, and hyperlinks to an
integration solution catalog entry.

Examples of Processes

Groups
0 1 2 3
Integration Guide Link shapes are 
placeholders for future links to entries in
the Retail Reference Architecture
Integration Guide. The Integration
Guide Link shapes will appear in
Integration Layer swimlanes on Level 3
process flows in conjunction with
Automated process steps.
Examples of Processes
The following sections provide examples of how a few processes are modeled. This
provides guidance when creating the models.
The sections do not explain how all the symbols listed above should be used or when to
use them. For more information on symbol usage and examples, especially for level 3, see
the following web site: www.bpmn.org.
Not all BPMN symbols are used. This is to simplify the design patterns and to make them
more widely actionable to the many different business process skill levels across retailers.
Retail Industry Model (Level 0)

The Retail Industry Model (Level 0) is a high-level picture of the business processes
within a retail industry. The model is a high-level grouping and categorization of
processes. There is only one level 0 for the entire retail industry. It categories processes
that are unique for retail, for example, retail store operations.
The processes that are found in every business (for example: human resources, strategic
planning), as well as processes that are found in every industry but have a unique aspect
within retail (for example: workforce scheduling).
The following is the summary for the Retail Industry Level 0:
 Only one level exists for the Retail Industry
 Grouping of Processes
 Covers the Entire Retail Enterprise

Business Area Process Models (Level 1)
Level 0 - Retail Industry

A collection of functional areas to describe the retail enterprise as a whole, using Value Added Chain notation.
Strategy and Planning

Merchandise
Plan and Market Business Planning Planning, Marketing Supply Chain
Strategic Planning
and Forecasting Optimization, and Planning Planning
Foundation
Retail Operations
Make Sourcing and Production

Product Operations
Development Management
Vendor and Deal Purchasing

Buy Management Management
Inventory Transportation Warehouse

Move and Fulfill Management Management Management
Consumer /
Sell and Service Direct to Business to
Store Operations Customer
Consumer Business
Services
Operations Support
Business
Risk Management
Management Financial Control Store Life Cycle Indirect Fixed Asset
and
and Control and Reporting Management Procurement Management
Loss Prevention
Human Resources Workforce Workforce Compensation

Management Recruiting
Deployment Management Management
Level 0 – Retail Industry

Like the Retail Industry model (L0), a Business Process area model is a grouping of
processes. The differences between the two breadths are:
 L0 Retail Industry Models covers the entire retail industry.
 L1 Models cover a business area.
Since business area is abstract, and there are business areas within business areas, there
can be several level 1 models for a particular business area. In addition, a L1 (Business
Area Model) assigns the process to an organizational area. For example, within the Retail
Industry Model is a box/symbol representing Inventory Management.

When expanding the process, it has several business areas, such as Manage Allocation,
Manage Replenishment, Manage Warehouse Receiving, and others. The Inventory
Management is a Level 1. Manage Allocations has several process groupings within
itself, such as Create Allocation, Allocate Inventory for New Store, Manage End of Life
Inventory, and others. Manage Allocations is another Level 1 design. It is a business
process area. For more information, see the diagram Retail Industry, Inventory
Management, and Manage Allocations.
Retail Industry, Inventory Management and Manage Allocations

The diagram Retail Industry, Inventory Management, and Manage Allocations shows
how multiple level 1s exist in a drill-down capability. This is to highlight a key point of
the modeling; the levels are not levels in a hierarchy, but levels of information.
A Level 1 is a business process area. It is a logical grouping of business processes
assigned to an organizational unit. It does not matter that a level 1 drills down to another
level 1, if it is being done to represent logical groupings of business processes.
There are two other key factors within a level 1. Some processes have multiple owners.
For example, the process Manage Physical Inventory Counts is assigned to the Financials
group in the Level 1 Inventory Management Model. But still Warehouse Operations and
Store Operations are very much involved in the process.

Multiple Groups
The rule is that when multiple groups are involved, the overall owner of the process is
assigned. As the process area is broken down, the other owners are assigned to their
processes. So for Manage Physical Inventory Counts, Financials is the overall owner.
When it is drilled down into, the execution processes are owned by the Store and
Warehouse groups.
Another key point of level 1s is their representation. A level 1 does not need have a
process flow, but the process flow is expandable. For example, the Inventory
Management Process Area represents every piece as a single box and the Manage
Allocations Level 1 has one section that flows and which contains many sections of
single boxes. Again, the purpose of the level 1 is a collection of processes within a
particular area. If those processes have a logical sequence between them, then they
represent with it; otherwise they will not.
Other Alternative Drawings

The other alternative drawings are explained in the following sections:
 Header and Related Process Grouping
 Entire Process
 Pick Right Drawing Pattern
Header and Related Process Grouping

The point of a level 1 visually depicts the business process area. There are numerous
ways to achieve this. The following diagram shows the header grouping and related
processes for other processes.
Organizational elements & Appl...

Wholesale customers = Franchisee,
Header Grouping
Corporate Owned Stores,
Wholesale stores sold to
Manage Manage Manage
Product Manage Wholesale
Manage Product Wholesale Manage Sales Wholesale Transport Wholesale's Manage Retail
Development / Customer Offers / Manage Returns
Catalogues Customer's Agents Plan Operational Merchandise Customer Services
Sourcing Funds / Allowances
Orders Finance Service
Plan Agents Allocate / Manage

Manage Manage Vendor
Analyze Plan & Manage Wholesale Sales Manage Tax Transfer Customer
Perform CPFR with Assortment for Pass-Through Manage Manage
Marketplace, Stock Rules Targets & Setup (VAT) Merchandise to Shipment
Manufactures / Customers Funds Customer Promotional
Trends, Prior Regions Customers Returns
Vendors / Customers Capture & Setup Displays
Performance
ex: Customer rejected
Manage Manage Manage Sales Wholesaler's Merchandise
Customer Price Wholesale Commission Manage Invoice Ship and Deliver during receipt
List & Suggested Manage Product Initiated Funds / Accurals & & Billing Product Manage Service Provide Retailer
Create Concepts Specific Requests / Shelf Space
Retail Price Offers Payments
in-line with Commitments Complaints Assistance
Market and Mange Customer
Brand Image Returns to
Manage Manage Sales Wholesaler
Manage Manage Receipt
Wholesale's Agents
Collections & & Proof of Manage Service Provide Retail
Manage Product Customer Fund Performance vs. Customer returns of
Capture Orders Discrepencies Delivery Level Sales Demand &
Build Product / Alternatives Compliance Plan "shop" merchandise
Finalize Product Agreements Price Assistance
Details
Wholesale Including: Manage
Operations Available to Promise (ATP), Manage Returns
Customer Manage Credits
Drop Shipped, to Manufacturer / Manage
Requested and Refunds
Source Product Vendor Customer Order
Manage Alternative Item, Funds
from Inquiry
Wholesale Self-Service Entry
Manufacturers /
Vendors Customer Offers
/ Funds / Manage
Allowances Manage Mobile Transportation, Manage
Sales Freight, Volume Royalties Customer
Manage Pre- Manage Product
Allowances Performs Self-
Production & Recalls
Service
Generate Similar to DSD,
Samples Trunk Sales, Manage

& Jobbers Manage Credit
Customer
LInes Setup &
Requested
Availablity
Allowances Manage Vendor /
Manage Product Salvage
Fulfill Orders Customer Overall
Production Merchandise
Commitments
Financial
Including Drop Shipped, Document
Cross Dock, Management
Transfers, etc.
Manage Manufacturer Approve Orders

/ Wholesale Selection with Credit Manage / Define
& Compliance Check Company
Payment Terms
Manage Order
Changes /
Cancellations
Manage
Customer Order
Inquiry
Manage
Wholesale Cash
and Carry Related Processes according to the grouping
Manage
Wholesale's
Customer's
Inventory
Monitor & Fulfill
Setup Monitor Inventory
Wholesale's Manage Mobile
Parameters to Parameters and
Customer's Sales
Monitor Inventory Effectiveness
Inventory
Similar to DSD,
Trunk Sales,
& Jobbers
Header Grouping
Related Processes according to the grouping
Header and Related Grouping

Entire Process
In other situations, there are instances where the entire conceptual process is shown. In
this case the level 1 and level 2 are grouped together to show the entire process. This type
of drawing only works given two conditions:
1. The entire level 1 is a sequential flow.

2. The entire level 1 and all level 2s are owned by the same organizational unit.
Other

With this drawing, the level 1 is a trunk and the level 2s are the branches. The level 1 can
either be drawn vertically or horizontally throughout the entire process. The level 2s are
the extensions. For more information, see the diagram Assortment Management process.
Level 1 information
Level 1 information
Level 2 information
Level 1 information
Level 1 information
Level 2 information
This area represents Level 1 Information.

This area represents Level 2 Information.
The details of this area is discussed in the next section.
Assortment Management process

Zooming in on the blue area in the above process shows the name of the process and also
the steps required to complete the process. For information on the highlighted blue area,
see the diagram Details of Level 1 Process, which is different from the Header Grouping
diagram.
In header grouping, the header grouping was to group similar processes together. They
were not sequential. In this example, the top box is the name of the process and the boxes
underneath are the steps to complete the process. There is also a slight difference in how
it is depicted. This drawing shows the boxes with arrows flowing in order from top to
bottom and back to the top. The Header and Related Grouping diagram has a single
arrow from the header box into each box underneath. Also, to help depict the grouping,
it is drawn slightly offset from the top box.

Name of the Process
Sequential Steps required for the process as described by the name.

(In this example it is the steps to "Develop Store Clusters for Assortment")
Details of Level 1 Process
Pick Right Drawing Pattern

To pick the right drawing pattern is not possible to achieve and a single drawing pattern
may not fit all process areas within a collection of models. The approach for drawing a
level 1 is to ensure it logically depicts all the business processes that are involved in the
area. The number of different drawing patterns allows the modeler to pick the most
appropriate pattern for the process area.

Organizational Business Process Flow (Level 2)
Level 1 for Business Area Models

The following are the summary for the business area model Level 0:
 Represents the entire process set for the business area.
 Assigns processes to an organizational group.
 Represents levels of information, not level in a hierarchy (such as, a level 1 can drill-
down to another level 1).
Organizational Business Process Flow (Level 2)

This business process model depicts the business process that is executed by the
organizational unit (or role). This process represents what needs to be done to execute a
process and who needs to do it. Structurally, largest difference between a level 1 and a
level 2 is that a level 2 must flow from beginning to end. See the example below of a
Create Allocation. In this example, a role Allocator is used, but often it is represented only
by an Organizational Unit.
The following is the summary for the Organizational Business Process Flow Level 2:
 Business Process aligned to an organizational unit or role.
 It must flow from beginning to end.
 The same level 2 can be used for multiple level 1 process boxes.
Allocator
Business/System Process Flows (Level 3)

Business/System Process Flow depicts both the business and system interaction to meet
the process. This flow shows:
 Who executes the process.
 The tasks or activities needed to complete the process.
 The system in which the steps are executed.
The largest point is that a business/system process flow is not a drill-down from a L2.
Rather it is a parallel process that targets different users and is to be used for different
purposes than the L2. It is targeted for users/team leads and for implementations. Hence,
it has more detailed information than a level 2, but both a level 2 and a level 3 describes
the end to end process.
An end to end process is a cross functional, cross application flow that points to other
processes at the same level (Level 2) or further detail (Level 3). The process represents a
broad business flow. Oracle or non-Oracle applications within that flow may or may not
be integrated with each other. A connection does not imply integration. Each end to end
process should be reviewed in conjunction with its supporting detail processes, to see
how varying applications may work together to fulfill the business process.

Business/System Process Flow (Level 2.5/3)
The diagram Business/System Process Flow explains the details for Create Allocations.
Business/System Process Flow

The following diagram shows the business/system process flow.
Business/System Process Flow

Also, a Business/System Process Flow uses a different standard than the L1 and L2. This
uses Pools and Lanes as defined by BPMN. A single lane is unique by the
system/actor(role). The Pool of the design is the participant of the process. The retail
enterprise or Enterprise is considered one participant. Others include Vendor, Customer,
Finisher, Bank, or those other outside entities.
Business/System Process Flow (Level 2.5/3)

The following is the summary for business/system process flow (Level 2.5/3):
 Business Process aligned to a role and system.
 Parallel Process, not a drill down.
 Designed to show more detail, but show the entire process.
Relationship of Level 2s to Level 3s

A Level 2 (higher/lower Level) does not need to be 1:1 with a Level 3
(supporting/complimentary). Varying relationships may exist depending on the
perspective from which each level is drawn. Any combination can be used, to best
represent the considerations involved for the organizational unit and that particular area
of business processes.
 A Level 2 Organizational Business Process Flow may be a higher level (1:1) depiction
of a Level 3 Business/System Process Flow (Example 1).
 A Level 2 may use one or more Level 2s or Level 3s as the supporting detail for
accomplishing the process flow–almost a day in the life of the organizational unit or
role with regards to that business area (Example 2).
Example 1: 1:1 Higher/Lower Level

The Level 3 Receive Inventory from Warehouse is a more detailed perspective of the
Level 2 Receive Inventory from Warehouse. In this case, a 1:1 relationship between the
Level 2 and Level 3 exists. There are also assignments to more flows that support
resolution of the inventory receipt, such as labeling and put away.

Receive Inventory from Warehouse or Finisher (Level 2)

The diagram below represents receive inventory from warehouse or finisher (level 2).
Receive Inventory from Warehouse or Finisher (Level 2)
Receive Inventory from Warehouse (Level 3)

The diagram below represents receive inventory from warehouse or finisher (level 2).
Receive Inventory from Warehouse (Level 3)

Example 2: Supporting/Complimentary/Day in the Life

Level 2s may provide a different perspective on the high level functions involved in a
business process area, with other Level 2s or Level 3s serving as supporting detail, for a
day in the life perspective of the organizational unit or role.
For example, Vendor and Deal Management level 2s also represents a breadth of
Merchandising considerations when managing deals and rebates:
 Negotiate Long Term (Annual) Deals.
 Negotiate Short Term (Promotion or One-Time Buy) Deals.
 Negotiate Funds for Promotions - Supplier Initiated.
 Negotiate Funds for Promotions or Markdowns - Retailer Initiated.
 Process Deal Terms and Entry.
 Process Supplier funded Promotion Entry.
 Process Supplier funded Markdown Entry.
 Process Rebates.
 Execute Pass-Thru Amounts for Franchisers/Wholesalers.
Level 2 Negotiate Long Term (Annual) Deals points to the Level 2 Process Deal Terms
and Entry, which points to Level 3 Create Deals and Rebates and Level 3 Maintain Deals
and Rebates. All of these flows help the audience understand the set of considerations
involved in negotiating, setting up, and maintaining deals and rebates, both from the
business system hands off approach, and the system steps that support the business
process.
Level 2 Negotiate Long Term (Annual) Deals

Level 2 Process Deal Terms and Entry
Create Deals and Rebates

3
Process Modeling Styles
This chapter provides instruction for generating a Retail Reference Model (RRM). It
provides the steps for using the Microsoft Visio templates and shape stencils to generate
Visio models.
Visio Templates and Shape Stencils

The Retail Reference Model utilizes specific Visio templates and stencils in order to
maintain its process and visual standards. To edit existing process flows or to create new
ones that comply with the Oracle Retail standards, the templates and stencils must be
available on the individual’s computer.
The templates and stencils are available within the Supporting Collateral folder in the
Retail Reference Model folder of the RRL download.
To access the templates, download the RRL using the following, use the following link:
https://support.oracle.com.
Templates
The following templates are used to create models in Visio using the Oracle Retail styles
and methodology:
 EPC_RGBU_TemplateDDMMYY.vst: With this Oracle Retail template, you can
create Level 1 and Level 2 process flows.
 BPMN_RGBU_TemplateDDMMYY.vst: With this Oracle Retail template, you can
create Level 1 process flows.
You can also save the existing model to a new model:
 All shapes are sampled on each page of the .vst, so that you can copy and paste
instead of drawing.
 If you want to create a completely new drawing using Microsoft Visio, select File
menu, New, and then Business.
Use the following templates:
– For Level 1 and Level 2 use EPC Diagram (Metric)
– For Level 3 use Basic Flowchart (Metric)
Note: An option is set for you to choose your own template.

In order to import the template, you must be aware of the
Business Process Model and the Business Process
Architecture.
Local Directory for Template

Save the templates (.vst) to your local drive along with your other Visio templates in a
location on your computer. You can save under Libraries>Documents>Templates or
C:\Documents and Settings\<userid>\Templates.
If Template folder does not exist, either create one or place the file in any another
directory (for example, Libraries>Documents>My Shapes).
Process Modeling Styles 23

General Drawing Shapes
Access the Template

To access the template in Microsoft Visio, select File menu, New and then New Drawing
from Template. Select Template from Location in which it was placed.
Stencils
A Visio stencil holds a collection of shapes that are common in use (that is, all of the
Oracle Retail Business Process shapes):
 EPC_RGBU_Stencil_[Date].vss: Use this template to create Level 1 and 2 process
flows.
 BPMN_RGBU_Stencil_[Date].vss : Use this template to create Level 3 process
flows.
Local Directory for Stencils

Save the stencils (.vss) to your local drive with your other My Shapes in a location on
your computer. For example, Libraries>Documents>My Shapes or C:\Documents and
Settings\<userid>\My Documents\My Shapes.
Access the Stencil

From the File menu, select Shapes and then select the desired Stencil.
Setting for Stencils

Follow the instructions to set up the options for the stencils:
1. From the File menu, select Shapes and then select My Shapes.
2. Select the desired StencilVisio Snapping and Gluing.
3. Turn off the Snap be option to align shapes.
4. Turn off the Glue be option to keep lines straighter.
Naming the Page Within Your Visio File

Enter the flow name in the Visio page tab. This makes it identifiable when imported into
Business Process Architect and Business Process Management Composer.

This section provides the instructions for drawing the shapes in Microsoft Visio.
Drawing Models
Flows should move from left to right and from the top to bottom direction. You can also
draw steps in other directions, connect in a wrapping fashion to the beginning of the next
line of steps, or connect to preceding steps, but no steps should read from backwards
direction. You must follow the western style of reading, which is left to right and top to
bottom.

Left to Right Reading Style
Top to Bottom Reading Style
Swimlane

Swimlane - Bottom and Upwards

There will be occasions, particularly in crossing swimlanes, where the flow goes up to a
preceding swimlane, but the flow should not start from the bottom and read upwards.
Preferred Shape of Models

Models should generally read longer to the right, than taller, particularly where the
subject matter is transaction oriented. This makes the model read more like a timeline.
If the reader scrolls more than two pages to the right in order to read the model, or two
pages down, consider dividing the model where appropriate.
Return Merchandise
Primary Oracle Application: Point-of-Service
Description: The return merchandise function is performed on the POS terminal and is the activity in which the customers returns previously purchased merchandise for refund or credit. Returns are typically a high fraud are of the retail business process, thus additional validation
steps are taken to ensure that the merchandise was originally purchased and is returned in good resellable condition or has a manufactures defect for which the retailer may receive a credit from the supplier.
By validating the return against the original transaction, the system safeguards against fraudulant returns. In the case where this can not be done, the Returns Management system tracks customers return patterns. Using a rules based approach, Returns Management will
flag return transaction for customers that excessively present items for returns and alert store management during the ORPOS return transaction for an additional level of approvals.
Present items Present original No Obtain return

Customer Customer
for return receipt? receipt
Start event OR
Yes
Transaction No Select another

Print sales Give receipt to
Yes Total = 0? refund tender
receipt customer
OR
Applicable Apply refund Yes
Original Yes Validate return Yes Validate item is Yes Additional No Determine if Returns No Cash
Scan Receipt Look up original Enter return Item applied to Enter return Refund Tender
transaction item on original Items to taxes are Management validation tender amount
Bar Code transaction item returnable transaction reason code selected Commit E-Receipt
found receipt Return? applied needed to transaction Apply refund
OR OR OR OR OR OR transaction to feature
No tender amount
No No local database enabled?
to transaction AND
Yes Refund tender Debit purchases are OR
type determined refunded as cash
Advise customer
by original Paper receipt and
item is not
transaction tender Mail Check Yes Yes E-receipt Print receipt
returnable
Apply refund No
Check it customer is No Collect
Yes tender amount Look up Customer And
linked to transaction customer
to transaction Customer Found?
information
OR No Yes
OR
Alternate No Select Non- Yes Additional No Yes Applicable Authorize Approved
Ring up return Validate item is Apply item to Enter return Input customer Look up Customer Process Select Refund
Transaction Receipted Item Look up Items to taxes are return
item returnable transaction reason code ID Customer Found? Response Tender OR
Lookup... Return Return? applied transaction
OR OR OR OR OR Declined
Point-of- Referral Credit Send Credit Send Process
Cashier / Return Managment
Service Yes Authorization Authorization authorization
Sales Associate response identifies
(Client) Advise View Returns Request request response
Enter different Approve valid refund tenders
No customer item Management OR
transaction transaction E-Receipt Enter customer
is not... No Collect Response Log E-mail receipt E-Receipt send
receipt detail OR Approved
customer E-mail address to customer successful?
No On-Line to
information
Decline Store Server? End event
Apply tender
View Returns Credit request
Cancel amount to
Enter Managment time out?
Transaction transaction
Customer Response Log
Information Cancel
User defined response Stored Value Card Scan / Swipe Send activation Apply refund No
message is displayed to the Store Credit request for tender amount
Cashier and optionally printed card refund amount to transaction
on customer receipt. OR
Enter Credit / Alternatively, the manager can Yes
Debit / Check log onto the RM server via the
information browser to view the results of
the Returns Management Returns data Transaction
rules engine for details of why sent data sent
the request was not approved
Enterprise
Credit / Debit
Customer Returns Return Customer Credit / Debit
Customer Activate Mdse Activation Customer authorization Transaction
Look up item Return results Lookup Management Authorization Lookup authorization
Integration Layer Transaction Lookup Credit card response Lookup response data
Return results response Authorization response response request
Lookup
Customer
Point-of- Customer Receive Update Update
Point-of- Lookup Send
Service Itelm Lookup Lookup Returns data transaction Transaction Customer
Service Look up item response transactions
(Server) response data Database Database
Configurable timer,
typically set to 30>60...
Customer
Customer
Transaction Lookup Receive Record
Return results Lookup
Central Office Lookup response transaction transaction
Central Office
data data
Process Returns Update

Send
Returns Authorization Customer's
Returns Response
Management Returns history
Management
Process
Activate Store Send Activation
Tender Tender authorization Send response
Credit Response
Authoriztion Authorization Tender Authorization request
Service Service Service (non Oracle)
Copyright © 2010, Oracle. All rights reserved.
Preferred shape

Appropriate Levels of Information
Less Desirable Shape (wrapping flow should proceed to right instead)
Points to Remember
The following points must be considered while drawing:
 Is the model visually useful and legible?
 Does it need dividing into more than one model for readability?

This section explains on the appropriate information to be given at each of the levels.
Appropriate Information for Level 2 Functions

The function should be what the organizational unit does with the information, not what
a user does with the software, not how the user interacts with the software, and not how
the information is used by the software.
Level 2 – Store to Store Transfer
Points to Remember
 Focus must be given on what is required and not what is the system doing.
 Use business process terms, not system terms.
 What business step does the software enable, that might not otherwise be possible?
Such as, Allocate from purchase order prior to merchandise receipt.

Correct Incorrect
Load data Determine source of data

Obtain most recent sales data
Preprocess data Cleanse/prepare data
Generate alerts Correct discrepancies
Identify anomalies
Auto approve Review and approve
Organizational Units on a Level 2 Swimlane

If multiple organizational units own or share the information and process steps, they can
each be modeled on the Level 2 Swimlane.
The Organizational Unit should never be a system. For example, Forecast Engine should
be Forecasting Group or other appropriate group of personnel within the retail
enterprise.
Points to Remember
 Who owns the information that is being worked on, in the functions?
 What people are responsible for its creation, management, validity?
Avoid Gateways on Level 2s

These are allowed by Event-Driven Process Chain notations, but are not part of the
Oracle standards. For clarify, label the function’s connections.
Appropriate Level of Information for Level 3 Functions

The function should be what the user does with the software, not how the user interacts
with it. Appropriate functions are Modify price, Modify quantity, Remove item, and
others. The steps do not need to be detailed to the point of key presses.
Points to Remember
 If you were doing the task on another presentation device, an Iphone, or by
voice, or on a handheld unit. The appropriate level of information is the steps
needed to accomplish the whole task. The order or details may be different if the
screen or interface is different.
 A function should have meaning as a standalone description.
 A function should represent what’s going on in the business, not what the steps
are in the application. For example, see the following diagrams.
Avoid Excess Information

Sending Information to Other Applications
Right Level Information
Lot of Details
Right Level of Details

Major steps should be modeled. Issues or problems should not be modeled.
Correct Incorrect
Flush the RIB Process sales data

Snapshot sales data in RMS
Snapshot sales data in SIM
Checklist for Appropriate Level of Detail

Maintain the following checklist to maintain appropriate level of details in the flow
process.
Points to Remember
The following points are used to remember while deciding the process flows.
 Does the model accomplish the business process?
 Does it show how the process is executed within the confines of the system?
 Do I believe that it is effectively designed? Is there a way it could be streamlined
outside the system?
 Does it effectively show the business process within the enterprise?
 Is it negatively limiting the enterprise in any way? (If so, revise.)
Sending Information to Other Applications

To send information to other applications through the interface layer, draw a function for
each lane (sending application, integration layer, and receiving application). This helps
identify where an interface exists or may be needed.
Do not name the specific application in the functions themselves. The application is
already labeled on each swimlane in each model, and the retailer might have a different
application that would need to perform the same function, in which case they would
only need to change the application on the swimlane rather than check for the
application named within each function.

Labeling Applications Outside the Immediate Application
Correct Incorrect
Send inventory adjustment to RMS Send inventory adjustment information

Record inventory adjustment in RMS Record inventory adjustment
Update inventory in SIM Update inventory
Level 3 – Execute Store Inventory Adjustment
Note: RPM, MOM, and Merchandising are all on the same

database; therefore, data does not transfer through the
integration layer. If applications are on the same database,
do not model an Integration Layer between them, because
the integration is direct.
Indicating Custom Integrations

If a customized integration is required, indicate with an Annotation stating “Client
specific implementation” on the function in the Integration Layer lane.
Send Client-specific Send
tax calculation implementation tax calculation
request result
Labeling Applications Outside the Immediate Application

For the applications outside the immediate application (for example, if working on SIM
flows and SIM needs to send information to RPM/Retail Price
Management/Merchandise Operations Pricing Management), do name the specific
Oracle application (in the application box on the swimlane) rather than generalizing such
as “enterprise price management tool.” Even if the solution is not Oracle’s, similar
processes must be occurring in order to run the retail business and provide the needed
information. The retailer could choose to reflect a different solution in their own
customized copy of the processes if needed.

Naming Functions
Naming Functions
Each function should starts with a verb.
 On Level 1s and 2s, use Title Case. The initial capital letters for each significant word.
Note: That the rule was introduced in 2011; updates to

match this style are ongoing.
 On Level 3s, only the first letter of each function should be capitalized, unless
referring to a proper name, acronym, or another flow title.
The Save/Write/Selection functions do not need to include “in database.” (This is
implied by automated or UI function).
Level 2 – Receive Inventory from Store
Level 2 Process Flow

Connecting from One Flow to Another

The following sections explain about connecting from one flow to another with
assignments.
Appropriate Function Shapes for Assignments

When the process needs to go from one flow to another, draw as the function with a
Hyperlink (LinktoVisio).
 The Collapsed Sub Process shape (sample labeled Call Process) has a sample
hyperlink on it in the BPMN_RGBU_TemplateDDMMYY.vst. (Level 3).
 In the EPC_RGBU_TemplateDDMMYY.vst. (Levels 1 and 2) contains sample
hyperlinks on them in Steps 7 and 9 functions.
Instructions to Update the Hyperlink:
1. Add a LinktoVisio shape to the desired shape (Collapsed Subprocess on Level 3,
Function or Process Interface on Level 1 or 2).
2. Click the LinktoVisio shape you want to link.
3. From the Insert menu, click Hyperlinks (Ctrl + K). The Hyperlink window appears.
4. In the Address text box, browse through the Address.
5. Enter a Description (used in W3C readability standards for HTML).
6. Check the Use relative path for hyperlink option.
7. Repeat (with an additional LinktoVisio shape) to add a link to a second model (such
as a Level 3 in addition to a Level 2).
HyperLinks Window
8. To navigate to the links, move over the shape and right-click. You should see the
linked pages in the pop-up list. Icon and label show when you hover over a shape
that has a Hyperlink.
9. Right-click to see the labeled Hyperlink.
10. Click Hyperlink to navigate to it.

Hyperlink Page
Include one link to the Visio source document at the upper right of the flow pool
background.
Level 0 - Retail Industry
A collection of functional areas to describe the retail enterprise as a whole, using Value Added Chain notation.
Strategy and Planning

Merchandise
Plan and Market Business Planning Planning, Marketing Supply Chain
Strategic Planning
and Forecasting Optimization, and Planning Planning
Foundation
Retail Operations
Make Sourcing and Production

Product Operations
Development Management
Vendor and Deal Purchasing

Buy Management Management
Inventory Transportation Warehouse

Move and Fulfill Management Management Management
Consumer /
Sell and Service Direct to Business to
Store Operations Customer
Consumer Business
Services
Operations Support
Business
Risk Management
Management Financial Control Store Life Cycle Indirect Fixed Asset
and
and Control and Reporting Management Procurement Management
Loss Prevention
Human Resources Workforce Workforce Compensation

Management Recruiting
Deployment Management Management
Level 0 – Retail Industry

On a Level 3, the Hyperlink appears on a Collapsed Process shape.

Collapsed Process Shape

On a Level 1 or Level 2, the Hyperlink goes on the Function (if the flow is within the same
folder/group in the Retail Reference Model) or Process Interface (if the flow is within
another folder/group in the Retail Reference Model).
Collapsed Process Shape
Connecting from One Level 1 or Level 2 Flow to Another

If the related model is within the same high level (0) process area, then draw a Function
with a Hyperlink. (LinktoVisio).
Maintain Role
Maintain Role
If the related model is outside the high level (0) process area (folder group), then draw a
Process Interface with a Hyperlink. .
Step 8
Step Folder
Points to Remember
The following points are used to remember while deciding the process flows:
 Does the model accomplish the business process?
 Does it show how the process is executed within the confines of the system?
 Do I believe that it is effectively designed? Is there a way it could be streamlined
outside the system?
 Does it effectively show the business process within the enterprise?
 Is it negatively limiting the enterprise in any way? (If so, revise.)

Connecting a Level 1 to Its Level 2s and 3s

A Level 1 needs to have a function for every Level 2 modeled, even if a Level 2 calls
another Level 2.
On a Level 1, connect via an Assignment to both the level 2 and level 3 models for each
applicable function. For example, Level 1 Manage Store Inventory Counts – the functions
that correspond to a model have Assignments to both the Level 2 and the Level 3
versions of the model.
Level 1 – Receive Inventory at Store

Connecting a Level 2 to its Level 3

A Level 2 is a higher level depiction of the detail that is in a Level 3. The user may want
to view the Level 2 then view the Level 3 for more detail. Since any one function in the
level 2 may represent several steps in the Level 3, include a Function with a Hyperlink
holding the link to the Level 3.
Level 2 – Receive Inventory from Store

Sending Information from One Store to Another Store
Sending Information from One Store to Another Store

The lanes are: Store 1, Store 2, but the same application and actor. Label the two stores
and their lanes appropriately, using Freeform text. Left-align the Freeform text within its
boundaries.
Freeform Text

Depicting Two Versions of One Application
Depicting Two Versions of One Application

One store, one application, but separate tasks are performed on handheld and user
interface. (see Perform Ad Hoc Stock Count; this will also apply for the WMS flows).
Label the Application with Freeform Text. Left align the Freeform text within its
boundaries.

Drawing a Gateway
Drawing a Gateway
The choice indicated by a gateway should be described in the function preceding the
diamond, and labeled with a statement rather than a question, such as:
 Determine if
 Select whether
 Check that
The OR, AND/OR, or AND should be in capital letters, and should be placed below the
gateway, even if a line intersects it.
Usage of OR, AND/OR, or AND
Labeling Connections
If one of the connections is labeled, the other should be labeled, for example, Yes and No,
Printed and Not printed, and others. The label should be placed in a legible position
along the connector.
Drawing the End Event

The End Event should be positioned to the lower right of the model, since this is where
the reader will tend to look for completion, according to left-to-right, down-the-page
reading.
Even if this model goes to another model for completion of the full process, draw a
connector from that function with its Assignment, to the End Event indicator.
If the model spans multiple Pages within Visio, and legibility is improved by having
more than one End Event, you can have more than one End Event rather than connecting
to another Page in order to end the flow.

Information to Appear at the Top of Level 1s, 2s, and 3s
End Event
Information to Appear at the Top of Level 1s, 2s, and 3s

The following points must be considered:
 Level number of flow and name of flow
 A free form text with the name of the flow.
 A free form text with the Primary Oracle Application.
 A free form text Description, with the purpose of the process flow and any
considerations or assumptions that are not explicit in the flow.
Level 2 – Receive Inventory from Supplier

Left Align All Text Box text
Level 3 – Receive Transfer at Warehouse
Left Align All Text Box text

All Text Box text needs to be left aligned within its boundaries for consistency.
Create Flows for Administration Data/Parameters/Security

To create flows for the Setup of administrative data, parameters, or security may be
modeled but is a low priority, and only where it is critical for solution understanding or
setup.

Numbering and Naming Conventions

The numbering convention used by the RGBU is as follows:
 Functional Domain = 01 and up followed by a decimal point.
 Level of diagram = 01 through 03 followed by a decimal point.
 Folder number within the Functional Domain and Level (Conceptual or Activity) =
00 and up.*
 Unique diagrams = 01 and up. The number of unique diagrams created at each level.

Notes on Unique Folder Numbering

Subfolders within 00 Conceptual Flows and 01 Activity Flows are numbered such that
the superset of subfolders is equal and in the same order, and as if all lower level
subfolders are expanded.
Unique Folder Numbering

If a subfolder does not have any flows, the folder numbering may appear to skip.
No Flows in the Subfolder

The unique numbering within 00 and 01 folders both starts with folder 01 and count
upwards. The number that represents the level of the flow maintains the uniqueness,
between Conceptual and Activity flows. Therefore, to ensure this uniqueness, do not
place a Level 3 Activity Flow in the 01 Activity Flows folders (root) and also have flow(s)
in a subfolder within 01 Activity Flows. This would cause flows at two levels to share the
same unique folder ID of 01, and hence the model numbering would not be unique.

Communication When Crossing Lanes
Unique Numbering
Process Flow and Folder Naming Conventions

Do not use / or \ or ‘ (apostrophe) in your process flow name or folder name. This
causes an error when attempting to export the process flow for publication or for use in
the browser-based viewer. Each word in the process or folder name must begin with a
CAP, again no special characters, dashes, and so on.
Examples:
Correct: 01.02.03.04_NegotiateLongTermAnnualDeals
Incorrect: 01.02.03.04_ NegotiateLongTerm(Annual)Deals
Correct: 02.03.04.05_CreateAndOptimizePrePack
Incorrect: 02.03.04.05_Create&OptimizePre-Pack
Communication When Crossing Lanes

Wherever the flow crosses to another pool that is an actor, there is a communication,
such as manually if person to person, or notification by email generation. This helps to
delineate where the application informs the user to perform the next step versus a human
doing so.
A notification function or automated function can be used for communication:
 If the system generates communication, such as an alert or email, use an automated
function.
 If a user must do the notification, such as by sending an email or fax or by placing a
phone call, use a notification function.
 An automated function and notification function might occur in parallel, if data or
notice is sent by the system, but a recipient user also must be told to check their
system for information in order to perform a task.

Separating Creation Versus Maintenance Processes
Separating Creation Versus Maintenance Processes

Create versus update or maintenance processes need only be separate models if the
business process is dramatically different, such as with large downstream affects of
updating an item’s department or classification, or changing a price.
Copyright Notice in Template

The copyright notice is included at the lower right corner of each model. Next to the
copyright notice date is a Last Updated date, indicates when the process was last
updated.
Level 1 – Business Process Flow
Level 3 – Business Process Flow

A
Appendix: Additional Information
This appendix provides additional information regarding the Retail Reference Model and
its offering in Microsoft Visio.
Development of the Models

The models were built with the knowledge gleaned from Oracle Retail’s Functional
Architects, Product Managers, Strategy, Consulting, and Presales. Partner implementers
added their application input and experience during model development. The models
are refined from ongoing feedback by all of the above and Oracle customers.
Maintenance of RRM
Solution Management product managers are responsible to ensure that their associated
product process models are updated as needed per release. You can send questions
regarding model maintenance to [email protected].
Inaccuracies or Suggestions
For any inaccuracies or suggestions for the updates, corrections, or improvements in
RRM, send an email to [email protected].
Business Process Models

The Retail Reference Models are available with the download of the Retail Reference
Library. RRL is complimentary to licensed Retail customers and certified partners. My
Oracle Support sign-on credentials are required.
To access the RRL, perform a search on My Oracle Support for “Retail Reference
Library.” You can also submit a question to [email protected].
Appendix: Additional Information 47

Copyright Notice in Template
Modeling Notations used RRM

The notations used are adapted from standards appropriate for the intended audiences,
as follows:
 Level 0: The Association of Retail Technology Standards Plan/Buy/Move/Sell
representation of Service Oriented Architecture, using value-added chain notations
 Levels 1 and 2: Event-driven Process Chain notation
 Level 3: Business Process Modeling Notation
For more information on the notations used, and the standards and intended usage, see
Process Modeling Standards.
Standard Retail Industry Process Models

There is no widely available, industry standard set of best practices, hence Oracle’s
creation of the Retail Reference Model. Modelers of the Oracle RRM have participated in
the Association of Retail Technology Standards (ARTS) efforts to develop a standard set
of retail industry models.
Release of an Application
For the Retail Reference Model, two release updates are planned throughout the calendar
year, reflecting updates for new releases of applications, feedback collected from usage,
and addition of new process models. The Retail Reference Model process updates are
always published after the Generally Availability of a new solution or solution release.
Contact
For additional information and questions, send your request to
[email protected].
Oracle Applications Outside the Retail Global Business Unit

There are Oracle applications outside of the Retail Global Business Unit. My Oracle
Support’s Knowledge Base holds business processes applicable to other Oracle
applications. Samples include, but are not limited to the following:
 PeopleSoft business process maps
 EPM business process maps
 Siebel Business Process Documentation Library
 JD Edwards business process models
Use the Search Knowledge Base field to search for applicable processes by name or
application name.

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright © 2015, Oracle. All rights reserved.

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.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.

Oracle Retail Reference Model: User Guide Release 14.1.1 June 2015

Uploaded by

Copyright:

Available Formats

Oracle Retail Reference Model: User Guide Release 14.1.1 June 2015

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Retail Reference Model: User Guide Release 14.1.1 June 2015

Uploaded by

Copyright:

Available Formats

Oracle® Retail Reference

Web Browser Requirement

Web Browser Support

Note: The navigator works differently with different

Microsoft Internet Explorer

Note: OmnigrafflePro does not support the hyperlinks

Index to Business Processes

2 Oracle Retail Reference Model

Process Modeling Standards 3

Name Description Primary Audience When to Use

Retail Industry A collection of  Executives Sales Cycle:

4 Oracle Retail Reference Model

Retail Industry (Level 0)

Symbol for Level 0

Symbol Description Used in Process

Business Process Areas (Level 1)

Organizational Business Process Flows (Level 2)

Symbols for Levels 1 and 2

The group within the business that is  

The person is represented through the  

The conceptual process step.  

Function underneath and grouped to functions, to

Process Modeling Standards 5

Symbol Description Used in Process

The Link to Visio shape used within the    

6 Oracle Retail Reference Model

Business/System Process Flows (Level 3)

Symbols for Level 3

Symbol Description Used in Process

Process Modeling Standards 7

Symbol Description Used in Process

A Gateway is used to control the  

While there are different BPMN

8 Oracle Retail Reference Model

Symbol Description Used in Process

Start Timer and Intermediate Timer are 

Text Annotations are a mechanism for a 

Process Modeling Standards 9

Symbol Description Used in Process

Data Objects are considered Artifacts 

10 Oracle Retail Reference Model

Symbol Description Used in Process

Retail Industry Model (Level 0)

Process Modeling Standards 11

Level 0 - Retail Industry

Strategy and Planning

Make Sourcing and Production

Vendor and Deal Purchasing

Inventory Transportation Warehouse

Human Resources Workforce Workforce Compensation

Level 0 – Retail Industry

Business Area Process Models (Level 1)

12 Oracle Retail Reference Model

Retail Industry, Inventory Management and Manage Allocations

Process Modeling Standards 13

Other Alternative Drawings

Header and Related Process Grouping

Organizational elements & Appl...

Plan Agents Allocate / Manage