Conigma CCM

TMS Object Filters

Functional scope

A TMS object filter is a set of rules for checking objects and table keys. A rule set contains a list of rules which are scanned from top to bottom for each object and trigger different behavior (see rule types). Each rule set has a unique Internal ID, which is referenced at the check points in the customizing. The check points can be freely customized in Conigma (e.g. object action, whitelist check at status transition, filtering at DevSync, etc.).

Creating and changing rule sets 

By default, rule sets can be created or modified by administrators in the Configuration/Software factory management/TMS object filter: Rule sets folder. 

Attributes of rules

Type

  • Inactive: this rule is ignored during the check. 

  • Allow: Objects that match this rule are allowed. 

  • Deny: Objects that fulfill this rule are forbidden. 

  • Information: an ABAP message of type "I" is sent for these objects. 

  • Warning: an ABAP message of type "W" is sent for these objects. 

Filter

With the filter you can define how you assign objects or table keys to the behavior type. 

  • All objects: The behavior selected for the type applies to all objects.

  • BAdI Implementation: The filter is defined in a customer-specific implementation of the BAdI /GAL/SH_TMS_OBJECT_FILTER. It is called with BAdI filter. 

  • Object ID (wildcard): Here you can enter a transport request number (with wildcard if necessary). 

  • Object directory (wildcard): Filter definition with object directory entry. 

  • Object list (wildcard): Filter definition with TMS object list. 

  • Table key (RegEx): Restriction of table keys with ABAP Regular Expression. 

  • Table key (wildcard): Restriction of table keys with wildcards. 

Parameters

Here you must store the value corresponding to the selected filter. 

Description

Short description of the rule

Last change user

The user who made the last change

Last change time

Date and time of the last change