Search Results contract_expiration_notifier

Overview

The package body APPS.OKC_REP_EXP_NTF_PVT is a private PL/SQL package belonging to the Oracle E-Business Suite Contracts (OKC) module. Its principal business function is to support the management and notification of contracts that are approaching their expiration date, commonly referred to as the contract expiration notifier. The package iterates through repository contracts that are about to expire and dispatches notifications to the relevant contract contacts, ensuring that contract owners and responsible parties are alerted before contractual obligations lapse. It is classified as PVT (private), meaning it is intended for internal use within the OKC schema rather than as a public integration API.

The package defines a standard library of global constants used throughout its execution, including the package name (G_PKG_NAME), application name (G_APP_NAME), and module identifier used for error logging (G_MODULE). It also declares canonical return code constants — success (0), warning (1), and error (2) — along with error-handling tokens such as G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, and G_SQLCODE_TOKEN. These conventions reflect the Oracle Application Object Library (AOOL) API error-handling standards.

Key Procedures and Functions

The package exposes two documented procedures:

• CONTRACT_EXPIRATION_NOTIFIER — The procedure at the center of the contract expiration notifier functionality. It iterates through contracts that are about to expire and invokes a corresponding repository_notifier() routine for each qualifying contract. Its documented role is to send notifications to all contract contacts. The procedure follows the standard Oracle API parameter conventions, accepting an API version and an initialization message list flag as inputs, and returning message data, message count, and return status as outputs. Supporting internal elements include an l_api_version variable and an EXPIRI cursor used to select the expiring contracts.
• CONTRACT_EXPIRATION_MANAGER — A companion procedure that governs the overall expiration-processing logic. While the documentation excerpt does not detail its body, its presence alongside the notifier indicates it serves as the orchestrating entry point for the expiration workflow.

Tables Accessed

The package reads from two documented tables through APPS synonyms:

• OKC_REP_CONTRACTS_ALL — the base repository contracts table. It is the primary source for identifying contracts that are approaching expiration and for retrieving the contact information needed to route notifications.
• OKC_REP_CONTRACT_VERS — the contract versions table. It supplies version-specific attributes such as effective and expiration dates that determine which contracts qualify for a notifier call.

Both tables are read-only in this context; the package selects records rather than modifying contract data.

Usage Notes

Because OKC_REP_EXP_NTF_PVT is marked as a private package, it is not exposed as a callable public interface. It is typically invoked indirectly by the Contracts module — for example, through a concurrent program or a scheduled background job that systematically identifies contracts nearing expiration and triggers the notification process. The metadata records that the package is referenced by zero other packages, confirming its role as a terminal implementation unit rather than a shared utility. Customizations and extensions should not call this package directly; instead, customers requiring similar functionality should rely on supported public APIs or the standard concurrent program configuration provided by Oracle Contracts.