Results for “bom_resources_val_v”

50+ results




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

Overview

BOM_RESOURCES_VAL_V is a predefined Oracle EBS view owned by the APPS schema and shipped as part of the Bills of Material (BOM) product family. It presents a list-of-values (LOV) oriented projection of the BOM_RESOURCES table, filtered to return only currently enabled resource records. The filter clause TRUNC(NVL(DISABLE_DATE, SYSDATE + 1)) > TRUNC(SYSDATE) expresses the "enabled" semantics: any resource row whose DISABLE_DATE is either null or in the future is treated as active, while resources whose disable date has passed are excluded.

Because the view exposes nearly every business-relevant attribute of a resource — codes, descriptions, UOM, cost element, cost code type, activity defaults, rate flags, accounts, expenditure type, descriptive flexfields, and batch/qualification attributes — it serves as the standard read-only interface used by Oracle Forms LOVs, concurrent reports, and custom integrations that need a curated, active-only resource list without re-implementing the enablement rule. In 12.1.1 and 12.2.2 the object is identical in shape; the 12.2.2 ETRM metadata confirms its status as VALID with APPS ownership.

Underlying Base Objects

The view is defined solely over the synonym/tablespace object BOM_RESOURCES. The column list is a one-to-one selection (BR.* fields) from that table — there are no joins, unions, or aggregations. Consequently, there is no denormalization: every column returned by the view maps directly to a column of BOM_RESOURCES, and the view adds no computed columns. Its only transformation is the row-level WHERE predicate on DISABLE_DATE.

This means the view inherits the table's organization scoping: ORGANIZATION_ID is carried through, and resource enablement is evaluated per row (per organization). When querying, callers should generally constrain by ORGANIZATION_ID to obtain resources valid for a specific manufacturing or costing organization.

Key Columns

Common Use Cases and Queries

Typical usage involves LOV population, active-resource reporting, and functional-currency-aware cost analysis. The following retrieves enabled resources for an organization that are rated in the functional currency:

  • Standard LOV query: SELECT resource_code, description FROM bom_resources_val_v WHERE organization_id = :org_id ORDER BY resource_code;
  • Functional-currency resource list: SELECT resource_id, resource_code, description FROM bom_resources_val_v WHERE organization_id = :org_id AND functional_currency_flag = 'Y';
  • Counting active resources by type: SELECT resource_type, COUNT(*) FROM bom_resources_val_v WHERE organization_id = :org_id GROUP BY resource_type;

Because the enablement predicate is resolved at query time using SYSDATE, results change automatically as disable dates pass; this makes the view suitable for point-in-time validation without custom logic.