Search Results extract_baseline

Overview

OPI_DBI_PTP_BASELINE_PKG is an Oracle Application Object Library (AOL) PL/SQL package owned by the APPS schema. It belongs to the Oracle Daily Business Intelligence (DBI) product family, specifically the Process Manufacturing / Profitability-to-Plan (PTP) analytics domain. In EBS 12.1.1 and 12.2.2, the package is deployed with the AUTHID CURRENT_USER clause, meaning its database objects resolve against the privileges of the invoking user rather than the package owner. The package is classified as OTHER in the ETRM API classification, indicating it is not a public open interface or business API, but an internal engine used to build and refresh the baseline data structures consumed by DBI dashboards and PTP reporting. Its purpose is to extract EBS operational data into the baseline staging/summary tables that support historical comparison and plan-versus-actual analysis.

Key Procedures and Functions

• EXTRACT_BASELINE — The principal entry point of this package and the object most commonly associated with the search term "extract_baseline". This procedure extracts source data from the EBS transactional and setup tables and populates the DBI baseline tables. It accepts the standard concurrent-program error and return-code parameters, which it uses to signal completion status back to the concurrent manager.
• REFRESH — Drives the refresh cycle for the baseline data set, regenerating and reconciling materialized views and related summarized structures. It also uses the standard error and return-code parameters for concurrent program status reporting.

No functions are documented; the package exposes only these two PL/SQL procedures. The metadata does not publish detailed parameter lists for either procedure beyond the standard concurrent program signature (errbuf / retcode).

Tables Accessed

The package reads and writes a broad set of DBI and EBS base tables, resolved through APPS synonyms:

• Source/operational tables: MTL_PARAMETERS, HR_ORGANIZATION_INFORMATION, and FII_TIME_DAY supply organization, inventory, and calendar/period context.
• DBI setup and plan tables: ISC_DBI_PLANS, ISC_DBI_PLAN_ORGANIZATIONS, OPI_DBI_BASELINE_DEFINITIONS, OPI_DBI_BASELINE_PLANS, and OPI_DBI_BASELINE_SCHEDULES define what baselines are extracted and which organizations and periods they cover.
• DBI fact/working tables: OPI_DBI_PTP_CONV, OPI_DBI_PTP_COST, OPI_DBI_PTP_PLAN_F, OPI_DBI_RUN_LOG_CURR, and OPI_DBI_PTP_LOG hold conversion factors, cost data, plan facts, and run logging/audit records.
• Utilities: DBMS_MVIEW and DBMS_SQL are invoked at runtime to refresh materialized views and execute dynamic SQL.

Usage Notes

OPI_DBI_PTP_BASELINE_PKG is an internal DBI engine and is not intended for direct invocation by custom code. It is typically invoked by concurrent programs registered in the DBI/PTP concurrent manager, which pass the standard errbuf and retcode parameters. Because the package runs AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying APPS synonyms. No other packages are documented as referencing it, so its primary consumers are the concurrent program definitions and dashboard refresh logic in the Oracle Process Manufacturing DBI module. As with all APPS-owned DBI packages, modifications or direct calls should be avoided; use supported DBI configuration and concurrent program scheduling instead.