Search Results okc_rep_exp_ntf_pvt




Overview
Explore in AI Chat

Overview

OKC_REP_EXP_NTF_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Contracts (OKC) reporting infrastructure, specifically the contract repository reporting sub-system built around the OKC_REP_* table family. The package name decomposes into its constituent functional elements: OKC (Oracle Contracts), REP (repository reporting), EXP (expiration), and NTF (notification). Its role is therefore to handle the notification and management logic associated with contract expiration within the contracts repository reporting framework.

As a package classified with an API type of PVT, OKC_REP_EXP_NTF_PVT is a private implementation package rather than a published, supported public API. Private packages in EBS are internal building blocks intended to be invoked by other packages within the same functional family, not by customer extensions. The package is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2, with its only external dependency being the SYS.STANDARD package, indicating that it relies primarily on standard PL/SQL constructs and on the OKC_REP_* tables through APPS synonyms.

Key Procedures and Functions

The documented package exposes two procedures or functions:

  • CONTRACT_EXPIRATION_NOTIFIER — This program unit is responsible for the notification aspect of contract expiration. Its purpose is to raise or dispatch expiration notifications, typically evaluating contracts that are approaching or have reached their expiration date and communicating the relevant status to the appropriate recipients or workflow processes.
  • CONTRACT_EXPIRATION_MANAGER — This program unit manages the expiration lifecycle for contracts held in the repository. It coordinates the handling of expired or expiring contracts, likely invoking the notifier logic and applying the appropriate state transitions or follow-up actions required by the contracts reporting model.

The two units operate as a complementary pair: the manager governs the overall expiration process, while the notifier handles the outbound communication element. Their precise signatures are not reproduced in the available metadata, and they should not be assumed to be publicly callable.

Tables Accessed

The package references two documented tables through APPS synonyms:

  • OKC_REP_CONTRACTS_ALL — The contracts repository header table. The package reads contract records from this table to identify expiring or expired contracts, and may update status or expiration-related attributes depending on the outcome of the expiration process.
  • OKC_REP_CONTRACT_VERS — A companion table holding contract version information. Because contract terms and expiration dates may vary by version, this table is consulted to determine the effective version against which expiration logic should be evaluated.

Usage Notes

Because OKC_REP_EXP_NTF_PVT is a PVT-classified package, it is invoked from within the applications code base rather than directly by users. Typical invocation contexts include:

  • Concurrent programs — Expiration processing is conventionally scheduled as a batch concurrent program that sweeps the contract repository on a periodic basis.
  • Internal package calls — Other packages in the OKC_REP_* family may call the expiration manager and notifier to ensure notification logic is applied consistently.
  • Forms and UI flows — Contract maintenance forms may trigger expiration handling when a contract's dates are modified.

Custom code should not call this package directly. The ETRM metadata records zero packages referencing it externally and no reverse dependencies other than itself, confirming that it is an internal implementation detail. Any requirement to customize expiration notification behaviour should be met through supported extension mechanisms rather than by invoking OKC_REP_EXP_NTF_PVT.