Search Results bom_structure_types_vl




Overview

BOM_STRUCTURE_TYPES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the Bills of Material (BOM) product family and presents the complete set of structure type definitions maintained by the application, combined with their translated display names. In Oracle EBS, structure types classify the purpose of a bill of material or routing — for example, manufacturing bills, engineering bills, model structures, planning bills, and option class structures. The "_VL" suffix denotes a "view with language" that joins a base table to its translation table and filters the translation rows to the session language, so each query returns exactly one row per structure type with the name and description rendered in the caller's language.

The view serves as the primary reference point wherever Oracle EBS reports, concurrent programs, and integration interfaces must resolve a structure_type_id into a user-readable name. Because it is a view rather than a table, it exposes no DML surface of its own; all maintenance is performed by the application through the underlying base and translation tables. Order Management, Work in Process, Engineering, and Advanced Supply Chain Planning all rely on this structure type configuration when deciding how a BOM is exploded, copied, or interpreted.

Underlying Base Objects

The documented view text defines BOM_STRUCTURE_TYPES_VL as a join between two synonyms that reside in the APPS schema:

The two are joined on BASE.STRUCTURE_TYPE_ID = TL.STRUCTURE_TYPE_ID, with the additional predicate TL.LANGUAGE = USERENV('LANG'). This predicate restricts the result set to the language of the current session, which is why the view produces a single row per structure type rather than one row per installed language. The SOURCE_LANG column identifies the language in which the record was originally entered, supporting the standard Oracle translation model in which a new language falls back to the source language until a translation is created.

Key Columns

  • ROW_ID — the ROWID of the base table row, useful for direct row addressing in the base table.
  • STRUCTURE_TYPE_ID — the unique primary key of the structure type.
  • STRUCTURE_TYPE_NAME — the translated name of the structure type, the column most commonly displayed to users.
  • DESCRIPTION and DISPLAY_NAME — translated descriptive text and the alternate display label maintained in the translation table.
  • LANGUAGE and SOURCE_LANG — the session language of the retrieved translation and the original source language of the record.
  • PARENT_STRUCTURE_TYPE_ID — self-referencing pointer establishing structure type hierarchy or sub-type relationships.
  • ITEM_CATALOG_GROUP_ID — the item catalog group associated with the structure type, used in configured item and catalog contexts.
  • EFFECTIVE_DATE and DISABLE_DATE — the active window during which the structure type may be used.
  • STRUCTURE_CREATION_ALLOWED, ENABLE_UNIMPLEMENTED_BOMS, ALLOW_SUBTYPES, ENABLE_ATTACHMENTS_FLAG — behavioral flags governing whether users may create BOMs of this type, whether unimplemented BOMs are permitted, whether sub-types are allowed, and whether attachments are enabled.
  • ATTRIBUTE_CATEGORY through ATTRIBUTE1–15 — the descriptive flexfield segments attached to the structure type.
  • Audit columnsCREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes LOV population, validation of structure_type_id values in inbound interfaces, and joins to BOM_BILL_OF_MATERIALS for reporting. A straightforward retrieval of all structure types in the user's language is shown below.

  • SELECT structure_type_id, structure_type_name, description FROM bom_structure_types_vl ORDER BY structure_type_name;
  • SELECT structure_type_name FROM bom_structure_types_vl WHERE structure_type_id = :p_structure_type_id;
  • SELECT b.bill_sequence_id, s.structure_type_name FROM bom_bill_of_materials b, bom_structure_types_vl s WHERE b.structure_type_id = s.structure_type_id;

In all cases the view guarantees language-sensitive names without requiring the caller to write translation joins, making it the preferred access path for both concurrent programs and external integrations.