Beispiel U-1: Benutzerdefinierte Objekteigenschaft
Inhaltsverzeichnis
Übersicht
In diesem Beispiel wird die Nutzung zusätzlicher Funktionen von Objekteigenschaften erklärt.
Was sind Objekteigenschaften?
Ein Beispiel für eine Objekteigenschaft ist [Artikel] (Order_Item) in der Auftragstabelle. Im Eigenschaftenfenster erkennt man Objekteigenschaften am schwarzen Pfeil vor dem Wert; durch einen Klick auf den Pfeil öffnen sich die Artikeleigenschaften. Sie können in Formeln den Namen von, im Auftrag gesetzten, Artikeln über ME.Order_Item.Item_Name, bzw. kurz ME.Item.Name beziehen.
Objekteigenschaft haben, mit wenigen Ausnahmen, inverse Eigenschaften. So ist etwa die inverse Eigenschaft für [Artikel] in der Auftragstabelle [Aufträge die diesen Artikel nutzen] in der Artikeltabelle. Diese Eigenschaft findet sich unter der Registerkarte [Link] des Eigenschaftenfensters. Wird eine Objekteigenschaft gelöscht, so wird auch die entsprechende inverse Eigenschaft automatisch gelöscht.
Auch benutzerdefinierte Eigenschaften können als Objekteigenschaften angelegt werden.
Vorteile
- Sie können Objekte in verschiedenen Tabellen direkt aus Kombinationslisten auswählen, so dass die Dateneingabe vereinfacht wird.
- Sie können Objekte in benutzerdefinierten Tabellen auswählen.
- Sie können Formel erstellen, die schneller ausgewertet werden.
- Sie kürzere Formeln erstellen.
Variante 1 - Add an object type user property to the integrated master table so that specifications can be selected for each master use instruction
Specifications can be specified for orders, items, and resources. If you set specifications for resources, only operations that match the specifications of the order or item will be assigned.
Here we will consider an example where this specification cannot be determined by resources alone but depends on the integrated master. In this sample data, container sizes (SS / S / M / L) and bottle capacities are defined in the Specification 1 table. Bottle capacities are a float type user property.
| Spezifikationscode | Flaschengröße (ml) |
|---|---|
| SS | 100 |
| S | 200 |
| M | 300 |
| L | 400 |
Packers 1, 2 and 3 in the filling process have the following limitations with regard to the size of the containers that can be filled.
ProductA ProductB
Machines S and under SS and under Packer 2 M and under L and under Filling machine 3 All All
In other words, since producible specification 1 depends on the item, specification 1 cannot be set for resources. Try adding an object type user property to the master use instruction class of the integrated master. The method for doing this is as follows.
From the popup menu of the column headers of the integrated master table, select [Column Settings].
There is no big problem in selecting "All instruction types" in the select box in the middle, but since this is only set for the master use instruction, select Master use instruction. For details, refer to “Adding a new property in the integrated master editor table”.
Specify “Object” for the data type, entering the information as follows.
Once the dialog is closed by pressing the OK button and the column settings are adjusted, the "Specification 1" column is displayed as shown below. Since this property is an object type, a list of the objects in the Specification 1 table is displayed in the select box by clicking a cell or by pressing the ALT and ? keys.
Then, set the valid condition expression for comparing the bottle capacity being assigned and the producible bottle capacity of each resource in the valid condition expression. ME is a split operation, and HOLDER is the master use instruction of the integrated master. ME.Order.Spec1.BottleSize<=HOLDER.Spec1.BottleSize
Even in past versions, this could be realized by adding the string-type user property Spec1Code to a use instruction of the Integrated Master and describing the following valid condition expression. ME.Order.Spec1.BottleSize<=PROJECT.Child['Spec1'].Child[HOLDER.Spec1Code].Spec1User_BottleSize However, this method has the following disadvantages.
The combo box for selecting objects in the Specification 1 table is not displayed. Processing time is extended depending on the number of objects of Specification 1 in order to search for objects in the Specification 1 table. The length of the expression makes it difficult to read.
In the Specification 1 table, the reverse property "Master use instruction" is displayed. In this sample, this reverse property is not used.
By rescheduling, you can see that the container size constraints you have set are met.
Setting 2 Add an object type user property to the resource table and display load graph on resource Gantt chart
The "standard" style of the resource Gantt chart for this sample data allows you to drill down to see the load graph. This also uses object type user properties.
The method for doing this is as follows. First, in the resource table or resource Gantt chart, launch the Column Settings dialog and add the object type user property.
Next, enter ME in the virtual property expression for this property. You can set this either from the resource table or the resource Gantt chart.
Next, set “Hierarchy Properties” (ASGTableViewProps_HierarchySetting) on the Table tab in Display Settings of the resource Gantt chart.
Click the black arrow of the Hierarchy Properties object, display the “Hierarchy Properties” property window, and set “Load amount graph” in “Hierarchy row display content” (ASGHierarchySetting_RowContent).
In this way, you can display yourself in the hierarchically displayed rows. Although you can also display additional load ratio graph rows from the right-click menu as shown below, this method cannot save the additionally displayed rows in Styles.
Praktische Anwendung
Besides the above two setting examples, object type user properties can be applied to various situations such as creating skill maps of workers in the user table and referencing this from valid condition expressions of the Integrated Master. Next, we will introduce a sample that generates rework orders by applying the function to automatically generate objects.
