Results for “remove_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKE_K_HOLDS table is a core transactional data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It stores contract hold application and removal information, capturing the lifecycle of holds placed against contract headers, contract lines, and deliverables. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the authoritative record of which holds are active, scheduled for removal, or already released, along with the associated reasons, comments, and workflow context.

Under a heuristic Data Vault classification mined from its foreign key structure, OKE_K_HOLDS is best modeled as a link. It does not behave as a hub because its identity is not a standalone business concept; instead, it associates a hold event with the contract header (OKE_K_HEADERS), contract line (OKE_K_LINES), or deliverable (OKE_K_DELIVERABLES_B) it applies to. This link-centric classification aligns with the table's role as an event/association table rather than a pure dimension or reference entity.

Key Information Stored

The table contains 37 documented columns. The most significant fields for functional and reporting purposes are:

• HOLD_ID — The surrogate primary key (OKE_K_HOLDS_PK), uniquely identifying each hold record. A unique index OKE_K_HOLDS_U1 also exists on HOLD_ID, confirming it as the candidate business key in practice.
• K_HEADER_ID — Foreign key to OKE_K_HEADERS, linking the hold to a specific contract header.
• K_LINE_ID — Foreign key to OKE_K_LINES, associating the hold with a contract line when the hold is line-level rather than header-level.
• DELIVERABLE_ID — Foreign key to OKE_K_DELIVERABLES_B, scoping the hold to a specific contract deliverable.
• HOLD_TYPE_CODE — Classifies the type of hold applied.
• HOLD_REASON_CODE — Records the business reason for applying the hold.
• HOLD_STATUS_CODE — Tracks whether the hold is applied, scheduled for removal, or removed.
• HOLD_COMMENT — Free-text commentary captured when the hold is applied.
• APPLY_DATE — The date the hold took effect.
• SCHEDULE_REMOVE_DATE — The planned removal date for the hold.
• REMOVE_DATE — The actual date the hold was removed.
• REMOVE_REASON_CODE and REMOVE_COMMENT — The reason and commentary captured at removal time.
• WF_ITEM_TYPE, WF_PROCESS, WF_ITEM_KEY — Workflow context columns enabling integration with Oracle Workflow for hold approval or release processes.
• Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Standard EBS audit fields.

The fifteen ATTRIBUTE (1–15) and ATTRIBUTE_CATEGORY columns provide descriptive flexibility for extensibility without schema changes.

Common Use Cases and Queries

Typical reporting scenarios include identifying all active holds on a contract, holds by reason code, and overdue holds past their scheduled removal date. A representative query joining to the contract header is:

• SELECT h.HOLD_ID, h.K_HEADER_ID, h.HOLD_TYPE_CODE, h.HOLD_STATUS_CODE, h.APPLY_DATE, h.SCHEDULE_REMOVE_DATE FROM OKE.OKE_K_HOLDS h WHERE h.K_HEADER_ID = :header_id AND h.REMOVE_DATE IS NULL;
• To find holds scheduled for removal but not yet removed: filter on SCHEDULE_REMOVE_DATE less than SYSDATE and REMOVE_DATE IS NULL.
• To trace line-level and deliverable-level holds: join K_LINE_ID to OKE_K_LINES and DELIVERABLE_ID to OKE_K_DELIVERABLES_B.

Related Objects

• OKE_K_HEADERS — Joined on OKE_K_HOLDS.K_HEADER_ID = OKE_K_HEADERS.K_HEADER_ID; the parent contract header.
• OKE_K_LINES — Joined on OKE_K_HOLDS.K_LINE_ID = OKE_K_LINES.K_LINE_ID; the affected contract line.
• OKE_K_DELIVERABLES_B — Joined on OKE_K_HOLDS.DELIVERABLE_ID = OKE_K_DELIVERABLES_B.DELIVERABLE_ID; the affected deliverable.
• Oracle Workflow tables — Referenced via WF_ITEM_TYPE, WF_PROCESS, and WF_ITEM_KEY for hold-related approval flows.
• OKE_K_HOLDS_PK and OKE_K_HOLDS_U1 — Primary key constraint and unique index enforcing HOLD_ID integrity.