Search Results edw_bres_resgroup_lcv




Overview
Explore in AI Chat

Overview

The EDW_BRES_RESGROUP_LCV view is a reporting and integration object within the Oracle E-Business Suite Engineering (ENG) module, exposed through the Enterprise Data Warehouse (EDW) layer. Its purpose is to present a consolidated, single-source listing of resource group information that spans two distinct Oracle product families: discrete/engineered manufacturing (Bills of Resources and Engineering) and Oracle Process Manufacturing (OPM). The view is designated as an "LCV" (Lightweight Collection View), a naming convention frequently used in EDW extraction routines to flatten and standardize descriptive flexfield-style lookup data into a uniform shape for downstream consumption.

The view's metadata confirms it "holds resource group information." It is documented as not implemented in this database in the source ETRM metadata, meaning it exists as a definition artifact for EDW and reporting purposes rather than as a installed, populated runtime object in the reference environment. It is defined WITH READ ONLY, indicating that it is intended strictly for query access and cannot be used to modify underlying data. The view is relevant to the user search term cr_rsrc_cls, since it directly references that table in its OPM branch.

Underlying Base Objects

Although the ETRM column for "Referenced base objects" is documented as none, the view text reveals the objects over which it is constructed:

  • FND_COMMON_LOOKUPS — queried with the alias RG and filtered by LOOKUP_TYPE = 'CRP_RESOURCE_GROUPS'. This supplies resource group definitions maintained as common lookup codes.
  • CR_RSRC_CLS — the OPM resource class table, aliased RC, supplying OPM resource class descriptions. This is the object matching the user's search term.
  • EDW_LOCAL_INSTANCE — aliased INST, joined in both branches to attach an instance code, enabling multi-instance and multi-org consolidation.

The definition is a UNION ALL: the first branch returns lookup-based resource groups, while the second returns OPM resource classes, concatenating RESOURCE_CLASS with the instance code and the literal suffix -OPM. This union produces a unified key space across both manufacturing paradigms.

Key Columns

  • RESOURCE_GROUP_PK — the resource group identifier; in the first branch derived from RG.LOOKUP_CODE, and in the OPM branch from the concatenated RESOURCE_CLASS-INSTANCE-OPM string.
  • INSTANCE — the EDW instance code (INST.INSTANCE_CODE), used to distinguish source instances.
  • ALL_FK — a literal 'ALL' value, acting as a constant foreign key for aggregation and "all values" reporting.
  • RESOURCE_GROUP_DP, NAME, RESOURCE_GROUP — descriptive attributes; the first three map to RG.MEANING or RC.RESOURCE_CLASS_DESC, providing display names.
  • DESCRIPTION — longer descriptive text from RG.DESCRIPTION or the OPM resource class description.
  • LAST_UPDATE_DATE / CREATION_DATE — audit timestamps from the source records.
  • OPERATION_CODE and USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — extended attributes; in the documented view text these are populated as NULL, reserved for future EDW enrichment.

Common Use Cases and Queries

Typical scenarios include building EDW extract mappings, cross-referencing resource groups between discrete and process manufacturing, and validating lookup configuration prior to data loading.

  • Listing all resource groups for a given instance:
    SELECT RESOURCE_GROUP_PK, NAME, DESCRIPTION FROM EDW_BRES_RESGROUP_LCV WHERE INSTANCE = :instance_code;
  • Isolating OPM-sourced resource classes:
    SELECT * FROM EDW_BRES_RESGROUP_LCV WHERE RESOURCE_GROUP_PK LIKE '%-OPM';
  • Searching for entries originating from CR_RSRC_CLS by keyword:
    SELECT RESOURCE_GROUP, INSTANCE FROM EDW_BRES_RESGROUP_LCV WHERE RESOURCE_GROUP LIKE '%CLASS%';

Because the view is read-only and defined over lookup and OPM class tables, it is best used as a conformed dimension source rather than a transactional query target.