Informatica Intelligent Data Management Cloud & BTP-IS Integration

[Nihal_Nath_Tiwary1]

Intelligent Data Management Cloud (IDMC) provides a robust cloud data integration architecture designed for scalability and flexibility. At its core is the Informatica Cloud Platform, featuring a user-friendly interface and a drag-and-drop Cloud Designer for creating integration mappings.

1. MDM Inbound Integration to CPI

The main inbound flow into Informatica IDMC is called reconciliation. Scope of MDM Inbound integration is to extract or receive data from source system and load it into MDM. This will be either by batch or near real time. CDI mapping should be established for batch integration. CAI process combined with OOTB MDM API to be used for near real time integration.

2. MDM Outbound Integration to CPI

The main outbound flow from IDMC is called Distribution, Once the master record is established for a
given entity, IDMC then distribute the mater record data to other applications or databases.

Scope of outbound integration is to make the master data available to downstream systems.

MDM will publish outbound payloads to an Azure Service Bus queue from where SAP BTP will consume the payload and act as a middleware to distribute master data to downstream systems. Master data along with the “distribution logic” will get pushed from MDM outbound layer to Azure Service Bus, so it can be distributed by BTP to downstream application

Purpose of each component and intermediate jobs are described in below diagram-

Distribution Approaches Considered:

A. Distribution Approach in BTP_IS

B. S/4 Data Replication Framework (DRF)

C. Distribution of MDM data in MDMHUB

Comparison of Approaches

Exception Handling in CPI & MDM HUB

The middleware layer (BTP_IS) plays a critical role in delivering master data to the target systems. During this process, exceptions can occur primarily due to:
    • Mapping or data validation failures within the middleware
    • Communication issues while connecting to the destination system

In the event of such failures, BTP_IS prepares a detailed error feedback, including the complete payload, the target system that failed, and specific exception information. To manage these failures effectively, a dedicated exception queue is maintained at MDM, which is responsible for collecting and tracking all failed messages.
The reprocessing of failed records from this queue is governed by the MDM team, ensuring that error handling aligns with data governance policies.

Additionally, for failures that occur within SAP S/4HANA, a separate interface sends acknowledgment
notifications back to MDM via the ALEAUD IDoc.

#IDMC #MDMHUB #CPI #MasterData #Integration#Middleware #BTP #IntegrationSuit