Search Results create_perf_measures

Overview

OKI_LOAD_OKV_PUB is a public PL/SQL package in the Oracle E-Business Suite APPS schema that supports the Oracle Knowledge Information (OKI) / Order Capture performance measurement infrastructure. Its documented role is to expose a programmatic entry point for creating performance measures records — the aggregated metrics used by Oracle Order Management and related OKI-based reporting to evaluate order capture effectiveness, cycle times, and fulfillment performance. The package body is a thin public wrapper: it accepts concurrent-program style inputs, normalizes the date parameter, and delegates the substantive processing to the private package OKI_LOAD_OKV_PVT. This separation follows Oracle's standard PUB/PVT convention, in which the public package defines the stable interface consumed by concurrent programs and external callers, while the private package encapsulates the implementation logic. Version history visible in the header indicates a NOCOPY refactoring dated 26-NOV-2002, consistent with the package's long-standing presence across the 11i, 12.1.1, and 12.2.2 release lines.

Key Procedures and Functions

The package body documents a single public procedure, CREATE_PERF_MEASURES. It is the only procedure exposed by OKI_LOAD_OKV_PUB, and it acts as the orchestration entry point for a performance-measure creation run.

• CREATE_PERF_MEASURES — Creates all performance measures records for the specified reporting period. It conforms to the Oracle concurrent program interface by returning the standard X_ERRBUF and X_RETCODE out parameters, allowing it to be registered and executed as a concurrent executable. Two inbound parameters identify the reporting calendar context: the period set name and the period type. A third inbound parameter, the summary build date, is supplied as a character string and is converted to a DATE using FND_CONC_DATE.STRING_TO_DATE before use. The converted value represents the effective date of the job run and is treated as the "current date" for bin calculations such as aging reports. After conversion, the procedure calls OKI_LOAD_OKV_PVT.CREATE_PERF_MEASURES, passing all parameters through unchanged apart from the date conversion, and returns the private package's error buffer and completion code to the caller.

Tables Accessed

The provided metadata does not enumerate the base tables referenced by OKI_LOAD_OKV_PUB, because the public package performs no direct DML — all data access is delegated to OKI_LOAD_OKV_PVT. Based on the OKI performance-measurement data model, the private implementation populates temporary or staging structures and then loads the performance measures repository, which in the OKI schema comprises the performance measure definition and value tables. The period set name and period type parameters drive lookups against the FND calendar tables (FND_PERIOD_SETS and FND_PERIOD_TYPES) to resolve the accounting or reporting period against which measures are calculated, while the summary build date governs the aging bins applied to outstanding order and fulfillment data. Report generation subsequently reads these populated measures to produce the performance dashboards and aging analyses.

Usage Notes

CREATE_PERF_MEASURES is designed for concurrent program invocation. It is typically registered as a Hosted or PL/SQL concurrent executable, with the period set name, period type, and summary build date supplied as run-time parameters and a value set attached to the date parameter to enforce valid input. The character-based date parameter means callers must format the build date according to the FND_CONC_DATE conversion conventions; submitting an unparseable string will fail during the conversion step before any processing occurs. Because the procedure is a public API, custom code may invoke it directly from a PL/SQL block, but doing so requires explicit handling of the X_ERRBUF and X_RETCODE outputs, since the procedure does not raise exceptions for business-level failures. The package is documented as referenced by zero other packages, confirming it is a terminal entry point rather than a shared library. Any error raised by the private package propagates through the public wrapper unchanged, so diagnostics should be read from the returned error buffer. Organizations upgrading between 12.1.1 and 12.2.2 should expect the interface to remain stable, given its NOCOPY-based signature and mature header revision.