Results for “parent_structure_type_id”

36 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The BOM_STRUCT_ATTR_GRP_ASSOCS_V view, owned by the APPS schema in Oracle E-Business Suite, presents the associations between Bill of Materials (BOM) structure types and Oracle EGO (Enterprise Object / attribute group) attribute groups. Its documented purpose, per the ETRM metadata, is to "Display BOM structure attribute group associations." In practice, the view answers the question: for a given BOM structure type, which attribute groups from the Oracle EGO attribute-group framework are associated with it?

The view bridges two functional areas. The BOM module defines structure types such as bill of material, routing, or engineering bill, while the EGO framework provides the extensible attribute group mechanism used to capture user-defined descriptive flexfield-style attributes. By joining these two worlds through the common STRUCTURE_TYPE_ID key, BOM_STRUCT_ATTR_GRP_ASSOCS_V exposes which attribute groups apply to which structure types. This makes it useful for reporting on attribute group configuration, for integration scenarios that must know the effective attribute groups per structure, and for diagnostics when extensible attributes are not appearing as expected for a given BOM structure type. Because it is a view rather than a table, it carries no data of its own and always reflects the current state of its dictionary sources.

Underlying Base Objects

The documented ETRM metadata specifies exactly two referenced base objects: BOM_STRUCTURE_TYPES_B (referenced as a synonym) and EGO_OBJ_ATTR_GRP_ASSOCS_V (itself a view). The view definition in the excerpt confirms this two-source join:

  • EGO_OBJ_ATTR_GRP_ASSOCS_V EOAGAV — supplies the attribute group association details, aliased as EOAGAV. Its CLASSIFICATION_CODE is cast to a character value and equated with the BOM structure type identifier carried on the BOM table.
  • BOM_STRUCTURE_TYPES_B BSTB — supplies the structure type identity and naming, aliased as BSTB. Its STRUCTURE_TYPE_ID is compared to the EGO classification code (via TO_CHAR), and its PARENT_STRUCTURE_TYPE_ID provides hierarchy information.

The join predicate is EOAGAV.CLASSIFICATION_CODE = TO_CHAR(BSTB.STRUCTURE_TYPE_ID), and the query is further restricted with EOAGAV.APPLICATION_ID = 702. Application 702 is the Oracle Bills of Material / related manufacturing application identifier, so the restriction ensures that only attribute group associations belonging to the BOM application context are returned. The dependency on EGO_OBJ_ATTR_GRP_ASSOCS_V means the view ultimately reads from the EGO attribute group association model, while the BOM tables provide the structure type labels.

Key Columns

The view exposes ten columns, summarized as follows:

  • STRUCTURE_TYPE_ID — the identifier of the BOM structure type; derived from EOAGAV.CLASSIFICATION_CODE. This is the column most commonly used to filter or join, and is the term the user searched for.
  • PARENT_STRUCTURE_TYPE_ID — the parent structure type identifier from BOM_STRUCTURE_TYPES_B, supporting hierarchical structure type relationships.
  • STRUCTURE_TYPE_NAME — the descriptive name of the BOM structure type.
  • ATTR_GROUP_NAME — the internal name of the associated EGO attribute group.
  • ATTR_GROUP_TYPE — the type classification of the attribute group.
  • ATTR_GROUP_ID — the unique identifier of the attribute group.
  • ATTR_GROUP_DESCRIPTION — the full description of the attribute group.
  • ATTR_GROUP_DISP_NAME — the display name shown to users.
  • OBJECT_NAME — the underlying EGO object name to which the attribute group is attached.
  • APPLICATION_ID — the application identifier; constrained to 702 within the view definition.

Common Use Cases and Queries

Typical uses include confirming which attribute groups are configured against a structure type, validating configuration after an upgrade or patch, and driving integrations that need the effective attribute group set per structure. A representative query filtered on the searched term follows:

  • SELECT structure_type_id, structure_type_name, attr_group_name, attr_group_disp_name, object_name FROM bom_struct_attr_grp_assocs_v WHERE structure_type_id = :p_structure_type_id;
  • SELECT * FROM bom_struct_attr_grp_assocs_v ORDER BY structure_type_name, attr_group_name; to list all structure-to-attribute-group associations.
  • SELECT structure_type_name, COUNT(*) FROM bom_struct_attr_grp_assocs_v GROUP BY structure_type_name; to audit how many attribute groups each structure type carries.

Because APPLICATION_ID is fixed at 702, no additional application filter is required. Filtering on SECTION_TYPE_ID is unnecessary and invalid; the correct identifier column is STRUCTURE_TYPE_ID.