Results for “setup_id”

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

Overview

BOM_RESOURCE_SETUPS is a transactional configuration table owned by the BOM schema within the Oracle E-Business Suite Bills of Material module. It defines the valid association between a manufacturing resource and a setup type, materializing which resource is permitted to perform, or transition through, a given setup state. In discrete and repetitive manufacturing environments, resources such as machines, work centers, and production lines accumulate setup time when switching between states—for example, changing a die, adjusting a fixture, or reconfiguring a tool. BOM_RESOURCE_SETUPS acts as the intersection that binds a resource to an allowable setup, providing the foundation against which setup transitions and setup time calculations are validated.

The table is populated and maintained through the Bills of Material resource and setup maintenance functions. Its heuristic Data Vault classification is satellite-leaning: it records descriptive state about the relationship between a resource and a setup type, with a composite natural key and limited hub-like independence. Analysts applying Data Vault modeling should treat it primarily as a satellite attached to resource and setup-type hubs rather than as an independent hub.

Key Information Stored

BOM_RESOURCE_SETUPS contains 24 documented columns. The most significant are:

• RESOURCE_ID — Identifies the manufacturing resource; part of the composite primary key and a foreign key to BOM_RESOURCES.
• ORGANIZATION_ID — Scopes the record to the operating unit/inventory organization; part of the composite primary key.
• SETUP_ID — Identifies the setup type; part of the composite primary key and a foreign key to BOM_SETUP_TYPES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Audit columns tracking the most recent modification and the responsible user.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns recording initial creation and login context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The flexible descriptive flexfield (DFF) segment set used for customer-specific extensions.

The surrogate primary key, BOM_RESOURCE_SETUPS_PK, is defined on (RESOURCE_ID, ORGANIZATION_ID, SETUP_ID). A unique index, BOM_RESOURCE_SETUPS_U1, covers the same three columns, confirming the business-key candidate set. Practitioners should note that the primary key is itself composite and effectively synonymous with the business key, since no separate single-column surrogate is documented.

Common Use Cases and Queries

Typical uses include validating which setups a resource may transition through, driving setup-time calculations in costing and scheduling, and reporting resource-to-setup configuration by organization. A representative query listing valid setups for a resource is:

• SELECT rs.resource_id, rs.organization_id, rs.setup_id FROM bom.bom_resource_setups rs WHERE rs.organization_id = :org_id ORDER BY rs.resource_id;
• Joining to resources: SELECT r.resource_code, st.setup_code FROM bom.bom_resource_setups rs JOIN bom.bom_resources r ON r.resource_id = rs.resource_id JOIN bom.bom_setup_types st ON st.setup_id = rs.setup_id WHERE rs.organization_id = :org_id;
• Detecting configured transitions: join to BOM_SETUP_TRANSITIONS on RESOURCE_ID, ORGANIZATION_ID, and FROM_SETUP_ID or TO_SETUP_ID to confirm each transition is backed by a valid resource-setup pair.

Common reporting scenarios include setup matrix audits, resource utilization analysis, and data-integrity checks for orphaned setup assignments within a specific organization.

Related Objects

The following objects are most significant to BOM_RESOURCE_SETUPS:

• BOM_RESOURCES — Referenced via RESOURCE_ID; parent of the resource definition.
• BOM_SETUP_TYPES — Referenced via SETUP_ID; defines the allowable setup states.
• BOM_SETUP_TRANSITIONS — References this table twice, via RESOURCE_ID/ORGANIZATION_ID/FROM_SETUP_ID and RESOURCE_ID/ORGANIZATION_ID/TO_SETUP_ID, governing permitted state changes.
• BOM_OPERATION_RESOURCES and related routing tables — consume resource and setup definitions downstream in manufacturing execution.
• MTL_SYSTEM_ITEMS_B — indirectly relevant through resource-to-item associations.

Because foreign keys are enforced only logically within EBS, referential integrity must be validated explicitly when auditing this table.