Items are the fundamental object used to model data in Teamcenter. They are commonly used to identify an element of a product (component, assembly, end item) or other data such as procurement specification, test procedure, standard part, shop tooling, change, and so on.
Data modeled using the Item business object is generally revision controlled data and all revisions of the information must be maintained, tracked, and recoverable. Data must also be modeled using the Teamcenter concept of item if you want to build a structure of the items such as a bill of material (BOM) for items that represent a product.
Item is the most common business object under which you create a new business object. Use the Item business object or its children when you want to create business objects to represent product parts. When you create a business object using Item (or one of its children) as the parent, in addition to the new business object, system also create an item master form, an item revision, and an item revision master form.
Item Data Model
An item in Teamcenter is a structure of related objects. The basic structure of any item consists of the following minimum objects:
Collects data that is globally applicable to all revisions of the item. You typically add custom attributes directly to the custom item business object.
A form object that is often used to extend the stored property data for an item to include data unique to the customer.
The storage object for the item master form.
Collects data that is applicable to a single revision of the item.
A form object that is often used to extend the stored property data for an ItemRevision object to include data unique to the customer.
The storage object for the item revision master form.
Extending Item business object
The Business Modeler IDE can be used to define more Item business objects in addition to those provided with base Teamcenter. Reasons for extending the Item business objects are:
Having more types of Item business objects may be a useful approach of categorizing data making it easier for users to find data and understand the differences between different kinds of data stored in the system.
Different rules for naming conventions, deep copy rules, and so on, can be configured for one type of Item business object compared to another type.
Default process model association for one type of Item business object versus another is easier to implement.
Different designs for the Item Master and ItemRevision Master forms may be desired. Each type of Item business object can have unique and different master form definitions.