Vous êtes sur la page 1sur 90

SALES AND DISTRIBUTION

SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 1

-----

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 2

PRHPL
Name

Signature

PwC
Date

Name

Vaibhav Kumar

Anupam Biswas

Asheem Rath

Debesh Kumar Ghosh

Shriti Malhotra

Milan Gupta

Signature

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

Date

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 3

Contents
1.0 BUSINESS REVIEW OF PLANET RETAIL HOLDINGS PRIVATE LIMITED .............................................................................................. 9
1.1 PLANET RETAIL HOLDINGS-CONCEPTS .................................................................................................................................................... 10
2.0

OVERVIEW OF SD FUNCTIONS................................................................................................................................................................ 14

2.1

MASTER DATA ............................................................................................................................................................................................ 14

2.1.1

CUSTOMER MASTER .................................................................................................................................................................................................. 14

2.1.1.1 AS IS ....................................................................................................................................................................................................................... 14
2.1.1.2 TO BE ..................................................................................................................................................................................................................... 14
2.1.2
ARTICLE MASTER ........................................................................................................................................................................................................ 19
2.1.2.1 Definition ................................................................................................................................................................................................................... 19
2.1.2.2 Integration ................................................................................................................................................................................................................. 20
2.1.2.3 Article Type ................................................................................................................................................................................................................ 21
2.1.2.4 Planet Retail Scenario: ............................................................................................................................................................................................... 22
2.1.2.5 Article Master View: .................................................................................................................................................................................................. 24
2.1.2.6 Article Category ......................................................................................................................................................................................................... 26
2.1.2.7 Single Article: ............................................................................................................................................................................................................. 26
2.1.2.8 Generic Articles: ......................................................................................................................................................................................................... 27

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 4

2.1.2.9 Empties & Full Products ............................................................................................................................................................................................. 27


2.1.2.10 Structured articles.................................................................................................................................................................................................... 28
2.1.2.11 Planet Retail Scenario: ............................................................................................................................................................................................. 28
2.1.3
SITES ........................................................................................................................................................................................................................... 31
2.1.4

DISTRIBUTION CENTRE............................................................................................................................................................................................... 32

2.1.5

STORE ......................................................................................................................................................................................................................... 32

2.2

STOCK TRANSPORT ORDER..................................................................................................................................................................... 36

2.3

OUTBOUND DELIVERY DOCUMENT ..................................................................................................................................................... 36

2.4

PICKING ........................................................................................................................................................................................................ 37

2.5

POST GOOD ISSUE ...................................................................................................................................................................................... 37

2.6

POST GOODS RECEIPT AT STORE ........................................................................................................................................................... 38

2.7

RETURN HANDLING .................................................................................................................................................................................. 38

3.0

ORGANIZATION STRUCTURE .................................................................................................................................................................. 40

3.1

SALES ORGANIZATION ............................................................................................................................................................................. 40

3.2

DISTRIBUTION CHANNEL ........................................................................................................................................................................ 41

3.3

DIVISION ....................................................................................................................................................................................................... 42

3.4

SHIPPING POINT .......................................................................................................................................................................................... 42

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 5

4.0

DISTRIBUTION (WHOLESALE) ................................................................................................................................................................ 43

4.1

AS IS ............................................................................................................................................................................................................... 43

4.2

TO BE ............................................................................................................................................................................................................. 43

4.2.1 CUSTOMER MASTER ......................................................................................................................................................................................................... 43


4.2.2 SALES ORDER ( For outright sales) .................................................................................................................................................................................... 43
4.2.3

OUTBOUND DELIVERY ORDER ................................................................................................................................................................................... 44

4.2.4

BILLING DOCUMENT .................................................................................................................................................................................................. 45

4.2.5

CREDIT & DEBIT MEMO.............................................................................................................................................................................................. 45

4.2.6

RETURNS PROCESSING ............................................................................................................................................................................................... 45

4.2.7

PROCESS FLOW (WHOLESALE DISTRIBUTION) ........................................................................................................................................................... 46

4.2.8

CONSIGNMENT PROCESS ........................................................................................................................................................................................... 48

5.0

PRICING......................................................................................................................................................................................................... 52

5.1

AS-IS............................................................................................................................................................................................................... 52

5.2

TO BE ............................................................................................................................................................................................................. 52

5.2.1
5.2.1.1
5.2.1.2

WHOLESALE PRICING ................................................................................................................................................................................................. 53


CONDITION TYPE .................................................................................................................................................................................................... 53
CONDITION TABLE.................................................................................................................................................................................................. 54

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 6

5.2.1.3 ACCESS SEQUENCE ................................................................................................................................................................................................. 54


5.2.1.4 PRICING PROCEDURE ................................................................................................................................................................................................. 55
5.2.1.5 PRICING PROCEDURE -DETERMINATION ............................................................................................................................................................... 55
5.2.1.6 CALCULATION OF TAXES ........................................................................................................................................................................................ 56
5.2.2
RETAIL PRICING .......................................................................................................................................................................................................... 56

6.0

PROMOTION ................................................................................................................................................................................................. 57

6.1

AS IS ............................................................................................................................................................................................................... 57

6.2

TO BE ............................................................................................................................................................................................................. 58

6.2.1

PROMOTION TYPES: ................................................................................................................................................................................................... 58

6.2.2

COUPONS (GIFT VOUCHER) ....................................................................................................................................................................................... 60

6.3 RETURNS ........................................................................................................................................................................................................... 61


6.4 PROCESS FLOW ................................................................................................................................................................................................ 61
7.0

ASSORTMENT .............................................................................................................................................................................................. 64

7.1

AS-IS............................................................................................................................................................................................................... 64

7.2

TO-BE ............................................................................................................................................................................................................. 64

8.0

POS INTERFACE .......................................................................................................................................................................................... 69

8.1

AS IS PROCESS............................................................................................................................................................................................. 69

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 7

8.2

TO-BE PROCESS .......................................................................................................................................................................................... 69

9.0

LIST OF REPORTS (AS PER THE AS-IS)................................................................................................................................................... 72

9.1

CATEGORY WISE REPORTS ..................................................................................................................................................................... 72

9.2

LOYALTY (LYB) PROMOTION (TO BE TAKEN IN PHASE II) ............................................................................................................. 73

9.3

MANUAL REPORTS FROM STORE .......................................................................................................................................................... 76

9.4

POS REPORTS............................................................................................................................................................................................... 77

9.5

SALE ANALYSIS .......................................................................................................................................................................................... 81

9.6

WALK IN ANALYSIS REPORTS ................................................................................................................................................................ 83

9.7

WEEKLY DSR ............................................................................................................................................................................................... 84

9.8

EFFICIENCY REPORT GENERATION ...................................................................................................................................................... 86

9.9

MALL WISE SALES ANALYSIS ................................................................................................................................................................ 87

9.10

MARKDOWN & SALES WISE SALE ......................................................................................................................................................... 87

9.11

MONTHLY OPERATING SUMMARY ....................................................................................................................................................... 88

9.12 NEW STORE OPENING TRACING ............................................................................................................................................................ 88


9.13

NEXT_WEST_GATE_ATT.SHEET ............................................................................................................................................................. 89

9.14

VENDOR REQUEST FORM......................................................................................................................................................................... 89

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 8

10.0 OPEN & CLOSED ISSUES .............................................................................................................................................................................. 90


10.1 CLOSED ISSUES .............................................................................................................................................................................................. 90

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 9

1.0 BUSINESS REVIEW OF PLANET RETAIL HOLDINGS PRIVATE LIMITED


Planet Retail is Indias leading lifestyle retail group offering premium and famous international retail options to the Indian consumer.
Planet Retail Holdings Pvt. Ltd. formerly known as Planet Sports Pvt. Ltd. is the leading lifestyle retailer in India today offering premium and
famous international retail options to Indian consumers.

Currently Planet Retail Holdings Pvt. Ltd. brings to India famous fashion brands like Marks & Spencer, Guess, Next, etc. catering to Fashion/
Lifestyle retailing segment. The company has recently forayed into Department stores through Debenhams and the Health and Beauty segment
with the launch of The Body Shop.

Planet Retail has over 70 stores of various concepts spread across India with a total retail space of over 1 Lac sq. ft. It employs more than 700
people across its offices and stores.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 10

1.1 PLANET RETAIL HOLDINGS-CONCEPTS

PLANET RETAIL

PLANET RETAIL HOLDINGS PRIVATE


LIMITED

GUESS
MARCIANO
NEXT
ACCESORIZE
DEBENHAMS
FASHION CUBE

SUPREME TRADELINKS PRIVATE


LIMITED

QUEST RETAIL PRIVATE


LIMITED

THE BODY SHOP


SOLE EFFECT

MARKS & SPENCER

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 11

Planet Retail Holdings as a corporate group has the following companies:


PLANET RETAIL HOLDINGS PRIVATE LIMITED
SUPREME TRADELINKS PRIVATE LIMITED (100% subsidiary of Planet Retail Holdings private limited.)
QUEST RETAIL PRIVATE LIMITED
GUESS: Established in 1981, GUESS began as a jeans company and has since successfully grown into a global lifestyle brand. Today
GUESS designs, markets and distributes full collections of womens, mens and childrens apparel as well as accessories. GUESS is
distributed throughout the United States and Canada in fine department and specialty stores, its retail and factory stores, and on its online
store GUESS.com. GUESS has licensees and distributors in South America, Europe, Asia, Africa, Australia and the Middle East.
MARCIANO: Marciano is the new runway-inspired collection designed for the contemporary "it girl." Marciano represents pure
glamour in everyday fashion. From intricately detailed tops, to body conscious party dresses and well-constructed slacks and coats, the
collection offers a trend-setting variety of mix-and-match pieces that will take one from morning meeting to cocktail hour in style.
Marciano accessories, including boldly-coloured leather handbags, stunningly sexy footwear, and attention demanding jewellery, are a
key element of this A-lister lifestyle.

Pairing the highest quality construction and intricate craftsmanship with the most luxurious fabrics, the Marciano collection is

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 12

unmistakably sumptuous. Elegant silk chiffons, soft cashmeres, and finely decorated jacquards add sensual femininity to this decadent
line. As distinguished through such elements as delicate beading and beautiful jeweled button accents, great detail and care go into the
design of each piece. Designer denim in the latest washes and figure flattering silhouettes also plays a key role in the Marciano line. The
first brand extension from GUESS, Inc., Marciano follows suit in true GUESS style with apparel and accessories that are on the edge of
the fashion forefront.
NEXT: Next is a UK based retailer offering stylish, good quality products in clothing, footwear, accessories and home products.
ACCESSORIZE: In the early 1980's Monsoon started to sell a small collection of accessories which became so popular that the idea
for the innovative new store format Accessorize was born. The first Accessorize store opened in London's Covent Garden Piazza in
1984 and the second in Carnaby Street in 1986. 1992 saw the first Accessorize store outside London with a store opening in Manchester.
In the same year the first airport store was opened at Gatwick South terminal. Building on the company's phenomenal success, a store
opening programme began, averaging 16 new stores each year.
Today there are more than 240 Accessorize stores in the UK and a blossoming international operation of over 300 stores.
See a list of all Accessorize stores throughout the UK and the world here.
With its own in-house design team, Accessorize holds a unique position on the high street with its inspirational, globally sourced, wellpriced and good quality collection of fashion accessories. Displayed in an original and impactful colour-bay design, the constantly

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 13

changing range includes every kind of accessory imaginable; bags, purses, jewellery, belts, hats, scarves, flip flops, gloves, hair
accessories and cosmetics.
DEBENHAMS: Planet Retails latest concept, Debenhams, is targeted at style conscious customers. Tagged as 'Britain's Favourite
Department Store', Debenhams delivers its own brand of style, comfort, and practicality in its product offering.
Debenhams has made its debut at Ambience Mall, Gurgaon. This lifestyle department store concept from the UK offers shoppers over 20
British brands under one roof - with an offering ranging from exclusive designer fashion to modern, contemporary home-ware.
FASHION CUBE: It is the factory-outlet kind of concept from Planet Retail Holdings from which the other brands are sold.
MARKS & SPENCERS: This brand has over 600 stores located throughout the UK, this includes our largest store at Marble Arch,
London. In addition, the Company has 240 stores worldwide, including over 219 franchise businesses, operating in 34 countries. First
established in the UK in 1884, M&S now trades across 30 countries, employing over 60,000 people with a turnover in excess of USD 15
billion.
THE BODY SHOP: The Body Shop International plc is a global manufacturer and retailer of naturally inspired, ethically produced
beauty and cosmetics products. Founded in the UK in 1976 by Dame Anita Roddick, it has over 2,100 stores in 55 countries, with a
range of over 1,200 products, all animal cruelty free, and many with fairly traded natural ingredients.
SOLE EFFECT: This format deals brings famous footwear brands nearer to the customers.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

2.0

OVERVIEW OF SD FUNCTIONS

2.1

MASTER DATA

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 14

2.1.1 CUSTOMER MASTER


2.1.1.1 AS IS

W A - LEGAL
AGREEMENT.doc

W C - PAYMENT
TERMS.doc

W D - TAX
STRUCTURE.doc

2.1.1.2 TO BE

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 15

A Customer is a party who procures goods and services from a company. Two general types of customers can be differentiated in the system for
the logistic processes:
1) Internal customers (for example own sites)
2) External customers (for example wholesale customers who buy goods at a DC)
The Customer master record contains data that controls how business transactions are recorded and processed by the system. Customer master
records are also used to reflect as much information about the customers as possible whether internal (stores) or external (wholesale buyers).
This is to enable the company to know their customers and to make it possible that the company can offer special payment terms for specific
groups of customers. Standard account groups will be used for the creation of customer master.
As customers are also debit-side business partners in accounting, customer master records are used in Financial Accounting and Sales and
Distribution. Additionally, as sites are customers from the point of view of delivery, each site has a customer master record.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 16

Customer Master Records:


The customer master record consists of the General Data, Company Code Data and Sales & Distribution Data as shown in the figure.

1) General Data

2) Company Code
Data

3) Sales and
Distribution Data

1) General Data
General data does not depend on the company code, the sales and distribution organization or the purchasing organization. General data applies
to one business partner for all company codes, and in all sales areas and purchasing organizations.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 17

Customer Master General Data has following tab pages/sections & the fields in each tab pages are as under.
TAB PAGE /SECTIONS

DATA FIELDS

Address

Customer Name, Search Terms, Street No, Postal Code, City, Region, Country, PO Box Address,
Language, Telephone, Mobile No, Fax, Email Id, Contact Person

Control Data

Location Code, VAT Regn No, Transport Zone

Payment Transaction

Bank Details of the customer

Marketing

Annual Sales Figure, Employee figure

2) Company Code Data


Company code data only applies to one company code. This data is only relevant to Financial Accounting.
Customer Master Company Code Data has following tab pages & the fields in each tab pages are as under.

TAB PAGE/SECTIONS

DATA FIELDS

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 18

Acct Management

Reconciliation Account, Previous Account No

Pmt Transaction

Terms of Payment

Correspondence

Dunning Procedure

Insurance

Policy No, Amount Insured

3) Sales and Distribution Data


The data for one customer can differ for each sales area. The sales area is a combination of sales organization, distribution channel and division.
This data is only relevant to Sales and Distribution.
Customer Master Sales Area Data has following tab pages & the fields in each tab pages are as under.

TAB PAGE /SECTIONS


Sales

DATA FIELDS
Customer Group, Customer Pricing Procedure, Currency

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 19

Shipping

Delivery Priority, Shipping Conditions, Delivering Site, Partial Delivery Allowed.


Maximum Partial Delivery Allowed

Billing
Customer Credit Master

Invoicing Date, Inco Terms, Account Assignment Group, Tax Category, PAN No.

Customer credit limit master is maintained with separate transaction code as opposed to while creating customer master. The rights for creating
the customer master and credit master however will be given to the same user, generally from the finance department.

2.1.2 ARTICLE MASTER


2.1.2.1 Definition

The article master is the main source of data on articles in a company. The article master is an identification of an article. It contains information
on all the articles that a company procures or produces, stores, and sells. It is the company's central source for retrieving article-specific data.
This information is stored in individual article master records.
An article master record contains:
Descriptive data, for example, Article Description, Size & Weight

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 20

Control data, for example, Article Type


Data that is automatically updated by the system, for example, Moving Average Price, Warehouse Stock
Article master records also contain data that is entered directly by the users and data that is updated automatically by the system.
It contains article-relevant data and data from other areas of the system that may be relevant for articles. These areas are called user departments
in the article master. Unnecessary data storage is reduced when all data is stored in a single database object.]
[Article: An article is the smallest unit that can be ordered independently and that cannot be spilt further into smaller units. Articles are, however,
not always sold in the form in which they were purchased. The single article is the standard article that is sold to the customer; it is the classic
SAP article.]
2.1.2.2 Integration

The article master is used by all components in the SAP Logistics System. The integration of all Article data in a single database object
eliminates redundant data storage. In the SAP Logistics System, the data contained in the article master is required, for example, for the
following functions:
In Purchasing for ordering

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 21

In Inventory Management for goods movement postings and physical inventory


In Sales and Distribution for sales order processing
Key factor in article master is Article type.
2.1.2.3 Article Type

Ddetermines how an article is procured and controls the following:

Subsequent screens

Field selection

Type of number assignment in article master record maintenance

Type of inventory management

Account determination

Raw Articles (ROH)

Semi-finished products (HALB)

Example

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 22

Finished products (FERT)

Trading goods (HAWA)

Non stock Materials (NLAG)

Beverages (FGTR)

2.1.2.4 Planet Retail Scenario:

In Planet Retail the article type will be based upon the concepts. For e.g. the following will be defined as the article types with their internal
number ranges.

Number Range
100000000-109999999
110000000-119999999
120000000-129999999
130000000-139999999
140000000-149999999
150000000-159999999
160000000-169999999
170000000-179999999

ARTICLE TYPE
ZHGU
ZHMA
ZHNX
ZHAC
ZHMS
ZHBS
ZHOB
ZHCT

Reference Article Type


HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA

ARTICLE TYPES DESCRIPTION


GUESS
MARCIANO
NEXT
ACCESSORIZE
MARKS & SPENCERS
BODY SHOP
OSHKOSH BGOSH
CARTERS

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

300000000-309999999
310000000-310029999
310030000-310059999
310060000-310089999
310090000-320019999
320020000-320049999
320050000-320079999
320080000-320109999
320110000-320139999
320140000-320169999
320170000-320199999
320200000-320229999
320230000-320259999
320260000-320289999
320290000-320319999
320320000-320349999
320350000-320379999
320380000-320409999
320410000-320439999
320440000-320469999
320470000-320499999
900000000-909999999
910000000-919999999

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 23

ZHDB
ZHBT
ZHBL
ZHBO
ZHBV
ZHCH
ZHCK
ZHCL
ZHDD
ZHDH
ZHGY
ZHGC
ZHHG
ZHIM
ZHJG
ZHLC
ZHMC
ZHMH
ZHMB
ZHYS
ZHVS
ZRNS
ZRPM

HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
HAWA
ROH
ROH

DEBENHAMS
BIOTHREM
BURBERRY LONDON
BOSS
BVLGARI
CAROLINA HERRERA
CALVIN KLEIN
CLINIQUE
DAVIDOFF
DUNHILL
GIVENCHY
GUCCI
HUGO
ISSEY MIYAKE
JEAN PAUL GAULTIER
LANCOME
MAC
MAISHAA
MONT BLANC
YSL
VERSACE
NON SALES ARTICLES
PACKING ARTICLE

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

911000000-929999999
920000000-939999999
940000000-949999999
990000000-999999999

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 24

ZRPS
ZRPI
ZRCS
ZNCS

ROH
ROH
ROH
NLAG

PRINTING & STATIONARY


PROJECT ITEMS
RAW MATERIAL
NON STOCK_CONSUMABLES

Logic for Article Type:


1st Character as Z

Stands for Customised

2nd Character as H

Stands for first digit of Reference Article Type

3rd & 4th Character Stands for Brand

2.1.2.5 Article Master View:


Basic Data

It contains all the details like article number, article description, base unit of measure, order unit of measure, delivery unit
of measure, sale unit of measure, International/European article no (EAN), merchandise category (MC), article type,
division, tax class, transportation group, loading group etc.
Listing

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 25

It consists of the details related to listing like assortment and distribution chain (for listing), sales organization, distribution
channel, assortment grade, listing procedure, listing period (for both Distribution centre and the Store).
Purchasing

This view has the details of data that are related to purchasing like vendor code, purchasing organization, purchasing
group, purchasing info record, net price, effective price etc.
Sales:

This view has the details of data that are related to sales like sales organization, distribution channel, sales unit, sales price,
mark up etc.
Logistics DC:

It contains the parameters relevant for the distribution channel in which the article is listed, viz. RP parameters like RP
type, general control parameters like availability check etc.
Logistics Store:

This view consists the parameters relevant for the store in which the article is listed, viz. RP parameters like RP type,
general control parameters like availability check etc.
POS

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 26

It contains the details regarding POS control for each distribution chain/site, POS selling period etc.

2.1.2.6 Article Category

Grouping together of articles by attributes. The following article categories are defined in the standard SAP Retail System:
Single articles
Generic articles
Variants
Empties and full products
Structured articles
2.1.2.7 Single Article:

Standard article as sold to the consumer, for example, a 250 g packet of chocolate chip cookies.
When creating a single article, be sure to assign the correct article category to it. In the standard SAP Retail System, this is article category 00. It
is not possible to turn a single article into a generic article, or vice versa.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 27

2.1.2.8 Generic Articles:

Variants are articles that differ only in certain characteristics such as colour, size, or flavour. They are grouped together as a generic article.
Defining a generic article simplifies the maintenance of variants since you need enter data that is the same for all variants only once for the
generic article. Generic articles themselves are not sold, only their variants (for example, the generic article "mens shirt" may have variants in
different size-colour combinations).
A generic article can have variant-creating characteristics. Characteristics defining the attributes of a variant are described as variant-creating
characteristics. One can restrict the characteristic values for the generic article, particularly the variant-creating characteristics. Only the
restricted characteristic values are then allowed for defining variants. In the following table, the two variant-creating characteristics (which will
be used in PRHPL) result in 5 variants:

Colour
Red
White

Size
34
X

Size
36
X

Size
38
X
X

Size
40
X

2.1.2.9 Empties & Full Products

Empties are a type of returnable transport packaging or sales packaging that is normally subject to a deposit. Empties are assigned to a full
product (for example, a crate containing 24 empty bottles is assigned to the full product lemonade).

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 28

Empties consist of several components that are summarized in a bill of material for empties. The full product and the unit of measure make up
the bill of material header. The unit of measure of the empties must be one of the units of measure permitted for the full product.
The individual components in the bill of material and the full product itself each have their own article master record.
2.1.2.10 Structured articles

Article comprising several components structured as a bill of material, for example:


Sets
Displays
Prepacks
A structured article always has the following:
BOM header article
Components
2.1.2.11 Planet Retail Scenario:

Generic Article : Articles with Style, colour & size Examples : Apparels
Single Article : No combination of variants Example: purse

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 29

Structured Article : Kitting Example : Pack of different articles combinations

SD related views for article master


View

Basic
Data

Field
Description
EAN
Units of
Measure/
Dimensions

Description
General description of the article
European article number
Base unit of measure, Order unit of measure, Delivery unit of
measure, Sales unit of measure, Gross weight, Net weight,
length, Width, Height, Volume, Conversion parameters for the
Base unit of measure

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

PAGE 30

Merchandise
category
Tax
classification
Supply source

Loading group
Assortment
grade
Listing

Sales

Listing from
Store/Distributio
n centre
Validities for
each distribution
chain
Cash discount
Calculated price

POS

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

Selling period

The merchandise category to which the group of articles belong.


The indicator with which the system determines output tax for
the material when processing sales and distribution-specific
documents.
Restricts the search for sources of supply for this material to
external (normal) or internal (stock transfer) sources of supply,
and also allows you to define a search sequence.
A grouping of materials that share the same loading
requirements.
The assignment of a material to an assortment grade defines the
assortment and the associated assortment users (such as retail
sites) for which this material is valid.
Listing procedure, Listing validity and Sales validity

Date from which the material is sold in the stores. The date is
limited by the validity period that has generally been defined at
material level (basic data screens).
Indicator that specifies whether this material qualifies for a cash
discount.
Net sales price, Gross sales price, final price, validity, margin
gross and net
For sales and to sales period

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 31

Control for each


Distribution/
Site

Discount allowed, Price required

2.1.3 SITES
Stores / Distribution centre master data should contain information to enable the following functions:
Procurement / Inventory Management
o To model the associated business processes such as goods receipt, physical inventory, goods issue.
o Planning: Replenishment planning, and purchase order processing
Sales / Taxation
o POS: To enable information to POS for ease of billing operations, cash and credit card sales
In SAP Retail such locations (Store/DC) can be created as sites.
General explanations

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 32

In a DC or a Store there would be requirement to maintain inventory records like goods receipt, issue, transfers, balances and values etc.
Similarly, documentation of goods stored in Distribution Centre and store is required for the purpose of inventory management. A DC or a store
has its own requirement planning for taxation and inventory management. By creating a site above can be achieved in SAP.

2.1.4 DISTRIBUTION CENTRE


It is the warehouse that caters to different stores. Goods are stored in a DC for short period of time and then transferred to stores or customers.
DC enables centralized buying for different stores thus, helping in achieve logistics and purchasing cost optimization. Further it helps in better
management of inventory. Generally wholesales are envisaged from DC and also stock transfers take place from DC to Store. Billing for
wholesale will be done through DC.
A distribution centre is assigned to a purchasing organization, and may also be assigned to a distribution chain for the purposes of sales
price valuation, stock transfers and statistics.
A distribution centre can also supply a number of distribution chains. In the same way, a site can also be supplied with goods from
different distribution chains.

2.1.5 STORE
Type of site in which goods are presented and sold to consumers. Store is assigned to one purchasing organization and one distribution chain.
(For Details on Purchasing Organization and Distribution Chain refer to Business blueprint section Organization Structure)

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 33

A site is always a combination of the site master and the customer master. The site master is required as sites are organizational units with their
own inventory management and requirements planning. A site is also a customer, because from a central point of view, sales functions are also
performed, such as deliveries and invoicing, hence customer master for the site has to be maintained. Designing site as a vendor/ customer will
not trigger any financial impact. Information for external customers will be available at all the sites.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 34

A store is always assigned to a distribution chain and may be supplied by distribution centres via several distribution chains. Each store is
assigned to one storage location for inventory management. Distribution centres can have more than one storage location. The merchant ID
assigned to a store is used for billing sales with a credit card (for example, American Express, Visa Card) at the relevant clearing point.
A distribution centre (DC) is also a vendor, as it provides other sites with merchandise; hence vendor master has to be maintained for site, which
is DC. A distribution centre delivers merchandise to stores that belong to one or more distribution chains. A distribution centre can be assigned
to one Distribution Chain. Vendor master will also be available at store wherever required.
Site Master Data:
Organizational/Calendar view: All organizational units to which the site is assigned is available here. Data as which sales org, purchase
org, company code, distribution channel, various purchase organizations and distribution chains the site is assigned.
Address view: Address for communication, tax information are maintained here
Valuation and inventory management view: Valuation area, Inventory management profile, retail re-valuation profile
Listing and requirement planning view: Listing conditions and assortment, requirement planning
Purchasing and Distribution view: Maintain data on Purchasing (regular vendor, source list) Distribution profile
POS view: Maintain the POS inbound and out bound profiles, POS currency and assortment list profile

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 35

Layout view: It is often desirable for stores belonging to the same distribution chain, or departments in a store, to have the same system
of merchandise presentation and shelving structure, regardless of their size. This allows customers to find their way better round a store,
no matter whether it is their home store or a store in a different town, and therefore provides greater customer satisfaction.
To achieve this as cost-effectively as possible, you can define site layouts in SAP Retail.You assign these layouts to sites or individual
departments. A site layout is divided into layout areas.Layout areas in turn are divided into layout modules, where articles are assigned.

The system proposes site master data from the reference site if you are using the reference site. Reference site helps in the creation of other sites,
where master records from the reference sites flows to the new site.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 36

Customer Master Data


When goods are transferred from one site to another the receiving site has to be a customer for the issuing site. Hence, the customer master data
is maintained for site.
The customer number of the store will be the same as the site number. Even Distribution Centres can have the function of a customer, when
goods are transferred from one site to the DC. The customer number of the DC will be the same as the site number. Customer master record has
to be maintained for all sites. The account group is defaulted from the site profile.

2.2

STOCK TRANSPORT ORDER

The physical transfer of goods from the distribution centre to stores or from one store to another store or from store to DC is done based on the
stock transport order. The stock transport order is released after the allocation of material (Please refer to the section of Allocation in MM
blueprint for details on the allocation process).

2.3

OUTBOUND DELIVERY DOCUMENT

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 37

The subsequent document for the stock transport order is the delivery document. Outbound delivery supports all shipping activities including
picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of
shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the
shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the
delivery.

2.4

PICKING

Picking is the intermediate process in delivery. In this process the individual items are picked from their respective storage location based on the
picking list generated by the subsequent followup document in delivery.

2.5

POST GOOD ISSUE

Post goods issue is the last process in shipping process. By posting the goods issue the physical inventory of the distribution centre is reduced &
corresponding value of inventory in financial accounting are also reduced.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

2.6

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 38

POST GOODS RECEIPT AT STORE

The receipt of goods in respective stores are also to be taken in the individual stores inventory. This is supported by the process of posting goods
receipt at store end.

2.7

RETURN HANDLING

This process handles the return of the defective goods from the stores to distribution centre. If the returned goods arrive in your warehouse, you
create a returns delivery for these as the goods receipt and post the stock. Returns can also happen for slow moving, excess, damaged, expired
stock and customer returns.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 39

Process flow of the retail cycle

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

3.0

ORGANIZATION STRUCTURE

3.1

SALES ORGANIZATION

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 40

The Sales organization is responsible for negotiation and fixing general Sales price conditions and terms with Customers. It is responsible for all
Sale transactions across Head office, Region, Zone, Distribution Centre and stores.
Implications:

One Sale organizations for each company code would be sufficient to meet the current requirements of :
o Ease in Article Data Management (Creation and Updation)
o Selling Products across different Distribution Chain / Formats

Recommended Sales Organizations are


1000 PRHPL Sales Org
1100 STPL Sales Org
2000 QRPL Sales Org

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

3.2

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 41

DISTRIBUTION CHANNEL

The distribution channel is the channel through which saleable materials or services reach the customer. Distribution channels include selling to
consumers through various types of retail outlet or via mail order.
Implications
Following distribution channel is being proposed for PRHPL project.
01- Retail DISTRIBUTION CHANNEL (Distribution Channel for sales at store)
02- Stock transfer DISTRIBUTION CHANNEL (Includes Consignment)
03- Wholesale DISTRIBUTION CHANNEL
04- Export DISTRIBUTION CHANNEL

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

3.3

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 42

DIVISION

A division is an organizational unit based on responsibility for sales or profits from saleable materials or services.

A way of Grouping Article, Products, or Services


SAP Retail does not use division for any functions but a division should still be defined.

Implications
Create one dummy division R1 Retail.

3.4

SHIPPING POINT

Shipping point is the highest level organizational units in shipping. Every delivery documents are created from a shipping point. Scheduling &
processing deliveries from the distribution centre happens through shipping point.
Implications
All the sites corresponding to the DC will be assigned to one common shipping point 1001 Kapashera Shipping point.
All the stores will have one shipping point for store deliveries. All the shipping points will have the same code as the site code for all the stores.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

4.0

DISTRIBUTION (WHOLESALE)

4.1

AS IS

W B - TYPE OF
SALE.doc

4.2

W E - SALE ORDER
PROCESS.doc

W F - SALES
INVOICE.doc

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 43

WJ - SALES
RETURN.doc

WH - DELIVERY AND
PAYMENT.doc

TO BE

4.2.1 CUSTOMER MASTER


Customer master for wholesale will be same as covered in section

4.2.2 SALES ORDER ( For outright sales)

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 44

During sales order processing, the system carries out monitoring the sales transactions, checking for availability, scheduling the delivery,
checking credit limits and creating printed or electronically transmitted documents (confirmations, and so on). Standard sales document types
will be used during the implementation.
At PRHPL , sales requisition are created and approved after checking for credit limit. Till then inventory is not blocked. Sales order are
processed after the approval. This can be met by standard setting in SAP. The create sale order screen will have an automatic credit check which
blocks the sale order but not the inventory. The block can be released by only authorised person. After the Sales Order is approved, inventory
will be blocked for other sales order.
Standard document types will be used.
Parameters of configuration will be covered in Configuration document.

4.2.3 OUTBOUND DELIVERY ORDER


Outbound delivery supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery
process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is
documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is
generated during shipping processing is included in the delivery.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 45

4.2.4 BILLING DOCUMENT


Billing invoices are created against sales orders issued for merchandise shipped, credit and debit memos. Deliveries, which are carried out on the
basis of sales orders, are invoiced to the customer. If no complaints are made about the delivery, the business transaction is considered
complete. From the S&D point of view the business transaction is complete only when the goods are delivered and payment is realised.

4.2.5 CREDIT & DEBIT MEMO


Credit memo - A sales document created on the basis of short/damaged claims by customer. This reduces receivables in Financial Accounting.
Debit memo - A sales document created on the basis of incorrect customer invoicing to settle unclaimed charges.
Credit memos are created for various reasons (for example, because of defective goods or because you have overcharged a customer). Similarly,
one might have create a debit memo, if, for example, the customer has not been adequately charged. When a user creates a credit or debit memo,
(s) he must refer to an invoice or a credit memo request.

4.2.6 RETURNS PROCESSING


Returns document are created when the customer wants to return damaged goods or goods that were delivered excess over order. The returns
document can be created with or without reference to the sales order. When the returned goods arrive back at PRHPL distribution centre, sales

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 46

office is then expected to create a returns delivery, which refers to the returns order document already created. The goods issue posted for the
returns delivery records the inward movement of the goods into companys own stock.

Sales returns will be having a default block always which will be removed only after authorized personnel removes it. Checks in return process
with respect to agreements, value etc are not available as part of Best Practices. The returns will have reference invoice number as well. Standard
reports on return processes are available for examining through drilldown mechanism.
Returnable samples will be mapped through the process of subcontracting. Non-returnable samples will be debited against cost center.

4.2.7 PROCESS FLOW (WHOLESALE DISTRIBUTION)


Creation of Standard Orders
Credit and article availability check
Creation of Delivery Document
Picking from the warehouse
Posting Goods Issue
Generating Customer Invoice
Automatic booking of sales in the accounts
Best practices for exports as a wholesale process will also be configured in the system.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 47

Process flow of the wholesale cycle

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 48

4.2.8 CONSIGNMENT PROCESS

Consignment goods are goods which are stored at the customer location but which are owned by Planet Retail. Since consignment
stocks still form part of PRs valuated stock.
However, consignment stock must be
Managed separately from the rest of your stock so that PR knows exactly what stock is stored at the customer location
Managed separately for each customer
In inventory management, the consignment stock is managed as special stock in PRs inventory and is assigned to specific
customers.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 49

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 50

The following 3 models have been identified --Model 1 Case such as VAMA: Goods will be transferred from Planet Retail to VAMA using stock transfer. VAMA is using Planet Retails
POS system. As such, Planet Retail has access to POS data. Based on POS sales data received in SAP system, sales order in favor of
VAMA will be created (possibly through BDC tool which will be explored during realization phase). Normal sales process i.e. delivery, PGI
(post goods issue) and billing will be executed to generate invoice in favor of VAMA after deduction of consignment commission.
Model 2 Case such as JK: Goods will be transferred from Planet Retail to JK (owned by third party) using stock transfer. Items will be
sold from POS to end-customer. This sale will directly be booked in the books of Planet Retail. A percentage of the entire sales will be
given to the third party as a commission. System will provide sales reports to assist calculation of commission. The commission entry will
be passed through FI.
Model 3 This model is similar to the model 1. The difference is that the consignee agent is using its own POS system, and this POS
data is not available in SAP system. Goods will be transferred from Planet Retail to consignee using stock transfer. Consignee will sell
goods through the POS to end-customer. Planet Retail will receive sales data from consignee in mutually agreed format. Based on this
data, sales order in favor of consignee will be created by user. Normal sales process i.e. delivery, PGI (post goods issue) and billing will
be executed to generate invoice in favor of the consignee agent.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 51

Treatment for Vama


Vama is to be treated as a consignment agent. The only difference with other consignment agents is that as Vama is using our POS
system, we have access to its sales data. We will get the POS data to SAP system, but unlike other stores, this data from Vama will
not lead to any inventory, sales or receivables postings. SAP will provide a report about Vamas end-sales. Based upon this report,
sales cycle from PR to Vama will be processed in the same manner as that of other consignment agents. PwC will look into
automation of consignment processing based upon data received from VAMA POS as discussed earlier (possibly through BDC tool
which will be explored during realization phase).

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 52

5.0 PRICING

5.1

AS-IS

R G - PRICING.doc

5.2

TO BE

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 53

5.2.1 WHOLESALE PRICING


Requirement of pricing is to pick up the right price for a given condition at the time of sales transaction. The other statutory requirements like
Excise, Sales tax, and should be automatically calculated by the system to eliminate the error while posting those values in the respective GL
accounts. Pricing should provide the scope of discount applicability for a customer / combination of customer and material / material on case-tocase basis.
Pricing should provide flexibility of changing the price and getting it approved before finalization of deals with the customer. The requirement of
having centralized control mechanism to ensure maximum realization to the company.
Sales order pricing should also be able to comprehensively capture all order related costs like freight, insurance, duties, material cost etc to arrive
at the net order contribution.
The rebate(turnover discount) will be adjusted at period end by way of rebate agreement functionality of SAP. The rebate adjustments are done
at period end by way of credit memos and are based on quantity/value of the sales during the specified period.

Components of Pricing
5.2.1.1 CONDITION TYPE

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 54

Condition types represent Price elements in SAP system. Price elements can be 1. Prices
2. Discounts
3. Taxes and surcharges
4. Freight
The above conditions need to be maintained either in terms of value or percentage basis. Price elements are stored in the system as condition
records.
Parameters of configuration will be covered in Configuration document.

5.2.1.2 CONDITION TABLE

Condition tables are used to define price dependencies. Combinations of fields for which condition records can be created are defined in
condition table.
Parameters of configuration will be covered in Configuration document.

5.2.1.3 ACCESS SEQUENCE

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 55

Access sequence is specified in condition type. The access sequence is a search strategy, which the SAP system uses to search for condition
records(or price/discount etc values) valid for a condition type.
5.2.1.4 PRICING PROCEDURE

Pricing procedure is assigned to the transactions by defining the following dependencies.


Customer Master
Sales document type
Sales area (A combination of sales organization, distribution channel and division)
5.2.1.5 PRICING PROCEDURE -DETERMINATION

Determination of pricing procedure depends on the following factorsCustomer pricing procedure


This is maintained in the customer master record for each sales area.
Document pricing procedure
This is specified in the sales document types and billing document types for each sales area.
During pricing, the SAP System automatically determines which pricing procedure is valid for a business transaction using the Document
and Customer pricing procedure and it takes the condition types contained in it into account one after the other.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 56

5.2.1.6 CALCULATION OF TAXES

Sales tax will be picked up through tax code. Based on the location of supplying distribution centre and wholesale customer.
Note 1: Separate tax codes will be created for different percentage rate of CST / VAT.
Note 2: Tax classification (E.g. Full tax, Form C etc.) will be maintained in the customer and material master record.
Freight will be a manual condition and can be changed at the time of Invoice creation based on the actual freight value.

5.2.2 RETAIL PRICING


The retail prices for domestic supplier (e.g third parties at debenham) articles will be uploaded into the system as the final sales prices to be
transferred to POS systems.
For domestic manufactured articles, and imported articles PRHPL follows the markup pricing based on net landed cost. The net landed cost
value is calculated including freight , customs, insurance. For MRP of these articles markup is calculated on the net landed cost.
Where international price is available the MRP is calculated based on uplift on the international price. Comparison on MRP with markup is done
and the better amongst them is selected as the MRP.
In SAP, condition types will be created to capture the MRP of articles. Also, MM module will capture the various cost components in different
condition types for capturing the net landed cost of the articles and the international retail prices.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 57

After configuration PwC will give a demo and PRPHL will take the final call on the parameters for pricing calculation which is to be fed into the
system.
PwC to develop a screen/report to reflect the MRP of the articles with the uplift percentages on the international prices with comparisons markup
on net landed cost.
Business Blueprint will be updated after finalization. Detailed pricing will be covered in the configuration document.

6.0

PROMOTION

6.1

AS IS

R F - Promotions.doc

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

6.2

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 58

TO BE

Promotion means an activity aimed at increasing the sales by offering the customer greater incentive to buy the product. Promotions will be run
for a certain validity period where articles will be offered to the customer at a special price, or free merchandise will be offered to customers.
Store specific promotion can be done.

6.2.1 PROMOTION TYPES:


Promotions could be of the following types:
Fixed price
Fixed Discount
Percentage Discount
Free Goods.
Free goods data can be maintained in the promotion only after the promotion has been created and saved. Free goods can be of two types:
Inclusive: In Inclusive free goods, the customer buys some quantity of free goods and gets some of it free of cost (of lowest cost). For example,
if a customer buys 5 shirts, he gets the 5th shirt free of cost. In other words, he gets 5 shirts but has to pay only for 4.
Exclusive: Buy an article and get the same or another article free (of lowest cost). For example buy a shirt and get another shirt or an Aftershave
free. (Available in IS-Retail, to be explored in Triversity and XI) .

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 59

The SAP system throws a warning whenever a user attempts to create another promotion over an existing promotion.

Some examples of different types of promotions that could be offered are:

Buy an item at a special price. For example, buy a watch at a special price of Rs 800 instead of regular price of Rs 1000.
Buy an item and get percentage discount. For example, buy a shirt worth Rs 1000 and get 10% off.
Buy more than one units of an item and get percentage discount on a scale manner. This means that with the increasing units of an article
the percentage discount is also increased. For example, buy items worth Rs.1000 and get 10% off, buy worth Rs.1500 and get 15% off.
(Available in IS-Retail, to be explored in Triversity and XI).
Buy an item and get an absolute discount. For example, buy a shirt worth Rs 1000 and get Rs 100 off.
Buy more than one units of an item and get absolute discount on a scale manner. For example, buy items worth Rs. 1000 get Rs 10 off,
buy worth Rs 1500 get Rs 15 off. (Available in IS-Retail, to be explored in Triversity and XI).
Buy an article and get some rupee off on purchase of some other article. For example, buy shirt along with trouser and get an absolute
discount.
Buy an article and get some percentage off on purchase of some other article. For example, buy shirt along with trouser and get a
percentage discount

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 60

Buy an article and get another article free (of the lower value). For example, buy shirt and get a watch free.
Buy three items for the price of two (of the lower values). For example, buy three CDs for the price of two.
Buy more than one item from an article group and get an absolute discount. For example buy 3 items from a group of articles and get 100
Rs off.
Buy more than one item from an article group and get a percentage discount. For example, buy 3 or more items from a group of items
and get 10 percent discount.
Buy items from an article group and an item free. For example, buy 2 items from a group of article and get another item free. (Available
in IS-Retail, to be explored in Triversity and XI).
Cross brand promotion for limited products will be available. Promotion listed here will be applicable to wholesale distribution as well.
Promotion analysis will be taken up in BIW phase II. Promotions for colour, size will be planned at SKU level.

6.2.2 COUPONS (GIFT VOUCHER)


After the promotion is created and saved, coupons can be assigned to it and bonus buy conditions can be maintained. Coupons will be created as
article masters in the system.
Coupons can be used as a prerequisite which entitles the customer to a bonus buy. The coupons that are involved in a promotion are maintained
in the promotion. The coupon data is downloaded to the POS. For each coupon a bonus buy condition can be maintained. This coupon has to be
maintained in the promotion.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 61

In SAP, coupons will be treated as articles. Therefore, if coupons are to be used in a promotion, then coupon articles will have to be created and
assigned to the promotion.

6.3 RETURNS
System generated vouchers would be used for all returns in the store. This voucher should have original invoice no. Of returned goods. This
voucher can be used in this store on same day and next day for all other group of stores.

6.4 PROCESS FLOW (For promotions)


1) Creating and Maintaining Site Group: Sites participating in the promotion are included in a "site group". Assign sites to the site group, then you
can plan promotion to this group of sites. (Optional)
2) Creating Allocation Rule: In the allocation rule, you define the ratio used to distribute the promotional merchandise to the participating stores.
(Optional)
3) Creating Promotions: Via creating a promotion, you can define the promotion type, set the article, sales price, quantity, periods etc in a defined
promotion. System will give a warning in case an existing promotion is getting overwritten.
4) Price Activation: Activating the promotion price
5) Carrying out listing: This function enables sites involved in the promotion can sell the article with the promotional price in the promotional
period.
6) Generating Allocation Table: Promotional articles are issued from DC and received at store refer to the allocation table. (Optional)

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 62

7) Create Follow on documents: Follow on documents (STOs) are created. (Optional).


8) Delivery: Goods are issued from the DC to the stores against the STOs.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 63

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

7.0

ASSORTMENT

7.1

AS-IS

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 64

R H - Merchandise
Planning.doc

7.2

TO-BE

Assortment definition: An assortment is a collection of articles, which is valid for a period of time. This assignment can be made either directly
of via assortment modules. The articles are used altogether in assortments. Assortment defines which articles are to be carried in which retail
sites (distinguished by different periods of time).

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 65

The assortment range is determined by assigning assortment modules. Assortment module is a group of articles that are to be managed together
over a specified period as an assortment or as part of an assortment. An assortment can consist of one or more assortment modules.
Articles are assigned to assortments through assortment modules created especially for the purpose
Generally create assortment modules to group together articles that have a relatively long life cycle or that are fairly uniform enterprise-wide or
that need to be grouped together for a specific purpose (such as a promotion). This method of assigning articles does, of course, still allow you to
apply assortment rules.
Local assortments:
These are designated as type A for stores and type B for distribution centres. When you create a site (store or distribution centre), the system
automatically creates a local assortment, which it then assigns to the site. This local assortment is site-specific and cannot be assigned to any
other site. Each site has exactly one local assortment.
General assortments:
General assortments can be assigned to any number of customers, with one or more assignments for each sales area. They can also be assigned to
any number of stores and distribution centres, provided you have activated the multiple assignment flag in Customizing.
Assortment User
An assortment user must be assigned to an assortment before it can use the articles in that assortment for its various business functions. The
scope of functions available is determined by the category of assortment user. Currently, there are the following categories of assortment users:
Stores
Distribution centres

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 66

Customers

Listing Procedures:
Listing procedures determine how the system checks the assignment of articles to assortments (and thereby to the stores, customers, or
distribution centres using those assortments).
Listing procedures control the result of the listing process. They allow a high level of flexibility in Assortment Management.
Basic Listing procedures:
SAP delivers a number of listing procedures intended to simplify Customizing, which is otherwise rather complicated.
The Standard listing procedure that will be used in PRHPL will be:
Basic procedure: Merchandise category /assortment level (B1)
This procedure checks:
Whether the article's merchandise category is assigned to the assortment and, if so the merchandise gets listed in the assortment.
PRHPL ASSORTMENT:
The proposed assortment for the project will be as under.
1) Assortments will be created brand wise and on other factors.
2) All the stores which will have those brands will be listed to the assortment as assortment users.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 67

3) For every assortment corresponding Assortment Modules will be created. For example, for National Assortment, National
Assortment Module and for regional assortment, Regional Assortment Module will be created.
4) All the articles which would be sold nationwide across all stores will be listed in the National Assortment Module and region specific
articles will be listed in the Regional Assortment Module.
5) Based on PRHPL requirements more assortments and assortment modules will be created based on other factors.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 68

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

8.0

POS INTERFACE

8.1

AS IS PROCESS

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 69

R D - POS
Interface.doc

8.2

TO-BE PROCESS

SAP IS-Retail system is being used for procurement, inventory management and sales. The specific scenario of selling through Point of sales
system needs to be interfaced with SAP. SAP POS interface enable you to provide your store POS systems, with all the relevant data required to
handle the store processes independently.
The IDoc technique enables all the messages that can be exchanged between SAP Systems and the store systems. Settings are made to define
which information (messages) is exchanged in the form of intermediate documents (IDocs). Checks are made to ensure that the data arrives even
if the receiving system cannot be accessed when the data is sent. You can regularly supply the POS systems in the stores with current data
(master data, such as EANs, conditions, and merchandise categories) via the POS interface - outbound. This means that the master data only has
to be maintained in the central system.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 70

Information can be uploaded from the POS systems to the central Retail system via the POS interface - inbound.In addition to the initial supply
of data, another important aspect is the continuous preparation of change data, such as price changes. If master data is changed, the system
prepares the data in question in IDoc format after initialization (initial supply of data to the store), taking account of the current store assortment.
As soon as a user maintains master data, the application creates a change document. If the modified field is relevant for the store, a change
pointer is created.
The Idocs and related features with XI will assist in transfer of data between SAP Retail and POS.
The required fields (vendor etc , if required) need to be specified and will be mapped in the Idocs. The detailed mapping of fields (discounts,
coupons etc) will be carried out in the realisation phase alongwith Triversity integration.
Types of business information that SAP Retail sends through the POS outbound interface to store system are as under.
Article master data
Article sales price
EAN/UPC assignment
Customer data
Products
Taxes
Merchandise Category Master
Label data

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 71

Assortment List
Promotion

Types of business information that SAP Retail can receive through the POS inbound interface from store system are as under.
Sales Data (receipt based and aggregated)
Cashier data
Payment types
Store Order
Financial Transaction
Inventory
Other business information (like customer based data & pricing) will be covered in POS blueprint.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.0

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 72

LIST OF REPORTS (AS PER THE AS-IS)


Demos of standard reports in the system will be shown to PRHPL after the unit testing and based on PRHPLs priority reports will be
developed.

9.1

CATEGORY WISE REPORTS


9.1.1

COPY OF DEPARTMENTAL PROGRESS REPORT NEXT

Copy of
Departmental Progress Report NEXT.xls

9.1.2

DEBENHAMS

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 73

DEBENHAMS.xls

9.1.3

TBS (THE BODY SHOP)

TBS.xls

9.2

LOYALTY (LYB) PROMOTION (TO BE TAKEN IN PHASE II)


9.2.1

DAILY
9.2.1.1

DAILY_LYB_KIT_SALES_REPORTS

Daily_LYB_KIT_Sales
_Report.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.2.1.2

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 74

DAILY_LYB_NET_SALES_REPORTS_FEB

Daily_LYB_Net_Sale_
Report_Feb.xls

9.2.1.3

LYB_NET_SALE_REPORT_FEB_08

LYB_Net_Sale_Repor
t_Feb_08.xls

9.2.1.4

LYB_SALES_ANALYSIS_FEB08

LYB-SALES-ANALYSI
S-Feb08.xls

9.2.1.5

TOP_20_SPENCERS_FEB

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 75

Top_20_Spenders_F
eb.xls

9.2.1.6.

TOP_20_SPENCERS_SALES_DETAILS_REPORT

Top_20_Spenders_S
ales_Detail_Report.xls

9.2.2

WEEKLY
9.2.2.1 BIRTHDAY_REMINDER_REPORT

Birthday_Reminder_
Report.xls

9.2.2.2 CARD_REGISTRATION_REPORT

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 76

Card_Registration_R
eport.xls

9.2.2.3 KNOW_CUSTOMER_REPORT

Know_Customer_Re
port.xls

9.3

MANUAL REPORTS FROM STORE


9.3.1

DSR

Dsr.xls

9.3.2

EXPENSE_PETTY_CASH_123

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 77

EXPENSE__PETTY_C
ASH_123.xls

9.4

POS REPORTS
9.4.1

RPT_CONSOLIDATED_PAYMENT_SUMMARY

rpt_consolidated_pa
yment_summary.xls

9.4.2

RPT_DAILYSALES_HOURLY

rpt_dailysales_hourly
.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.4.3

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 78

RPT_DETAILEDSALES

rpt_detailedsales.xls

9.4.4

RPT_DETAILEDSALES_DIVISION

rpt_detailedsales_div
ision.xls

9.4.5

RPT_DETAILEDSALES_STYLE

rpt_detailedsales_st
yle.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.4.6

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 79

RPT_DETAILEDSALES_STYLE_BEST_SELLER

rpt_detailedsales_st
yle_best_seller.xls

9.4.7

RPT_PAYMENTSUMMARY

rpt_paymentsummar
y.xls

9.4.8

RPT_SALESPERSONRESULTSSUMMARY

rpt_salespersonresul
tssummary.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.4.9

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 80

RPT_SALESSUMMARY

rpt_salessummary.xl
s

9.4.10 STCARD2

stcard2.xls

9.4.11 STDLEDGER

stkledger.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.5

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 81

SALE ANALYSIS
9.5.1

ABC ANALYSIS

ABC Analysis.xls

9.5.2

BEST SELLER REPORTS

Best Seller
Report.xls

9.5.3

CALENDER YEAR ANALYSIS

Calendar Year
Analysis.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.5.4

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 82

FY SALE ANALYSIS

FY Sale Analysis.xls

9.5.5

LIKE FOR LIKE (LFL) REPORT

Like for Like (LFL)


Report.xls

9.5.6

NEW PRODUCT SALE PERFORMANCE REPORT

New Product Sale


Performance Report.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.5.7

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 83

NO_OF_BILL_COUNT_FEB

No_Of_Bill_Count_Fe
b.xls

9.5.8

SKU WISE SALES

SKU wise sales.xls

9.6

WALK IN ANALYSIS REPORTS


9.6.1

NEXT-WALKINS DETAILS REPORT

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 84

Next - WALKINS
Details Report.xls

9.7

WEEKLY DSR
9.7.1

ACCESSORIZE

Accessorize.xls

9.7.2

BODYSHOP

BodyShop.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.7.3

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 85

CONSOLIDATED BRAND WISE

CONSOLIDATED
BRAND WISE.xls

9.7.4

DEBENHAMS

Debenhams.xls

9.7.5

MALL WISE DSR

MALL WISE DSR.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.7.6

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 86

MONTHLY DSR BRAND WISE

MONTHLY DSR
BRAND WISE.xls

9.7.7

NEXT

NEXT.xls

9.8

EFFICIENCY REPORT GENERATION

Efficiency Report
Generation.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

9.9

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 87

MALL WISE SALES ANALYSIS

MALL-WISE-SALE-AN
ALYSIS.xls

9.10 MARKDOWN & SALES WISE SALE


MARKDOWN &
SPACE WISE SALE.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 88

9.11 MONTHLY OPERATING SUMMARY


Monthly Operating
Summary.ppt

9.12 NEW STORE OPENING TRACING


NEW STORE
OPENING TRACKING.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 89

9.13 NEXT_WEST_GATE_ATT.SHEET
NEXT_WEST_GATE_
ATT.SHEET.xls

9.14 VENDOR REQUEST FORM


Vendor Request
Form.xls

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY

SALES AND DISTRIBUTION


SAP IS-RETAIL
IMPLEMENTATION
LOCATION : GURGAON

VERSION NO 3.0

TO-BE BUSINESS PROCESS SCRIPTS

PAGE 90

10.0 OPEN & CLOSED ISSUES


SAP Comments and PwC response discussion

BBP_Planet_Retail_R
eview Report SD.doc

10.1 CLOSED ISSUES


Mark down planning to be covered in phase II.
Best practices for Export sales will be configured. BBP will be updated accordingly.
Returns samples will be mapped through the sub-contracting process. Non returnable samples to be debited against cost center.
Standard Document types will be used. Details about parameters of configurations will be covered in the configuration document. BBP
will be updated accordingly.
FI Configuration document will document GL mapping and other related accounting configurations.
Pricing components & pricing schema for stock transfer will be covered in MM module and for POS sales will be covered in Triversity.
After configuration PwC will give a demo and PRPHL will take the final call on the parameters for pricing calculation which is to be fed
into the system. BBP will be updated accordingly.

ST

FINAL BBP SD ISSUED ANKITA (PWC) FOR SOLMAN UPLOAD PURPOSE DATED 31 JULY