Groups, Subgroups, and *ALL

The Expert Configurator is designed to allow many parts to share similar processing without duplicating the rules that define the processing.  This is done through groups, subgroups, and *ALL.

A rule can be defined for a group instead of a part by entering the group name preceded by an asterisk (*) in the part number field of the rule header screen.  These group rules will then be processed whenever that group is assigned to a configured part being processed, assuming the rules are released and the version numbers are correct.  This avoids duplicating the exact same set of rules for various parts.

*ALL is the most general substitute for a part number.  It applies to all parts, and *ALL rules will be processed for any configured part if the rule is released and the version numbers are correct.  Group rules will be processed only for parts that are in the group.  Subgroups are further divisions of groups.  A part in a subgroup is also a member of the parent group, and will use both the group and subgroup rules.  Groups, subgroups, and *ALL are defined for a specific plant.

Groups, subgroups, and *ALL are defined and maintained in the Reference File, categories Y21, Y22, Y23, Y24, Y25, and Y26.  Groups are two characters long.  Subgroups are four characters long, the first two being a defined group, and the last two being the subgroup name.  *All is maintained as the subgroup 'ALL'.  The group 'AL' is not allowed as a group so it will not interfere with the *ALL processing.

Parts can be included in groups and subgroups in Part Master Maintenance.  A group part must be a member of a group before it can be a member of a subgroup.  All parts are automatically a member of *ALL subgroup.

Groups, subgroups, and *ALL have version numbers.  The version number determines which version of the group, subgroup, or *ALL rules to process.  For example, if group BB is set at version 99, only the BB group rules with a version of 99 will be processed.  Version numbers are maintained in Reference File maintenance.

When creating a bill of rules consisting of rules defined for groups, subgroups, or all parts, the release of rules must be from general to specific.  Rules are only processed if they are released.  For example, if a rule defined for specific part A releases a rule defined for group BB, the group BB rule will only be released when part A is ordered.

Matrices can also be defined for a group, subgroup, or *ALL.  This allows for a common matrix to be shared by many parts.  This avoids duplicating the exact same matrix for each part, group, or subgroup.

Matrices are defined uniquely by the matrix name, part number, and database type (sales order entry, pricing, and manufacturing), but are referred to by only the name.  This means that there can be more than one matrix with the same name and same database type, but different part numbers.  For example, if there are two matrices with the name M1, with one defined for part A and the other defined for group BB, and if part A, which is a member of group BB, uses matrix M1, which one is used?  The Expert Configurator has a hierarchy for matrices to handle these cases.  If a part specific matrix exists, it will be used.  Subgroup matrices will be used second, group matrices will be used third, and *ALL will be used last.