SAP MDG · UTILITIES

How do I create HANA-based analytics for SAP Data Replication in SAP MDG?

Use SAP HANA-based Analytics to build two calculation views and one XSOData service for MDG data replication monitoring. The guide applies to MDG 7.0 SP02 and higher and uses Change Request data plus replication-status information to evaluate agreed KPIs.

Use SAP HANA-based Analytics to build two calculation views and one XSOData service for MDG data replication monitoring. The guide applies to MDG 7.0 SP02 and higher and uses Change Request data plus replication-status information to evaluate agreed KPIs.

This guide shows how to build SAP HANA-based analytics for SAP MDG data replication. It uses Change Request information together with replication-status data to monitor whether replication happens according to agreed KPIs, then publishes the analytical query through an XSOData service.

Process flow

  1. Enable HANA-based analytics for SAP Master Data Governance.
  2. Configure the deployment scenario as Replication Scenario or Integrated Scenario.
  3. Create a HANA Studio project in the HANA Development Perspective.
  4. Create the `DataReplication` folder structure and an `odata` subfolder.
  5. Select `Cross Client` and the default schema.
  6. Create `DataReplication`.
  7. Join `DRFD_OBJ_REP_STA` with `MDG_BUS_SYS_TECH`.
  8. Create `Projection_Status_Text` on `D07T` with `DOMANE = 'DRF_REPSTAT'`. Create `Join_RplctnStatus_to_Text` as a text join. Create `ProjRplcntStatusWithBusSyst`. Create `Projection_OTC_Text` on `MDGI_OTC_T_BS`. Create `Join_RplctnStatus_to_
DRFOUT

Trigger data replication; it calls the outbound implementation configured in Customizing and can run as initialization or for collected change pointers.

Referenced tables

ObjectPurpose
DRFD_OBJ_REP_STASource table for replication-status information.
MDG_BUS_SYS_TECHSource table for technical business-system information.
MDGI_OTC_BSSource table for Business Object Type information.
MDG_BUS_SCYS_ATTRSource table for business-system/object replication attributes.
D07TSource table used for replication-status text in `Projection_Status_Text` with the filter `DOMANE = 'DRF_REPSTAT'`.

ILLUSTRATIVE ABAP SAMPLE

XSOData service example from the guide

This is the source-supported XSOData definition pattern for exposing `DataReplicationQuery` as an analytical service.

1service {"tmp.ORTHG.DataReplication::DataReplicationQuery" as 2"DataReplicationQuery" 3 keys generate local "GenID" 4 aggregates always; 5} 6 7annotations 8{ 9 enable OData4SAP; 10}

The remaining configuration, implementation details, and testing guidance continue from this answer more…

Related questions and keywords

Alternative questions

  • What is this guide about?
  • How do I create HANA-based analytics for SAP Data Replication?
  • Which releases are applicable?

Possible questions

  • What information is used for MDG replication KPIs?
  • Why create replication analytics?
  • What must be configured before creating the views?
  • Does MDG HANA analytics need to be enabled first?
  • How can data replication be triggered?
  • What is DRFOUT used for?
  • What is the Membership API used for?
  • When does MDG call the Membership API?
  • Which table stores replication status information?

Keywords

SAP MDGHANA-based AnalyticsData ReplicationMDG 7.0 SP02KPIChange Requestreplication informationprocess monitoringtechnical prerequisiteReplication ScenarioIntegrated ScenarioHANA analyticsDRFOUToutbound implementationCustomizinginitializationchange pointersMembership APIBusiness PartnerCustomerDRFD_OBJ_REP_STAMDG_BUS_SYS_TECHMDGI_OTC_BSMDG_BUS_SCYS_ATTRDataReplicationDataReplicationQueryXSOData