• ARP produces are "target picture": Which article will be active / inactive in which MaGr / in which store?
    In the MMS Mass Data Maintenance, data are uploaded if the activation status is changing.

  • ARP provides the input ready to use for MMS Mass Data Maintenance
    But the MMS activation process still needs to be managed by the local Master Data and/or IM/Orga Team!

  • The MMS upload files will be prepared in ARP in 2 versions: (1) German, (2) English, for all other countries

  • In addition to the mass upload files, ARP has for selected metrics / codes a direct interface with MMS (ODIN = Object Data Inbound).
    The Local Code is directly related with the MMS Activation process, therefore covered also in this section
     
  •  With the introduction of the store exceptions MaGr activations and store activations have dependencies to previously processed activation files, so also the export of any activation file (not only the MMS upload) has to be done first after the previous activation file is processed.



ARP & MMS Mass Data Maintenance Workflow



Please note:


  • MMS manual maintenance: steps 10, 20
  • MMS maintenance via Mass Uploads: steps 25, 30, (35*), 39, 40, 45, 50 
  • Direct MMS maintenance from ARP via ODIN interface ("Send to MMS" button):step 32 (Local Code and Assortment)
    • In "ARP -> MMS" --> "ODIN Interface" you can see whether a field is maintained in MMS or not. In case the MMS field is empty, click on "Send to MMS" button.

Example: "Local Code Actual MMS" is empty


Click for more information about the ODIN data transfers

  • "Assortment Cluster" is a mandatory metric for all articles
  • "Local Code" must be set for all Local articles
    • A “Local” article in ARP is activated at store level in MMS
    • Make sure all "local" articles have the local flag set
    • Make sure all “local” articles also have the MMS Local Code set. Otherwise the activation is lost

Example: In case you change the MaGr of a store, all existing activations are “cleaned” – except for articles with a Local Code set.

  • "Season Code" is a mandatory metric for all articles with the Assortment Cluster SEASONAL
  • "Presence Period" is a mandatory metric for all articles with the Assortment Cluster SEASONAL or IN-OUT
  • "Price Tiers" and "Brand Levels" are optional fields



Examples of files generated by ARP for the mass upload in MMS:


During the ARP export we add a numeric prefix of the process (see below) to the file name. The prefix indicates the order of the uploads and has to be removed before upload to MMS

 

For MaGr activation and store activation the mass upload file structure is identical.


25 Maintain Article Class (= Order Assortment)

25_massendaten_akl.csv


30 Assign Articles to AssG - Mass Upload

30_massendaten_sortgrp.csv


35 Inactivate Display articles 

35_massendaten_aktiv.csv 

 

39 Inactivate articles per MaGr

39_massendaten_aktiv.csv 


40 Activate via MaGr

40_massendaten_aktiv.csv

 

45 Assign Stores to MaGr - Mass Upload

45_massendaten_ct126.csv

 

50 Activate at Store Level (revised)

50_massendaten_aktiv.csv



For additional information regarding the Activation Process, as well as information regarding each workflow step (e.g. Comments, ARP Output File Name, MMS Script / Manual MMS Maintenance, JIRA), please check: MMS Article Activation Process.


*MMS feature only used by Metro DE