Search Results contract_status_updater




Overview

OKC_REP_STATUS_UPDATE_PVT is a private PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, owned by the APPS schema and defined with AUTHID CURRENT_USER. Its documented API name is contract_status_updater, which is the identifier most commonly surfaced when developers or administrators search for this object. The package provides the core business logic responsible for advancing or otherwise modifying the status of contracts that have reached their termination date. In effect, it automates lifecycle state transitions so that expired contracts no longer remain in an active or approved status once their end date passes.

The package is classified as PVT (private), meaning it is intended for internal consumption by the Contracts application and is not published as a supported public API. It is not referenced by any other documented package, indicating that it operates as a self-contained unit whose procedures are invoked directly by the concurrent manager infrastructure and related internal callers rather than through a layered API stack.

Key Procedures and Functions

Two procedures are documented in the package specification:

  • contract_status_updater — The primary worker procedure. Per the embedded comments, its function is to update the status of contracts reaching their termination date. It accepts an API version, an initialization flag for the message list, and a target status value as inputs, returning standard EBS API return values: a return status, a message count, and message data. The message data and count parameters are declared NOCOPY for performance. This procedure encapsulates the actual status-change logic.
  • contract_status_update_manager — The concurrent-program entry point. Documented as being called from the Concurrent Manager, it drives the batch update of contract statuses for contracts reaching their termination date. It accepts a status parameter and returns the standard concurrent program OUT parameters errbuf and retcode, both declared NOCOPY. This procedure is what a scheduled concurrent request executes.

No parameter lists are reproduced beyond what the package specification documents, and no additional functions are present.

Tables Accessed

The package operates against the following tables (via APPS synonyms):

  • OKC_REP_CONTRACTS_ALL — The main contracts table holding contract records and their current status. This is the primary target of the status update, since the termination-date check and the resulting status write are applied to contract headers.
  • OKC_REP_CONTRACT_VERS — The contract versions table, which tracks versioned contract data, including effective and termination dates used to determine which contracts have reached termination.
  • PLITBLM — A standard EBS PL/SQL table used internally by the message-handling framework for accumulating and retrieving API error and information messages.

Usage Notes

OKC_REP_STATUS_UPDATE_PVT is not a public API and should not be called directly from custom code; reliance on private packages is unsupported and risks breakage across patches. In standard operation, contract_status_update_manager is scheduled as a concurrent program so the Concurrent Manager periodically evaluates contracts that have reached their termination date and updates their status accordingly. The contract_status_updater procedure performs the underlying update work invoked by that manager routine. Administrators troubleshooting expired contracts that retain an active status should inspect the concurrent request log for this program, verify the termination dates on OKC_REP_CONTRACT_VERS, and review the message data returned through PLITBLM to diagnose failures.