Search Results receive_date




Overview
Explore in AI Chat

Overview

OKE_CHG_REQUESTS is the primary transactional table in the Oracle E-Business Suite Project Contracts (OKE) module that stores information about contract change requests. In release 12.1.1 and 12.2.2, the table resides in the OKE schema and is classified as VALID in the ETRM repository. Each row represents a single change request raised against a contract header, capturing the request lifecycle from initiation through approval and implementation. The table is central to the contract change management workflow, tracking what changed, who requested it, when it was approved, and which contract versions were affected.

Heuristically, the mined foreign-key structure suggests a Data Vault classification of hub for this object. The presence of a single surrogate primary key (CHG_REQUEST_ID), a business-key unique constraint, and numerous downstream tables referencing it are consistent with hub-style modeling, where the change request identifier serves as the durable business key around which related satellites and links are organized.

Key Information Stored

The table contains 39 documented columns. The most significant are:

The table also includes the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1–15 descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting scenarios include open change request tracking, cycle-time analysis between REQUESTED_DATE and APPROVE_DATE, and funding-impact review. A common query joins the change request to its contract header:

  • List all pending change requests for a contract: SELECT c.CHG_REQUEST_NUM, c.CHG_STATUS_CODE, c.REQUESTED_DATE FROM OKE_CHG_REQUESTS c WHERE c.K_HEADER_ID = :header_id
  • Resolve the current status description: join to OKE_CHG_STATUSES_B on CHG_STATUS_CODE.
  • Audit trail: join to OKE_CHG_LOGS on CHG_REQUEST_ID or via LAST_CHG_LOG_ID.
  • Approval history: join to OKE_APPROVAL_HISTORY on CHG_REQUEST_ID.
  • Version comparison: use PREV_VERSION and NEW_VERSION in conjunction with OKE_K_VERS_NUMBERS_H (joined via CHG_REQUEST_ID).

Related Objects

  • OKE_K_HEADERS — parent contract header; join on OKE_CHG_REQUESTS.K_HEADER_ID.
  • OKE_CHG_STATUSES_B — status lookup; join on CHG_STATUS_CODE.
  • OKE_CHG_LOGS — child change log records; join on CHG_REQUEST_ID or via LAST_CHG_LOG_ID.
  • OKE_APPROVAL_HISTORY — approval audit rows; referenced by OKE_APPROVAL_HISTORY.CHG_REQUEST_ID.
  • OKE_K_BILLING_EVENTS — billing events tied to the change; join on BILL_CHG_REQ_ID.
  • OKE_K_COMMUNICATIONS — communications linked to the request; join on CHG_REQUEST_ID.
  • OKE_K_RELATED_ENTITIES — associated related entities; join on CHG_REQUEST_ID.
  • OKE_K_VERS_NUMBERS_H — contract version history referencing the change; join on CHG_REQUEST_ID.