Results for “bombv_mfg_resources”

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

Overview

The view APPS.BOMBV_MFG_RESOURCES is a reporting and integration object within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema and flagged as VALID. It is a Bills of Material (BOM) product construct whose documented description designates it as "- Retrofitted," indicating it was re-established during the 12.x release and consolidated upgrade cycle rather than designed as a net-new object. The view presents a denormalized, business-user-oriented projection of manufacturing resource definitions, joining each resource record to organization-level descriptive data so that resource information can be consumed without requiring callers to perform multi-table joins themselves.

Functionally, the view exposes manufacturing resource master data — including resource codes, descriptions, unit of measure, cost-related attributes, and account relationships — alongside the organization context in which each resource is defined. A notable characteristic of the view text is its heavy reliance on Oracle EBS descriptive-flexfield and lookup token syntax (for example _LA:RE.AUTOCHARGE_TYPE:MFG_LOOKUPS:BOM_AUTOCHARGE_TYPE:MEANING and _LA:RE.RESOURCE_TYPE:MFG_LOOKUPS:BOM_RESOURCE_TYPE:MEANING). These tokens are resolved at runtime by the EBS lookup/attribute translation layer, allowing the view to return human-readable lookup meanings in place of stored codes. The view is additionally defined WITH READ ONLY, making it strictly a read-only reporting surface.

Underlying Base Objects

The ETRM 12.2.2 metadata documents three referenced base objects, all consumed through synonyms: BOM_RESOURCES, HR_ALL_ORGANIZATION_UNITS, and MTL_PARAMETERS. The primary driving table is BOM_RESOURCES (aliased RE), which supplies the resource-level attributes and identifiers. Joins to MTL_PARAMETERS (PA) and HR_ALL_ORGANIZATION_UNITS (AL) both occur on ORGANIZATION_ID, enriching each resource row with the organization code and organization name. A mandatory security predicate, '_SEC:RE.ORGANIZATION_ID' IS NOT NULL, enforces multi-org access control, so the view returns only the resources for organizations the querying responsibility is permitted to see.

Key Columns

• RESOURCE_CODE, DESCRIPTION, UNIT_OF_MEASURE — Core identifying attributes of the manufacturing resource.
• ORGANIZATION_CODE, ORGANIZATION_NAME — The owning inventory/organization context derived from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• INACTIVE_DATE — Sourced from RE.DISABLE_DATE; indicates when the resource is no longer active.
• PURCHASE_ITEM_ID — Ties the resource to the MTL_SYSTEM_ITEMS item used when the resource is procured; this is the column users searching "purchase_item_id" most commonly target.
• RESOURCE_ID, ORGANIZATION_ID — Primary and organization keys used to join back to base tables.
• COST_ELEMENT_ID, DEFAULT_ACTIVITY_ID — Costing element and default activity associations.
• ABSORPTION_ACCOUNT, RATE_VARIANCE_ACCOUNT, EXPENDITURE_TYPE — Accounting and costing attributes.
• Lookup-translated columns (_LA:AUTOCHARGE_TYPE, _LA:COST_CODE_TYPE, _LA:DEFAULT_BASIS_TYPE, _LA:FUNCTIONAL_CURRENCY_FLAG, _LA:ALLOW_COSTS_FLAG, _LA:STANDARD_RATE_FLAG, _LA:RESOURCE_TYPE) — Return display meanings for coded flags.
• UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — Audit columns remapped from LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY.

Common Use Cases and Queries

The view is typically used for resource master reporting, integration extracts, and resolving a resource's associated purchasing item. A representative query retrieving resources linked to a purchase item follows:

SELECT resource_code,
       organization_code,
       organization_name,
       purchase_item_id,
       unit_of_measure,
       inactive_date
FROM   apps.bombv_mfg_resources
WHERE  purchase_item_id = :p_purchase_item_id
AND    inactive_date IS NULL;

Analysts also use it to enumerate active, costable resources per organization or to feed downstream costing and procurement reconciliations, relying on the built-in security and lookup translations to deliver responsibility-appropriate, presentation-ready output.