SAP MDG: Step-by-Step Guide to FI Object Replication with DRF

SAP MDG: Step-by-Step Guide to FI Object Replication with DRF

Step-by-Step Explanation of SAP MDG DRF for FI Objects

The diagram describes the SAP MDG (Master Data Governance) DRF (Data Replication Framework) setup process for replicating FI objects like GL accounts, profit centers, and cost centers.

1. ALE Configurations – Data Provider (HE4CLNT400 Sender)

  1. Create RFC Destination: Establish a connection from the sender system (HE4CLNT400) to the receiver system (T41CLNT401) by creating an RFC destination. This is the foundation of communication between the two systems.
  2. Create Port: Define a port that will be used to transfer IDOCs (Intermediate Documents) between the sender and receiver systems. This port serves as a technical representation of the communication link.
  3. Define Logical System: Configure the sender system and receiver system as logical systems. Assign a logical system name to the sender and receiver systems for identification.
  4. Create Partner Profile for Receiver: Define the partner profile for the receiver system to handle inbound messages. Configure inbound message types and assign processing functions for the receiver system.
  5. Create Cross-System Company Code (Optional): Assign the company code from the sender to the global company code in the receiver system, if required.
  6. Create Distribution Model: Create and assign outbound message types to the defined logical systems. Ensure that the message types for GL account, profit center, and cost center are included.
  7. Activate Change Pointers: Enable change pointers for the specified message types to track changes in the master data. Change pointers ensure that only modified data is sent to the receiver system.

2. ALE Configurations – Data Consumer (T41CLNT401 Receiver)

  1. Create RFC Destination: Establish a connection from the receiver system (T41CLNT401) to the sender system (HE4CLNT400) by creating an RFC destination.
  2. Create Port: Define the port for the receiver system, mirroring the setup for the sender system.
  3. Define Logical System: Configure the receiver system with its logical system name.
  4. Create Partner Profile for Receiver: Define the partner profile for the receiver system to handle inbound IDOCs. Configure message types for the replication process.
  5. Assign Cross-System Company Code (Optional): Assign the company code in the receiver system to align with the sender system's configuration.

3. DRF Configurations (HE4CLNT400 Sender)

  1. Define Business Systems: Add the business systems (e.g., Consmr SLD) in the DRF configuration for the sender system. Ensure that the business systems are correctly assigned to the DRF.
  2. Define BOs (Business Objects) for Business System: Assign relevant business objects to the business system: 892 for GL accounts 229 for profit centers 158 for cost centers
  3. Define Communication Channels: Configure the communication channels for each business object to enable data replication using IDOCs.
  4. Define Replication Model: Create replication models for each FI object: GL Account Master Profit Center Cost Center
  5. Assign Outbound Implementation to Replication Model: Assign the appropriate outbound implementation to each replication model: 1012 for GL Master IDOC 1120 for Profit Center IDOC 1100 for Cost Center IDOC
  6. Assign Target System to Replication Model: Add the receiver business system (Consumer) to the replication model for each object.
  7. Replicate Data: Execute transaction DRFOUT to replicate data from the sender system to the receiver system.

Key Points to Check

  1. SMT (Service Mapping Tool) Configuration: If you are using reuse active area, ensure that the mappings in the SMT are updated for the new fields or attributes in the FI objects.
  2. Change Request Management: Before replication, ensure that all change requests linked to the data model are adjusted and processed using program USMD_ADJUST_STAGING.
  3. IDOC Monitoring: Use transaction WE02 or WE05 to monitor the IDOCs and troubleshoot any issues during replication.
  4. Post-Replication Validation: Verify the replicated FI objects in the receiver system to ensure successful replication and data integrity.

#GLAccountReplication #ProfitCenterReplication #CostCenterReplication #SAPFIMDG #SAPDRFOUT #FIObjectReplication #FinancialMasterData

要查看或添加评论,请登录

Vinoth Kannan的更多文章

社区洞察

其他会员也浏览了