Grouping/Filters

Allows setting up plant and distribution chain (DChain) groups and allows defining filters.

Plant groups / DChain-groups

Certain settings can be limited to certain plants resp. to certain distribution chains.

In this setting the wild chard character * can always be used. But sometimes the usage of * is not possible and the settings must be replicated for each organizational unit.

Example:

Plant 1000, 1150, 2000 and 2150 exist. A setting shall be valid for plant 1000 and 2150 only. However it is not possible to define a *-mask, which will exactly define these two plants.

In order to avoid this problem, groups of organizational units, which shall be treated equally, can be defined by setting up plant or distribution chain groups. The group key contains of a three digit code and to these groups will then be assigned the organizational units.

The groups can then be used in the relevant settings, starting with a „&" before the group code. The groups can be used in the following settings:

Data packages
Activation of processing scenarios by plant and distribution change status.
All relevant object dependencies
Assignment Org./status net for configuration types.

The relevant search help functions will list all possible groups and all defined organizational units.

In the groups themselves, the masking character * can also be used again for the keys of the organizational unit (plant, sales organization and sales view).

For example, a plant group ALL (&ALL in the usage) can be created and only one record with plant = * can be inserted as the plant assignment. This group then always applies to all plants in the system.

Filters

Filters are being used for processing scenarios and for display filters, which will limit the display and selection of ProConfiguration objects. These filters can be defined in the following settings.

Filter definition

Definition of filter identification and description of filter.

Selection conditions

Defines the selection conditions of the filter, e.g. which data will activate the filters (for a display filter this may result in exclusion).

Rules:

Fields in the selection conditions will be linked AND. If one value is not valid, the conditions will not be fulfilled.
Several filter conditions will be linked OR, e.g. if one selection condition is valid, the filter will become active.
Empty fields will be interpreted as empty, therefore mask sign" "* must be used. Example: Empty for field „org.unit" means the filter will only become active for data packages NOT assigned to a organizational unit.