Results for “bom_components_ocv”

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

Overview

BOM_COMPONENTS_OCV is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the Bills of Material (BOM) product family. Despite its name, which suggests a flattened set of bill of material components, the documented view definition exposes only the rows and columns of the structure type reference data set. The view is defined as a simple projection over BOM_STRUCTURE_TYPES_VL, returning STRUCTURE_TYPE_ID, STRUCTURE_TYPE_NAME, and LANGUAGE. It therefore functions as an alternate, view-based access point to the list of bill of material structure types rather than as a component explosion view.

In the context of Oracle EBS 12.1.1 and 12.2.2, the object is registered in ETRM as a VALID view under the BOM module. Its role is primarily reporting and integration: it allows concurrent programs, Oracle Reports, BI Publisher data models, and external interfaces to retrieve structure type codes and descriptions without querying the underlying _VL view directly. Because it is a read-only projection with no business logic, performance is equivalent to querying the base view, subject to the same language and MLS filtering of the _VL construct. The "OCV" suffix is consistent with the Oracle convention used across EBS for views intended for output or concurrent use, though in this instance the underlying definition is a thin wrapper over structure type reference data.

Underlying Base Objects

The only documented referenced base object is BOM_STRUCTURE_TYPES_VL, itself a view in the APPS schema. BOM_STRUCTURE_TYPES_VL is the MLS (Multi-Language Support) view over the BOM_STRUCTURE_TYPES base and translation tables. It presents the structure type identifier, the translated structure type name, and the language of that translation, hiding the join between the base table and the _TL translation table.

Because BOM_COMPONENTS_OCV selects directly from BOM_STRUCTURE_TYPES_VL without joins, filters, or aggregation, it inherits all row-level and language behavior of the _VL view. There are no additional tables, no unions, and no materialized constructs involved. Any change to the structure type setup data, such as adding a new bill of material structure type or changing a translated name, is immediately reflected through this view.

Key Columns

• STRUCTURE_TYPE_ID — Numeric primary key identifying the bill of material structure type. This value is used as a foreign key reference throughout BOM tables to indicate which structure type a bill is associated with.
• STRUCTURE_TYPE_NAME — The translated display name of the structure type, for example the name associated with a given BOM structure classification. The value reflects the language returned by the _VL view.
• LANGUAGE — The language code of the translation row returned. This column supports MLS environments and determines which translated structure type name is presented.

No other columns are documented in the ETRM view text. The metadata does not expose creation or update audit columns, nor the typical _TL surrogate keys such as SOURCE_LANG, which are internal to the underlying translation table.

Common Use Cases and Queries

The view is most useful when the objective is to list valid bill of material structure types with their translated names, for example to populate a parameter list of values in a concurrent program or to validate a structure type identifier supplied by an interface. A representative query is:

• SELECT structure_type_id, structure_type_name, language FROM apps.bom_components_ocv ORDER BY structure_type_name;
• SELECT structure_type_id, structure_type_name FROM apps.bom_components_ocv WHERE language = USERENV('LANG') ORDER BY structure_type_name;
• SELECT structure_type_id FROM apps.bom_components_ocv WHERE structure_type_name = :p_structure_type_name;

Typical scenarios include building a data model for a report that groups bills by structure type, joining the returned STRUCTURE_TYPE_ID to other BOM entities, or exposing the structure type list through an inbound interface. Note that the view cannot be used to explode components; for component-level analysis the appropriate BOM component views and tables should be queried instead. Also note the view name contains "COMPONENTS" but the exposed data is structure type reference data, so catalog searches using partial text such as the user query "Bin ovc" should be validated against the actual ETRM definition rather than the object name alone.