Search Results g_program_update_date

Overview

OKI_LOAD_ETR_PVT is a private (PVT-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite, operating within the Oracle Knowledgebase Integration (OKI) module — specifically the Oracle Contracts/Order Management expiration-to-renewal processing area. The package header carries the RCS identifier OKIRETRS.pls 115.4, dated 01-DEC-2002, confirming its lineage in the EBS 11i codebase carried forward into 12.1.1 and 12.2.2. The stated purpose of the package is to load the OKI_EXP_TO_RNWL table — the expiration-to-renewal staging table — with records derived from the active summary/transaction data maintained by the module.

The package is intended exclusively for internal consumption; the _PVT suffix indicates that it is not part of the public API surface exposed to customers or integrators. Public access is instead provided through companion packages that are documented as referencing this one. The header is declared AUTHID CURRENT_USER, so all SQL statements execute with the privileges of the invoking APPS session rather than those of the package owner, a standard pattern for APPS-resident packages accessing data through APPS synonyms.

Key Procedures and Functions

The documented interface exposes a single procedure:

• CRT_EXP_TO_RNWL — Creates the expiration-to-renewal records. This is the sole entry point in the package and is responsible for populating the expiration-to-renewal table for a given processing window. Its parameter list is not reproduced here because the metadata excerpt documents only the signature names, not the semantic contract; the presence of date-range parameters indicates the procedure processes a bounded set of summary builds rather than the entire dataset at once. The procedure follows the standard concurrent-program callback convention of returning error buffer and return code OUT parameters (declared NOCOPY, a change logged in the 26-NOV-2002 revision by rpotnuru).

No functions, secondary procedures, or overloads are documented in the package specification.

Tables Accessed

The package declares global variables based on the OKI_REFRESHS table, binding the concurrent request context (request ID, program application ID, program ID, and program update date) for the job run being logged. Notably, the identifier the user searched for — g_program_update_date — is a package-level global anchored to oki.oki_refreshs.PROGRAM_UPDATE_DATE%TYPE. It captures the FND concurrent program update timestamp for the executing job, allowing records written by the load to be reconciled to the precise program version and run that produced them. In EBS 12.1.1 and 12.2.2 this anchoring pattern ensures the global inherits any change in the underlying column definition.

Two application tables are documented as referenced through APPS synonyms:

• OKI_EXP_TO_RNWL — the expiration-to-renewal table that the package's purpose statement identifies as the load target. Records created by CRT_EXP_TO_RNWL are written here for downstream renewal processing.
• OKI_SALES_K_HDRS — the sales header knowledge/interface table supplying source header data used to derive the expiration-to-renewal rows.

Usage Notes

Because the package is classified PVT and the header states its purpose as loading a staging table, it is not expected to be invoked directly from an Oracle Forms screen. Its natural invocation path is a concurrent program registered in FND for the OKI module, which supplies the request ID, program application ID, program ID, and program update date logged by the package globals. The procedure's OUT parameters (error buffer and return code) match the concurrent manager's standard submission contract, and the NOCOPY declaration was introduced specifically to reduce overhead when the concurrent manager passes large buffers.

Custom development should call the public wrapper package rather than OKI_LOAD_ETR_PVT directly, since private packages are subject to unannounced change in EBS patches and the 12.1.1-to-12.2.2 upgrade path. The 2002-era source header further indicates the package has been stable for the life of the 11i and 12.x releases; any custom code referencing g_program_update_date should be reviewed for reliance on a private global that Oracle does not guarantee.