(Glue-2305) Trigger delta type

Owned by SNP
May 16, 2023
2 min read

For general information about this delta type, see (Glue-2305) Delta Mechanisms.

Trigger state

On activation of the SAP Table Fetcher with delta type TRIGGER, the saving of newly added records is not automatically turned on (mentioned in the link above).
There are two ways to do this:

  • Execute extraction with any (Glue-2305) Fetcher except the basic Full Load (Repair) Without Delta Update
  • Manually activate triggers through the use of the (Glue-2305) Trigger Management functionality accessible via the Manage Trigger button

The state of the trigger is also displayed next to Manage Trigger button. There are three different states in which the trigger can be: Active, Inactive, Inconsistent (can be repaired by reactivation the trigger in Trigger Management).

Trigger delta additional settings

  • Read deleted entries: When this is checked, also the keys of entries that were deleted since the last extraction will be read after entries that were inserted or updated. With this setting, only the key fields can be marked for the Selection.
  • Deduplicate deleted entries: Deleted entries, for which there were any inserts after the deletion, will not be transferred (not supported for cluster tables).

Trigger delta for Database Views

SAP Table Fetcher also supports trigger delta for Database Views. For this scenario to work, it is required to specify the trigger table name.

It must be one of the tables that is part of the Database View. It is strongly advised to have all key fields of the trigger table name in the output of the Database View. Otherwise, it might lead to a situation, where an excessive amount of data is replicated in the target storage. This is due to the fact that one entry in the shadow table might be translated into multiple entries from the Database View due to missing key fields in the output of the Database View.

Trigger delta for tables with compatibility view in place

If the trigger table name is filled with the name of a table, which uses a compatibility view, a pop-up will be shown. The pop-up window provides an option for the user, whether the compatibility view should be used instead of the original table. In case the user wants to use the compatibility view, it is required to specify the trigger table name. Otherwise, the original table will be used as the trigger table name and this table will not be considered a view.