Business objects are the building blocks of Teamcenter which hold the properties and allows configuring rules on top of it.
Business objects can be configured either as Primary business object or Secondary business object based on our need.
Primary Business object
A primary business object corresponds to a POM Class. The name of the POM class is same as the name of the corresponding primary business object. Teamcenter stores the data of the primary business object in its corresponding POM class.
Whenever a new primary business object is created in Teamcenter application, the POM class is instantiated. That is, a new row is inserted into the POM class table in the database.
As primary business object has its own class(storage table), it can have its own custom persistent properties. Persistent properties are created through BMIDE (Look for the Teamcenter properties blog for more information). A new persistent properties creates a new column in the corresponding table in database.
Examples of primary business objects are Item, Part, Design, etc. Each of these objects has its own storage class to hold its own set of properties and to configure its own set of rules.
Secondary Business object
A Secondary business object does not have its own POM class. Its properties and behavior are inhered from its primary business object. As secondary business object does not have its storage class/table, we cannot create a persistent properties on the secondary business object.
Examples of secondary business objects are PDF, MSWord, MSExcel, etc. Each of these objects are derived from its primary business object Dataset.
How to decide between Primary and Secondary Business object:
Before creating a new custom business object in BMIDE, we should decide whether we are going to create it as primary or secondary business object. This decision is based on the use case requirement and the solution design.
Some scenarios and the decision taken:
Case 1: Create 5 custom part objects with same set of properties in each of the part.
Here. create a primary business object(base object) with all the properties, followed by 5 parts of secondary business object by selecting the parent object created above. By this configuration, all the properties from parent business object is derived to secondary business objects.
Case 2: Create design part and manufacturing part
In this case, both parts have different sets of properties. Create both these parts as primary business objects and then add the respective properties to them.
Benefits of secondary business object:
BMIDE configuration is simple and easy.
Creation of repetitive properties are eliminated.
As the tables are not created for secondary business object, database size is reduced by creating secondary business object.
How to create primary/secondary business object in BMIDE:
For creating primary business object. check the box as shown below during new business object creation.
For creating secondary business object, uncheck the box during new business object creation.