MDG - Master Data Governance.
It helps to gain a single, trusted view of data and to address digital, analytical, and operational challenges head on, to simplify enterprise data management,
increase data accuracy, and reduce total cost of ownership with a single solution that facilitates consolidation and central governance.
There are 10 different types of workflows available, one of which is optional.
There is an initial request submission, followed by validation steps, then a global data maintenance, then finally the plant-specific data maintenance.
ZMAT01 - For material creation
ZMAT02 - Extend/add plant/sales area
ZMATACT - Reactivate material
ZMATFIC2 - Change local (plant) data FICO
ZMATGEN2 - Change general data
ZMATPLN2 - Change local plant data - planning
ZMATQM2 - Change local plant data - QM
ZMATSP02 - Change sales organization purchasing data
ZMATWM02 - Change local plant data - storage/warehouse
ZMAT06 - Set deletion flag
MDG will manage the data of 2 different systems: RCS and PF1. There will be some instances where a code, such as Plant Blocking code “Z0”, is used in both systems but have different meanings in the respective systems. In this example a new blocking code “ZD” will be used in MDG. A trans-code table will convert the “ZD” to Z0 for when the data arrives in RCS and Z4 when it arrives in PF1.
New codes in MDG will be created with the number beginning 3xxxxxx. This code will be the same in MDG and RCS/PF1.
Pre-Existing RCS/PF1 materials created before MDG implementation will keep their code in their respective ERP systems, but in MDG they will be assigned with a new number: 3xxxxxx.
There will be a trans-code table to convert these values SM30: Z4R_MDG_T_TARSYS
OTHER DATA TRANS-CODE
Plant block
Availability Check
MRP Type
Valuation class
Material type (PF1)
Receiver Determination
Receiver determination assigns work items created by the workflow to receiver groups based on a set of predefined attributes
The SAP receiver determination table accessible through SM30: Z4M_T_MAT_RCV
Business units currently in MDG:
CS - Novecare
CH - Special Chemicals
SD - Soda Ash
Step assignment:
BA | Business Approver |
DA | GBU Data Admin/Mgr |
DF | Contributor Finance & Controlling |
DP | Contributor Production Planning / MRP |
DQ | Contributor Quality Management |
DS | Contributor Storage - Warehouse Mgt |
GD | Global Data Steward |
PS | Product Steward / Regulatory Affairs |
It is necessary to find MDG Production System and connect the same way as to any other SAP system
Afterwards transaction NWBC should be entered and saved in favorites for easy access to MDG homepage in Internet Explorer
MDG homepage is being used to treat incoming Change requests, Maintain material data using requester role, create link between systems and other functions.
As many materials have been loaded in MDG from target systems PF1 and WP1, MDG article number will differ from the one in the other SAP platform. However, there is a simple way to search for MDG or target system number.
By using search Material function, MDG number to be processed can be found this way:
Search method has to be changed to Remote Client Search if target system number is available and MDG number needs to be found.
In ID value, article number should be entered
Business system WP1_400 or PF1_020 has to be specified, after entering these values and pressing "Search" button, MDG number will be displayed below. By clicking on it, material change request can be opened right away if needed.
Using the Enterprise Search Option, material can be found by description or MDG number.
Once material number has been found, it can be displayed by clicking on it and it will open a new Internet explorer window containing all material data.
All of the material data that you would typically find in MM03 transaction will be displayed in MDG.
Remember, you can continue to display the master data in the RCS/PF1 system in transaction MM03.
Once Material is opened, data can be seen by sections or by using "Expand All" option, all available information will be visible at once.
Quick Navigation – You can navigate quickly using the Assignment Block at the top right of the page and choose necessary area where changes are needed.
To immediately start editing all of the available data click on the edit button in the header.
You can launch the Material MAINTENANCE PROCESS this way or you can return to the homepage by closing the window if no changes are required.
Data Exceptions to be maintained directly in RCS or PF1
Classification data views (direct maintenance)
Commodity code in Foreign trade views (GTS, or direct maintenance). Forecast views
Quality Management views (for inspection types) Label data views (GLM).
Accounting/Costing views
The ZPRC (PRCOM) material will be created directly in MDG (MM01) without the classification view. It will be transferred into the ERP at the same time as the ZMAT transfer. Then the classification view is added.
To submit a new creation request it can be done through MDG Homepage by choosing option Create Finished Goods
New window will open where plant, sales area and distribution channel has to be entered as a minimum. On the right side Template option can be used to copy data from similar material from the same GBU.
If you do not enter any information here then the Plant and Sales Organization must be indicated in the following screen.
Correct sales area can be chosen by clicking on the small arrow in the corner and choosing "Custom Filter" then option appears to enter necessary sales area, in the same way other missing data can be added such as plant, storage location, warehouse etc.
NOTE: the plant and sales organizations must belong to the same country. This is to reduce the complexity of the receiver determination.
Page Layout
Save: save current status, you can exit and return to your request later.
Submit: if all mandatory data is completed you can submit. The request moves to the next step in the workflow.
Cancel: cancels the open request. You will have to close the open screen.
Edit: if you are viewing a material, or have opened a WF request waiting for your input you must click on Edit.
Check: will check that the data entered is valid and that no mandatory data is missed.
Collapse All: collapses all data sections
Expand All: expands all data sections
NOTE: The Material code $2192 is a temporary number. It is not the final material code.
A description with asterisk * next to it means that the field is mandatory. You cannot submit until it is populated. The orange box means that the data is already entered by the system.
The Change request number is indicated. Note it for reference.
The description of the Request is already populated. Note - it is not the Material Description
It is possible to add additional information in Notes and Attachments. If you are going to WITHDRAW or RETURN a request then it is mandatory to add a note.
For Urgent and Emergency requests Priority can be added for a team to know if CR needs to be treated with priority.
Currently Three Global Business Units (GBU) are handled by Data Operations team in MDG system, all Change requests coming to the team are already approved by Business Approver. Nevertheless, all the steps and information in MDG has to be validated by Global Data Steward which is our step, to insure data quality passing to the target system.
| GBU | Scope | MatGroup | Contact | |
| Special Chem (CH) | EMEA + APAC | Z33 / Z34 | Rolf Tarrach | Rolf.Tarrach@solvay.com |
| Special Chem (CH) | LAM | 0450 | Sylvie Barros | sylvie.barros@solvay.com |
| Soda Ash (SD) | EMEA + APAC | Z10 / Z11 / Z13 | Sylvia Prudky | sylvia.prudky@solvay.com |
| Soda Ash (SD) | LAM | Z10 / Z11 / Z13 | Andreia Bortoli | andreia.bortoli@solvay.com |
| Soda Ash (SD) | NAM | Z10 / Z11 / Z13 | Amanda Peng | amanda-weili.peng@solvay.com |
| Novecare (CS) | EMEA | 0450 | Peter Rollason | peter.rollason@solvay.com |
| Novecare (CS) | LAM/NAM | 0450 | Carlos Morales | carlos.morales@solvay.com |
| Novecare (CS) | NAM PF1 | Z50 | Marlene Islas | marlene.islas@solvay.com |
| Novecare (CS) | RU PF1 | Z50 | Christina Weiser | christina.weiser@solvay.com |
| Novecare (CS) | APAC | 0450 | Yoomi Kim | yoomi.kim@solvay.com |
Change request Inbox can be accessed by pressing on "Change Requests" or "Workflow Inbox"
Change requests currently available for approving will be displayed in the list, to open the request, please click on it and new window will open.
Before starting to process Change request, Check button can be pressed to see what is missing for this specific change, errors will be helpful to detect what exactly is missing and in which area, after they can be corrected by pressing Edit button on the header level.
In the Change Request view basic information about the request itself can be seen.
If the notes or attachments are added, it will have a number displayed next to it mentioning the amount of notes and attachments.
Each Change request has ID number which can be compared to a ticket number in the Freshdesk system.
In the Reason GBU for the material is indicated.
In the CR Status You can see in which step this request currently is displayed. Data Operations team will mostly receive Data Steward step with few exceptions.
Type of Change Request will always inform about the nature of changes, either its new creation, extension or update in Purchasing data or other options.
In target system view RCS or PF1 number can be seen which is linked to MDG material code. In the example case Requester is extending MDG material already existing in PF1 system to WP1 plant therefore RCS number is not yet available because Change Request is not yet approved. Nevertheless, for new creations and extensions target system number will match with MDG code. Only historically loaded materials are keeping old system code.
There are several things to pay attention to maintaining material data.
Material number will be assigned by the system and will be displayed in General data.
Business Unit is always displayed, that determines all MDG Workflow for approvals and depending on that there are some rules to pay attention to in material setup.
Base unit of measure is mainly KG but can also be LB, sometimes new material code can be requested as a duplicate because of different Base Unit of measure.
Material Group is 0450 for WP1 and Z**-**** for PF1 system. Each time MDG code is open for both SAP platforms, it needs to have Material group set up as per PF1 system rules. Description should be copied from Basic material if RCS code exists.
Old material Number is required for CS business unit, if it has RCS code available which differs from MDG code. For new creations it has to be removed as MDG code will match with RCS code.
Division codification is set up per RCS rules, PF1 code will be indicated in the brackets in the division name.
Product Hierarchy is mandatory to be added when material is extended to PF1 system, if WP1 product is being extended to PF1, this field needs to be filled and hierarchy has to be found in PF1 system using transaction Z0R2 sorting by the division.
Generic Item Group Category is always NORM.
Material Group Packaging Materials is filled for WP1 system - 0005 for packed, 0001 for bulk codes.
Basic material is mandatory for WP1 material codes, for CS it is set up by Sylvie Mazzon and for SD by Sylvia Barros
Environmentally Relevant flag is always marked.
Dangerous Goods Indicator profile - in PF1 000 for non dangerous and 001 for dangerous
in WP1 Z00 for non dangerous, GPP for dangerous
Codes are mapped and if material exists in both systems, it does not need to be changed.
EAN code is mandatory when material is created for SD business unit in PF1 system.
EAN Category always HE
To find code which can be used, MARA table in SE16 transaction needs to be opened in PF1 and EAN code 5413735* entered, then the results need to be sorted in the descending order.
In the site https://www.gs1.org/services/check-digit-calculator last used EAN code has to be entered without the last digit (checking digit) and the last remaining number should be increased by +1
Meaning, if the last code was 5413735000859, number 9 is removed and code 541373500086 entered in the site for calculation and system gives code to copy to material master.
EAN code needs to be always inserted not only in the Base unit of measure but also on the handling package of the material, so for example if material is handled in Pallets you need to enter the SAME EAN code for the PAL.
Additional data are usually completed by the requester.
NET Weight is always 1 KG
Gross Weight is never the actual Gross Weight value, it needs to be a difference between Gross and Net Wt, usually pre-filled by requester as we do not have actual gross weight information.
Volume for CS GBU is 1,5 with unit CD3 is not filled by requester already.
DESCRIPTIONS
add the material description
in the languages below:
PT
PL
JA
KO
ZH
Z9
ES
IT
DE
FR
BASIC DATA TEXT
add the material description in the languages
listed above.
DIMENSIONS
add the dimensions below: 11023 LB = 5000 KG
1 KAI = 1 KG
1 TO = 1000 KG
If a DRUM or TE (Tote/IBC) is defined then add
the relevant conversion;
example
1 DR = 200 KG 1 TE = 1060 KG
SALES
add the dimensions below:
GENERAL DATA
CROSS DIST.CHAIN MATERIAL
= 63/61
DATE = current date
SHIPPING
TRANSPORTATION GROUP = as required
All materials will be available for sale at initial creation to avoid additional LAUNCH process for data admin.
Ensure that the correct sale area line is selected before proceeding...
DISTRIBUTION CHAIN: SALES
if it is a packed material (Drum, IBC):
QUANTITY STIPULATIONS
MINIMUM ORDER QUANTITY= PACK
SIZE MINIMUM DELIVERY QTY= PACK
SIZE DELIVERY UNIT= PACK SIZE
ROUNDING PROFILE= Z50%
DISTRIBUTION CHAIN: GROUPING
if it is a packed material (Drum, IBC):
SALES
ACCOUNTASSIGNMENT GROUP= F
→ If product is coming from 3RD PARTY THEN= T (Trading)
ITEM CATEGORY GROUP= NORM HALIFAX 8058 = ZMAN
OLDBURY 0214 = ZMAN
DISTRIBUTION CHAIN: TAX
In each line Add
Tax Classification = 1
Except for Country FR, TAX Category LCFR. Tax class = A
PLANTS
ENSURE THAT THE CORRECT PLANT LINE
IS SELECTED BEFORE PROCEEDING
PLANT: GENERAL DATA
PLANT SPECIFIC MAT.STATUS
If the standard practice is to
put a block in place then add ZC
FORECAST REQUIREMENTS
PERIOD INDICATOR: M
ATP
AVAILABILITY CHECK GROUP: X2, X7, X8 - depending on zone
PLANT: FOREIGN TRADE
GENERAL DATA
MATERIAL CFOP CATEGORY= 0
:add code for BRAZIL products
CONTROL CODE = add code for BRAZIL
products if known
COUNTRY OF ORIGIN=
REGION OF ORIGIN=
PLANT: SALES
GENERAL DATA
MATERIAL FREIGHT GROUP= add code for US products
SHIPPING DATA
LOADING GROUP= 0001 Bulk, 0002 Packed
FINAL CHECK
MDG – CREATION WORKFLOW – Planning MRP
only for 0005 plnts
The PLANNING contributor will complete the MRP* and Production data of the material master.
The Planning contributor will receive a notification during the plant contribution steps and a final notification when the material is complete.
Additional data such as BOMs/Recipes will be maintained in the ERP System (WP1 / PF1).
In some cases the MRP data will be managed by the requestor/Demand Planner
FIRST ACTIONS
Click on EDIT at the Header Level.
Navigate directly to the Plants section using the Assignment Block: ALWAYS expand the Plants section, then be sure to select the correct plant line that you want to maintain. It is important to do this if there are multiple plants attached to the material.
PLANT: GENERAL DATA
GENERAL DATA
PLANT-SPECIFIC MATERIAL STATUS: ZC
add ifa block is needed*
Note that the MDG blocking codes are not the same codes as RCS / PF1. There is a transcodification.
*If a blocking code is added then remember that a NEW CHANGE REQUEST must be submitted in MDG to remove the block!
FORECAST REQUIREMENTS
PERIOD INDICATOR: M
ATP
TOTAL REPLENISHMENT LEAD TIME: as required
MDG – CREATION WORKFLOW: Storage / Warehouse Management
The STORAGE contributor will complete the Storage/Warehouse data of the material master.
*He/she could also have authorisation to maintain the MRP data. Both MRP and storage data can be maintained at the same time*
The storage contributor will receive a notification during the plant contribution steps and a final notification when the material is complete.
If STORAGE LOCATION is created via MIGO be sure to create the StorLoc in MDG to keep the systems aligned
FIRST ACTIONS
Click on EDIT at the HEADER level
ALWAYS expand the Plants section, then be sure to select the correct plant line that you want to maintain. It is important to do this if there are multiple plants attached to the material.
MDG – CREATION WORKFLOW: Quality
The QM contributor is part of the MDG process but will enter some minimal data (inspection interval), or perhaps no data. There is a check and a validation to be made in order to complete the PLANT CONTRIBUTION steps.
The QM contributor will receive a notification during the plant contribution steps and a final notification when the material is complete.
The QM Inspection setup will be maintained in the ERP System (WP1 / PF1) with MM01 or MM02 as normal.
FIRST ACTIONS
There is no data for the QM Contributor to enter in MDG except for “Inspection Interval”.
If the Inspection Interval is not maintained then all that is needed is to click on SUBMIT.
FIRST ACTIONS - INSPECTION INTERVAL
At minimum the QM "task" in MDG is a validation. However, if the QM Inspection Interval value is maintained then it must be done in MDG...
Click on EDIT at the HEADER level
ALWAYS expand the Plants section, then be sure to select the correct plant line that you want to maintain. It is important to do this if there are multiple plants attached to the material...
You can find the QM Inspection Interval in Plant: Quality Management…
Then click on SUBMIT.
Inspection plan in RCS
1. If MDG QM task is only "submit" (no Inspection Interval is maintained), then when the code is created in RCS system there is no QM plant view.
The user must create the QM view in MM01, then to add the Inspection setup as normal.
2. If MDG QM task includes maintaining the Inspection Interval then the QM view will be created automatically in RCS. The user must manage the Inspection setup in MM02
FIRST ACTIONS
Click on EDIT at the HEADER level
ALWAYS expand the Plants section, then be sure to select the correct plant line that you want to maintain. It is important to do this if there are multiple plants attached to the material.
PLANT: GENERAL DATA
GENERAL DATA
PLANT-SPECIFIC MATERIAL STATUS: ZC
add if a block is needed*
Note that the MDG blocking codes are not the same codes as RCS / PF1. There is a transcodification.
*If a blocking code is added then remember that a NEW CHANGE REQUEST must be submitted in MDG to remove the block!
PROFIT CENTER
the profit center can be added or changed
PLANT: COSTING
GENERAL DATA
VARIANCE KEY : Z_Z001
QUANTITY STRUCTURE DATA
COSTING LOT SIZE: as required
SPECIAL PROCUREMENT: optional
VALUATION AREA PLANT
you must add a Valuation Header.
Click on ADD
VALUATION AREA PLANT: COSTING
The Material Origin and Costed with Quantity options should already be ticked by default.
FINAL STEP - COMPLETION - CODE TRANSFER
When all plant contribution steps are completed the new material code is created in the MDG system.
The code will be transferred into the ERP system (RCS / PF1) almost immediately.
NOTIFICATION
A final email notification will be sent to all stakeholders in the MDG workflow. The email will confirm the new material code.
RCS/PF1 further maintenance Reminder: BOM, Costing, Quality Inspection, Label, Sales release
→ Some data will continue to be maintained in the ERP systems(RCS/PF1)
Classification data views (direct maintenance)
Commodity code in Foreign trade views (GTS, or direct maintenance).
Forecast views
Quality Management views (QA08)
Label data views (GLM).
Accounting/Costing views will be opened in MDG, but the costing run will be made in the ERP system.
The ZPRC (PRCOM) material will be created directly in MDG (MM01) without the classification view. It will be transferred into the ERP at the same time as the ZMAT transfer. Then the classification view is added.
MDG – CREATION BY Copy - put in beginning
To submit a new change request click on Change Material....
All BASIC DATA is locked.
This Extension request will not allow creation or change of General data (from MARA table).
You are concerned only with the new PLANT / SALES data.
MENTION DELETION PROCESS AND COUNTRY BY COUNTRY STUFF.