Search Results opi_dbi_inv_cpcs_pkg




Overview
Explore in AI Chat

Overview

OPI_DBI_INV_CPCS_PKG is a PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER, meaning its database objects are resolved against the privileges of the invoking user rather than the package owner. It belongs to the Oracle Process Manufacturing (OPM) / Discrete Intelligence (DBI) inventory reporting family, which supplies the Oracle E-Business Suite Inventory Intelligence (formerly Daily Business Intelligence for Inventory) dashboards and period-close analytics. Its core business function is to compute and persist period-close inventory adjustments and the summary values that feed the Inventory Intelligence period-close reporting layer. The package header carries a version marker dated 2004, indicating it is an early-generation DBI component that has been retained for backward compatibility in the 12.1.1 and 12.2.2 application releases. Within the ETRM documentation it is classified as OTHER rather than as a public API, reflecting that it is intended primarily for internal invocation by concurrent programs rather than by third-party integrations.

Key Procedures and Functions

The documented interface exposes a single procedure, RUN_PERIOD_CLOSE_ADJUSTMENT. Its purpose is to execute the period-close adjustment calculation for the inventory organization context in which it is called, reconciling staged transactional data against the period-close summary tables and writing the resulting adjustment and log records. Because the ETRM metadata presents only the procedure name and not its parameter list, no parameters are asserted here beyond what the source header shows: the procedure follows the standard concurrent-program entry-point convention, accepting errbuf and retcode as NOCOPY IN OUT VARCHAR2 parameters so that it can be registered directly as a concurrent executable and report success, warning, or error status back to the Concurrent Manager. It performs no user-facing dialogue and returns all results through its outbound status parameters and through the database tables it populates.

Tables Accessed

The package reads and writes a well-defined set of APPS synonyms. It reads MTL_MATERIAL_TRANSACTIONS, MTL_SYSTEM_ITEMS_B, and MTL_PARAMETERS for transactional, item-master, and organization-level inventory context. ORG_ACCT_PERIODS supplies the open/closed status and date boundaries of the accounting period being processed, while CST_PERIOD_CLOSE_SUMMARY holds the period-close summary figures that the adjustment reconciles against. The DBI-specific staging and value tables are central: OPI_DBI_INTRANSIT_STG and OPI_DBI_ONHAND_STG hold staged in-transit and on-hand quantities; OPI_DBI_INV_VALUE_F stores the inventory value fact records; OPI_DBI_INV_VALUE_LOG records valuation history; and OPI_DBI_CONVERSION_RATES provides currency conversion factors applied to the reported values. OPI_DBI_CONC_PROG_RUN_LOG captures the concurrent program run audit trail, and DUAL is used for singleton scalar evaluation. Together these tables support the extract, stage, value, and summarize cycle that produces the period-close adjustment.

Usage Notes

The procedure is intended to be invoked as a concurrent program submitted from the Inventory Intelligence responsibility or scheduled by the Concurrent Manager at period close. The presence of OPI_DBI_CONC_PROG_RUN_LOG among the referenced tables confirms that the package logs its own runs and is designed for unattended batch execution. Because the package is referenced by two other packages, it may also be called programmatically from within the DBI inventory processing chain; however, direct custom invocation is not recommended, since the procedure is undocumented as a public API, has no declared exception contract in the metadata, and depends on the caller supplying a valid organization and period context. Customizations should treat it as an internal component and integrate with the supported DBI concurrent programs instead. As with all DBI inventory logic, results depend on the staging tables being populated by the preceding extract steps, so the package should be run only after the upstream DBI data load has completed successfully.