Search Results crt_rnwl_aging

Overview

The OKI_LOAD_RAG_PUB package body is a public API layer within the Oracle E-Business Suite (EBS) Order Management / Oracle Knowledge Integration (OKI) schema owned by APPS. Its principal business function is to generate renewal aging records — the underlying data set used to classify and report on the age of service, subscription, or support renewal contracts relative to a reference (build) date. In ETRM terminology, the aging calculation bins renewal line items according to how many periods (days, months, or accounting periods) have elapsed since an effective date, which directly supports renewal pipeline analysis and forecasting.

The package follows the standard Oracle PL/SQL layered architecture: a thin public (PUB) wrapper composes and validates inputs, then delegates the substantive processing to a private package, OKI_LOAD_RAG_PVT. This separation allows the private package to be modified without altering the public contract consumed by concurrent programs and external callers.

Key Procedures and Functions

The documented package exposes a single public procedure:

• CRT_RNWL_AGING — Standard concurrent-program entry point that creates all renewal aging records. Its responsibilities include:
  • Accepting the reporting context via input parameters: the accounting period set name (p_period_set_name), the period type (p_period_type), and the summary build date (p_summary_build_date supplied as a VARCHAR2 character date).
  • Returning the standard concurrent manager OUT parameters x_errbuf and x_retcode for error and completion-status reporting.
  • Converting the character-form build date to a true DATE data type using FND_CONC_DATE.STRING_TO_DATE. This converted value becomes the effective "current date" for all bin and aging calculations.
  • Invoking OKI_LOAD_RAG_PVT.CRT_RNWL_AGING, passing the period set name, period type, and the converted build date, along with the error buffer and return code, to perform the actual record creation.

The use of NOCOPY on the OUT parameters reflects a performance optimization introduced in the 26-NOV-2002 revision (version 115.4), avoiding unnecessary parameter copying for potentially large values.

Tables Accessed

The package metadata does not document direct table references through APPS synonyms for the public layer. This is expected: OKI_LOAD_RAG_PUB is a pure delegation wrapper and performs no direct DML. All INSERT, UPDATE, and SELECT operations against the renewal aging staging and result tables occur inside OKI_LOAD_RAG_PVT. Consequently, the tables read and written by this package family are not exposed through the public body and should be traced in the private package definition.

Usage Notes

OKI_LOAD_RAG_PUB.CRT_RNWL_AGING is designed to be registered as an Oracle EBS concurrent program. The three IN parameters correspond to concurrent program parameters, and the two OUT parameters align with the standard x_errbuf/x_retcode convention required by the concurrent manager. Typical invocations include:

• Scheduled or on-demand submission of a concurrent program that populates renewal aging data for reporting.
• Direct calls from custom PL/SQL or other packages that require programmatic regeneration of renewal aging records.
• Invocation following period-close or pipeline-refresh processes, using the appropriate p_summary_build_date to anchor the aging bins.

Callers must supply a valid period set name and period type recognized by the General Ledger calendar, since the private logic depends on these to resolve period boundaries. Because the public package holds no business logic beyond date conversion and delegation, troubleshooting should focus on OKI_LOAD_RAG_PVT and on the validity of the concurrent program parameters.