Вы находитесь на странице: 1из 55

Oracle Retail Merchandising

System

Foundation Data

Presenter:

Date:

T-PT0108/04 Copyright 2005 Wipro Technologies Wipro confidential 1


Index
Foundation Data - Introduction

Foundation Data
Organization Hierarchy
Merchandise Hierarchy
Supplier Maintenance
Other Foundation Data
Questions

T-PT0108/04
Foundation Data - Introduction
Data required for almost all business operations
Organizational Elements:
Stores;
Warehouses (WH);
Merchandise Elements:
Merchandise Levels;
Items;
Suppliers;
Currencies;
Language;
Calendar;
VAT;

ORMS promotes the central definition of all Foundation data to


be shared thru the company;
The main advantage is to avoid the creation of the Foundation data in
other systems loosing the control of it.

T-PT0108/04
Organization Hierarchy
Company
Chain
Area
Region
District
Store
Warehouse
Organization Hierarchy (1)

Creates the system relationships that are necessary to support


the operational structure of a company.

Allows client to define the names for each level of the


hierarchy (except the last level Store and Warehouse).

Each level can be assigned to an individual responsible, for


that area of the business (except the high level).

To accommodate an unused level, it must be defined with a


one-to-one relationship, to the level above.

Reporting can be done at all levels of the organizational


hierarchy.

T-PT0108/04
Organization Hierarchy (2)

T-PT0108/04
Organization Hierarchy (3)

T-PT0108/04
Organization Hierarchy - Company

Highest level of the


organizational
hierarchy.

Only one company per


instance of ORMS.

Shared by both the


organizational and
merchandise
hierarchies.

The Database table


name is Comphead

T-PT0108/04
Organization Hierarchy - Chain

Used to distinguish
brands or trading
names within a
company.

The application allows


up to 9,999 chains.

The Database table


name is Chain

Chain attributes:
Chain Number (Client defined)
Description (free form text)
Manager name (free form text)
Currency (used for reporting)

T-PT0108/04
Organization Hierarchy - Area
Typically
used to
define a
geographical
grouping
within a
chain.
An area will
only belong
to one chain.
The
application
allows up to Area attributes:
9,999 areas. Area Number (client defined)
The Description (free form text)
database Manager name (free form text)
table name Currency (used for reporting)
is Area Chain Number and Name that Area is associated with
Location traits - Options (used for reporting)

T-PT0108/04
Organization Hierarchy - Region
Typically
used to
define a
geographical
grouping
within an
area.
A region will
only belong
to one area
The
application
allows up to Region attributes:
9,999 Region Number (client defined)
regions. Description (free form text)
The Manager name (free form text)
Database Currency (used for reporting)
table name is Area Number and Name which the Region belongs to
Region Location traits Options (used for reporting)
T-PT0108/04
Organization Hierarchy - District
Typically used
to define a
geographical
grouping
within an
region.

One district
will only
belong to one
region.

Up to 9,999 District attributes:


districts are District Number (client defined)
allowed. Description (free form text)
The Database Manager name (free form text)
table name is Currency (used for reporting)
Region Region Number and Name that District is associated with
Location traits Options (used for reporting)
T-PT0108/04
Organization Hierarchy - Store
The retail location

One store will only


belong to one
district

The application
allows up to
9,999,999,999
stores

After store creation


at on-line, a batch
program needs to
run
The Database table
name is store
NOTE:
- Unique Tran.No.By: Uniqueness of POS transactions numbers by Store or Store/Register;
- Integrated POS: Whenever is implemented OReSA this should have Y value;
- Org Unit ID: This field is only available if your organization uses Oracle Financials, version 11.5.10 or later;
- Stockholding: Indicates if the store will be a physical or a virtual store. Its not possible to do transfers with
virtual stores;
- Walk Through: During the receiving process, goods may come into the receiving area shared by multiple
"walk-thru" stores. If store A is designated as walk-through store for store B, the reverse is not necessarily true.
T-PT0108/04
Org. Hierarchy Store Options Menu (1)
Store Attributes
A form that is used for customized store attributes needed by the client that
are interfaced to legacy systems

Store Department Area


Form used to define selling square footage by department
Used in reporting

Location Traits
Client defined traits that are used to do alternate store groupings outside
the Organizational Hierarchy
Promotions
Location Lists
ORMS Reporting

Assign Competitors
Competitor name and locations near this store.
Competitive Shopping Module
ORPM

T-PT0108/04
Org. Hierarchy Store Options Menu (2)
Activity Schedule
Defines the days that the store is closed for Receiving, Shipping and Sales
Replenishment
Sales Audit
Warehouse Management

Store Data
Defines what data Sales Audit should be expecting to import from the store
as well as what data Sales Audit should be exporting for this location

Delivery Schedule
Defines the delivery schedule (frequency days and times) to the location
from both warehouses and Vendors
Replenishment

Geocodes
Defines the Sales Tax Geography Code of the location

T-PT0108/04
Org. Hierarchy Store Options Menu (3)

T-PT0108/04
Organization Hierarchy - Warehouse
Defines a physical
storage, cross-dock,
and/or distribution facility.

Can be optionally tied to


any level of the
organizational hierarchy
for reporting.

Activity schedule for


shipping and receiving
can be defined.
The Database table name
is WH
NOTE:
- Break Pack Warehouse: A distribution center that receives merchandise from a vendor, divides the
merchandise per individual store order, and ships the smaller quantities to the store;
- Redistribution Warehouse: When selected, indicates that the warehouse is used to receive items on a
purchase order when the actual distribution is yet to be determined;
- Inbound handling days: The number of days that the warehouse requires to receive any item and get it to
the shelf so that it is ready to pick.

T-PT0108/04
Org. Hierarchy WH Options Menu (1)
Attributes
A form that is utilized for customized warehouse attributes needed by the client
that are interfaced to legacy systems

Activity Schedule
Defines the days that the warehouse is closed for Receiving and Shipping
Replenishment

Delivery Schedule
Defines the delivery schedule (frequency days and times) to the location from
both warehouses and Vendors

Virtual Warehouses (required if Multi Channel)


Defines the virtual warehouses (stockholding locations within RMS) that are
available within the physical warehouse
The Finisher field indicates if the virtual warehouse is used for finishing
At Options we can find:
Warehouse/Inventory Attributes Parameters of Replenishment, Investment
Buy and Stock Management;
Warehouse Department Parameters some finance parameters by department.

T-PT0108/04
Org. Hierarchy WH Options Menu (2)

T-PT0108/04
Organizational Hierarchy Multi-
Channel
To distinguish locations (Stores and WHs) by business channels
(Physical Store, Websites, Catalogues, etc.);

One store belongs to only one channel;

Defined at setup and may not be changed;

In multi-channel environment, each physical WH must have one or


more virtual WHs (associated to a channel);
For Reception area, Storage area, RTV area, Expedition area, and
others;

Each virtual WH must be associated with a channel;

Virtual WHs are treated like stockholding and belong to a physical


WH that is non-stockholding;

The business can use Multi-Channel to track the inventory and


T-PT0108/04
profitability.
Organizational Hierarchy Multi-
Channel
There are 4 scenarios available:

Single Channel Retailer / Mono-Channel RMS Multi-Channel Retailer / Mono-


Channel RMS
STORE

SUPLIER WH(P) STORE SUPLIER WH(P)

WEBSTR

Single Channel Retailer/ Multi-Channel RMS Multi-Channel Retailer / Multi-


Channel RMS WH(P)
STORE
WH(P) Ph_St(L)
SUPLIER STORE SUPLIER
Ph_St(L)
Vi_St(L) WEBSTR

Ph_St Physical Stores


Vi_St Virtual Stores
(P) WH Physical
(L) WH Logical
T-PT0108/04
Organizational Hierarchy - Transfer Legal Entity

This functionality facilitates the set up of separate legal entities and


the movement of goods from one corporate entity to another, while
employing a single repository for stock ledger data and visibility to
inter-company margins.

The transfers between different legal entities is sent to the General


Ledger (GL) for the financial operations.

The ORMS does not send this store attribute to the ORDW (i.e. it
wont be possible to do analysis based on this attribute).

Its a parameter to be defined at the ORMS setup and cannot be


changed later.

T-PT0108/04
Organizational Hierarchy example

T-PT0108/04
Merchandise Hierarchy
Company
Division
Group
Department
Class
Subclass
Merchandise Hierarchy (1)

Defines relationships within the system for product


management, financial support and productivity report.

Support of performance reporting by grouping items within the


Company.

Maintenance of the stock ledger accounting method is defined


at the department level.

Allows client to define the name for each level of the


hierarchy.

Each level can be assigned to an individual responsible for


that area of the business.

T-PT0108/04
Merchandise Hierarchy (2)

T-PT0108/04
Merchandise Hierarchy (3)

T-PT0108/04
Merchandise Hierarchy - Company

Highest level of the


merchandise hierarchy.

Only one company per


instance of ORMS.

Shared by both the


organizational and
merchandise hierarchies.

T-PT0108/04
Merchandise Hierarchy - Division
Defines types of
merchandise at the
highest level.

The application allows up


to 9,999 divisions.

The database table name


is Division

T-PT0108/04
Merchandise Hierarchy - Group
A group will only belong to
one division.

The application allows up


to 9,999 groups.

The database table name


is groups

T-PT0108/04
Merchandise Hierarchy Department
(1)
Level at which key inventory
information is tracked and
reported (most important).

A department will only belong


to one group.

The application allows up to


9,999 departments.

The database table name is


deps

T-PT0108/04
Merchandise Hierarchy Department
(2)
Markup Calculation Type:
Determines whether the markup on items are calculated as a percentage of
the cost or the retail price:
% Cost: Markup = ((RP CP)/CP) * 100
% Retail: Markup = ((RP CP)/RP) * 100

Used when creating new items and the system suggests a retail based on
which calculation type is defined at the department level as well as the
Markup % that is defined.

Profit Calculation Type:


Used to determine how to update the fields of ORMS Stock Ledger tables, e.g.
Month Data table:
Direct Cost the fields will be updated with the Cost of the item;
Retail Inventory the fields will be updated with the Retail of the item.

T-PT0108/04
Merchandise Hierarchy Department
(3)
Purchase Type:
Each department, either contain all:
Normal items:
Purchased from a supplier before being for sale
Inventory on hands are maintained for all items in the department

Consignment items:
Purchased from the supplier only when the goods are sold to the customer
Inventory on hands are not tracked for these items

Concession items:
The goods belongs always to the supplier, the retailer only rents the space
Inventory on hands are not tracked for these items

Note: The way that we have to know if the items are Normal,
Consignment or Concession is accessing to their Dept and see this
Purchase Type value.

T-PT0108/04
Merch. Hierarchy Dept. Options Menu
(4)
User Defined Attributes (UDA)
Client defined attributes that link items together for reporting and selection.
Ability to set as mandatory for all items in this department
Ability to set a default value
Flow to Data Warehouse

Store/Department Area
Tracks total area of department per store
Tracks effective date for use in major floor moves
Can be used for reporting purposes
Flows to Data Warehouse

Up Charges
Utilized to attach internal charges to the cost of items during transfer of
merchandise

VAT Maintenance
For each VAT region a default VAT code for the department must be specified

T-PT0108/04
Merch. Hierarchy Dept. Options Menu
(5)

T-PT0108/04
Merch. Hierarchy Dept. Options Menu
(6)

T-PT0108/04
Merchandise Hierarchy Class (1)
A class will only belong to one Department.

Allows up to 9,999 Classes.

Class Options Menu


User Defined Attributes
Merchandise Hierarchy Defaults
T-PT0108/04
Merchandise Hierarchy Subclass (1)
A sub-class will only belong to one Department/Class.

The application allows up to 9999 Subclasses.

Subclass Options Menu


User Defined Attributes
Merchandise Hierarchy Defaults
T-PT0108/04
Merchandise Hierarchy example

T-PT0108/04
ORMS Hierarchies

Organization Merchandise
Company

Division
Chain OTB Group

Area Department
Stock
Class
Ledger
Region
Subclass

District
Transaction
Data ITEMS
Warehouse Store

T-PT0108/04
Suppliers

Supplier Maintenance
Suppliers (1)
A Supplier is an organization that provides products / materials that
the retailer will pay for the product. It is uniquely identified by a
number up to 10 digits

Every orderable item must have a primary supplier

Possible to Activate/Inactivate suppliers


Cannot raise Purchase Order to inactive suppliers

Supplier costs are entered by Item/Country but can also be entered


by Item/Country/Location

Supplier information affects:


Purchase Orders
Returns
Automatic Replenishment
Electronic Data Interchange (EDI)
Contracts
T-PT0108/04
Suppliers (2)
A Suppliers can be maintained by a specific team in the Finance department and
integrated at ORMS by RIB or directly in ORMS (main menu, Control >> Supplier)

VMI (Vendor Managed


Inventory) is used to allow
a supplier to manage the
inventory levels of
designated product at the
Warehouse. Inventory data
is shared with the supplier
and Inbound POs will be
generated in worksheet or
approved status

EDI (Electronic Data


Interchange) is the method
of communication used
between ORMS and
supplier to provide
information related to store
sales and Inventory
information

T-PT0108/04
Suppliers (3)

Supplier Inventory Management


Supplier related information, to be defaulted to items
Can be entered by:
Supplier
Supplier/location
Supplier/department
Supplier/department/location
Lead times (to be defaulted to item/supplier/country level)
Pick up lead time (to be used if company picks up the
merchandise)
Supplier minimums
Replenishment defaulting attributes
Scaling and truck splitting constraints

T-PT0108/04
Suppliers Attributes

EDI support
Required documents
Addresses and contact information
Import attributes
Language
Currency
Expenses
Payment terms
VAT region
Inventory Management levels
Bracket Costs
Delivery schedule
RTV acceptance
Invoice Matching information
Vendor Managed Inventory

T-PT0108/04
Suppliers - EDI support

ORMS includes the ability of exchanging data files with


suppliers using Electronic Data Interchange (EDI) standards

These are the types of transactions that can be processed:


Inbound:
New items and changes to items;
Supplier stock availability;
Purchase Orders / Revisions confirmations;
ASN (Advanced Shipping Notice);
Cost price changes;

Outbound:
Locations addresses
Purchase Orders and revisions
Sales and Stock reports
Contracts

T-PT0108/04
Suppliers Options Menu (2)

T-PT0108/04
Other Foundation Data
Languages
Partners
Currency
Exchange Rates
Value Added Tax
Languages

The system language of an Oracle Retail is defined in a system


parameter (System Parameter Maintenance Window).

The definition of language can also be made at user level:


Different users can interact with ORMS, according to their
preferences, in the following 9 different languages:
English
French;
German;
Portuguese;
Spanish;
Simplified Chinese;
Traditional Chinese;
Japanese;
Korean.

T-PT0108/04
Partners

A Partner is someone or something that has an association


with the company in different areas of the procurement
process.
Types of partners include:
Agents
Brokers,
Banks,
Freight forwarders,
Factories,
Manufactures,
Applicants,
Distributors,
Wholesalers,
Consolidators,
Consignees

T-PT0108/04
Currency
Primary Currency defined in the system setup (cannot be changed)

Local Currency defined from Chain level to Store and warehouse level

Supplier Currency used by default in purchase orders

Currencies are used in most of transactions. ORMS will automatically convert and
consolidate data between different currencies;

T-PT0108/04
Exchange Rates
The expectation is that the exchange rates and their effective dates are
fed from Oracle Financials.

Several types are


available, but only
Consolidated type is
really used others
require
customization!

T-PT0108/04
Value Added Tax (1)
ORMS VAT parameters includes the definition of VAT regions, VAT
types, VAT codes and VAT taxes qualified by effective date;

All these definitions should be made according to business needs

T-PT0108/04
Value Added Tax (2)
VAT regions and types are defined at Department level;

The VAT regions contain the VAT code and tax;

All locations and suppliers are linked to a certain VAT Region

T-PT0108/04
?

Thank You
T-PT0108/04