Limitations and considerations

The following limitations apply when using SAP HANA as a source:

General limitations

• Change Processing is not supported with SAP BW tables.
• The AR_H_USER header column is not supported.
• Compatibility views are not supported and will not be available for selection.
• CA views are not supported and will not be available for selection.
• Row store data storage is not supported.
• Multitenant architecture is only supported on a single host.

• Only transparent tables (including SAP S/4HANA transparent tables) are supported.

Limitations and considerations when using the Trigger-based CDC method

• Changes to a table's Primary Key will not be replicated to the target.

• By default, the longest supported transaction length is 60 seconds. If there are transactions in your environment that exceed 60 seconds, set the Transactional consistency value in the endpoint's Advanced tab to the required value.

• For tasks configured with the Apply Changes replication option, transformation filters can only use Primary Key columns.

• Latency when applying changes - The latency shown in the User Interface is the interval between Replicate capturing a change from the source (i.e. not the source commit time), and that change existing on the target.

• DDL operations are not supported.

• Tables without a Primary Key are not supported.

Limitations and considerations when using the Log-based CDC method

• Replicate creates a hana__row_id column on the target as a Unique Index and changes the original Primary Key/Unique Index to a standard column.
• Capturing DELETE and UPDATE operations for filtered records is not supported.
• Transformations that affect multiple columns are not supported.
• When storing changes in Change Tables, only the Row_id and changed columns of the after-image will be stored. All other columns will have NULL values.
• The TRUNCATE table and PARTITION DDLs are not supported. On detecting a table with such operations, Replicate will suspend the table and require it to be reloaded.
• As the SAP HANA endpoint can be configured to connect to one instance only, in the event of failover in a HA environment, the endpoint must be manually reconfigured to point to the new instance. Then reload all associated tasks.

• The following Apply Conflicts error handling policy is not supported:

  No record found for applying an UPDATE: INSERT the missing target record

• The following Change Processing Tuning option is not supported:

  Using the Apply changes using SQL MERGE option in the Batch optimized apply mode