Search Results initial_opm_res_actual

Overview

APPS.OPI_DBI_RES_OPM_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, declared with AUTHID CURRENT_USER. It belongs to the Oracle Process Manufacturing (OPM) resource intelligence layer that feeds the Daily Business Intelligence (DBI) and related reporting/collection infrastructure for process manufacturing. Its purpose is to extract, stage, and maintain resource-related transactional and availability data from the OPM and Oracle Manufacturing schemas so that downstream reporting, dashboards, and analytical summaries reflect current resource consumption, availability, and standard values.

The package header dates to 2003 and carries a "noship" designation in its source header, indicating it is an internal, non-shipped component. Its procedures are organized around two collection modes — initial (full) and incremental (delta) — and three subject areas: actual resource consumption, resource availability, and resource standards. This design is typical of DBI collection programs, which distinguish an initial population load from recurring incremental refreshes.

Key Procedures and Functions

The documented callable units (8 total) are:

• CHECK_SETUP_GLOBALS — Validates prerequisite configuration and global setup required before resource collection can proceed. It follows the standard concurrent program signature convention with errbuf and retcode, allowing it to report failure cleanly to the concurrent manager. The user search term "check_setup_globals" refers directly to this procedure.
• INITIAL_OPM_RES_ACTUAL — Performs the initial (full) load of actual resource transaction data. Again uses the errbuf/retcode convention.
• INITIAL_OPM_RES_AVAIL — Performs the initial load of resource availability data.
• INITIAL_OPM_RES_STD — Performs the initial load of resource standard data; uniquely, this procedure accepts an additional p_degree parameter (a NUMBER), typically used to control parallelism/degree of processing.
• INCREMENTAL_OPM_RES_ACTUAL — Refreshes only new or changed actual resource data since the last run.
• INCREMENTAL_OPM_RES_AVAIL — Refreshes incremental resource availability data.
• INCREMENTAL_OPM_RES_STD — Refreshes incremental resource standard data.
• PUT_LINE — Referenced in the header as a commented-out debug/logging helper (declaration commented out at line 6).

Tables Accessed

The package reads and stages data across OPM, costing, inventory, and calendar tables, accessed through APPS synonyms:

• Resource and routing masters: CR_RSRC_MST_B, CR_RSRC_DTL, CM_RSRC_DTL — resource definitions, details, and standard rates.
• Resource transactions and availability: GME_RESOURCE_TXNS, GMP_RESOURCE_AVAIL — actual resource consumption and availability windows.
• Batch and step execution: GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_RESOURCES, GME_MATERIAL_DETAILS — the batch context linking resources to production activity.
• Calendar and policy: CM_CLDR_HDR_B, CM_CLDR_DTL, GL_PLCY_MST — production calendars and policy/costing definitions.
• Inventory and warehouse: IC_ITEM_MST_B, IC_WHSE_MST, MTL_SYSTEM_ITEMS_B — item and warehouse master data used to resolve resource-to-item/warehouse joins.

Usage Notes

OPI_DBI_RES_OPM_PKG is invoked primarily by OPM/DBI collection concurrent programs. CHECK_SETUP_GLOBALS is typically executed first as a pre-requisite validation step; if it returns a failure retcode, the collection is aborted with a meaningful message in errbuf. The INITIAL_* procedures are run once during initial implementation or after a full data reset, while the INCREMENTAL_* procedures are scheduled on a recurring basis (daily or intra-day). INITIAL_OPM_RES_STD can be run with a degree for parallel processing on large volumes. The package is not referenced by other packages (0 dependents), so it is a top-level collection entry point rather than a shared utility, and custom code should call it only via the standard concurrent program interface.