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.
The process in material management for the various types of Change Requests
Workflow - Change Request Types
Activity split of data maintenance
Change Request: CREATION workflow
Creation Workflow of Finished Goods
The workflow with 9 steps, 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.
Change Request: EXTENSION workflow
Extend = Add Plant and/or Sales Area (only add, no change - no change of basic data)
Change Request: Change workflow
Change Plant data = example ; change MRP/Storage/Finance data
+Qm change Inspection Interval
The workflow is simplified: there is no need for business validation or global data changes by GBU data manager.
Receiver Determination
Receiver determination assigns work items created by the workflow to receiver groups based on a set of predefined attributes
Receiver determination assigns work items created by the workflow to receiver groups based on a set of predefined attributes
The SAP receiver determination table: Z4M_T_MAT_RCV
Transcoding of some data elements
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 transcode table will convert the “ZD” to Z0 for when the data arrives in RCS and Z4 when it arrives in PF1.
MATERIAL CODIFICATION
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 a new number: 3xxxxxx.
There will be a transcode table to convert these values.
SM30: Z4R_MDG_T_TARSYS
OTHER DATA TRANSCODE
SAP MDG for Finished Goods Master Data Management – Overview 2
MDG - connection to MDG systems
MDG runs in a browser based front-end. To connect you will use a URL (see below). MDG will use Single-Sign-On, so it is not necessary to indicate user-id & password.
MDG - Production system
TIP: Save this shortcut to your Favourites or your desktop
→ If you want to connect in a different language change the language code in URL: https://mqgsapr3.ibm.be.solvay.com:44373/nwbc/?sap-nwbc-node=root&sap-theme=sap_corbu&sap-client=100&sap-language=FR
Supported Lang:
English EN
German DE
French FR
Spanish SE
MDG - TEST SYSTEM MQG
If you want to use the test system this is the link to the Quality area: https://mqgsapr3.ibm.be.solvay.com:44373/nwbc/?sap-nwbc-node=root&sap-theme=sap_corbu&sap-client=100&sap-language=EN
Copy this link into your favourites, or place it as a shortcut on your desktop. Only use this if you have one test user-ID.
OPTIONAL - MQG Testing with multiple user-IDs If you are testing the workflow with more than one ID (a requestor ID, business approver ID, …) then you will need to connect using the SAPLOGON PAD:
Search for “MDG Quality” in the saplogon pad, then Right-Click on the line, followed by “SNC Logon without Single Sign On”. You are obliged to indicate the ID and password. Language can be changed here.
In SAP you must launch the transaction “NWBC”.
MDG – Homepage
The homepage gives you direct links to process a material (search, create, change..) and to view requests that are in progress.
Customizing the Layout
You can hide some elements by right-click on the title and then ‘User settings > Hide “xxxxxxxx”’
You can reset the layout by right-clicking on the title and then “User settings >More > reset user settings for running application”
The layout settings will be saved for all subsequent sessions.
MDG – Search
To search for existing materials to display or maintain the data…
Click on Search Material.
You will be presented with the Search crietria selection.
MDG – Search by Description
MDG – Search by Plant Code
MDG – Search by RCS Code
MDG – Material Display
All of the material data that you would typically find in MM03 transaction will be displayed in MDG.
BASIC DATA SALES DATA PLANT DATA
Remember, you can continue to display the master data in the RCS/PF1 system in transaction MM03.
You can hide the elements that do not interest you, as explained before.
Quick Navigation – You can navigate quickly using the Assignment Block at the top right of the page.
To immediately start editing the data click on the edit buttin in the header.
You will be presented with some options to select the type of change…
You can launch the Material MAINTENANCE PROCESS this way
MDG – Transcoding of some data elements
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 transcode table will convert the
“ZD” to Z0 for when the data arrives in RCS and Z4 when it arrives in PF1.
MATERIAL CODIFICATION
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 a new number: 3xxxxxx.
There will be a transcode table to convert these values. SM30: Z4R_MDG_T_TARSYS
OTHER DATA TRANSCODE
See list
Full presentation: https://docs.google.com/presentation/d/1-fCLckZS5xpvzFepZkAaSknhaZZclCTrGof7LelV6rI
MDG – Creation Workflo w
MDG – Extension Workflow
MDG – Change General Data Workflow
MDG – Change Sales/Purchasing Data
MDG – Change Planning Data
MDG – Change FICO Data
Some data will continue to be maintained in the ERP systems(RCS/PF1) in MM01 or MM02...
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 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.
SAP MDG for Finished Goods Master Data Management – Overview 3
i. Creation by Copy Template
MDG – Creation Workflow
The workflow above shows the 9 stakeholders in the process and the main steps:
→ Requestor – Approval – Global Dara Enrichment – Local Plant Data Enrichment – Code Creation
MDG – Creation Workflow: Requestor
The requestor initiates a new MDG change request.
The Requestor indicates some essential information such as:
Reminder: 1 MDG request = 1 ZMAT creation
MDG – Homepage
You will most often use
these two sections
when you want to
maintain materials
or to review the open
Change Request
MDG – Creation Workflow: Requestor
To submit a new creation request click create Finish Goods.
Reminder: 1 MDG request = 1 ZMAT request
It is recommended to indicate the Organization Data in this screen:
At minimum:
PLANT
SALES ORGANIZATIO
DISTRIBUTION CHANNEL
Change Request Type = ZMAT01
If you do not enter any information here then the Plant and Sales Organization must be indicated in the following screen.
Click on CONTINUE to proceed.
Important: the plant and sales organizations must belong to the same country. This is to reduce the complexity of the receiver determination.
TIP: you can create a material by copying the template.
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.
REFRESH: similar as Check. Click on refresh after Submit to display validation options for Business Approver.
COLLAPSE ALL: collapses all data sections
EXPAND ALL: expands all data sections
Note: The Material code $1306 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.
HIDE unwanted sections
There is a lot of data that is dysplayed by default. Soma data is not relevant to you, the requestor.
You u can hide the unwanted sections by right-clicking on the box header and then:
User Settings > Hide “xxxxx”
SUGGESTION: The requestor may wish to hide all parts, except:
CHANGE REQUEST SALES
BASIC DATA DISTRIBUTION CHAINS
DESCRIPTIONS PLANTS
DIMENSIONS PLANTS-GENERAL DATA
BASIC TEXT FOREIGN TRADE
The layout settings will be saved for all subsequent sessions.
RESTOR HIDDEN SECTIONS
You can reveal the hidden sections by right-clicking on any
section header and then:
User Settings > Hidden Screen Elements > Restore “xxxxxxx”
CHANGE REQUEST
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.
OPTIONAL: to add suplementary information
In NOTES some additional information can be entered. If you are going to WITHDRAW or RETURN a request then it is mandatory to add a note.
In ATTACHMENTS you can attach a file.
BASIC DATA
General Data
SALES
In SALES in the Shipping part, you must indicate the TRANSPORTSTION GROUP:
DISTRIBUTION CHAINS
You already added a sale org/channel in the iniitial step. You can add an additional distribution channel by clickling ADD.
PLANT
You already added a plant code un the initial step. You can add an addictional plant by clicking ADD.
Reminder: the NEW plant and sales organizations that YOU ADD must belong to the same country. If there is an error then remove the Sales Area and add it in a new change request.
ERROR CHECKING
You can click on CHECK in the header to see if any mandatory data is missed.
Occasionally, when you modify a field, MDG will sistematically refresh the data and it will automaticlaly verify the data.
PLANT GENERAL DATA
The errors shown in the last slide concern the Plant mandatory data:
INDUSTRIAL ORIGIN FOR ACCOUNTING: the plant code that produces the material
MATERIAL USAGE REASON: PRO = Production RES = Resale
You can also indicate the PROFIT-CENTER if it’s known.
PLANT FOREIGN TRADE
Here you must indicate:
COUNTRY OF ORIGIN
REGION OF ORIGIN
Select the appropriate codes from the
list, or enter them directly if known.
For plants in BRAZIL you must also indicate:
MATERIAL CFOP CATEGORY = 0
CONTROL CODE = IF KNOWN
To change the Control Code after the creation you will need to submit a ZMATSP02 change request (Change sales or purchasing data).
MRP DATA?
Note, as a REQUESTOR you can also populate the data in the other parts of the material. For example, if you are responsible for completing some MRP data then it is possible to do so in this Requestor step.
! Note that in this case the “PLANT PLANNING” Contributor step is mandatory later on in the process. It will at least need to be approved, or additional data added by the plant stakeholder.
FINAL CHECK
EMAIL NOTIFICATIONS
- There will be sent two email notifications.
Notification to the Requestor confirming the new Change Request has been submitted and the CR number.
Notification to the Business Approvers (next in Workflow) that a CR is waiting for their attention.
IF THE REQUESTOR IS ALSO DEFINED AS THE BUSINESS APPROVER
You can immediately click on REFRESH in the header...
then you will see the APPROVAL options...
Click on DIRECT APPROVE or SEND FOR REG.AFFAIRS APPROVAL to complete the Business Approver step.
VIEW THE STATUS OF THE WORKFLOW: 1
In your current screen you can see the status of the request; who is next in line for the validation/maintenance.
At the header of the request click on Workflow Log
REVIEW THE WORKFLOW 1
The workflow steps will be listed, including any that are completed or “Ready” to be processed. You can click on the Processor entry “Multiple..” to view who will be managing the next step in the workflow.
REVIEW THE WORKFLOW 2
You can also see the status of your requests from the main MDG Homepage
Clicking on My Change Requests will go to the Change Requests overview. You can see all requests that you have created.
You can immediately see the current status
In order to view the Workflow first clicl on the line to select the request, then click on the Workflow Log.
MDG – CREATION WORKFLOW: Business Approver
The BUSINESS APPROVER provides the initial validation. He/she can Approve immediately, send the request to Regulatory Affairs for validation, or return/reject the request.
Reminder:
if the requestor also acts as the Business Approver then in the previous step he/she can refresh the request immediately to show the validation options.
REVIEW THE REQUESTS WAITING FOR YOUR ATTENTION
CREATION WORKFLOW – BUSINESS APPPROVAL
If the options above are not completely visible the click on the double arrow to show a drop-down list.
Choose:
● Direct approve : approve the request, send it to the GBU Data Manager to enrich
● Send for Reg.Affairs Approval : ask for Product Stewardship to record their validation (TBC)
● Send back to requestor : revert to previous step, requestor must confirm some information
● Withdraw : reject this request
● Cancel : if you are in Edit mode click on Cancel to cancel changes and return to Display mode
● Check : check that all mandatory data is completed
● Edit : some information to be changed or supplemented
Click on DIRECT APPROVE or SEND FOR REG.AFFAIRS APPROVAL to complete the Business Approver step.
*EU BULK requests will be sent to Regulatory Affairs*
MDG – CREATION WORKFLOW: Regulatory Affairs
Initially the REGULATORYAFFAIRS validation will only be done in the EUROPEAN zone. In other words when an EU plant is attached to the new material.
Rules: For a new creation only ask for the BULK code to be validated by Regulatory Affairs.
CREATION WORKFLOW – BUSINESS APPROVAL
If the options above are not completely visible the click on the double arrow to show a drop-down list.
Choose:
● Approve : approve the request, send it to the GBU Data Manager to enrich
● Send back to Business Approver: revert to previous step, requestor must confirm some information
● Cancel : if you are in Edit mode click on Cancel to cancel changes and return to Display mode
● Check : check that all mandatory data is completed
● Edit : some information to be changed or supplemented
Click on APPROVE to complete the Regulatory Affairs step.
*EU BULK requests will be sent to Regulatory Affairs*
MDG – CREATION WORKFLOW – GBU Data Manager
The GBU Data Manager will complete any additional data such as: PRCOM (Basic Material) code if it not already added Purchasing Group.
→ Initially the GBU data managers will be : Peter Rollason / Yoomi Kim / Carlos Morales
First Actions
Click on EDIT in the header then CHECK. You will see some missing data:
BASIC DATA
BASIC MATERIAL: 9xxxxxxx PRCOM code. Typically it should already be entered by the requestor. MATERIAL GROUP: 0450
PLANT: PURCHASING
PURCHASING GROUP: ### Suggest intercompany/trading purchasing group
AUTOMATIC PURCHASE ORDER ALLOWED: TICKED
FINAL CHECK
You can click on CHECK in the header to see if any mandatory data is missed.
All missing mandatory data should now be completed. Some other data can be completed by the Data Manager. it should be decided what will be managed by the Service-center.
When all data is compelted click on SUBMIT.
MDG – CREATION WORKDLOW: Global Data Steward
The Global Data Steward will complete any additional data such as: additional languages for Descriptions & Basic Text, additional Units of Measure, tax classifications.
Initially for Europe the Data Steward role will be managed by Lisbon Service-centre.
For other zones (NAM/LAM/APAC) the Data Steward role will be managed by Yoomi Kim / Carlos Morales / Peter Rollason.
FIRST ACTIONS
Click on EDIT in the Header then CHECK. You will see some missing data:
BASIC DATA
GROUPING
GENERIC ITEM GROUP CATEGORY: NORM
MATERIAL GROUP PACKAGING MATERIALS: 0001 BULK, 0005 PACKED IN PALLET
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
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
Option 2:
connect directly into MDG using the shortcut:
From the MDG homepage click on
MY CHANGE REQUESTs.
Change the filter to be:
TO BE PROCESSED BY ME
Click on the change request number to display the request.
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
OPTION2
From the MDG homepage,
click on MY CHANGE REQUESTS
Change the filter to:
TO BE PROCESSED BY ME
Click on the change request number to display the request.
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
MDG – CREATION WORKFLOW: Finance
The FINANCE contributor will complete the Costing & Accounting data of the material master.
NOTE - no costs are maintained in the MDG system
The finance contributor will receive a notification during the plant contribution steps and a final notification when the material is complete.
The costing is launched in the ERP system (WP1, PF1) when the local material data is completed (BOM..).
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
SAP MDG for Finished Goods Master Data Management – Overview 4
MDG - EXTEND PLANT/SALES WORKFLOW
TODAY
A process exists for when we add an additional PLANT or SALES area into an existing material.
Typically an email, or a form, or an external process (Navigator) is used to send a request directly to a data administrator. He/she will add the plant/sales data and then coordinate the plant data-enrichment with specific stakeholders in the same way as for a new material creation.
ADDITIONAL VALIDATION
Depending on the region and the local processes it could be necessary to ask for validation from Supply Chain or from Regulatory Affairs.
IN MDG
The process is similar in MDG. There is a specific workflow with specific stakeholders.
The flow is similar as the MDG Creation process except that the initial validation arrives directly at the GBU Data Manager for data enrichment: it could be the case that the plant/sales extension is already validated outside of MDG, or the requestor is already the Business Approver so no validation is required. Therefore a direct approval is considered.
On the other hand, the GBU data Manager can decide that the business and/or Regulatory Affairs must validate the request.
MDG - EXTEND PLANT/SALES - Requestor
The REQUESTOR initiates a new MDG change request. In this case it is to either:
add a new plant and sales area to an existing material, or
add a new sales area to an existing material (-> in this case there will be no plant contribution steps).
Reminder:
1 MDG Request = 1 ZMAT creation
1 new plant or 1 new Sales Area is required.
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.
MDG – EXTENSION WORKFLOW: GBU Data Manager
The GBU data manager reviews the new request.
MY CHANGE REQUEST
Review the requests waiting for your attention. From the homecreeen:
Click on the change request number to display the request.
As in the Creation workflow check for and complete any missing data such as Purchasing Group. Remember to select the NEW Plant and/or Sales line before changing any data.
When all data is completed...
Choose:
● Direct approve : approve the request, send it to the GBU Data Steward to enrich
● Send for Business Approver Approval : ask for business validation
● Send for Reg.Affairs Approval : ask for Product Stewardship to record their validation*
● Send back to requestor : revert to previous step, requestor must confirm some information
● Cancel : if you are in Edit mode click on Cancel to cancel changes and return to Display mode
● Edit : some information to be changed or supplemented
● Check : check that all mandatory data is completed
Click on DIRECT APPROVE or SEND FOR REG.AFFAIRS APPROVAL to complete the GBU Data Manager step. *EU BULK requests will be sent to Regulatory Affairs*
MDG – EXTENSION WORKFLOW: Business Validation
The Business Approver reviews the new request.
MY CHANGE REQUESTS
Reviw the requests waiting for your attention. From the homescreen:
Choose:
● Approve : approve the request, send it to the GBU Data Manager to enrich
● Send for Reg.Affairs Approval : ask for Product Stewardship to record their validation (TBC)
● Send back to Data Manager : revert to previous step, requestor must confirm some information (must Edit + Comment)
● Withdraw : reject this request
● Edit : you can add or change some information
● Check : check that all mandatory data is completed
Click on APPROVE or SEND FOR REG.AFFAIRS APPROVAL to complete the Business Validation step. *EU BULK requests will be sent to Regulatory Affairs*
MDG – EXTENSION WORKFLOW: Regulatory Affairs
The Regulatory Affairs Approver reviews the new request.
MY CHANGE REQUESTS
Review the requests waiting for your attention. From the homescreen:
Choose:
● Approve : approve the request, send it to the GBU Data Manager to enrich
● Send for Reg.Affairs Approval : ask for Product Stewardship to record their validation (TBC)
● Send back to Data Manager : revert to previous step, requestor must confirm some information (must Edit + Comment)
● Withdraw : reject this request
● Edit : you can add or change some information
● Check : check that all mandatory data is completed
Click on APPROVE or SEND FOR REG.AFFAIRS APPROVAL to complete the Business Validation step. *EU BULK requests will be sent to Regulatory Affairs*
MDG – EXTENTION WORKFLOW: Global Data Stewaard
The Global Data Steward will complete any additional data such as: tax classifications, Loading Group, Freight Group,...
MY CHANGE REQUESTS
Review the requests waiting for your attention. From the homescreen:
Complete the data in the request in the same way as for a CREATION
SUBMIT the request in order to send it to the Plant Contributors.
MDG – EXTENSION WORKFLOW: Plant Contribution
MY CHANGE REQUESTS
Review the requests aiting fot your attention. From the homescreen:
Complete the data in the request in the same way as for a CREATION workflow:
● PLANNING
● STORAGE
● QM
● FINANCE
MDG – CREATION WORKFLOW
FINAL STEP – COOMPLETION – CODE TRANSFER
When all plant contribution steps are completed the new material code is updated in the MDG system.
The modifications 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 updated material code.
RCS/PF1 further maintenance Reminder: BOM, Costing, Quality Inspection, Label, Sales release
MDG – DATA EXCEPTIONS
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 – EXTEND SALES WORKFLOW
When adding only a new Sales view in the material we are not concerned with the plant data. In this case the Workflow will be smaller.
You can manage the next part or leave it for the Data Steward to complete.
Go to the section “Distribution Chains: Grouping.” You can specify :
Accounting Assignment Group= F (Finished) or T (Trading)
Item Category Group=
● NORM
● ZMAN
● ZSAM for samples
Go to the section “Distribution Chains: Tax.”
You can specify:
Tax classification=1 for all except FR/LCFR=”A”
FINAL CHECK
You can click on CHECK in the header to see if any mandatory data is missed.
When there are no errors found you can click on SUBMIT
You will receive a change request number and a Notification to confirm that the request has been submitted (next slide).
MDG – EXTEND SALES: Data Manager/Steward
After the Requestor step is completed it is the responsibility of the GBU Data manager (and optionally the Business approver, Regulatory Affairs) and then the Global Data Steward to verify/complete any additional data.
Once these steps are completed the new sales area is applied to the material in MDG and then transferred to RCS/PF1.
MDG – CHANGE PLANT DATA: MRP/Storage/FICO
For changes made to PLANNING / STORAGE / FICO data there is a shorter workflow since it concerns PLANT data. There is always a requestor in the first step. He/she submits a request to modify the material. Generally it is the person who specifically manages the data of a given plant. It is possible it is someone not directly involved with the plant.
The local plant contributors will always receive the new request to review/validate/enrich the new changes. Once approved the change is applied in MDG and the ERP system.
MDG - PLANT BLOCKING: MRP/FICO
The plant block is maintained at the plant level. Therefore, in MDG, it involves the participation of the plant contributors.
Once again the workflow is limited to only the Requestor and the plant contributor. Generally it will be the same person in both roles.
MDG – PLANT BLOCKING: Data Admins
If the GBU data admin wants to add a plant block (to be followed by a deletion flag) then it is better to use the change type: ZMATSP02 Change sales or purchasing data.
In this case there is no “plant contribution” and the workflow stays within the Data Admin group for the validation.