Hero Backgroud Elements 2
Reading Time: 10 Min

Capabilities of the ABAP-Adapter Connection – Fast Track

Learning Article
  • SAP Data Warehouse Cloud is supporting the ABAP-Adapter to connect, access and replicate data from ABAP managed on-premises Systems.

    In this Blog I’m focusing on the capabilities of the ABAP-Adapter in the context of a SAP BW/4HANA & SAP S/4HANA on-premises system – fast Track mode.

    The ABAP-Adapter is capable to connect to the BW/4HANA & S/4HANA Data Dictionary and according objects and artifacts, like:

    • ABAP Tables
    • Extractors
      • ABAP_CDS
      • BW
      • SAPI (Service API)

    The folder “ABAP Tables” provides the access to the tables available within the SAP Data Dictionary, where you find all the technical tables you might be aware working on the SE11/SE16 Transaction from a ABAP perspective.

    The sub-folders within the Extractor folder provides access to the ABAP_CDS View (here: BW/4HANA & S/4HANA), the BW objects and the SAPI folder contains the Service API’s structures.

    It’s important to mention that the integration to the BW/4HANA & S/4HANA ABAP Dictionary objects & structures from a SAP Data Warehouse Cloud perspective can be separated into

    • federate access (remote): simply connect to the BW/4HANA & S/4HANA objects and trigger SAP Data Warehouse Cloud to create a remote table, integrate the remote table structure into a SAP Data Warehouse Cloud Model. No data management (extract & persist the data) is required on the SAP Data Warehouse Cloud side of the house. The Data Modeler / LOB User can focus on building data models to get their business problem solved. (CONNECT and not COLLECT)
    • replicated (Refresh Frequency: none -> Snapshot): transition data access from federated access (remote) into SAP Data Warehouse Cloud local data persistence/table, by executing a data load job to insert the data set from the remote object into the SAP Data Warehouse Cloud local data persistence/table. It’s important to mention that the previously created models and stories in SAP Data Warehouse Cloud remain consistent / untouched, as we’re only working on the data access layer of the previously created remote tables (transition the remote table access into a local table access). It’s always possible to revert back to federate access (remote) without impacting the created models and stories in SAP Data Warehouse Cloud. (COLLECT and not CONNECT)
    • replicated (Refresh Frequency: Real-time): in addition to the (Refresh Frequency: none), SAP Data Warehouse Cloud is also leveraging the technical services for some of the deployed BW/4HANA ABAP Dictionary objects to enable Real-time data replication to SAP Data Warehouse Cloud local persistence/table. Real-time replication is enabled to support BW/4HANA DSO Objects, tables hosting a Primary Key and SAPI’s hosting a Primary Key and S/4HANA ABAP CDS-Views, SAPI’s hosting a Primary Key. It’s important to mention that the previously created models and stories in SAP Data Warehouse Cloud remain consistent / untouched, as we’re only working on the data access layer by transition from the remote table & Snapshot table to Real-time data replication. It’s always possible to revert back to federate access (remote) or Snapshot without impacting the created models and stories in SAP Data Warehouse Cloud. (COLLECT and not CONNECT)

    Author: Axel Meier, Solution Management SAP Data Warehousing