How to use MDG_BS_SUPPL_HARM - MDGS: CVI Settings

SAP Transaction Code - Details

• Transaction Code: MDG_BS_SUPPL_HARM

  Description: MDGS: CVI Settings

  Release: S/4HANA and ECC 6

• • Program: MDG_BS_SUPPL_HARM

    Screen: 0

    Authorization Object:

  • Development Package: MDG_BS_ECC_SUPPLIER_ACCESS

    Package Description: Access to Vendor Master Data for MDGS

    Parent Package: MDG_ECC_SUPPLIER

  • Module/Component: CA-MDG-APP-SUP

    Description: MDG Supplier (Central Parts)

Smart SAP Assistant

• SAP Tcode: MDG_BS_SUPPL_HARM - MDGS: CVI Settings

   for Supplier Harmonization
  
  Overview: 
  MDG_BS_SUPPL_HARM is a SAP transaction code used to configure the CVI (Central Validation Interface) settings for supplier harmonization in the Master Data Governance (MDG) system. This transaction code is used to ensure that the data entered into the MDG system is consistent and accurate. 
  
  Functionality: 
  The MDG_BS_SUPPL_HARM transaction code allows users to configure the CVI settings for supplier harmonization in the MDG system. This includes setting up the CVI rules, which define how data should be validated and how errors should be handled. Additionally, this transaction code can be used to define which fields are mandatory and which are optional, as well as which fields should be checked for duplicates. 
  
  Step-by-step How to Use: 
  1. Access the MDG_BS_SUPPL_HARM transaction code by entering it into the command field in the SAP GUI. 
  2. Select the “CVI Settings” tab and then select “New Entries” from the drop-down menu. 
  3. Enter the desired CVI settings, such as which fields should be mandatory or optional, and which fields should be checked for duplicates. 
  4. Once all of the desired settings have been entered, click “Save” to save your changes. 
  5. To activate your changes, click “Activate” from the toolbar at the top of the screen. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the available CVI settings before making any changes in order to ensure that they are making the most appropriate choices for their organization’s needs. Additionally, users should always test their changes in a test environment before activating them in a production environment to ensure that they are working as expected.