null
Skip to end of banner
Go to start of banner

Object Relations

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

In register Object relations Configtypes / Documents and Object relations BOM / routing the objects dependencies are defined, which are handled by ProConfiguration.
This may be an object status control in relation to a status change of another object. Or if an object status change triggers a status change of another object.

  • See Configuration Types / Relations for the assignment of the object relations to the configuration types.
  • Configuration types of the same family can also have relations, depending on their status definitions. See also Status Network.
  • Using the information icon in the list of object dependencies, you can call a dialog box in which the types of object dependencies used, the records entered in them, and the individual field values are displayed.


Possible object relations
Below an overview over the possible object relations. For derails see online documentation in customizing.
Object relations Configtypes / Documents

  • Cross plant <-> Document
    • Defines relations between cross plant material status and document info records.
  • Document <-> Document
    • Defines relations between different document types.
    • Checks and actions between documents of different organizational units are not possible. But it is possible to create a relation between two documents, if one is linked to another organization unit and the other one not (x-plant).
  • X-Plant <-> Plant Specific Material Status
    • Defines relations between x-plant and plant specific material status.
  • X-Plant <-> DChain Specific Material Status
    • Definition of relations between x-plant and distribution chain specific material status.
  • X-Plant -> X-DChain Material Status

    • Definition of relations between x-plant and x-dchain material status.

Checks on the cross distribution chain material status are only executed, if a distribution chain view for the material master record exists.
Actions on cross distribution chain material status are only executed, if a distribution chain view for the material master record exists OR the action is executed directly (option Set directly, no follow-up actions possible activated).

  • Plant Specific <-> DChain specific Material Status
    • Geben Sie hier den Text ein.Definition of relation between plant dependent and distribution chain specific material status.
  • Plant Specific Material Status <-> Document
    • Defines relations between plant specific material status and documents
  • DChain specific Material Status <-> Document
    • Defines relations between distribution chain specific material status and documents.
  • Material Change -> Data Package Change
    • Allows starting a change on a data package based on a status change of the x-plant material status.

Object relations BOM / Routing

  • Allowed Configuration Types in BOM / Inheritance
    • Definition of allowed configuration types within a BOM. Document and text positions are not affected by these checks. Furthermore the inheritance of documents will be activated.
  • Configuration Types -> BOM Items

    • Defines checks on BOM components when reaching defined material statuses.

BOM positions with option "recursiveness allowed" will NOT be checked. This because otherwise a defined status change could be prevented by each other material.

  • Data Packages -> BOM items
    • Defines whether the BOM items of a data package shall be checked for a certain status, after the data package has reached a certain status. (x-plant or plant dependent material state).
  • Configuration type -> BOM
    • Defines relations between configuration types and BOM's.
  • Document -> BOM
    • Defines relations between document types and BOM's.
  • Actions/Checks BOM
    • Defines different actions and checks on BOMs. Depending on the BOM, the checks or actions will be for the material master record (material BOM) or the document info record (document structure).
    • Object Type / Status (BOM)
      • Whether a BOM can be maintained or not generally depends on the settings „BOM maintenance" according Actions/Checks BOM. In case the maintenance is restricted, it will still be possible, as long as the data package is in a change status.
      • The settings will allow to define whether the maintenance shall only be possible for a specific status of a data object within the data package. For more then one set of settings, at least one requirement must be fulfilled to allow the BOM maintenance (OR relation).

      • Note for document status:

Any status entered here, allows editing of the BOM, ignoring the status type or if marked "Discontinued".

  • Control of routing assignments

    • Using this setting it is possible to define which assignments for a routing can made. This can be none (e.g. for a reference operation set) or only 1:1 or 1:n relations.

Rules for selecting the customizing records

If due to multiple material assignments more than one object relation is selected, then for the checks of the assignments the "strongest" setting is used. This is valid for "Mat. assignment" and "Plant assignm."

    • Configuration type -> Routing
      • Defines relations between configuration types and routings.
    • Document -> Routing
      • Defines relations between document types and BOM's.
    • Actions/Checks Routings

      • Defines actions and checks for routings and inspection plans.

Rules for selecting the customizing records

  • If more than one plant is assigned to a routing and therefore more than one customizing record is valid, the record which matches best the plant from the routing header is used. Example: if a record for plant 1000 and one with plant * exists and in the routing header the plant 1000 is entered, then the record with plant 1000 will be used.
  • If this way no record can be determined, the first of all selected records is used.
  • If due to multiple material assignments more than one object relation is selected, then for the checks of the routing references the "strongest" setting is used.
  • For the settings "Check changes reference object", "Check change number" and "Use alternative dates" following rules must be followed:
    • If for the routings multiple object relations are used, then the object relation definitions which can be used on the same routing types must use the same settings on the fields mentioned above. Otherwise the behaviour is undefined, because the definitions to be used is not predictable.

  • With ProNovia Trace, event CFM 4005 it is possible to log which of the records has effectively been used.|

Usage of routing, for which theses settings are valid (* allowed, empty = all).

The "Usage" in a routing can be changed by the user. To keep the data consistent, ProConfiguration implements some actions and rules to ensure this. See following description.

Following special actions and rules applies on the "Usage" field, if a routing type is relevant for ProConfiguration object relations:

  • When creating a routing, by default the usage can not be entered on the initial screen. But to determine the correct relation definition, ProConfiguration has to know this:
    • If the routing is created without any material master record assignment, no checks are made. In this case any later material master record assignment is checked (see below).
    • If on the start screen a profile was specified and in this profile the usage is defined, this value is used. The material master assignment will be checked as described below.
    • If according to the ProConfiguration customizing for the entered material master record only one usage is valid, this usage is used.
    • Otherwise the usage is asked from the user. The user can select from a list, build from all usages defined in the object relation customizing for the corresponding configuration type of the material master record.
  • When saving a routing, following checks are performed:
    • Any changed usage is checked:
      • The new usage must be valid for all assigned material master records.
      • "Assigned material master records" means:
        • When creating a routing, all assigned material master records.
        • When changing all but the removed and newly added material master records. Newly added material master records are checked separately, see below.
      • The new usage is valid, when a definition for this usage exists for each object relation definition of the corresponding configuration types for the assigned material master records.
    • After validating any change of the usage, newly assigned material master records are checked:

      • A material master record can be added, when the object relation definition of the corresponding configuration type has a definition for the current usage of the routing.

If the user changes the usage, depending on the customizing different object relation settings may be used. Defining different such object relation settings which allow to change the usage must be "compatible". This means they should have the same settings for checking the change number, material assignment and references.

  • Object type / Status (Routing)
    • Whether a routing can be maintained in general depends on the setting under "Check changes reference object" as described in Actions/Checks Routings. In case the handling is restricted, it will still be possible in combination with data packages, as long as the data package is being changed.
    • If the maintenance shall only be possible for a specific status or dependent on another data object, it can be defined in this setting „Object type / status (routing). If more than one set is defined, at least one set must meet the defined conditions, so the BOM handling will be possible. (OR linkage).

Note for document status:

Any status entered here, allows editing of the routing, ignoring the status type or if marked "Discontinued".

  • No labels

© ProNovia AG | Imprint | Data Protection