(Glue-2308) SNP Glue™ Table Consumer

Owned by SNP
Aug 23, 2023
2 min read

SNP Glue™ Table Consumer uses the SNP Glue™ table as a target for data. 

Creation of the SNP Glue™ Table Consumer

Perform the steps outlined in How to Create a Consumer Object with the option SNP Glue™ Table Consumer selected under the Component implementation dropdown of step 4.

Activation of the SNP Glue™ Table Consumer

After creation, the object is in the saved state. For activation, all mandatory inputs need to be filled in.


  • SNP Glue™ Table
    • Name of the SNP Glue™ table as a target for data
    • Provided with F4 help
  • Enable merge
    • The flag that will enable the merge operation
    • Can also be enabled/disabled in the Extraction process selection screen
  • Keep deleted entries
    • This flag will keep deleted entries in the target table while using merge functionality.
    • Enable merge must be allowed.
    • If field GLREQUEST is present it is important that this field is not a key field.
  • Deletion flag fieldname
    • Only visible when the Enable merge checkbox is checked
    • Name of the field that flags if the record was deleted
    • Must exist in the SNP Glue™ table (can be added using the  button in the Import fields screen).

It is possible to adjust the structure of the SNP Glue™ Table consumer automatically when it is used in combination with Advanced DSO in the Extraction Process. For more information, see the chapter (Glue-2308) Automatic adjustment of Consumer structure. 

Transparent storages with secondary DB

There is no deletion flag required for transparent storages with a secondary DB connection. However, keeping deleted entries is also not supported.

Merge in secondary DB connection storage is handling simple operations (INSERT, UPDATE, DELETE) that are not advanced, for example, INSERT → UPDATE.

Connection to storage failed

When connection to storage failed and merge was enabled, there is a possibility to force delete merge metadata after deactivating a consumer.