You can use trigger management to manage triggers created as a part of the SNP Glue Extractor with the delta-type TRIGGER. This function can be accessed from the menu in the Tools tab in the SNP Glue Cockpit screen or by using transaction /DVD/GL_DBT.

Main screen (list overview)

After you access the trigger management function, a screen with a list of all triggers is displayed.

The list of triggers is composed of the following columns:

Status: Icon showing the current status of the trigger.
- Active (green square): The trigger is active and is collecting data.
- Inactive (red stop sign): The trigger has been dropped.
- Disabled (yellow triangle): The trigger has been created but is not collecting data.
- Inconsistent (yellow diamond with exclamation mark): The trigger is in an inconsistent state and needs to be checked.
Table Name: Name of the table on which the trigger is created.
Trigger: Name of the database trigger.
Description: Description of the table.
Object Name: Name of the Extractor or Fetcher object that has a trigger delta.
Shadow table count: The number of entries in the shadow table. To update this column, select triggers in ALV and then press the button Count rows in the ALV toolbar.
Created on: Date of creation.
Created by: Name of a user who created the trigger.
Changed on: Date of the last change.
Changed by: The name of a user who last changed the trigger.

Several actions can be performed from the list overview screen:

Activate: activate selected trigger(s)

Note

If the structure of the source table is changed, you must reactivate the trigger.
If the key fields of the source table were changed, both the fetcher and the trigger must be reactivated.

Deactivate: deactivate selected trigger(s)

Note

After the trigger deactivation, the shadow table will still contain the data that was collected before the deactivation

Check: Check the consistency of selected trigger(s)
Show object: Display the parent object (column Object name) of the selected trigger
Advanced settings: Possibility to alter the settings
Repair Trigger: If there are any inconsistencies with the DB trigger, shadow table, or sequence, this function will resolve them automatically. Note that in case of inconsistencies, it may discard and recreate the object so that you may lose content.
Cleanup Trigger: This function deletes all objects related to the trigger (DB trigger, shadow table, sequence) if they exist and deletes the related metadata.

Detail View

You can double-click any trigger to display a screen with a detailed view of the trigger.

For active/disabled/inconsistent triggers the button Deactivate is provided and the button Count Rows is enabled which after use shows the number of entries in a shadow table. Triggers with inactive status have been provided with Activate button and the button Count Rows is disabled. Next to the Shadow table field is a button redirecting you to the Data Browser (SE16).

Editable parameters Cache size and Number of partitions are available only for HANA triggers and can be set only for triggers with saved status.

The Cache size specifies which range of sequence numbers will be cached in a node. By default Cache size is not set which means that sequence numbers will not be cached in a node.

The Number of partitions specifies the number of partitions created of the column TIMESTAMP in the shadow table. By specifying the number of partitions and activating the trigger shadow table will be partitioned by hash function. By specifying the number of partitions to 0 merges of existing partitions will be performed. Operations table partition and merge of table partitions may take a long time depending on the size of the table, available system resources, and so on.

If partitioning operation will be performed, and a warning popup will be displayed before the activation of triggers. By confirming this popup, the activation of the trigger will continue. Option No will cancel the activation.

If merge of existing partitions will be performed, and a warning popup will be displayed before activation of triggers. By confirming this popup, the activation of the trigger will continue. Option No will cancel the activation.

On the bottom of the screen, specific Database triggers are shown for each DML operation (INSERT, DELETE, UPDATE), with its current status.

In the case of failed deactivation, a confirmation popup will be displayed. After clicking on Yes, trigger's metadata will be changed and logs from failed deactivation with information about changed metadata will be displayed. When option No is chosen, only logs from failed deactivation are displayed.

Advanced settings

Here you have access to change:

Global sequence settings: (with an option to mass alter sequence)

Sequence cache: Number of values allocated in memory. Default value: 15.
Sequence max value: Largest value in sequence numbers. Default value: 999999999.

Other settings:

Create triggers retry: Number of retries when creating triggers. Default value: 0.
Create triggers lock timeout: Number of seconds to wait before timeout error occurs. Default value: 0.
Trigger name pattern: For more information see the section Trigger name pattern

Trigger name pattern

In the advanced settings for triggers, we can find the trigger name pattern setting. This setting is used to change the names of Glue triggers. Possible patterns are:

<DEFAULT>: The trigger names will be in the format ZDVD*************
<INTEGER>: The name will start with 8 digits.

The setting is applied when we activate the SAP table Fetcher. To change the names of triggers on existing active fetchers, we need to deactivate them and activate them again. In this case, mass activation/deactivation of Glue objects can be used.

Trigger Mass Deactivation > Reactivation

There is a possibility to mass deactivate and reactivate triggers via trigger reactivation report. This is accessible from the SNP Glue cockpit.

Using this functionality it is possible to mass deactivate and then reactivate triggers.

Deactivation: Deactivate triggers using the select option. If the select option is empty all active triggers are deactivated.

Reactivation: Reactivate triggers that were deactivated using this functionality if the select option is empty all triggers that were deactivated are reactivated.

Clear buffer table: A clear buffer table (allowed only for deactivation) is useful to get rid of any leftovers or inconsistent triggers in the buffer table.

SAP Tables: Select the option for source tables for triggers.

Note

Only triggers deactivated using this functionality can be reactivated by this functionality.

Browser not supported