Object Relation Rules

Within one relation, the values will be related AND, e.g. all conditions must be fulfilled, before the check or action will be performed.

For checks (e.g. status checks), more lines will be linked OR, e.g. if one condition is fulfilled, the check is OK.

• Exception:
  Checks on the entrance screen concerning BOMs and routings. Eventually only one set will be used, when a definite relation to the data package is required. Data will be read so that the set best matching set will be used.

For actions, multiple lines are possible and all matching records will be executed. Using the priority order, a document or material can directly run through several statuses.

• Exception:
  Actions on BOMs and routings. Eventually only one set will be used, when a definite relation to the data package is required. Data will be read so that the set best matching set will be used.

In case a status action cannot be performed (status change) and another action with identical priority order on the same objects is possible, or the status is already set, no error message will be indicated. This supports parallel status sequences.
Example:

• IA > PP > FP or IA > PS > FS are possible status sequences.

• One action could set status FP and one could set status FS.

• If one of the actions is possible (previous status PP or PS) the other one will be ignored.

The status sequence is also relevant for relation types. This may be important for example if an action on a material, which triggers other checks, must be performed before an action on the document. Else it may occur, the document status will be set, but the material status won't be set, because of an error during the check.

Generally empty fields are regarded as "*". This is not valid for status fields, which must always have an entry. Predecessor status / „status from" will be interpreted as defined in the basic setting "Interpret. St. From = empty in object relation".

Another exception are plant fields in a BOM: empty = no plant = x-plant BOM. Therefore it may be required to enter *. The variable * will select all plants and also x-plant data (empty).

The document selection can be via object type and/or object relevance. For example object „Drawing" or a relevance „primary document".

Object relations between material status types must be direct, intermediate steps, e.g. a document action, are not allowed.

• Example – not allowed:

  • Plant dependent material status > sets document > sets x-plant material status.

  • This way, the x-plant material status cannot be set, because the material will be blocked.

• Correct solution:

  • Plant dependent material status > sets document

  • Plant dependent material status > sets x-plant material status

Document relations to a plant dependent or distribution chain specific material status, will be effective only for documents of the specific organizational unit.

If the product ProMaterialData is used together ProConfiguration, the relations (actions) between the different material status types will be performed after the MMS actions. In general only product should handle the specific material status.