B&M SOP 9 - Change in supplying DC (Replenishment)
Suplying DC
Change in Supplying DC for Replenishment
Table of Contents
1. Change in Supplying DC
1.1. Approach
1.2. Prerequisite
1.3. Impact on downstream system
Change in Supplying DC
Approach
|
Objective: |
This document is to define a process of change in supplying DC for replenishment |
|
Overview: |
Currently from replenishment point of view, SSL is maintaining supplying DC at “Site Level” or “MC – Site Level” only. Note: Before change in supplying DC either at “Site Level” or “MC – Site Level”. Make sure that effected article – site data are updated again in system. |
|
Impact: |
Historical transaction will not change (e.g. STO/PO.) |
|
Approval: |
B&M need to take approval from following team before requesting “Change in supplying DC”
|
|
Prerequisite: |
B&M team need to make sure that for new Supplying DC
|
|
Initiator: |
B&M to upload data and approval mail in MDM portal (i.e. spandhan) in below format. |
|
Format: |
|
|
Executer: |
MDM Team |
|
Action: |
Maintain “Article – Site - Supplying DC” data in S4. Maintain supplying DC at “Site Level” or “MC – Site Level” in S4. |
|
Note: |
Till the time this activity didn’t get completed, replenishment job should be on hold. |
Impact on downstream system
|
Sn |
System |
Impact |
Comment |
|
1 |
POS |
No |
No impact |
|
2 |
CRM |
No |
No impact |
|
3 |
eScheme |
No |
No impact |
|
4 |
eVRF |
No |
No impact |
|
5 |
Hybris |
No |
No impact |
|
6 |
WMS |
No |
No impact |
|
7 |
B2B |
No |
No impact |
|
8 |
Loyalty |
No |
No impact |
|
9 |
BW |
No |
No impact |
|
10 |
Vistex |
Yes |
Depends on data |
|
11 |
DIAL + MIAL |
No |
No impact |
Sign-off
|
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> |
|
|
5 |
|
Purnima Shetty <Purnima.Shetty@shoppersstop.com> |
|
|
6 |
|
Junaid Kuravle <Junaid.Kuravle@shoppersstop.com> |
|
|
|
NAME |
DATE |
|
Initial Draft |
Vishal Varlyani <Vishal.Varlyani@shoppersstop.com> |
09-10-2020 |
|
Reviewer |
Uttam Rawat <Uttam.Rawat@shoppersstop.com> |
09-10-2020 |
|
TEAMS Path |
DISHA Collaboration -> General -> 03 Realize -> 3.8 Draft SOPs for B&M -> 3.8.1 To be release for DocuSign |
Related Articles
B&M SOP 7 - Change in Vendor or Vendor business model
Vendor Change Change in Vendor business model Or Vendor Table of Contents 1. Vendor Change 1.1. Approach 1.2. Old vendor activities. 1.3. New vendor activities. 1.4. Impact on downstream system 2. Sign-off Vendor Change SSL has created following ...B&M S4 FAQ
S 4 F A Q s 1 ERROR TYPE PO CREATI ON This error indicates that one or more of the mandatory fields are currently blank in the upload file Purchase Group, Vendor, Article, Site, PO Qty are the mandatory fields which need to be filled in by the user 2 ...B&M SOP 4 - Impact of Change in PIR on Sales and Inventory
PIR Maintainance Impact of Change in PIR Table of Contents 1. PIR Maintenance 1.1. Approach 1.2. Highlights: 1.3. Impact on transaction: 1.4. Impact on downstream system 1.5. Question and Answers: 2. Sign-off PIR Maintenance Overview: A Purchase Info ...B&M SOP 8 - TAX Change
TAX Maintainance TAX Maintenance (Trade) Table of Contents 1. TAX Maintenance (Trade) 1.1. Approach 1.2. Impact on downstream system 2. Sign-off TAX Maintenance (Trade) The Harmonized System Nomenclature (HSN) code is the 8 digit uniform code used ...B&M SOP 5 - Change in article hierarchy
Change in Article Hierarchy Change in Article Hierarchy Table of Contents 1. Change in article hierarchy 1.1. Impact 1.1.1. Purchase Group and Authorization matrix: 1.1.2. PIR 1.1.3. Open PO (Released & Unreleased) 1.1.4. L4 vs Characteristic and MC ...