Search Results oke_k_holds




Overview
Explore in AI Chat

Overview

The OKE_K_HOLDS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as the central repository for managing the application and removal of holds on contract documents. In the context of contract lifecycle management, holds are mechanisms to prevent further processing or modification of a contract, its lines, or its deliverables due to specific business conditions, such as pending approvals, missing information, or compliance issues. This table tracks the complete lifecycle of each hold, recording its creation, status, and eventual release, thereby enforcing business controls and providing an audit trail for contractual actions.

Key Information Stored

The table stores metadata and status information for each hold instance. While the full column list is not detailed in the provided metadata, the primary and foreign key structure reveals its critical components. The primary key is HOLD_ID, a unique identifier for each hold record. The table links to the primary contract entities via foreign keys: K_HEADER_ID references the contract header in OKE_K_HEADERS, K_LINE_ID references a specific contract line in OKE_K_LINES, and DELIVERABLE_ID references a deliverable in OKE_K_DELIVERABLES_B. This structure allows holds to be applied at the header, line, or deliverable level. Typical columns in such a table would include HOLD_TYPE, HOLD_REASON_CODE, HOLD_DATE (application date), RELEASE_DATE, RELEASED_BY, and STATUS, providing a comprehensive history of the hold event.

Common Use Cases and Queries

A primary use case is generating reports to identify all active holds preventing contract approval or billing. Administrators run queries to audit hold history for compliance. A common SQL pattern retrieves active holds for a specific contract:

  • SELECT h.HOLD_ID, h.HOLD_TYPE, h.HOLD_REASON, h.HOLD_DATE FROM OKE_K_HOLDS h, OKE_K_HEADERS kh WHERE h.K_HEADER_ID = kh.K_HEADER_ID AND kh.CONTRACT_NUMBER = '<CONTRACT_NUM>' AND h.RELEASE_DATE IS NULL;

Another critical query involves joining with related entities to list holds impacting specific deliverables or lines for operational review. The data is also essential for workflow notifications, where the presence of a hold triggers an alert to the responsible party for resolution.

Related Objects

The OKE_K_HOLDS table has defined foreign key relationships with three primary tables in the Project Contracts schema, as documented in the metadata:

  • OKE_K_HEADERS: Joined via OKE_K_HOLDS.K_HEADER_ID. This links a hold to a master contract agreement.
  • OKE_K_LINES: Joined via OKE_K_HOLDS.K_LINE_ID. This links a hold to a specific line item within a contract.
  • OKE_K_DELIVERABLES_B: Joined via OKE_K_HOLDS.DELIVERABLE_ID. This links a hold to a specific contractual deliverable.

These relationships are fundamental, ensuring referential integrity and enabling accurate reporting on which contract entity is subject to a hold. The table is also referenced by various Project Contracts application forms, reports, and APIs that manage the hold application and release processes.