BBP - RET - 002 - Site Master Data Management - V1.2

SAP Implementation
at
Project Name
Business Blueprint Document

Version No.: 1.2
Effective Date:23.12.2016
Module: SAP FMS Retail

Process: Site Master Data Management
Document No.: BBD_RET_002_Site Master Data Management
ARVIND / IBM Confidential

Business Blueprint Document – Retail (Module) – Site Master Data Management
(Process Details)
Document No: BBD_ RET_002 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind
Table of Contents
1.0 DOCUMENT INFORMATION..........................................................................................................4

1.1 DOCUMENT VERSION.....................................................................................................................4
1.2 DOCUMENT APPROVAL DETAILS.......................................................................................................4
1.3 REFERENCE DOCUMENT DETAILS (IF ANY)..........................................................................................5
1.4 ABBREVIATIONS USED (IF ANY)........................................................................................................5
2.0 BUSINESS REQUIREMENT............................................................................................................5

2.1 APPLICABILITY...............................................................................................................................5
2.2 DETAILS OF BUSINESS REQUIREMENT................................................................................................7
2.3 BUSINESS REQUIREMENT FLOW DIAGRAM (IF ANY).............................................................................8
3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................8

3.1 SITE PROCESS DETAILS....................................................................................................................8
3.2 SITE CREATION..............................................................................................................................9
3.2.1 Site Number (Code).................................................................................................9
3.2.2 Site profile................................................................................................................9
3.3 SITE MAINTENANCE.....................................................................................................................10
3.4 SITE BLOCKING............................................................................................................................10
3.5 SITE CLOSING..............................................................................................................................11
3.6 PROCESS MAPS:..........................................................................................................................11
3.7 BUSINESS PROCESS STEPS.............................................................................................................11
3.8 KEY DATA STRUCTURE ELEMENTS...................................................................................................12
3.9 ASSOCIATED MASTER DATA ELEMENTS (IF ANY)...............................................................................12
3.10 INTERFACE MAPS (IF ANY)............................................................................................................12
3.11 REPORTS MAPPING (IF ANY).........................................................................................................12
Arvind/IBM Confidential
Page 2 of 24
(Process Details)
3.12 PROCESS VARIATIONS / EXCEPTIONS (IF ANY)...................................................................................12
4.0 INTEGRATION POINTS (IF ANY).................................................................................................13
5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................13
6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................13
7.0 GAPS...........................................................................................................................................13
8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................14

8.1 DATA CONVERSION CONSIDERATIONS.............................................................................................14
8.2 INTERFACE CONSIDERATIONS.........................................................................................................14
8.3 FORM CONSIDERATIONS...............................................................................................................14
8.4 REPORTING CONSIDERATIONS........................................................................................................15
8.5 FUNCTIONAL ENHANCEMENT CONSIDERATIONS................................................................................15
9.0 AUTHORIZATION REQUIREMENTS............................................................................................15
10.0 ANNEXURE (IF ANY)SS............................................................................................................16
11.0 Flow Chart Legend..................................................................................................................17
Page 3 of 24
(Process Details)
1.0 Document Information
Document Category Business Blueprint Document

Document Title Assortment Management
Author Chandra
File Name BBP_RET_002_Site Master Data Management_V1.0
Created On 24.10.2016
1.1 Document Version
Date Version No. Author Change Description

24.10.2016 V1.0 Chandra Initial Release
Post incorporation of changes in
25.11.2016 V1.1 Naina Acharya blue print validation workshop
Post incorporation of changes in
23.12.2016 V1.2 Naina Acharya blue print validation workshop
1.2 Document Approval Details
Function Name (Designation) Role Sign & Date

Chandra Kumar IBM Team Member 24.10.2016
Prepared By
Abhijit Nag Core Team Member
Naina Acharya IBM Team Lead 27.10.2016

Reviewed By
Process Owner
T Sudhir IBM Project Manager 02.11.2016
Abel Correa Arvind Project Manager

Approved By
Page 4 of 24
(Process Details)
1.3 Reference Document Details (If any)

Department /
Title of the Document Version No Organization Reference / Remarks
KDS for Site
1.4 Abbreviations Used (If any)

Abbreviation Description
Distribution Centre
DC
Key Data Structure
KDS
2.0 Business Requirement
2.1 Applicability
The process described in this document details Site Master Data Management processes necessary for for
enabling ARVIND’s various business processes defined under Business Blueprint Document for Retail
module.
The document is applicable for following business verticals of Arvind group:

Business Vertical Applicability (Yes/No)
Yes
The Arvind Stores
Yes
Fashion division
Yes
Sports division
Yes
Arvind True Blue Ltd
Page 5 of 24
(Process Details)
Business Vertical Applicability (Yes/No)

Yes
Arvind Premium Retail Ltd
Yes
Arvind Ruff and Tuff Ltd
Yes
Arvind Internet Limited
Yes
Garment export division
Page 6 of 24
(Process Details)
2.2 Details of Business Requirement

Requirements
Business Description Comments
Fashion/Footwear/Sports / Warehouse, EBOs COCO and FOFO stores need to be created. For DC , there is
ATBL ARTL/APRL MBOs to be created one location physically but there are 5 logical warehouses for
Fashion, Footwear , ATBL , ARTL and APRL.
TAS The Arvind store and Currently Arvind has plan deal with three different types of
Warehouses needs to store format:
be created.  COCO – Company owned & operated
 COFO – Company owned & Franchisee Operated
 FOFO – Franchisee Owned and Operated
GED Factory outlets need

to be created as sites.
EBO’s need to be
AIL created. They have 9 EBO’s which will be created.
Fashion/Footwear/Sports / Sites’s / Location’s Below attributes needs to be maintained for site & for its
ATBL attributes needs to be customer:
ARTL/APRL/TAS/GED/AIL created.  TIN #/CIN #
 VAT Registration Number
 Business Model – will derived based on Distribution
Channel
 Customer Group
 Tax Structure
 Store Opening Date – SAP Code creation date
 Address details
 Geo Hierarchy (Region |State |City)
Fashion/Footwear/Sports Site/ location Sites must have hierarchy as per geography
/ATBL Hierarchy needs to be (Region/State/City)
ARTL/APRL/TAS/GED/AIL created For ex. South/Karnataka/Bangalore/MG Road / Store 1.
Fashion/Footwear/Sports
/ATBL Site/ Location A site can be closed temporarily (for example, the road
ARTL/APRL/TAS/GED/AIL Blocking where the site is placed is closed, for renovation…).
Fashion/Footwear/Sports
/ATBL A site can be close permanently (etc. it is sold, loses its
ARTL/APRL/TAS/GED/AIL Site / Location Closing license, market decisions etc.).
Page 7 of 24
(Process Details)
2.3 Business Requirement Flow Diagram (If any)
3.0 Business Process Description

This business blueprint document covers the process of creating and maintaining sites.
Sites are the organisational unit in which stocks are managed and/or sold. SAP Fashion Management
system distinguishes between two different site categories. Distribution centers (DC) receive
merchandise from external vendors and deliver it to stores. Stores receive merchandise from external
vendors and/or DCs and sell it to consumers.
Stocking and sales of merchandise in sites require maintenance of other master data objects
- Replenishment data needs to be maintained on article/site level.
- In the vendor master the supply region of a site needs to be maintained to allow deliveries to
a site.
- Listing conditions which represent the link between articles and sites are created based on
listing.
3.1 Site Process Details
The sub-processes covered in this document are:
 Site creation
 Site maintenance
 Site blocking
 Site closing
3.2 Site Creation

This sub-process covers the creation of new sites in the system including the creation of the site’s vendor
and customer. For Arvind we will create DC (distribution centre) and stores for all formats (COCO, COFO &
FOFO). For each DC we will create its Vendor & Customer and for store will create its customer only. For
DC we will have multiple cost centre and profit centre while a store have only one cost centre and profit
centre. We will create reference store (virtual store) for each of the division of Arvind to manage the
actual site creation.
Page 8 of 24
(Process Details)
Site Creation
Predecessor process: None

Step Input Process description Output Role
1 Estate A new site is to be opened and is Site details:

Managemen required to be entered it in the system. Characteristics
t Format of store (COCO,
COFO, FOFO…) etc
2 Site Details The site profile is determined for the Site Profile
store based on the site details
3 Site Details A decision is a new site profile is needed Site Profile
has to be taken
4 Site Details A new Site Profile is created in SAP Site Profile in SAP
5 Opening date Site Master Data is entered in the system: Site ID

Site details Organization/ Calendar
Site Profile
Address
Valuation/Inventory
Management
Listing/Materials Planning
Purchasing/ Distribution
POS
Layouts/Blocks
Characteristics
6 Site ID A cost center and a Profit Center are Cost center ID Finance
created and associated to the site Team
7 Site Details The site customer is created in the Customer ID
system. The partner profiles are assigned
Site Profile to the site customer in order to identify
its rights and responsibilities.
8 Site ID The site range is implemented in the Category
Layouts system. This is an external process, which Managem
Format is explained in its own process definition ent Team
Range document.
Page 9 of 24
(Process Details)
3.2.1 Site Number (Code)

The site code in SAP is a 4-character alphanumeric code. So for all the legal entities of Arvind , the site
numbering convention will be as follows:
 The first character will be a letter representing store format (COCO, COFO & FOFO or Factory
outlet), and the last three characters will be alphanumerical and consecutive characters.
 Site’s Vender & Customer will have same code as its site.
*** Changes Version 1.1
3.2.2 Layout
A site layout will have a number of layout areas. Layout areas are used to divide up the space in
a site or department.
For TAS , we will create separate layout modules for brands like Arrow , USP etc.
The stores will have a layout which will be attached to the layout modules. The total
sales area of a store will be defined in the site Master. The area to be allocated for each brand
needs to be mentioned in the customization. Any change in the area for brands cannot be done
by the user. It is a customization request and need to be routed through IT team.
*** End of change.
3.2.3 Site profile
Sites will be created using a site profile, which is used to differentiate between site categories, i.e.
stores or distribution centres. Site profiles also determine what data is mandatory or optional for a
site record, and how common data for all the sites in that profile are automatically populated e.g.
valuation, purchasing, listing, POS and layout data. This data is maintained in a reference site and
reference site is assigned to each site profile.
For Arvind, each site format (DC, COCO, COFO & FOFO) will have separate site profile.
Page 10 of 24
(Process Details)
3.3 Site Maintenance

This sub-process covers all the changes in the site master data including the changes in the site’s
vendor & customer. The main data that could change in the site master record for the Arvind sites
is (if required):
 The purchasing data, the POS outbound and inbound
 The valuation and inventory management as it has important implications in stock
valuation and therefore in the financial accounts.
 The merchandise category data for site
 The supplying distribution centre for the site
Changes in the site customer data:
 Site customer data changes are uncommon, but some data such as the bank account.
Page 11 of 24
(Process Details)
START
1
Change
Customer MD Store/ Site MD
Customer?
Update Customer Update Site

2 Master Data in Master Data in 3
SAP SAP
END
3.4 Site Grouping

Site Groups are used for grouping stores for different objectives such as pricing, promotions, listing,
mass article maintenance, and reporting.
Page 12 of 24
(Process Details)
Start
Decision
to Create
Site Group
Site Groups
Created in SAP
Sites Assigned to
Site Groups
End
Pricing Promotions Listing
Site Hierarchy Creation

1 Arvind can define a site group for pricing, Site group definition
promotions listing or any other purpose.
2 Site group Site group is created in the system. Site group created in SAP
3 Site group Sites are assigned to the site group Sites assigned to the site
and sites group
4 Site Groups The following processes are executed in Prices activated,
SAP: Promotion assigned to
 Pricing the sites
 Promotion Articles Ranged
 Listing Etc.
 Etc.
Page 13 of 24
(Process Details)
3.5 Site Hierarchy

This process covers the creation of a site hierarchy according to Arvind’s territorial structure. The site
hierarchy will be used for reporting as an alternative to the company organization structure.
Page 14 of 24
(Process Details)
Site Hierarchy Creation

1 Arvind defines a site hierarchy Site hierarchy

definition
2 Site Site groups are created in the system Site groups created for
hierarchy the hierarchy in SAP
3 Site groups Site groups are assigned to superior site Site hierarchy Structure
groups to form the hierarchy created in SAP
4 Site groups Sites are assigned to the lowest level site Site hierarchy created
and sites group in the hierarchy. in SAP
3.6 Site Blocking
A site can be closed temporarily (for example, the road where the site is placed is closed, for
renovation…) or permanently (etc. it is sold, loses its licence, market decisions etc,). Both events
have to be updated in the system. Permanent closure is covered as a separate sub-process.
For a temporary closing, the period of time and a blocking reason must be entered in the site
master data. To avoid further downloads to/uploads from the store, the POS Outbound/POS
Inbound profile is temporarily removed. When the site is reopened, the master record needs to be
updated again.
Page 15 of 24
(Process Details)
Site Temporary Closing

1 Arvind decides to temporarily block a Blocking reason and

store blocking dates
2 Blocking Blocking reason and blocking dates Site blocked in SAP
reason and updated in the system.
blocking
dates
3 POS outbound is deactivated for the Site POS Outbound

store removing its POS profile. block.
Page 16 of 24
(Process Details)
3.7 Site Closing

When the site is closed permanently a different process is carried out in SAP. The first step is to enter the
closing date in the site master data. The site will still be available in the system and if for some reason is
reopened it would be able to start operations again. When the information is no longer required the site
discontinuation function can be used. This function consists on the following steps:
 The related master data is normally archived first
 The customer master data is archived
 General site data is archived.
 In case archived and deleted master data is needed back in the system there is a reloading
program.
Page 17 of 24
(Process Details)
Site Permanent Closing

1 BP Decides to close a store Closing Date
2 Site Closing Closing date and archiving flag se-up in the Site Closed in SAP
date system
3 Site Closed POS outbound is deactivated for the store Site POS
removing its POS profile. Outbound blocked
4 Site Closed Is the Site Master Data going to be
archived?
5 Site Closed Archive Site Master Data Record Site Master Data Technical
archived Team
6 Site Closed If the site is not going to be archived, Is the
site going to be reopened?
7 Site Closed If the site is going to be reopened the Site Reopened
closing date and the archiving flag is reset.
8 Site POS Outbound is activated for the Store
Reopened
9 Site Closed If the site is not going to be reopened it will Site Closed
remain in this situation until a decision is
taken.
Page 18 of 24
(Process Details)
3.8 Process Maps:
Creation of New Store
start
Event
Confirmation for creating Confirmation for creating New

New store DC
Master Data Team
Creation of site master

(EBO/MBO/Factory Outlet/
DC) in SAP
3.9 Business Process Steps

Key Process Steps
Sr.
Activity TCode Input Output
No.
Create Site with its
1. WB01
Vendor & Customer
2. Change Site WB02
3. Display Site WB03
Page 19 of 24
(Process Details)
4.
5.
6.
7.
8.
9.
3.10 Key Data Structure Elements

3.11 Associated Master Data Elements (If any)
3.12 Interface Maps (If any)
3.13 Reports Mapping (If any)

(Detail the SAP Standard reports which is planned to address the business requirements in the SAP
System).
3.14 Process Variations / Exceptions (If any)

(Detail the process variations / exceptions which is planned to address the business requirements in the
SAP System).
4.0 Integration Points (If any)

(Detail the integration of other modules, other application data’s, etc. in the SAP System).
Page 20 of 24
(Process Details)
5.0 Key Business Improvements (If any)

(Detail the business improvements in addressing the requirement in the SAP System).
6.0 Changes to Existing Organization (If any)

(Detail the changes which need to be adopted by the organization)
7.0 Gaps
Process Reference / Description of Recommendation to fulfil
Reference No. Details Functional Deficits the Gap
8.0 Development Considerations (RICEFW)
8.1 Data Conversion Considerations

Description of the Data Conversion Method
Objects / Data to be (like LSMW, iDoc, BDC, Reference Development
Reference No. converted etc.) Specification No
Page 21 of 24
(Process Details)
Description of the Data Conversion Method

Objects / Data to be (like LSMW, iDoc, BDC, Reference Development
Reference No. converted etc.) Specification No
8.2 Interface Considerations

Description of the System / Reference Interface Specification
Reference No. Process to be interfaced Document Number
BBD_RET_001_I005 Customer Master data of site
send from SAP FMS to POS
8.3 Form Considerations

Reference Form Development
Reference No. Description of the Forms Specification Document Number
8.4 Reporting Considerations

Description of the Report Reference Report Development
Reference No. Requirements Specification Document Number
Page 22 of 24
(Process Details)
Description of the Report Reference Report Development

Reference No. Requirements Specification Document Number
8.5 Functional Enhancement Considerations

Description of the Functional Reference Functional Enhancement
Reference No. Enhancement Requirements Specification Document Number
9.0 Authorization requirements

Authorization to the transaction codes in the SAP System will be based on the role played by the person in
the organization.
Below table is an example of the Authorization Matrix. The users (super user, middle level user, end user)
are assigned with a role in the SAP System.
Transaction Code will be detailed in the Authorization Matrix.
Role 1 Role 2 Role 3

SAP T.Code Transaction Description (Role Name) (Role Name) (Role Name)
WB01 Create Site
WB02 Change Site
WB03 Display Site
WB07 Change Site’s customer
WB08 Change Site’s vendor
Page 23 of 24
(Process Details)
10.0 Annexure (If any)s

 Annexure-1 – KDS Document
 Annexure-2 – BPML Document
11.0 Flow Chart Legend
(Process Description)
Start/ End
SAP Process
(Responsible Department/ Role)
SAP Background
Process
Manual Process
(Outside SAP)
Decision
Printout/ Form
Other Defined
Process
Page 24 of 24

BBP - RET - 002 - Site Master Data Management - V1.2

Uploaded by

Copyright:

Available Formats

BBP - RET - 002 - Site Master Data Management - V1.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BBP - RET - 002 - Site Master Data Management - V1.2

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What processes are covered in the document?

What processes are covered in the document?

SAP Implementation

Business Blueprint Document

Module: SAP FMS Retail

ARVIND / IBM Confidential

1.0 DOCUMENT INFORMATION..........................................................................................................4

2.0 BUSINESS REQUIREMENT............................................................................................................5

3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................8

3.12 PROCESS VARIATIONS / EXCEPTIONS (IF ANY)...................................................................................12

4.0 INTEGRATION POINTS (IF ANY).................................................................................................13

5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................13

6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................13

8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................14

9.0 AUTHORIZATION REQUIREMENTS............................................................................................15

10.0 ANNEXURE (IF ANY)SS............................................................................................................16

11.0 Flow Chart Legend..................................................................................................................17

1.0 Document Information

Document Category Business Blueprint Document

1.1 Document Version

Date Version No. Author Change Description

1.2 Document Approval Details

Function Name (Designation) Role Sign & Date

Naina Acharya IBM Team Lead 27.10.2016

T Sudhir IBM Project Manager 02.11.2016

Abel Correa Arvind Project Manager

1.3 Reference Document Details (If any)

1.4 Abbreviations Used (If any)

2.0 Business Requirement

The document is applicable for following business verticals of Arvind group:

Business Vertical Applicability (Yes/No)

2.2 Details of Business Requirement

GED Factory outlets need

2.3 Business Requirement Flow Diagram (If any)

3.0 Business Process Description

3.2 Site Creation

Predecessor process: None

1 Estate A new site is to be opened and is Site details:

5 Opening date Site Master Data is entered in the system: Site ID

3.2.1 Site Number (Code)

3.3 Site Maintenance

Update Customer Update Site

3.4 Site Grouping

Pricing Promotions Listing

Site Hierarchy Creation

Predecessor process: None

3.5 Site Hierarchy

Site Hierarchy Creation

Predecessor process: None

1 Arvind defines a site hierarchy Site hierarchy

3.6 Site Blocking

Site Temporary Closing

Predecessor process: None

1 Arvind decides to temporarily block a Blocking reason and

3 POS outbound is deactivated for the Site POS Outbound

3.7 Site Closing

Site Permanent Closing