Search Results bom_resources_u1




Overview

BOM.BOM_RESOURCES is a foundational master table within the Oracle E-Business Suite Bills of Material schema. It stores the definitions of resources, overheads, material overheads, and material sub-elements used across manufacturing, costing, work-in-process (WIP), purchasing, and project accounting flows. The COST_ELEMENT_ID column determines whether a given row represents a resource, an overhead, or a material overhead, and resources are further classified as either material resources or outside processing resources.

Because BOM_RESOURCES is the authoritative parent for a large number of dependent transactional and costing tables, it functions as a central reference point for cost rollup, rate definition, and shop-floor resource charging. In Data Vault modeling terms, the mined foreign key structure characterizes this object as a hub: RESOURCE_ID acts as a stable business key to which many descriptive attributes and dependent satellites would attach. This classification is a modeling suggestion rather than a physical property of the EBS table itself.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes are held in APPS_TS_TX_IDX. The object is documented as VALID in ETRM 12.2.2 with 57 columns under the BOM schema.

Key Information Stored

The most operationally significant columns include:

The two unique indexes, BOM_RESOURCES_U1 (ORGANIZATION_ID, RESOURCE_CODE, COST_CODE_TYPE) and BOM_RESOURCES_U2 (RESOURCE_ID), are the documented business-key candidates. The non-unique BOM_RESOURCES_N1 supports lookup by ORGANIZATION_ID and PURCHASE_ITEM_ID.

Common Use Cases and Queries

Typical usage centers on listing active resources for an organization, resolving the cost element for a resource, and joining resource definitions to the transactions that consume them.

SELECT RESOURCE_ID, RESOURCE_CODE, DESCRIPTION, RESOURCE_TYPE
FROM   BOM.BOM_RESOURCES
WHERE  ORGANIZATION_ID = :org_id
AND    DISABLE_DATE IS NULL;

Cost rollup and overhead analysis frequently require joining BOM_RESOURCES to CST_ITEM_COST_DETAILS on RESOURCE_ID, while shop-floor reporting joins to WIP_OPERATION_RESOURCES and WIP_TRANSACTIONS. Purchasing reports use the PURCHASE_ITEM_ID linkage to PO_* tables, and project accounting uses PA_RESOURCE_ASSIGNMENTS and PA_RESOURCE_LIST_MEMBERS to bind billable costs.

Related Objects