But any Oracle PLM has the power to go some steps further. A user can define his items by making a user-defined attribute group. The ego_mtl_system_items_b table contains a single record which holds the user defined attributes which are defined within groups in the said table. The user can have a choice from a distinct amount of character, numerical or data columns so he can define the attributes in one user defined attribute group. The attribute groups are tied to the items using the item_id, organization_id, and the attribute_group_id within that table. The user can then have a choice whether to have only one row or record of the attribute group per item or enable multiple row option during the definition of the attribute group. After having defined the attribute group, the user can then create a database view of the attribute group so that it would be a lot easier to find the data.
As to the difference between a single row user defined attribute or multi-row user defined attribute, it is often difficult to state the reason for choosing one over the other but in many cases there are many business reasons that can be cited for creating a single row attribute group. For example, in a single row user define attribute group, a user might create three groups “Certification group”, “Label Group”, and “Legacy Data Group”. The “Certification group” is defined so that it shows what certifications a certain item has. The “Label Group” contains the values of the attribute to be printed on a particular item and “Legacy Data Group” is for bringing oven the item information from the system that Oracles is replacing because they don’t map to the operational attributes.
Using the multi-row user defined attribute allows the user to possess more than one row, record or instance of the attribute group per item record. The user can have the choice of storing additional types of definitions which would depend on the item, organization, attribute group as well as a unique value within the attribute group. Although there is no need for defining an attribute within the multi-row attribute group, it can help doing such in cases when the user tries to mass update the attribute group through Oracle “Web ADI”. One of the circumstances when there is a need for using a multi-row user-defined attribute group is when there is a conditional need for label and the user wants to select from multiple rows of the same attribute group based on the label type. The unique key attribute of the group would be the Labels type so that no items will have multiple rows of the group for the same label type.
But whether single or multi row user defined group is used, both can be controlled at the view or edit by assigning or creating a role that gives access privileges.