In this blog, I will provide a simplified explanation of four key IMG configuration nodes related to the technical configuration of SAP Master Data Governance (MDG) on S/4HANA.
The SPRO configuration node path is as follows:”
TC: MDGIMG -> General Settings -> Technical Settings for Master Data:
Node “Tansports”:Node “Client Copies”:Node “Profile Parameter Setting”:Node “Define MDG Landscape Profile”:
1. Node “Transports”
This node allows you to configure transport settings for MDG objects. It ensures that changes made in one system (e.g., Development) can be transported to another system (e.g., Quality or Production).
Transporting Customizing Settings from Client 100 to 110
The main purpose of the Wizard for RFC Destinations is to assist in setting up RFC (Remote Function Call) connections for communication between clients within the same SAP system or across systems, specifically for tasks related to transport methods (like transporting customizing settings or performing client copies).
Examples:
Transporting Customizing Settings: If you want to transport settings to client 110 from client 100 and you use the wizard to create the RFC connection by specifying 110 as the target client.Create the RFC in Client 100. This is because the source client (100) needs to communicate with the target client (110) to execute transport-related activities.
2. Node “Client Copies”
This node manages settings for client copies in SAP systems. It allows you to replicate data, customizing, or user settings between clients in the same or different systems.
Client Copy (Config & Cust) from Client 100 to 110
The diagram represents a Local Client Copy Process in SAP MDG (Master Data Governance), illustrating the relationship between the following clients:
Client 000 (Admin Client): Used for global configurations and SAP MDG system-wide settings.Client 100 (Configuration/Development Client): Where customizations and configurations are developed.Client 110 (Target Client): Destination client for the local client copy.
Steps:
Create RFC Destination: Use the “Wizard for RFC Destinations” to define a target RFC connection. Example: Create an RFC destination with the name MDGTR@S21CLNT110, which points to Client 110.Assign RFC Destination for Transport Methods: Link the RFC destination to transport methods (e.g., before-export and after-import processing).Postprocessing Configuration: After configuration, use “Complete Postprocessing” to finalize settings within Client 100.
Data and configuration settings are copied from Client 100 to Client 110.
3. Node “Profile Parameter Setting”
This node helps you define and adjust SAP system profile parameters that influence the technical behavior of MDG.
Optimizing Profile Parameters for SAP MDG:
When setting up SAP MDG Application Framework, ensure proper configuration of profile parameters to avoid performance issues like memory bottlenecks.
One critical parameter is abap/shared_objects_size_MB, which determines the memory allocated for ABAP Shared Objects. For medium-sized systems, allocate 100–300 MB, adjusting based on additional requirements from other software layers.
Purpose of this configuration:
– The shared objects memory acts as a high-speed cache, reducing the load on the SAP HANA database and improving response times for users.
step-by-step explanation of the diagram:
1. Users like Purchasers, Sales, Production Team, and FI/Reporting teams access the SAP system through the SAP GUI.
2. The dispatcher manages and allocates tasks to available work processors.
3. Work processors handle the actual processing of tasks.
4. Shared Objects Allocation: The parameter abap/shared_objects_size_MB determines how much memory (e.g., 100 MB in diagram) is allocated for storing shared objects (Frequently accessed product master data is copied into shared memory for faster access).
5.The database holds the complete master data, and only frequently accessed data is moved to shared memory for better performance.
4. Node “Define MDG Landscape Profile”
This node is used to define landscape profiles that describe your MDG system setup, including central and connected systems.
Technical Settings “Define MDG Landscape Profile”
Customer Issue:
A customer using SAP MDG on ECC is facing significant performance issues with master data searches and duplicate checks.
Solution:
As an SAP MDG consultant, implement SAP HANA-based search and duplicate checks by leveraging SAP HANA as a secondary database.
Replicate MDG data into the SAP HANA search schema using tools like SAP Landscape Transformation (SLT) or other methods.
Establish and maintain a database connection to the SAP HANA schema for search operations.
This architecture enhances performance by utilizing SAP HANA’s optimized search and duplicate-check capabilities.
#SAP #SAPMDG #SAPConfiguration #SPRO #IMGNodes #MasterDataGovernance #SAPS4HANA #SAPTransport #ClientCopy #ProfileParameters #MDGLandscape #SAPBlog #SAPConsultant #SAPTech #SAPExperts #DataGovernance #SAPHANA #SAPIntegration
In this blog, I will provide a simplified explanation of four key IMG configuration nodes related to the technical configuration of SAP Master Data Governance (MDG) on S/4HANA.The SPRO configuration node path is as follows:”TC: MDGIMG -> General Settings -> Technical Settings for Master Data:Node “Tansports”:Node “Client Copies”:Node “Profile Parameter Setting”:Node “Define MDG Landscape Profile”:1. Node “Transports”This node allows you to configure transport settings for MDG objects. It ensures that changes made in one system (e.g., Development) can be transported to another system (e.g., Quality or Production).Transporting Customizing Settings from Client 100 to 110The main purpose of the Wizard for RFC Destinations is to assist in setting up RFC (Remote Function Call) connections for communication between clients within the same SAP system or across systems, specifically for tasks related to transport methods (like transporting customizing settings or performing client copies).Examples:Transporting Customizing Settings: If you want to transport settings to client 110 from client 100 and you use the wizard to create the RFC connection by specifying 110 as the target client.Create the RFC in Client 100. This is because the source client (100) needs to communicate with the target client (110) to execute transport-related activities.2. Node “Client Copies”This node manages settings for client copies in SAP systems. It allows you to replicate data, customizing, or user settings between clients in the same or different systems.Client Copy (Config & Cust) from Client 100 to 110The diagram represents a Local Client Copy Process in SAP MDG (Master Data Governance), illustrating the relationship between the following clients:Client 000 (Admin Client): Used for global configurations and SAP MDG system-wide settings.Client 100 (Configuration/Development Client): Where customizations and configurations are developed.Client 110 (Target Client): Destination client for the local client copy.Steps:Create RFC Destination: Use the “Wizard for RFC Destinations” to define a target RFC connection. Example: Create an RFC destination with the name MDGTR@S21CLNT110, which points to Client 110.Assign RFC Destination for Transport Methods: Link the RFC destination to transport methods (e.g., before-export and after-import processing).Postprocessing Configuration: After configuration, use “Complete Postprocessing” to finalize settings within Client 100.Data and configuration settings are copied from Client 100 to Client 110.3. Node “Profile Parameter Setting”This node helps you define and adjust SAP system profile parameters that influence the technical behavior of MDG.Optimizing Profile Parameters for SAP MDG:When setting up SAP MDG Application Framework, ensure proper configuration of profile parameters to avoid performance issues like memory bottlenecks.One critical parameter is abap/shared_objects_size_MB, which determines the memory allocated for ABAP Shared Objects. For medium-sized systems, allocate 100–300 MB, adjusting based on additional requirements from other software layers.Purpose of this configuration:- The shared objects memory acts as a high-speed cache, reducing the load on the SAP HANA database and improving response times for users.step-by-step explanation of the diagram:1. Users like Purchasers, Sales, Production Team, and FI/Reporting teams access the SAP system through the SAP GUI.2. The dispatcher manages and allocates tasks to available work processors.3. Work processors handle the actual processing of tasks.4. Shared Objects Allocation: The parameter abap/shared_objects_size_MB determines how much memory (e.g., 100 MB in diagram) is allocated for storing shared objects (Frequently accessed product master data is copied into shared memory for faster access).5.The database holds the complete master data, and only frequently accessed data is moved to shared memory for better performance.4. Node “Define MDG Landscape Profile”This node is used to define landscape profiles that describe your MDG system setup, including central and connected systems.Technical Settings “Define MDG Landscape Profile”Customer Issue:A customer using SAP MDG on ECC is facing significant performance issues with master data searches and duplicate checks.Solution:As an SAP MDG consultant, implement SAP HANA-based search and duplicate checks by leveraging SAP HANA as a secondary database.Replicate MDG data into the SAP HANA search schema using tools like SAP Landscape Transformation (SLT) or other methods.Establish and maintain a database connection to the SAP HANA schema for search operations.This architecture enhances performance by utilizing SAP HANA’s optimized search and duplicate-check capabilities.#SAP #SAPMDG #SAPConfiguration #SPRO #IMGNodes #MasterDataGovernance #SAPS4HANA #SAPTransport #ClientCopy #ProfileParameters #MDGLandscape #SAPBlog #SAPConsultant #SAPTech #SAPExperts #DataGovernance #SAPHANA #SAPIntegration Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
