Delete-Capture Triggers Cause System-Wide Locking in SAP BW/4HANA

Issue

Fivetran delete-capture triggers cause locking that affects multiple SAP BW/4HANA processes instead of remaining isolated to a specific table or connection.

Environment

• Connector: SAP ERP on HANA
• Source system: SAP BW/4HANA

Resolution

To resolve this issue, choose one of the following options:

• Limit delete-capture triggers to selected tables:

  1. In your SAP system, run the /N/FIVETRAN/CONFIG transaction.
  2. Set Deletes detection using triggers to Use only for selected tables.
  3. Specify only the tables for which you need to capture deletes.

  For more information, see Disable delete triggers for specific tables.

• To avoid delete-capture triggers entirely, create a new SAP ERP on HANA connection that uses the No-trigger sync mechanism. This mechanism detects deletes using queries instead of triggers and shadow tables.

Cause

This issue occurs because Fivetran delete-capture triggers and their associated shadow tables are created on shared SAP source tables and aren't isolated to an individual Fivetran connection. When these triggers handle a high volume of operations, the resulting locks can affect other SAP BW/4HANA processes and overall system performance.