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
RESOURCE_ID— surrogate primary key of the resource; the correct foreign key for joins to bills, routings, and resource cost tables.RESOURCE_CODE,DESCRIPTION,UNIT_OF_MEASURE— the identifying and UOM attributes used in LOV displays and reports.ORGANIZATION_ID— the owning inventory/manufacturing organization; essential for org-scoped filtering.COST_ELEMENT_ID,COST_CODE_TYPE,STANDARD_RATE_FLAG,DEFAULT_BASIS_TYPE— costing and rate-definition attributes.FUNCTIONAL_CURRENCY_FLAG— indicates whether the resource's rate is expressed in the ledger's functional currency; central to resource-rate and cost-rollup interpretation, and the column referenced by the search term.DISABLE_DATE— drives the view's active-only filter.DEFAULT_ACTIVITY_ID,RESOURCE_TYPE,AUTOCHARGE_TYPE,ALLOW_COSTS_FLAG— routing and cost-charging behavior controls.ABSORPTION_ACCOUNT,RATE_VARIANCE_ACCOUNT,EXPENDITURE_TYPE— accounting and Oracle Projects integration attributes.ATTRIBUTE_CATEGORYthroughATTRIBUTE15— the descriptive flexfield segment columns.BATCHABLE,MIN_BATCH_CAPACITY,MAX_BATCH_CAPACITY,BATCH_CAPACITY_UOM,BATCH_WINDOW,BATCH_WINDOW_UOM— process-manufacturing batch attributes.COMPETENCE_ID,RATING_LEVEL_ID,QUALIFICATION_TYPE_ID— resource qualification references.PURCHASE_ITEM_ID,BILLABLE_ITEM_ID,SUPPLY_SUBINVENTORY,SUPPLY_LOCATOR_ID— procurement and supply sourcing columns.LAST_UPDATE_DATE,CREATION_DATE, and audit columns — standard WHO/audit tracking;REQUEST_ID,PROGRAM_APPLICATION_ID,PROGRAM_ID,PROGRAM_UPDATE_DATEidentify the concurrent program that last touched the row.
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.
-
View: BOM_RESOURCES_VAL_V 12.2.2
View for resource list of values - only enabled records
APPS.BOM_RESOURCES_VAL_V·↳ BOM_RESOURCES·Explore BOM module →
-
View: BOM_RESOURCES_VAL_V 12.1.1
View for resource list of values - only enabled records
APPS.BOM_RESOURCES_VAL_V·↳ BOM_RESOURCES·Explore BOM module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.BOM_RESOURCES 12.2.2
-
SYNONYM: APPS.BOM_RESOURCES 12.1.1
-
PACKAGE BODY: APPS.QA_SS_LOV 12.2.2
-
PACKAGE: APPS.QA_SS_LOV 12.1.1
-
PACKAGE: APPS.QA_SS_LOV 12.2.2
-
PACKAGE BODY: APPS.QA_SS_LOV 12.1.1
-
APPS.QLTTRAWB SQL Statements 12.1.1
-
APPS.QLTTRAWB SQL Statements 12.2.2
-
PACKAGE BODY: APPS.QA_SS_LOV 12.2.2
-
PACKAGE BODY: APPS.QA_SS_LOV 12.1.1
-
PACKAGE BODY: APPS.QLTTRAWB 12.1.1
-
PACKAGE BODY: APPS.QLTTRAWB 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.