Search Results implement_date

Overview

OKE_CHG_REQUESTS_V is an APPS-owned reporting view within the OKE – Project Contracts module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It exposes the contract change request entity together with its descriptive and lookup-derived attributes, providing a denormalized, human-readable projection of change request header data for reporting, inquiry, and integration purposes. Because change request records reference several coded values — change type, change status, and change reason — the view resolves these codes into translatable names and meanings, sparing downstream consumers from performing multiple joins against lookup and translation tables. The view is defined as VALID in the data dictionary and is intended for read-only consumption by reports, concurrent programs, and external interfaces. Among its exposed columns, RECEIVE_DATE is particularly relevant to users tracking the lifecycle of a change request, as it records the date the request was received into the approval workflow, distinct from the requested and approved dates.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKE_CHG_REQUESTS (synonym) — the primary change request header table, supplying core columns such as CHG_REQUEST_ID, CHG_REQUEST_NUM, dates, versions, and descriptive flexfield attributes.
• OKE_CHG_STATUSES_B (synonym) — the base change status table, joined on CHG_STATUS_CODE to derive the status type code.
• OKE_CHG_STATUSES_TL (synonym) — the translation table for change statuses, joined on CHG_STATUS_CODE and restricted to the session language via USERENV('LANG').
• PER_ALL_PEOPLE_F (synonym) — the person effective-dated table, joined to REQUESTED_BY_PERSON_ID, with the requested date constrained between the person's effective start and end dates to return the correct person version.
• FND_LOOKUP_VALUES_VL (view) — the standard lookup view, joined twice: once for lookup type 'CHANGE_TYPE' and once for 'CHANGE_REASON', both filtered to VIEW_APPLICATION_ID = 777 (the OKE application).

The joins are inner joins keyed on person, status, language, and lookup codes. Consequently, a change request whose requested person version, status, type, or reason does not resolve to a matching row will not appear in query results.

Key Columns

• CHG_REQUEST_ID / CHG_REQUEST_NUM — primary key and user-visible change request number.
• RECEIVE_DATE — the date the change request was received; useful for cycle-time and aging analysis alongside REQUESTED_DATE, APPROVE_DATE, and IMPLEMENT_DATE.
• EFFECTIVE_DATE — the date on which the change takes contractual effect.
• CHG_TYPE_CODE / CHG_TYPE_NAME — the change type code and its lookup meaning.
• CHG_STATUS_CODE / CHG_STATUS_NAME / CHG_STATUS_TYPE_CODE — status code, translated status name, and status type classification.
• CHG_REASON_CODE and reason meaning — the reason for the change request.
• REQUESTED_BY_PERSON_ID / FULL_NAME — the requesting person and their name.
• PREV_VERSION / NEW_VERSION — the contract versions before and after the change.
• IMPACT_FUNDING_FLAG — indicates whether the change impacts funding.
• DESCRIPTION / CHG_TEXT — short description and full change text.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard descriptive flexfield columns.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, plus ROW_ID for row addressing.

Common Use Cases and Queries

Typical uses include open change request registers, cycle-time reporting from RECEIVE_DATE to APPROVE_DATE and IMPLEMENT_DATE, status aging, and version-history extracts.

• Open requests received in a period:

  SELECT chg_request_num, full_name, receive_date, chg_status_name
  FROM   oke_chg_requests_v
  WHERE  chg_status_name <> 'Implemented'
  AND    receive_date BETWEEN :p_from AND :p_to;

• Cycle-time analysis:

  SELECT chg_request_num, receive_date, approve_date, implement_date,
         TRUNC(implement_date - receive_date) days_to_implement
  FROM   oke_chg_requests_v
  WHERE  implement_date IS NOT NULL;

• Requests by type and reason:

  SELECT chg_type_name, chg_reason_code, COUNT(*)
  FROM   oke_chg_requests_v
  GROUP  BY chg_type_name, chg_reason_code;

Queries should filter on indexed base columns where possible, as the view performs multiple joins, and should account for the language restriction on status translations.