Search Results edw_bres_dept_class_lstg

Overview

EDW_BOM_RES_M_C is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It forms part of the Enterprise Data Warehouse (EDW) collection layer that supports Oracle Business Intelligence and related reporting products delivered with EBS 12.1.1 and 12.2.2. Its business function is to extract, transform, and load Bill of Materials (BOM) resource and department reference data from the operational EBS tables into the staging structures consumed by the EDW repository.

The package is classified as OTHER rather than as a public or private API, confirming that it is an internal collection utility rather than a supported integration interface. The "M" suffix denotes the main or master collection driver, and the "_C" suffix denotes a collection package. The object is reported as VALID in the ETRM metadata for release 12.1.1, and the documented dependency list shows it relies on collection utility routines (EDW_COLLECTION_UTIL), logging (EDW_LOG), and message resolution (FND_MESSAGE), which are standard components of the EDW framework.

Key Procedures and Functions

The package exposes ten documented procedures, each responsible for populating a specific EDW staging table:

• PUSH — The main driver procedure. It orchestrates invocation of the individual PUSH_* routines in the correct sequence and manages the overall collection cycle.
• PUSH_EDW_BRES_PLANT — Collects plant/organization reference data into the plant staging table.
• PUSH_EDW_BRES_PLANT1 — Handles a secondary plant collection path, populating the PLANT1 staging table.
• PUSH_EDW_BRES_RESOURCE — Extracts individual BOM resource records.
• PUSH_EDW_BRES_RESGROUP — Extracts resource group definitions.
• PUSH_EDW_BRES_RESTYPE — Extracts resource type classifications.
• PUSH_EDW_BRES_RESCAT — Extracts resource category definitions.
• PUSH_EDW_BRES_PARENT_DEPT — Extracts parent department relationships.
• PUSH_EDW_BRES_DEPT — Extracts department records.
• PUSH_EDW_BRES_DEPT_CLASS — Extracts department class definitions.

Parameter lists are not published in the ETRM metadata and should not be assumed; callers should treat each routine as an internal collection step rather than a callable API.

Tables Accessed

The package writes to nine staging tables referenced through APPS synonyms: EDW_BRES_DEPT_CLASS_LSTG, EDW_BRES_DEPT_LSTG, EDW_BRES_PARENT_DEPT_LSTG, EDW_BRES_PLANT1_LSTG, EDW_BRES_PLANT_LSTG, EDW_BRES_RESCAT_LSTG, EDW_BRES_RESGROUP_LSTG, EDW_BRES_RESOURCE_LSTG, and EDW_BRES_RESTYPE_LSTG. The "_LSTG" suffix indicates load staging, so these are transient collection targets.

The package also references corresponding "_LCV" collection views (EDW_BRES_DEPT_CLASS_LCV, EDW_BRES_DEPT_LCV, EDW_BRES_PLANT_LCV, EDW_BRES_RESCAT_LCV, EDW_BRES_RESGROUP_LCV, EDW_BRES_RESOURCE_LCV, and EDW_BRES_RESTYPE_LCV), which present the source EBS data in the normalized form required by the EDW model. Source data originates from the BOM resource and department tables in Oracle Manufacturing.

Usage Notes

EDW_BOM_RES_M_C is not referenced by any other database object, confirming it is a terminal collection program invoked directly rather than called by dependent code. It is normally executed as part of an EDW collections request set or through a concurrent program during a full or incremental data warehouse load, commonly on a nightly or periodic schedule. Because it is an internal object, it should not be invoked from custom forms or bespoke code; applications requiring BOM resource or department data for analytics should query the populated EDW staging or target tables instead. The user search term edw_bres_dept_class_lstg corresponds directly to the staging table populated by PUSH_EDW_BRES_DEPT_CLASS, which is the authoritative target for department class data within this package.