Results for “bom_setup_types”

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

Overview

BOM_SETUP_TYPES is a master setup table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores the definition of setup types — reusable classifications that describe the resource setup activity performed at an operation. A setup type typically maps to a duration or activity basis (for example, fixed setup versus resource-unit-driven setup) that drives how manufacturing setup time is calculated and scheduled. The table functions as a shared, low-volume reference entity consumed by both BOM and Work in Process (WIP) resource definitions, making it a foundational element for cost rollup, capacity planning, and shop-floor scheduling.

The documented relationship structure, in which BOM_SETUP_TYPES carries a surrogate primary key (SETUP_ID) that is referenced by many downstream resource and resource-requirement tables, supports a hub-leaning Data Vault classification. In a Data Vault model, SETUP_ID would serve as the business key of a hub, with BOM_RESOURCE_SETUPS, BOM_OPERATION_RESOURCES, and the various WIP/MSC resource tables acting as links or satellites that capture the contextual relationships and descriptive attributes over time.

Key Information Stored

The table comprises 25 columns, most of which are standard audit and descriptive-attribute fields. The most significant columns are:

• SETUP_ID — The surrogate primary key, enforced by BOM_SETUP_TYPES_PK and also by the unique index BOM_SETUP_TYPES_U1. It is the value propagated to every foreign-key reference in downstream resource tables.
• SETUP_CODE — The user-facing alphanumeric code that uniquely identifies a setup type. Together with ORGANIZATION_ID it forms the business-key candidate enforced by unique index BOM_SETUP_TYPES_U2.
• ORGANIZATION_ID — The inventory organization to which the setup type belongs, enabling the same setup type to be defined independently per organization. It is part of the composite unique index BOM_SETUP_TYPES_U2.
• DESCRIPTION — Free-text explanation of the setup type, used in list-of-values and reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit trail columns capturing who created and last modified the row and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The flexible descriptive flexfield columns that allow customers to extend the setup type definition without schema changes.

Common Use Cases and Queries

Setup types are most commonly queried when building or troubleshooting resource definitions, when analyzing manufacturing lead times, or when reconciling shop-floor data. A typical lookup resolves a setup code to its internal identifier:

SELECT setup_id, setup_code, description
FROM   bom_setup_types
WHERE  organization_id = :org_id
AND    setup_code = :setup_code;

A frequent join pattern enumerates the resources that use each setup type:

SELECT bor.resource_code, bor.setup_id, bst.setup_code
FROM   bom_operation_resources bor, bom_setup_types bst
WHERE  bor.setup_id = bst.setup_id;

Data extraction and reporting layers frequently join BOM_SETUP_TYPES to MSC_RESOURCE_REQUIREMENTS, MSC_OPERATION_RESOURCES, or EAM_FORECAST_WOR to attribute planned and actual setup effort. Integration or ETL routines that load WIP_JOB_DTLS_INTERFACE or MSC_WIP_JOB_DTLS_INTERFACE must resolve SETUP_ID against this table before populating the interface, making it part of the standard reference-data validation set.

Related Objects

The following objects are the most significant references to BOM_SETUP_TYPES. Each carries SETUP_ID as a foreign key back to the primary key.

• BOM_RESOURCE_SETUPS — links a resource to the setup types it supports; the most direct operational dependency.
• BOM_OPERATION_RESOURCES — identifies the setup type associated with an operation resource on a routing.
• BOM_SUB_OPERATION_RESOURCES — extends the setup-type reference to sub-operation resources.
• BOM_OP_RESOURCES_ARCHIVE — archived routing resource rows retaining the setup-type reference for historical analysis.
• WIP_OPERATION_RESOURCES and WIP_SUB_OPERATION_RESOURCES — carry the setup type into discrete work-in-process jobs.
• WIP_JOB_DTLS_INTERFACE — the job-detail interface table used during WIP import.
• MSC_RESOURCE_REQUIREMENTS, MSC_OPERATION_RESOURCES, MSC_JOB_OP_RESOURCES, and MSC-ST staging tables — the Advanced Supply Chain Planning (ASCP) side, where the setup type is retained for capacity and scheduling calculations.
• GMP_APS_OUTPUT_DTL — a process-manufacturing output detail reference.
• EAM_FORECAST_WOR — Enterprise Asset Management work-order forecast reference.

Because these foreign keys are enforced only by application logic in most cases, referential integrity requires attention during data migration and interface loading. No public PL/SQL API is documented for direct DML; setup types are normally created and maintained through the Bills of Material responsibility setup forms.