SAP Implementation

at

Project Name

Business Blueprint Document

Version No.: 1.2

Effective Date:23.12.2016

Module: SAP FMS Retail

Process: Assortment Management
Document No.: BBD_RET_003_Assortment Management

ARVIND / IBM Confidential

 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 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................................................................................................6
2.3 BUSINESS REQUIREMENT FLOW DIAGRAM (IF ANY).............................................................................6

3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................6

3.1 PROCESS DETAILS..........................................................................................................................6
3.2 PROCESS MAPS:............................................................................................................................6
3.3 BUSINESS PROCESS STEPS...............................................................................................................6
3.4 KEY DATA STRUCTURE ELEMENTS.....................................................................................................7
3.5 ASSOCIATED MASTER DATA ELEMENTS (IF ANY).................................................................................7
3.6 INTERFACE MAPS (IF ANY)..............................................................................................................7
3.7 REPORTS MAPPING (IF ANY)...........................................................................................................7
3.8 PROCESS VARIATIONS / EXCEPTIONS (IF ANY).....................................................................................7

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

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

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

7.0 GAPS.............................................................................................................................................8

8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)..............................................................................9

8.1 DATA CONVERSION CONSIDERATIONS...............................................................................................9

Arvind/IBM Confidential
Page 2 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

8.2 INTERFACE CONSIDERATIONS...........................................................................................................9

8.3 FORM CONSIDERATIONS.................................................................................................................9
8.4 REPORTING CONSIDERATIONS........................................................................................................10
8.5 FUNCTIONAL ENHANCEMENT CONSIDERATIONS................................................................................10

9.0 AUTHORIZATION REQUIREMENTS............................................................................................10

10.0 ANNEXURE (IF ANY)...............................................................................................................11

11.0 Flow Chart Legend..................................................................................................................12

Arvind/IBM Confidential
Page 3 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

1.0 Document Information

Document Category Business Blueprint Document

Document Title Assortment Management
Author Chandra
File Name BBP_RET_003_Assortment Management_V1.0
Created On 22.10.2016

1.1 Document Version

Date Version No. Author Change Description

22.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 22.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

Arvind/IBM Confidential
Page 4 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

1.3 Reference Document Details (If any)

Department /
Title of the Document Version No Organization Reference / Remarks
Project Kick off Arvind
Bangalore

1.4 Abbreviations Used (If any)

Abbreviation Description
Distribution Channel
DC

2.0 Business Requirement

2.1 Applicability
The process described in this document details Manage Assortment processes necessary 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

Arvind/IBM Confidential
Page 5 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

Business Vertical Applicability (Yes/No)

Yes
Arvind True Blue Ltd
Yes
Arvind Premium Retail Ltd
Yes
Arvind Ruff and Tuff Ltd
Yes
Arvind Internet Limited
Yes
Garment export division

2.2 Details of Business Requirement

Open Point: Business has to be confirm that how many general assortments wants to be create:

Business Requirements Description Comments

Fashion/Footwear /ATBL Allocating Articles to site The Articles need to be allocated to the stores
ARTPL/APRL/TAS/GED/AIL (Warehouse, EBO, MBO & of Arvind Ltd for purchase and sales.
Factory outlet) to be done for
purchase and sales for a
particular season.
Fashion/Footwear /ATBL Articles grouping
ARTPL/APRL (Assortment)
/TAS/GED/AIL

2.3 Business Requirement Flow Diagram (If any)

3.0 Business Process Description

This section describes the SAP Assortment Management functionality and how it maps to the Arvind’s
business processes and requirements.
The aim of Assortment Management is to define which articles are to be listed for a store group.
Articles are listed based on a validity period. The assortments of a site consist of all the articles in which it
trades. By assigning assortments to sites you control which assortments — and which articles — a store can
purchase or sell. A site cannot purchase or sell an article that is not contained in one of its assortments.

Arvind/IBM Confidential
Page 6 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

A site can have different assortments – it always has one local site-specific assortment and it can also be
assigned several general assortments, if multiple assignments between site and assortment have been
activated. Multiple assignment means that a site may have several different assortments, and that an
assortment may be assigned to several different sites.
The assortment management demands of retailers differ greatly. Some require identical assortments in all
areas, while others demand assortments unique (for example) to each store. Some have mainly non-
replenishable seasonal merchandise and thus require frequent assortment changes, while others have mainly
replenishable basics and thus assortments that are subject to fewer changes. Assortment management takes
account of these differences and offers a variety of tools for making the assignment of articles to assortments
and the assignment of assortments to assortment users.

3.1 Manage an Assortment

An assortment is an object to which articles are assigned for a specific time frame (validity period). The
assignment of the individual articles to assortments is recorded in what are called listing conditions.
An assortment user must be assigned to an assortment before it can use the articles in that
assortment for its various business functions. Assortment users can be either customers or sites.
The following types of assortment are available:
 Local assortments
These are designated as type A for stores and type B for distribution centers. When you
create a site (store or distribution center), 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 centers, provided you have activated the multiple assignment functionality.
Multiple assignment means that a site may have several different assortments, and that an
assortment may be assigned to several different sites, so it is a n:m assignment. Multiple
assignments can significantly reduce the number of listing condition records in the
database. These results from the fact that articles are listed for assortments and not for

Arvind/IBM Confidential
Page 7 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

sites and therefore, the listing conditions created for an assortment are valid for all the
sites assigned to the assortment.
For TAS , each brand will have an assortment for RMG and one separate assortment for
Fabrics. Internally it would be creating layout modules which will be attached to a layout
and the layout to a particular site.
For Fashion/Footwear /ATBL /ARTPL/APRL we will have one assortment per division and
it will be assigned to the store and the articles will be listed to the layout modules.

For AIL , we will have two assortments associated with two stores – one for MBO and
another CREYATE which will be listed to the layout modules.

Figure 1: Local and General Assortment

3.2 Manage Listing

The listing operation is the creation of a link between an article and an assortment (creation of WLK1 line).

Arvind/IBM Confidential
Page 8 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

Listing updates listing conditions in table WLK1. Among other things, listing conditions contain the
validity periods and the module numbers. Data is also added to MVKE & MARC tables in which the
sales data for the article is stored.

3.3 Delisting

Deleting Listing Conditions called delisting. You can remove an article by either deleting the
listing conditions or discontinuing the article. Discontinuing Articles Discontinuation has greater
implications than mere deletion of listing conditions. Discontinuation removes the article master
record from the database, along with all data for that article, including the purchasing and listing
conditions.

3.4 Process Maps:

Manage Assortment

Assign Assortment Assign Assortment

Create General
User/ Assign Sites to Execute Listing Delisting User/ Assign Sites to
Assortment
General Assortment General Assortment

Remove
SAP FMS

Assortment User/
Delete Assortment
Assign Sites to
General Assortment

3.5 Business Process Steps

Key Process Steps
 Define a general assortment
 Assign Stores to General Assortment
 List the Articles - Listing
Arvind/IBM Confidential
Page 9 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

 Delisting – Delete Listing condition

 Delete Assortment

Sr.
Activity TCode Input Output
No.

Creating General WSOA1 Assortment

1.
Assortment Assortment Type

2. Assign Assortment User WSOA6

3. Change Assortment WSOA2

4. Display Assortment
WSOA3

5. Delete Assortment
WSOA7
Assign Merchandise
6. WSOA7
Categories

7. Listing (mass)
WSM3

8. Listing Individual
WSP4
Delete Listing /
9. WSP6
Delisting

3.6 Key Data Structure Elements

Key Data Structure Elements required to configure the business requirements in the SAP System:

 Sales Organization
 Distribution Channel
 Assortment Type
 Listing procedure
 Assortment Grades

Arvind/IBM Confidential
Page 10 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

 Assortment Grade Rules

3.7 Associated Master Data Elements (If any)
The required master data elements in the SAP System:
 Article Master
 Site Master
 Merchandise Category

3.8 Interface Maps (If any)

(Detail the required third party application interfaces and other electronic device interfaces (like printer,
bar code reader) required to address the business requirement in the SAP System).

3.9 Reports Mapping (If any)

(Detail the SAP Standard reports which is planned to address the business requirements in the SAP
System).

3.10 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).

5.0 Key Business Improvements (If any)

(Detail the business improvements in addressing the requirement in the SAP System).

Arvind/IBM Confidential
Page 11 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

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

Arvind/IBM Confidential
Page 12 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

8.2 Interface Considerations

Description of the System / Reference Interface Specification
Reference No. Process to be interfaced Document Number

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

Arvind/IBM Confidential
Page 13 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

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)

10.0 Annexure (If any)

 Annexure-1 – KDS Document
 Annexure-2 – BPML Document

Arvind/IBM Confidential
Page 14 of 15
 Business Blueprint Document – Retail (Module) – Assortment Management
(Process Details)
Document No: BBD_ RET_003 Version No: 1.2 Effective Date:
23.12.2016 Project Arvind

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

Arvind/IBM Confidential
Page 15 of 15