Search Results bom_resource_equipments_u2

Overview

BOM.BOM_RESOURCE_EQUIPMENTS is a transactional table in the Oracle E-Business Suite Bill of Materials (BOM) schema that stores the association between Equipment Type resources — resources of subtype "Machine" — and the specific equipment instances identified by inventory items, for the Warehouse Management System (WMS). In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is marked VALID in the ETRM repository. Its FND Design Data reference is BOM.BOM_RESOURCE_EQUIPMENTS.

Each row answers the question of which inventory item represents a given machine resource within a given organization. The combination of resource, organization, and inventory item forms the business key, and the table is therefore best regarded, from a Data Vault modeling perspective, as a hub-like entity for the resource-to-equipment relationship rather than as a descriptive satellite.

Key Information Stored

The table defines 29 columns, of which the following are the most consequential for development, integration, and reporting work:

• RESOURCE_ID — Unique identifier of the resource (Equipment Type / Machine). This is the primary linkage to the BOM resource definition.
• ORGANIZATION_ID — Identifier of the inventory organization that owns the equipment record. Organization context is mandatory for correct multi-org resolution.
• INVENTORY_ITEM_ID — Identifier of the inventory item representing the physical equipment instance.
• INSTANCE_ID — Instance identifier, indexed non-uniquely by BOM_RESOURCE_EQUIPMENTS_U1; used by WMS to resolve equipment instances.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield structure and segment columns, each VARCHAR2(150) for the segments, available for customer-specific extension data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns present on all rows.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns populated when the row is created or updated by a batch process.

The declared primary key is BOM_RESOURCE_EQUIPMENTS_PK over (RESOURCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID). The unique index BOM_RESOURCE_EQUIPMENTS_U2, on the same three columns, enforces the same business key at the physical level, while BOM_RESOURCE_EQUIPMENTS_U1 provides non-unique access by INSTANCE_ID. This redundancy means the composite triple functions simultaneously as surrogate primary key and business-key candidate; there is no separate synthetic single-column key.

Common Use Cases and Queries

Typical applications include validating equipment-resource assignments before releasing WMS work, reconciling machine capacity against inventory item definitions, and extracting equipment metadata for shop-floor dashboards. A frequent pattern is a join back to the resource definition to resolve the resource name:

• List all equipment for an organization: SELECT RESOURCE_ID, INVENTORY_ITEM_ID, INSTANCE_ID FROM BOM.BOM_RESOURCE_EQUIPMENTS WHERE ORGANIZATION_ID = :org_id;
• Resolve a single resource's equipment: filter on RESOURCE_ID and ORGANIZATION_ID, the leading columns of both unique indexes, to obtain an index-driven access path.
• Instance lookup by WMS: query on INSTANCE_ID to exploit BOM_RESOURCE_EQUIPMENTS_U2 for non-unique instance resolution.
• Flexfield reporting: select ATTRIBUTE_CATEGORY and the relevant ATTRIBUTEn columns when customer-specific equipment attributes must be surfaced.

Because the table carries no foreign keys in the metadata, joins are convention-based rather than declarative; query performance depends on supplying ORGANIZATION_ID to constrain the multi-org data set.

Related Objects

The following objects are the most significant reference points for this table, joined on the documented key columns:

• BOM.BOM_RESOURCES — master definition of resources; join on RESOURCE_ID to obtain resource names and types.
• BOM.BOM_DEPARTMENTS — departmental context for resources, typically reached through the resource record.
• MTL_SYSTEM_ITEMS_B — inventory item master; join on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve item descriptions and attributes.
• MTL_PARAMETERS — organization definition; join on ORGANIZATION_ID to resolve the operating unit and organization code.
• WMS-related equipment and instance tables — consume INSTANCE_ID to link the equipment record to WMS execution data.
• BOM.BOM_RESOURCE_EQUIPMENTS child or history objects (if implemented locally) — any customer-specific extension tables keyed on the same three-column composite.