Skip to Content
Technical Articles

Replicating House Bank Data from Dev systems to integrated business systems in S4HANA landscape

Introduction

The way house bank FI data was sent to QA and PRD systems in ECC landscape, is now changed in S4 world. This FI data was traditionally written in a transport and moved to higher systems. In S4HANA systems, this data is replicated to other integrated business systems using IDOCs with the help of standard data replication program (Transaction – DRFOUT ). This way, you ensure that the master data is identical and in sync across all the systems in the landscape. The following features are supported –

  • Replicate existing house banks, house bank accounts, and bank accounts to receiver systems in mass
  • Replicate changes that occurred in the sender system during a specified time interval to receiver systems
  • Manually select and transfer data to receiver systems

There are many integration scenarios, since I worked on below scenario. Throughout this blog all the settings mentioned may not work for other scenarios, so you need to verify that once.

SAP has provided the following message types for using the replication program to replicate house banks, house bank accounts and bank accounts.

The use of the message types depends on whether the receiver system is an SAP S/4HANA system. The table below explains the use of the message types in different scenarios.

 

Getting Started (Configuration)

 

The configuration is divided into three sections below.  Kindly refer the sections below make sure that you have made the following settings before using this program to replicate house banks, house bank accounts, and bank accounts

  • Generic Settings
  • Configuration for Sender Systems
  • Configuration for Receiver Systems

 

Generic Settings

  • In transaction SU01, create users for ALE transfers.

  • Create logical systems in Customizing activity De􀁆ne Logical Systems and then assign clients to logical systems in Customizing activity Assign Logical System to Client. You can find these Customizing activities in Customizing under SAP NetWeaver Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems.

 

 

  • In transaction SM59, create RFC connections for the integrated systems.

 

 

  • In transaction WE21, create port for IDOC processing.

 

 

Configuration in the Sender System

 

a) Maintain Partner Profile (transaction WE20)

 

 

BAMMAST –

 

HBHBAMAST –

 

 

b) Object with Change Document: Set Up Change Indicators for Table Fields

 

IN BD52 TCODE for message type BAMMAST, please make sure all relevant fields from below object and table combinations are added . sample screenshot is also added below following table.

 

 

 

IN BD52 TCODE for message type HBHBAMAST, please make sure all relevant fields from below object and table combinations are added . sample screenshot is also added below following table.

 

 

c) Object with Change Document: Activate Change Indicators for Message Type

 

    • Add message types BAMMAST and HBHBAMAST.
    • Select the active checkbox for both entries.

In TCODE – BD50  activate change pointers for both of these message types.

 

d) Maintain Additional Data for Message Type –

In TCODE – BD60, maintain settings like below for these two message types

 

 

 

e) Configuration for Transaction DRFIMG

In the sender system, make the following settings using transaction DRFIMG.

  • Define business systems for receiver systems.

 

 

f) Define replication models

 

 

 

g) Create a new replication model for message type HBHBAMAST and then do the following:

 

  • Select the entry created and then double-click Assign Outbound Implementation.

 

  • Enter the outbound implementation HBANK_IMP and select Replication via I Doc for the Communication Channel Field

 

  • Select the implementation created and double-click Assign Target Systems for Repl. Model/Outb.Impl

 

  • Choose New Entries. Enter the business systems and save.
  • Go back to the Define Replication Model view and choose Activate to activate your settings.

 

 

  • Create another replication model for message type BAMMAST.
  • Select the entry created and then double-click Assign Outbound Implementation.

 

  • Enter the outbound implementation BAMMAST and select Replication via I Doc for the Communication Channel Field.

  • Select the implementation created and double-click Assign Target Systems for Repl. Model/Outb.Impl.

  • Choose New Entries. Enter the business systems and save
  • Go back to the Define Replication Model view and choose Activate to activate your settings.

 

  • Enable the replication mode in transaction DRFOUT.
  • Go to below path

 

  • Create the following entries

 

  • Check settings for the replication mode

Go to below BADI-

 

 

h) Make sure that the implementation DRF_CP_PROCESSING is active.

 

 

Configuration in Receiver Systems

a) Create a logical system in Dev and move it to receiver system

 

 

b) Create an inbound partner profile in WE20

 

 

 

IDoc Generation (DRFOUT)

Once the configuration has been completed, transaction DRFOUT shall be executed to trigger the IDocs from sender system and receive the IDoc in the receiver system.

 

 

Outbound IDOC Created (Sender System)

 

Inbound IDOC received (Receiver System)

 

Conclusion

The above completes the process of replicating the House Bank/Account ID data into the remote systems and also keeps the data in sync across the SAP landscape

Further Reading

Following are some of the resources one can use for further reading on this topic

2305593 – Replication of Bank Accounts, House Banks and House Bank Accounts to Remote Systems

https://help.sap.com/viewer/ac319d8fa4ea4624b40a58d23e3c4627/1809.002/en-US/a4eb9b521e4b4568a7fa924709384536.html

 

Technical Consultant

Sujay Nantekar

Be the first to leave a comment
You must be Logged on to comment or reply to a post.