L1

L2

L3

L4

L5

L6

L7

Company

Business Type

Category

Sub-category

Brand

Product

Fashion Pyramid

Code

S

E

B01

C009

D0193

E186

R

Eg:

SSL

EXCLUSIVE BRAND

APPAREL WOMEN WESTERN WEAR

CASUAL

ELLIZA DONATEIN

TROUSERS

FASHION

Node

X

X

X

X

X

X

Len

1 Char

1 Char

3 Char

4 Char

5 Char

4 Char

1 Char

Impact area of change

Impacted area

L2 – L3

L4

L5

L6 – L7

Purchase group 

X

Authorisation matrix

X

PIR

X

Open PO (Released & Unreleased)

X

L4 vs Char and MC vs Char mapping

X

X

Informative characteristic

X

X

Vistex margin

X

X

X

WMS mapping

X

X

X

Employee discount %

X

X

X

POS 18 DESC

X

X

X

POS Flags (MMRP...)

X

X

X

Article master

X

X

X

X

MIS Report

X

X

X

X

Scheme – (Promotions)

X

X

X

X

Overview:

Purchase group is a group of buyers who are responsible for procurement of material. The release strategy defines the approval process for purchase requisitions, which is dependent on purchase group.

Impact:

• SSL Purchase group code is concatenation of L2 and L3, so change in L2 – L3 will change purchase group code

• Historical transaction will not change.

• After article and PIR upload, Purchase group of an article and PIR master gets update automatically.

Overview

Purchase info records are information about terms for purchasing a specific material from a vendor. As per design, PIR upload utility takes “Purchase Group” from article master for PIR. This info record purchasing group is used in the authorization check and its list in reports like ME1L, ME1M and ME1W.

Impact

If we change purchase group then “Purchase info records” needs to be re-uploaded.

Overview

Change in L2-L3 will result in change in purchase group and re-uploading PIR

Impact

Purchase group in Open PO will not match with Purchase group on Article and PIR Master

Activity

B&M to cancel Open PO (Released & Unreleased) and create New PO

Overview

Characteristics code are mapped with MC # and AH L4. 

Impact

B&M team need to compare Old vs New “L4/MC- Char mapping” and in case of any addition/deletion of Characteristics or MC in existing L4 then B&M team needs to maintain this by re-uploading the articles. B&M to Log MDM ticket along with the data.

Approval

Business Head

Impact

Vistex contracts are based on L5. So B&M to check active contracts and if needed, request MDM to cancel old contracts and create new contracts in Vistex

Approval

Retail Finance (Bhavesh Shroff <bhavesh.Shroff@shoppersstop.com>)

Impact

As per design, WMS item family mapping is based on AH L5. So WMS team need to check mapping and if needed, request MDM to change (situational)

Approval

SCM (Krishnakant Pandey <Krishnakant.Pandey@shoppersstop.com>)

Impact

As per design, Employee discount % are based on AH L5. So MDM team need to check mapping and if needed, MDM to change the Employee discount % (situational)

Approval

Head Planning Archish Raghunathan <Archish.Raghunathan@shoppersstop.com>

Impact

POS flag matrix are based in L5. So MDM team need to check mapping and if needed, MDM team need to update articles (situational)

POS 18 Char is the concatenation of MC description and AH L5 description. So ideally Article reclassification will not impact POS 18 char but, if there is any change AH L5 or MC description then POS 18 Char needs to be updated

Sn

System

Impact

Comment

1

POS

Yes

Historical transaction will appear in old hierarchy (e.g. Sale...)

2

CRM

No

No impact

3

eScheme

Yes

Schemes (Created at L3 to L6 Node level) would be active at POS and Vistex. So unwanted scheme (situational) should be ended

4

eVRF

No

No impact

5

Hybris

Yes

Hybris articles are based on “mapping b/w S4 hierarchy vs Hybris category hierarchy”. So Article reclassification in S4 will lead to article reclassification in Hybris system too.

6

WMS

Yes

L5 wise Item family need to change (situational)

7

B2B

Yes

Historical transaction will appear in old hierarchy (e.g. PO, GRN, Sale...)

8

Loyalty

Yes

Historical transaction will appear in old hierarchy (e.g. Sale...)

9

BW, Click

Yes

Data needs to be re-loaded in Click and summary tables needs to be rebuild in BW and AWS.

10

Vistex

Yes

Scheme and contracts needs to change.

11

DIAL + MIAL

No

No impact (based on listing)

Frequency:

Twice in a year i.e. in March and September

Impact:

Historical transaction will not change (e.g. Sales, PO, ST...)

Initiator:

B&M to Fill hierarchy creation / change form

B&M to take approval from Planning Head and B&M head

B&M to upload approval mails, list of article detail with old and new hierarchy in MDM portal (i.e. spandhan).

Approval:

B&M Head, Planning Head, and Retail Finance

Activity Owner:

MDM Team

Plan:

MDM to plan hierarchy change activity 30 days prior to the execution date

Day

Who

Activity

1st

MDM

Publish business head wise plan

2nd to 10th 

B&M

Upload data and approval mails in MDM portal

11th to 20th 

MDM

Perform reclassification activity

11th to 20th 

MDM

Release for sign-off (Business head wise)

21th to 24th

B&M

Verify and sign-off

25th

MDM

Send closure mail to respective business head

Day

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

SSL Business Approval

Sr. No.

Date

Name

Signature

1

Planning Head - Archish Raghunathan <Archish.Raghunathan@shoppersstop.com>

2

Project Head - Krishnan Parameswaran <Krishnan.Param@shoppersstop.com>

3

Project Head - Mandavi Singh <Mandavi.Singh@shoppersstop.com>

4

Governance & Compliance - Ramnath Kamath <ramnath.kamath@shoppersstop.com>

NAME

DATE

Initial Draft

Vishal Varlyani <Vishal.Varlyani@shoppersstop.com>

11-07-2020

Reviewer

Uttam Rawat <Uttam.Rawat@shoppersstop.com>

11-07-2020

TEAMS Path

DISHA Collaboration -> General -> 03 Realize -> 3.8 Draft SOPs for B&M -> 3.8.1 To be release for DocuSign