SAP ECC on Oracle In Dev

SAP ECC (ERP Central Component) is an on-premises enterprise resource planning suite from SAP. The SAP ECC on Oracle connector replicates data from an SAP ECC system running on top of an Oracle database by reading Oracle redo and archive logs directly and unpacking packed SAP table formats (cluster, pool, and long text) into transparent, query-ready tables in your destination.

We connect directly to the Oracle database that backs your SAP system and sync your data from there; no SAP application server components are required.

Features

Supported deployment models

We support the SaaS and Hybrid deployment models for the connector.

SAP table type support

We support all four SAP ECC physical storage models: transparent tables, pool tables, cluster tables, and long text tables such as STXL. In the destination, we expose the corresponding virtual tables.

Setup guide

Follow our step-by-step SAP ECC on Oracle Setup Guide for specific instructions on how to set up your Oracle database and configure the connector.

Sync overview

We perform an initial sync followed by incremental updates using Oracle log-based change data capture (CDC) infrastructure.

Initial sync

During the initial sync, we execute SELECT statements directly against the SAP-managed Oracle tables.

• Transparent tables are read row-by-row from the physical table that backs the logical table.
• Pool, cluster, and long text tables are read from their physical container (for example, RFBLG for the BSEG and BSEC cluster tables), then unpacked using SAP Data Dictionary metadata before being written to the destination.

Incremental sync

After the initial sync, we switch to log-based CDC. We read Oracle redo and archived logs to capture changes on the physical SAP tables, then apply the same unpacking transformation used in the initial sync. We write changes to the destination only when a complete transaction has been captured, so the destination never contains partial or intermediate states.

Supported sync modes

The SAP ECC on Oracle connector supports the following sync modes:

• Live mode (default)
• Soft delete mode
• History mode

Cluster tables are locked to Live mode and don't support Soft delete or History mode.

Schema information

We replicate the schema you select during setup. You specify a single SAP schema (for example, SAPSR3) and a destination schema prefix. We create one destination schema for the selected SAP schema, prepended with your chosen prefix.

Fivetran-generated columns

We add the _fivetran_synced (UTC TIMESTAMP) column to every table in your destination. It indicates the time when Fivetran last successfully synced the row.

We add the following columns depending on the table's sync mode:

• In Live mode (default), we don't add any other Fivetran-generated columns. When rows are deleted in the source database, we remove them from the destination.
• In Soft delete mode, we add the _fivetran_deleted (BOOLEAN) column to mark rows that were deleted in the source database.
• In History mode, we add the _fivetran_active (BOOLEAN), _fivetran_start (TIMESTAMP), and _fivetran_end (TIMESTAMP) columns to track history.

Every SAP table has primary key columns defined in the SAP Data Dictionary, and we use those key columns as the primary key in your destination. Tables without primary key columns are not supported.

For more information about these columns, see our System Columns and Tables documentation.

Type transformations and mapping

We derive column data types from the SAP ABAP Data Dictionary rather than from Oracle system views. This ensures that columns such as DATN (timestamp), numeric character strings (NUMC), and SAP-specific decimal types (CURR, QUAN, DEC, D16D, D34D) are typed according to their ABAP semantics in your destination, not according to the Oracle physical column type.

If we don't support a certain data type, we automatically change that type to the closest supported type or, in some cases, don't load that data at all.

Long text (STXL) tables

For long text tables, we do not replicate the internal SRTF2, CLUSTR, and CLUSTD columns. Instead, we add the /FIVETRAN/STXL_TEXT (STRING) column, which contains the decoded long text assembled from the compressed source fragments.

Schema changes

We re-read the SAP Data Dictionary on every sync. When a column is added to or removed from an SAP table definition, we update the destination schema during the next sync. For a newly added column, we sync values for rows captured after the schema change. To populate that column for rows that were already in your destination, trigger a re-sync of the affected table.

Selecting data to sync

The SAP ECC on Oracle connector does not automatically include all available SAP dictionary tables in a connection. Instead, each connection syncs only the virtual SAP tables selected for that connection.

We use SAP Data Dictionary metadata in the SAP schema to build the available virtual SAP table list. This metadata lets us expose virtual SAP tables, such as BSEG, MARA, T001, and STXL, while preserving the mapping to their underlying physical storage:

For packed SAP table types, we automatically resolve the underlying physical container and handle unpacking. For example, if you select BSEG, we resolve its physical container, RFBLG. You cannot select or sync physical container tables such as RFBLG or ATAB directly — always select the virtual tables, and we read the underlying container for you.