Transporting MDMGX objects from SAP ECC to Material Repository in MDM
Maybe include a bit of an intro?
MDMGX (MDM Generic Extraction Framework) is a standard SAP transaction code available within core SAP ERP systems depending on your version and release level.
At NIMBL, one of our major clients – a global services professional company – had a business requirement to add OverheadGroups functionality to their material repository in MDM. In order to accomplish this, we first had to perform local table (LT) configuration for OverheadGroups in our SAP ECC Development client as all local table configurations are maintained in SAP ECC in our client landscape.
To share what I learned, in this blog, I will provide the steps I performed to accomplish this requirement.
First off, our client’s ECC landscape is architectured according to SAP best practices.
Note: Transporting individual configuration objects under MDMGX is not possible – so it is recommended that all of the configuration objects under MDMGX need to be transported in order to maintain consistency across the landscape. Tip: Use an asterisk (*) to include all objects under a specific transport.
Configuring LT_Overheadgroups under MDMGX for Material repository
Step1: Login to the Development client
Step 2: Execute MDMGX transaction and click on Maintain Ports and Check-Tables
Step 3: Provide the appropriate System and Repository information to perform LT configuration
Step 4: Click new file to perform LT_OverheadGroups configuration
Step 5: Enter following details for LT_OverheadGroups configuration as shown below. This configuration provides data in English for LT_OverheadGroups table in MDM Data manager. This information will be available to user through portal.
Step 6: Copy the configuration to Testing client using the SCC1 transaction code. Make sure to include all of the objects under MDMGX as mentioned above.
After Successful testing and importing transports to your ECC production environment, we next need to perform the following steps to extract data to and from the ECC production LT_OverheadGroups table enabling data flow from the MDM Data Manager
Step 7: Execute transaction MDMGX and select “Start Extraction”
Step 8: Provide the Client details and port name of the table to which data needs to be extracted in the MDM Data manager. Click execute to start the extraction process.
Step 9: Login to the MDM Data Manager and make sure the data is available
So there you go. Easy as pie right? I think this is a best approach to make the data flow from SAP ERP system to MDM if the local tables are maintained in SAP ECC system.
Please stay tuned for my next blog covering how to maintain ports within the MDM console. I would love to hear your thoughts, comments, and own ideas. Please feel free to email me at firstname.lastname@example.org anytime.
Hope this helps!!!