Results for “bom_resources_v”

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

Overview

BOM_RESOURCES_V is an APPS-owned database view within the Oracle E-Business Suite Bills of Material (BOM) product family. Its documented purpose is to present "resources, overheads, material cost codes, and material overheads" in a single consolidated result set. In EBS 12.1.1 and 12.2.2 the view carries a VALID status and is exposed through the APPS schema, which is the standard convention for objects intended for use by forms, concurrent programs, reports, and external integrations rather than direct base-table access.

From a reporting standpoint, BOM_RESOURCES_V abstracts the physical organization of resource data spread across BOM_RESOURCES and the activity master CST_ACTIVITIES. Rather than forcing report authors and integration developers to join these tables manually, the view resolves the resource's default activity identifier into its descriptive activity name. It also performs a small but significant piece of decode logic against the functional currency flag, described further below. Because the object is a view rather than a table, it holds no persistent data; all columns are derived at query time, and it cannot be updated directly.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents exactly two referenced base objects, both exposed to the view owner as synonyms: BOM_RESOURCES and CST_ACTIVITIES. The defining query selects from BOM_RESOURCES (aliased BR) and performs an outer join — expressed in legacy Oracle syntax as CA.ACTIVITY_ID(+) = BR.DEFAULT_ACTIVITY_ID — to CST_ACTIVITIES (aliased CA). The outer join direction is deliberate: it guarantees that every resource row survives even when no matching activity record exists in CST_ACTIVITIES, in which case DEFAULT_ACTIVITY returns a null value. The view also materializes ROWID from BOM_RESOURCES as the ROW_ID column, giving consumers a stable handle to the underlying resource row.

Key Columns

• RESOURCE_ID / RESOURCE_CODE — the surrogate key and the user-facing identifier of the resource; RESOURCE_CODE is the value most commonly filtered on in reports and loaders.
• ORGANIZATION_ID — the inventory organization that owns the resource, establishing multi-org context for every row.
• DEFAULT_ACTIVITY_ID and DEFAULT_ACTIVITY — the activity key plus the associated descriptive activity name resolved from CST_ACTIVITIES through the outer join.
• COST_ELEMENT_ID, COST_CODE_TYPE, FUNCTIONAL_CURRENCY_FLAG — cost classification attributes. The view applies a DECODE on FUNCTIONAL_CURRENCY_FLAG, mapping a flag value of 1 to a resource type of 6, otherwise passing the stored RESOURCE_TYPE through unchanged. This means the RESOURCE_TYPE column returned by the view may differ from the raw column value in BOM_RESOURCES.
• ABSORPTION_ACCOUNT and RATE_VARIANCE_ACCOUNT — accounting flexfield assignments used when resource costs are charged and when rate variances are recognized.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, plus concurrent manager columns REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE.
• Descriptive and control attributes — DESCRIPTION, DISABLE_DATE, UNIT_OF_MEASURE, AUTOCHARGE_TYPE, STANDARD_RATE_FLAG, DEFAULT_BASIS_TYPE, ALLOW_COSTS_FLAG, and the fifteen generic ATTRIBUTE columns, together with batch-related fields such as BATCHABLE and the batch capacities.

Common Use Cases and Queries

Typical consumers use BOM_RESOURCES_V to list chargeable resources per organization, to feed costing and capacity reports, and to reconcile resource rates and accounts before month-end. A representative query filtering to active resources in one organization follows:

SELECT resource_code, description, resource_type,
       default_activity, unit_of_measure,
       absorption_account, rate_variance_account
FROM   apps.bom_resources_v
WHERE  organization_id = :org_id
AND    NVL(disable_date, SYSDATE + 1) > SYSDATE;

For costing extracts, select COST_ELEMENT_ID, COST_CODE_TYPE, and the account columns alongside the resource identifiers. For integration loads, remember that the view is read-only; DML must target BOM_RESOURCES directly, and the RESOURCE_TYPE returned here should be compared against the base table only after accounting for the FUNCTIONAL_CURRENCY_FLAG decode.