(Glue-2405) Trigger Delta Type

For general information about this delta type, see chapter Trigger delta.

Trigger state

On activation of the SAP Table Fetcher with the delta-type TRIGGER, the saving of newly added records is not automatically enabled.
There are two ways to do this:

  • Execute the extraction with any load type except the basic Full Load (Repair) Without Delta Update
  • Manually activate triggers through the use of the trigger management function by clicking Manage Trigger to the right of the Delta type drop-down menu.

The state of the trigger is also displayed next to Manage Trigger. There are three possible states:

  •  Active
  •  Inactive
  •  Inconsistent (this state can be repaired by reactivation the trigger in trigger management).

Trigger delta: additional settings

  • Read deleted entries (Enabled default): If selected, 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. This setting is not supported for cluster tables.

Trigger delta for database views

SAP Table Fetchers also support trigger deltas for database views. For this scenario to work, you must specify the trigger table name in the Trigger table name field.

The trigger table 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, this might lead to a situation, where an excessive amount of data is replicated on the target storage. This is because 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, that uses a compatibility view, a pop-up is shown. The pop-up provides the option, to decide whether to use the compatibility view instead of the original table. If you want to use the compatibility view, you must 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.


Archiving using Trigger delta

There is a possibility to use trigger delta for archiving. 

Using this functionality, deleted records captured by a trigger are marked as archive instead of delete. When a record is archived, the deletion flag (by default GLDELFLAG field) contains the 'A' character.

If you want to use the archiving functionality, you must execute the extraction in the trigger delta mode with a specific user. The archiving users must be specified in the transaction /DVD/GL_SETT in the setting 'EXT2_ARCHIVING_USERS'  separated by ',' delimiter.

If a trigger delta is already initiated, changing this setting will not take effect. To do so, you must reactivate the deletion trigger. 

NOTE

This feature is now only available for the HANA database.