PLM2 — Item_use_query Reference

PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.49 and Figure 9.65 Cause: Item_use_query does not provide an attribute called maximum_resursion_number---this is only provided by the Recursive_query. Furthermore, the Location_step instance item_instance_step selects all Item_instance instances no matter if they are related (i.e. used) by another Item_instance instance via Item_definition_instance_relationship elements or not. In order to constrain the set of selected Item_instance instances with respect to the semantics intended by the Item_use_query, an additional Relationship_predicate has to be added to Location_step instance item_instance_step. New Specification Text: In figure 9.65 the Location_step instance item_instance_step has to be added a Relationship_predicate to the named relationship related_object_predicate of the Location_step. The predicate instance has to be named inverse_item_definition_instance_relationship_predicate with its attributes initialized as follows: * attribute inverse is set to true, * attribute role_name is set to related and * attribute role_declaring_type_name is set to Item_definition_instance_relationship. Finally, for consistency reasons, the Location_step instance inverse_assembly_component_relationship_step has to be renamed to inverse_item_definition_instance_relationship_step.

In Figure 9.65 the Location_step instance item_instance_step has to be added a Relationship_predicate to the named relationship related_object_predicate of the Location_step. The predicate instance has to be named inverse_item_definition_instance_relationship_predicate with its attributes initialized as follows:
· attribute inverse is set to true,
· attribute role_name is set to related and
· attribute role_declaring_type_name is set to Item_definition_instance_relationship
Finally, for consistency reasons, the Location_step instance inverse_assembly_component_relationship_step has to be renamed to inverse_item_definition_instance_relationship_step