Results for “bom_setup_types_v”

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

Overview

BOM_SETUP_TYPES_V is a standard Oracle E-Business Suite view owned by the APPS schema and catalogued as VALID. It belongs to the Bills of Material (BOM) product family and is described as "BOM Setup types." The view exposes the setup type reference data used by Oracle Bills of Material and related manufacturing and inventory modules. Setup types classify the way a bill of material or routing is structured and used in production — for example distinguishing standard, model, option class, and planning bills — and therefore underpin a wide range of BOM processing and validation logic.

The object name is frequently surfaced in searches for "setup_code" because SETUP_CODE is one of the principal business-facing columns the view returns. Reporting, integration, and personalization layerings commonly need to resolve the human-readable setup code and its description rather than the internal numeric SETUP_ID, and BOM_SETUP_TYPES_V provides a convenient denormalized path to that data. In Oracle EBS 12.1.1 and 12.2.2 the view is delivered as a seeded, read-mostly component; it is not intended for direct DML.

Underlying Base Objects

The view text is a direct projection over a single base object:

SELECT ST.ROWID ROW_ID, ST.SETUP_ID, ST.SETUP_CODE, ... FROM BOM_SETUP_TYPES ST

ETRM metadata for 12.2.2 documents the referenced base object as BOM_SETUP_TYPES (SYNONYM). The synonym resolves to the underlying APPS table that stores the setup type definitions. Because the view performs no joins, no unions, and no filtering predicates, it is a straightforward one-to-one wrapper: every row in BOM_SETUP_TYPES surfaces as a corresponding row in BOM_SETUP_TYPES_V, and no aggregation or transformation occurs. This simplicity makes the view inexpensive to query and safe to embed in reports, though it also means performance characteristics are governed entirely by the base table and its indexes.

Key Columns

• ROW_ID — The base table ROWID, exposed for tools and templates that require a unique physical row identifier.
• SETUP_ID — The internal numeric primary key for a setup type; used as a foreign key from BOM and routing entities.
• SETUP_CODE — The user-visible setup code. This is the column most often targeted when users search on "setup_code."
• DESCRIPTION — The descriptive text associated with the setup type.
• ORGANIZATION_ID — The inventory organization to which the setup type row is scoped, enabling multi-org filtering.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY and LAST_UPDATE_LOGIN provide the standard who-column audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS flexfield/descriptive attribute columns, available for customer-specific extensions and reporting.

Common Use Cases and Queries

Typical uses include lookups that translate SETUP_ID into SETUP_CODE, validation reports for setup type configuration, and integration extracts that populate downstream planning systems. Because the view is not organization-restricted in its SQL, callers should usually filter on ORGANIZATION_ID when operating in a multi-org environment.

SELECT setup_id,
       setup_code,
       description,
       organization_id
FROM   apps.bom_setup_types_v
WHERE  organization_id = :p_org_id
ORDER  BY setup_code;

To resolve a setup type from a BOM entity, join on the numeric key:

SELECT b.bill_sequence_id,
       v.setup_code,
       v.description
FROM   apps.bom_bill_of_materials b,
       apps.bom_setup_types_v     v
WHERE  b.setup_type = v.setup_id
AND    b.organization_id = :p_org_id;

In Oracle EBS 12.1.1 and 12.2.2 the definition is consistent; no edition-specific differences are documented in the ETRM metadata. As with all APPS views, use of the APPS synonym for reporting is supported, while direct writes are not.