Definition of ProConfiguration configuration types, the assignment of objects to them and relations between configuration types.
...
Settings are only required, if objects of organizational unit shall be handled and displayed. See also chapter about organizational units in ProConfiguration document „Tips and Tricks".
Assignment Processing Scenario
...
Assignment of a data package to a configuration type.
Relations between Configurations
n case a material master record is created with a template or if a material master record changes its configuration type, it is possible to influence the behavior of ProConfiguration with a definition of a relation between configuration types.
Relation between Object Types
Defines the relation of objects when changing the configuration type. This is necessary, when document properties and eventually the original must be copied to a destination document with different object types.
Classes / Characteristic Values to Copy
MM standard will assign no classes nor copy characteristic values if the classification screen is not processed when creating a new material with a template (MM01).
This setting defines which class assignments and characteristic values will always be copied, even if the user is not processing the classification screen.
| Info |
|---|
This setting will only be used of relations, which will create a new material master record. |
| Info |
|---|
If one of the defined classes has already been assigned, because the user has processed the classification screen, no further actions for this class will be performed. |
| Info |
|---|
To restrict class type, class and characteristic value, the mask character * can be used. |
Additional Parameter
Definition of additional relation parameter. Currently supported parameters and functions:
Parameter | Value / Function |
|---|---|
BSZID[Suffix] | Allows filtering relation sets for configuration changes according to triggering processing scenarios. Multiple parameter settings are possible, by using any suffix to the key value. Additionally several processing scenarios can be registered using symbol ";". Example: Parameter BSZID → KW-1 Parameter BSZID_2 → KW-2;KW-3 These two parameter settings will only allow the usage of the application when the triggering processing scenario is KW-1, KW-2 or KW-3.| |