You are on page 1of 19

In-Store Merchandise and

Inventory Management

SAP Best Practices for Retail (France)

SAP Best Practices

Scenario Overview 1

Purpose and Benefits:

These components of the SAP SAP ECC Retail System are used in the store.
Together with the central SAP SAP ECC, they form a complete retailing system.
Procurement, goods movement and sales postings make up the mass business
of a store. With SAP Retail Store, these postings can be executed by employees
directly in the store.

Low running costs and hardware requirements
Use of standard technologies
Intuitive, easy-to-use user interface
Business processes designed for store needs
Integration into central merchandising & accounting system
Scenario Overview 2

Purpose and Benefits:

Key process flows covered

Store to store stock transfer
Physical inventory count
Goods movements
Goods receipt
Scenario Overview 3

SAP Applications Required:

SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows

Retail Masterdata Manager
Retail Store Manager
Retail Warehouse Clerk
Retail Promotion Planner
Retail Purchaser
Process Flow Diagram Master Data
Retail Sales Person

Check User Log-on to SAP

Parametres Retail Store

Create/change Apply for new Change sales price Check Assortment

customer master article list
Master Data Person HQ

Create new article Assortment list
Process Flow Diagram Purchasing and Goods
Retail Sales Person

Create purchase
Create stock Post goods receipt order to external Post goods receipt
transport order vendor
Retail Store Manager
Retail Walrehouse Clerk

Create Outbound Create and confirm Post goods issue

Delivery transfer order
Process Flow Diagram Physical Inventory
Retail Sales Person

Create physical
inventory Count articles
Retail Store Manager

Post differences
Process Flow Diagram Allocation
Retail Purchaser

Create followon
Create Allocation documents
Retail Store Manager

allocation Create Allocation
quantities table
Retail Walrehouse Clerk

Create outbound Create and confirm Post goods issue

delivery transfer order
SAP Retail Store Landscape

SAP Retail Store

purchasing activities
inventory management
IDES Smart Retailer Inc.
master data support

Sales data
cashier statistics

POS Server
converter at night:
article and price

Menu groups in SAP Retail Store
Internet Transaction Server
Purchasing process of the store

Order data

Store Head Office

or delivery

goods issue

DC Vendor
Replenishment in SAP Retail Store

Head Office

Purchase requisition
Replenishment run SAP Retail Store
Quantity Quantity Stock Open Material
proposal receipts
10,000 10,000 0,000 100,000 PCS-01-
9,000 9,000 0,000 90,000 PCS-01-
8,000 8,000 0,000 0,000 PCS-01-

Planning by visual
Goods receipt in SAP Retail Store

Vendor Head Office

goods issue

Goods movements in the store


Store Head Office

stock store 1 stock store 2

xxx xxx


stock Other Store
Inventory in SAP Retail Store

counting articles

Store Head Office

inventory result
inventory book inventory
xxx ? xxx

physical inventory scanner

count inventory count
Sales process

sales order order

Store Head Office Vendor


Promotion information

external Business Information

bonus buy systems
free-goods table
conditions order

volume-rebate promotion
goods receipt
Price calculation

additional goods issue

catalog order
processing processing
assortments POS incoming

Symbol Description Usage Symbol Description Usage Comments


Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
Payable Clerk or Sales Representative. This band contains tasks Diagram

can also identify an organization unit or group, common to that Diagram

rather than a specific role. role. Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario. Hardcopy / Document: Identifies a Does not correspond to a task
printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External Events: Contains events that start or end the Document generated by a task step; this

scenario, or influence the course of events in the shape does not have any outgoing
to SAP

scenario. flow lines

Financial Actuals: Indicates a Does not correspond to a task

Flow line (solid): Line indicates the normal sequence Connects two financial posting document step in a document; instead, it is
tasks in a Financial used to reflect a document
of steps and direction of flow in the scenario. scenario generated by a task step; this
Flow line (dashed): Line indicates flow to infrequently-
Actuals shape does not have any outgoing
process or a
used or conditional tasks in a scenario. Line can non-step event flow lines
also lead to documents involved in the process flow.

Business Activity / Event: Identifies an action that Does not Budget Planning: Indicates a Does not correspond to a task
either leads into or out of the scenario, or an outside correspond to a budget planning document step in a document; instead, it is
Business Process that happens during the scenario task step in the used to reflect a document
Budget generated by a task step; this
Activity / document
Planning shape does not have any outgoing
Event flow lines

Unit Process: Identifies a task that is covered in a Corresponds to

step-by-step manner in the scenario a task step in Manual Process: Covers a task Does not generally correspond to
the document that is manually done a task step in a document;
Unit Process Manual instead, it is used to reflect a task
Proces that is manually performed, such
s as unloading a truck in the
warehouse, which affects the
process flow.
Process Reference: If the scenario references another Corresponds to
scenario in total, put the scenario number and name a task step in
Process here. the document Existing Version / Data: This block Does not generally correspond to
Reference covers data that feeds in from an a task step in a document;
Existing external process instead, this shape reflects data
Version / coming from an external source;
this step does not have any
Sub-Process Reference: If the scenario references Corresponds to Data incoming flow lines
another scenario in part, put the scenario number, a task step in
Sub- name, and the step numbers from that scenario here the document
Reference System Pass / Fail Decision: This Does not generally correspond to
System block covers an automatic a task step in the document;
Pass/F decision made by the software instead it is used to reflect an
ail automatic decision by the system
Process Decision: Identifies a decision / branching Does not that is made after a step has been
point, signifying a choice to be made by the end usually Decisio executed.
user. Lines represent different choices emerging correspond to a n
Proces from different parts of the diamond. task step in the
s document;
Decisio Reflects a
n choice to be
made after step