IMG MDG -2

Master Data Governanace, Central Governance

• General Settings:General Settings for Material,General Settings for Business Partner
  • Technical Settings for Master Data
    • Transports and Client Copies : profile parameter setting, define MDG Landscape Profile
      • transports
        • wizard for RFC Destinations
          • this wizard helps you to set up for a specific client  an RFC connection that is used by transport methods.
          • note: the RFC connections always display the current system and are only requesred for the communication between two clients.
          • standard settings : you can change the assignment of the RFC connection to the target in the activity assign RFC connections for transport methods.
          • activities: start the wizard and enter the target clients for method excution.
          • example
            • you want to transport customizing setting to client 100 of the current system. to do this, you start the wizard and enter 100 as the client.
            • you want to make a client copy from client 000. to do this, you start the wizard and enter 000 as the client.
        • assign RFC Destinations for Transport Methids
          • use: in this customizing activity, you maintain the RFC destinations that are used to execute transport methods(before-export and after-import). you can use these RFC destination for the following purposes.
            • transport postprocessing : technically, postprocessing of transports takes place in client 000 of the target system, but logically, postprocessing occurs in the import client. to be able to run these methods in the import client, you need an RFC connection for the respective target client in the target system of the transports.
            • local client copy(transaction SCCL) : an analysis phase(also called analysis exists of client copy) is started using the RFC destination in the source clients of a local client copy. the client copy is started in the target client and the analysis is executed through the RFC destination in the source cleint. this analysis phase is used to copy settings that require a special activity MDG_TR_EXEC_AI(postprocess client copy) in the target client.
            • copy by transport request(transaction SCC1): if the request was not released, the export preprocessing is started through an RFC connection in the cource client of the transport request before the data is copied to the target client.
              • for a given cleint, you can use the same destinations for all purposes menthioned
      • Client Copies
      • Reorganization
  • Data Modeling:Edit Data Model,Define Business Object Type Codes,Define Entity Type to be Used by Business Object Type,Define Prefixes for internal Key Assignment,Define Authorization Relevance per Entity Type,Generage Data Model-Specific Structures
    • Create and Edit Mappings
      • Define Package Groups
      • Create and Eidt Mappings
      • Check Customizing
    • Extend Mappings
      • Define Package Groups
      • Extend Mappings
  • UI Modeling:Define Field Properties for UI, Manage UI Configurations, Define Available UI Applications, Define Print Forms for Single Processing, Assign Print Forms for Single Processing, Define System Alias for OBN
    •  Business Add-Ins
      • BAdl:adjust user interface for single processing
      • BAdl: Change Data to be Printed
  • Data Quality and Search
    • Search and Duplicate Check
    • Validations and Enrichments
    • Data Quality Remediation
    • Business Add-Ins
  • Process Modeling: Define Governance Scope, Create Edition Type
    
    • Business Activities : Define Logical Actions, Create Business Activity, Link Log
    • Change Requests: Edit Statuses of Change Requests, Create Change Request Type, Configure Properties of Change Request Step
      • Form-based Change Requests: Define Priorities for Change Requests, Define Reasons for Change Requests, Define Rejections Reasons for Change Requests, Define Print Form for Change Requests
      • Change Request Archiving: Define Residence Times, Archive Change Requests
      • Business Add-Ins
        • BAdl: Adjustment of Fields in Creation of Change Requests
        • BAdl: Customizing User Interface for Change Requests
        • BAdl: Change Data to be Printed
        • BAdl: Access to Customer-Dependent Field Property Settings
    • Workflow : Activate Event Type Linkage, Configure Workflow Tasks, Define Change Request Actions, Define Change Request Step Types and Assign Actions.
      • Rule-Based Workflow: Define Change Request Steps for Rule-Based Workflow, Define Service Names for Rule-Based Workflow, Configure Rule-Based Workflow
        • Business Add-Ins: BAdI
      • Other MDG Workflows: Define Change Request Step Numbers, Assigne Processor to Change Request Step Number(Simple Workflow), BAdI:assign processor to change request step
    • Hierarchies : define scope for changes, create hierachy versions, BAdI:adjustment of hierarchy processing user interface
  • Data Replication: overall information
    • Define Custom Settings for Data Replication
      • Define Technical Settings : Define Replication Models, Define Business Object Settings
    • Enhance Default Settings for Outbound Implementations : Define Parameters, Define Filter Objects
      • Define Business Objects and Object Identifiers: Define Service Operations Available for Replicatoin, Define Outbound Implementations, Define Reference Data Mapping
    • Business Add-Ins(BAdIs) : BAdI(Inbound Processing of ALE Audit Messages),BAdI(Definition of language-dependent Texts),BAdI(Creation of MDG Change Pointers from ALE Change Pointers
  • Value Mapping : Overall Information, Maintain Value Mapping, Assign Code Lists to Elements and Systems, Define Technical Settings for Business Systems
  • Key Mapping : overall information, customize business objects for key mapping
    • enhance key mapping content : Define Business  Objects, Define Object Identifiers, Assign Key Structures to object identifiers, assign key structures to object identifiers
    • define a mapping context for UKMS
    • Define Technical Settings
  • Data Transfer
    • Configuration Workbench
• Central Governance for Business Partner: set up business partner
  • multiple customer vendor assignments
    • specify multiple assignment categories
    • specify multiple assignment reasons
  • configure predefined change request types
    • import predefined change request types
    • import predefined change request types for SAP FIORI
    • processor determination for other MDG workflows
  • SAP Business Parnter screening:activate BC set to reset governance scope,import predef.Fld Modif. criteria for trans BP using MDG-BP,import predef.Fld Modif. criteria for Trans BP Using MDG-S,Import Predef.Fld Modif. criteria for Trans BP using MDG-C,Import Predef Fld Modif. Criteria for Trans. BP Using relationschips,activate/deactivate business partner function modules for replcation,specify handler processed by access class
  • BAdIs for Data Replication : BAdI : Business partner replication request inbound, BAdI: Business partner replication request outbound, BAdI:business partner replication confirmation inbound, BAdI:BP Relartionships Replication Request outbound, BAdI:BP relationships Replication Confirmation inbound
• Central Governance for Supplier
  • Integration with Vendor Master in ERP:Import predefined change request types,import predefined change request types for SAP Fiori
  • ERP Vendor UI(Alternative to the supplier UI):Specify Chnage Request Types to Enable Account Group Change, Define Number Ranges for Supplier Account Groups per Target System, Define Number Ranges for Supplier Contact Persons per Target System.
  • Workflow: Assign Processor to Change Request Step Number in BRFplus for Supplier
• Central Governanace for Customer
  • Integration with Customer Master in ERP : set up integration with special consumer systems, import predefined change request types, import predefined change request types for SAP Fiori
  • ERP Customer UI (Alternative to the Customer UI) : specify change request types to enable account group change, define number ranges for customer account groups per target system, define number ranges for customer contact persons per target system, BAdI for MDG Business Partner Search Service
  • Workflow: assign processor to change request step number in BRFplus for Customer
• Central Governance for FI Contract Account : set up FI contract account, assign processor to change request step number
  • BAdIs for data replication
• Central Governance for Material : import predefined change request types, import predefined change request types for multi-record processing, import predefined change request types for SAP Fiori, import predefined change request types for lean classification, import predefined Change Request Types for SOAP product inbound, import BC set to reset governance scope, maintain fields for iDoc Key Mapping, maintain Fields for iDoc Value Mapping
  • Business Add-Ins: BAdI: Change Request Data Enrichment, BAdI: Extension of the API with customer-specific segments, BAdI: Define alternate DRF Filter Provider