Search Results oki_load_rag_pvt




Overview
Explore in AI Chat

Overview

OKI_LOAD_RAG_PVT is a private PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Order Capture and Contracts (OKI/OKC) renewal and service forecasting functionality. Its stated purpose, taken directly from the package header, is to load the OKI_RENEWAL_AGING table. The package is therefore a data-population engine for renewal aging and forecast information rather than a user-facing API. It is classified as a PVT (private) package, meaning it is not intended for direct external calls and is instead wrapped by a corresponding public package within the OKI modules.

The package header, dated 2001 with a 2002 NOCOPY revision by rpotnuru, declares AUTHID CURRENT_USER, so it executes with the privileges of the invoking session (typically APPS) and resolves unqualified objects through the APPS synonym layer. The extensive inline documentation describes an aggregation-oriented algorithm: for each distinct customer, organization, and subclass code in OKI_SALES_K_HDRS, and for each valid period returned from GL_PERIODS, the package calculates aging bucket ranges, computes forecast amounts, and then determines whether a given OKI_RENEWAL_AGING record should be inserted or updated. The same logic is repeated at customer/organization granularity and again at organization-only granularity, producing a layered set of aging and forecast rows.

Key Procedures and Functions

  • CRT_RNWL_AGING — the single documented procedure and the core engine of the package. Its responsibility is to create the forecast renewal aging records. It derives aging bucket boundaries from the valid GL periods, calculates forecast amounts for the relevant customer, organization, and subclass combinations, and performs the insert-or-update decision against OKI_RENEWAL_AGING. Following completion, the procedure (or its caller) updates OKI_REFRESHS with concurrent manager run statistics such as request ID, program application ID, program ID, and program update date.

No additional public functions or procedures are documented for this package. The global variables g_request_id, g_program_application_id, g_program_id, and g_program_update_date are declared using anchored types from OKI_REFRESHS and are used exclusively to log the concurrent program execution context.

Tables Accessed

  • OKI_SALES_K_HDRS — read as the primary source of contract/renewal header data; the package iterates its distinct customer, organization, and subclass combinations to drive the forecast calculations.
  • GL_PERIODS — read to obtain the valid accounting periods used to define the aging bucket ranges and forecast period windows.
  • OKI_RENEWAL_AGING — the principal target table; the procedure inserts or updates rows here to store the computed aging and forecast amounts.
  • OKI_RENEWAL_AGING_S1 — referenced in conjunction with the aging table, supporting the insert/update determination logic associated with the aging records.
  • DUAL — used for single-row computations and utility operations.

In addition, the package references the OKI_REFRESHS table in its global variable declarations to capture concurrent manager statistics for the job run.

Usage Notes

Because OKI_LOAD_RAG_PVT is a PVT package, it should not be invoked directly from forms or from custom application code. It is designed to be called by a public OKI package or by a concurrent program that orchestrates the renewal aging load. The metadata confirms that the package is referenced by one other package, which is the intended entry point for external callers. The concurrent manager context captured through the OKI_REFRESHS globals indicates that this logic is normally scheduled as a batch concurrent request rather than being triggered interactively.

Implementers extending or debugging renewal forecasting in EBS 12.1.1 or 12.2.2 should treat OKI_LOAD_RAG_PVT as an internal implementation detail of the renewal aging load process. Any customization should target the calling public API or the concurrent program definition, since the private package signature is not part of the supported public interface and may change between releases.