Mapping properties to occurrence properties

You can map properties to occurrence properties in Teamcenter so that business users can interact with domain-specific properties derived from BOMLine or ModelElement types. The Awb0BOMToOccurrence property constant helps you in this mapping, enabling properties like awb0BoundingBox to fetch values from bl_bounding_boxes.

Domain-specific occurrences contain properties relevant to the specific domain. End users understand and interact with these domain-specific properties. These properties are mapped from the BOMLine or ModelElement type onto the occurrence. This mapping is provided by property constants defined in the Business Modeler IDE and the property constants are scoped to the Awb0Element type. Default properties are provided on Awb0Element and its subtypes, but you can add custom properties necessary for your implementation.

All custom properties must be mapped to a property defined on the type specified in the Awb0BOMToOccurrence type constant. The property mapping is then achieved through the Awb0BOMToOccurrence property constant. The value of this property constant is inherited and can be overridden at any level.

For example, the awb0BoundingBox property on the Awb0PositionedElement business object has the value of bl_bounding_boxes. It also has the value BOMLine for the Awb0BOMToOccurrence type constant. Consequently, whenever the awb0BoundingBox property is requested on an Awb0PositionedElement object, the value is fetched from the bl_bounding_boxes property of the BOM line.

Mapping of common default properties

Business object	Property	Awb0BOMToOccurrence value
Awb0Element	awb0Parent	bl_parent
Awb0Element	awb0Name	bl_line_name
Awb0Element	awb0ElementId	—
Awb0Element	awb0Archetype	bl_revision
Awb0ConditionalElement	awb0ArchetypeEffFormula	bl_revision_effectivity
Awb0ConditionalElement	awb0ElementId	awb0BomLineItemId
Awb0PositionedElement	awb0BoundingBox	bl_bounding_boxes
Awb0PositionedElement	awb0Transform	bl_plmxml_abs_xform

Default getter and setter methods are registered for all properties of Awb0Element and child business objects that have a mapping defined in the Awb0BOMToOccurrence property constant. You must provide a custom getter and setter for all properties that are not already mapped. For example, the awb0NumberOfChildren property specifies the number of child elements and does not have a value for the property constant; custom getter and setter methods are registered for it. You can use the same mechanism to register getter and setter methods for properties on custom Awb0Element subtypes.

Many configured runtime properties on BOMLine are derived from Item, ItemRevision, or another object. These are always of type string, irrespective of the type from which they are derived. Mapping to such a property will result in losing the type information about the property that the system requires for proper filtering of Solr results. To avoid this, instead of mapping to a configured runtime property, define a new compound property on the backing object and use the relations or reference properties to get the source property. This maintains the type information for the property so that it can be used in mapping.

For example, you may want to get the last modified date stored in the configured runtime property bl_rev_last_mod_date on the BOM line. Instead of using the bl_rev_last_mod_date property, consider the awb0RevisionLastModifiedDate compound property on the BOM line. This uses the bl_revision property to access the item revision and you can get the last_mod_date property from there. An awb0ArchetypeRevLastModDate property is defined on the Awb0DesignElement business object and then mapped to the awb0RevisionLastModifiedDate property.