EAN Maintainance
EAN/UPC Maintenance
Table of Contents
1. EAN (i.e. UPC) Maintenance
1.1. Approach
1.2. Note:
1.3. Impact on downstream system
2. Sign-off
|
Objective: |
This document is to define EAN change process in S4 system |
|
Rule: |
If inventory is present against an article then EAN deletion cannot be done |
|
Approval: |
B&M need to take approval from SCM Team before requesting EAN deletion. SCM - Purnima Shetty <Purnima.Shetty@shoppersstop.com> |
|
Initiator: |
B&M to upload EAN data and Approval mail in MDM portal (i.e. spandhan) in below format. |
|
Format: |
|
|
Executer: |
MDM Team |
|
Action: |
Maintain EAN in S4 |
|
After EAN Change |
Article detail will re-flow to downstream system (i.e. POS, hybris, WMS…) with New EAN # |
|
Change Log |
|
MDM team will use following tCodes for maintaining EAN’s in S4.
|
Custom t-Code |
Base t-Code |
Remark |
|
/nZMM_EAN |
|
Bulk EAN addition utility is available for mapping multiple EAN |
|
|
/nMM42 |
As of now, bulk EAN delete utility is not available in S4. |
|
While Article creation |
Private Brand |
Non Private Brand |
|
If EAN# Present in article upload data |
System will map running EAN# from “S4 configuration”. System will ignore EAN # present in article upload data. |
System will MAP EAN # present in article upload data. |
|
If EAN# is not present in article upload data |
System will map running EAN# from “S4 configuration”. |
System will MAP Old Article # as EAN # in article Master. |
|
Sn |
System |
Impact |
Comment |
|
1 |
POS |
Yes |
Article detail will reflow with new EAN |
|
2 |
CRM |
No |
No impact |
|
3 |
eScheme |
No |
No impact |
|
4 |
eVRF |
No |
No impact |
|
5 |
Hybris |
Yes |
Article detail will reflow with new EAN |
|
6 |
WMS |
Yes |
Article detail will reflow with new EAN |
|
7 |
B2B |
Yes |
Article detail will reflow with new EAN |
|
8 |
Loyalty |
No |
No impact |
|
9 |
BW |
Yes |
Article detail will reflow with new EAN |
|
10 |
Vistex |
No |
No impact |
|
11 |
DIAL + MIAL |
Yes |
Article detail will reflow with new EAN (if listed) |
|
SSL Business Approval |
|||
|
|
|||
|
Sr. No. |
Date |
Name |
Signature |
|
1 |
21-07-2020 |
Planning Head - Archish Raghunathan <Archish.Raghunathan@shoppersstop.com> |
|
|
2 |
21-07-2020 |
Project Head - Krishnan Parameswaran <Krishnan.Param@shoppersstop.com> |
|
|
3 |
21-07-2020 |
Project Head - Mandavi Singh <Mandavi.Singh@shoppersstop.com> |
|