Search Results oks_interaction_hist_v




Overview
Explore in AI Chat

Overview

The OKS_INTERACTION_HIST_V view is a reporting and integration object within the Oracle E-Business Suite Service Contracts (OKS) module, owned by the APPS schema. It is a thin, pass-through view defined over the OKS_INTERACTION_HISTORY table, meaning that it exposes the same column set as its base object without joins, filters, or aggregations. Its principal role is to provide a stable, externally addressable interface through which the interaction history of service contracts can be queried. Because OKS_INTERACTION_HISTORY records the audit trail of renewal and contract-processing interactions, the view is a natural source for renewal-cycle reporting, workflow diagnostics, and downstream data extraction. In EBS 12.1.1 and 12.2.2 the view is documented as VALID, and it is catalogued in ETRM as part of the OKS product metadata. The user's search term "renewal_status" corresponds directly to the RENEWAL_STATUS column exposed by the view, indicating that the object is most commonly located in the context of renewal tracking queries.

Underlying Base Objects

The view is defined over a single documented base object, OKS_INTERACTION_HISTORY, referenced through a synonym of the same name. The view text selects every column of the base table, aliased with INH for clarity, and adds the base row identifier as ROW_ID. No WHERE clause or join condition is applied, so the view returns the complete interaction history dataset, subject only to whatever predicate the calling query supplies. Because OKS_INTERACTION_HISTORY is an operational table populated by the Service Contracts renewal and concurrent processes, the view inherits its transactional grain: one row per interaction record. Administrators should note that the view itself carries no additional privileges; access is governed by grants on the underlying table and on the APPS-owned view. Some implementations create additional synonym or grant layers so that custom reports can reference the view without direct table privileges.

Key Columns

The column list maps one-to-one with the base table and includes the following attributes relevant to renewal analysis:

  • RENEWAL_STATUS — the status of the renewal associated with the interaction; central to the user's search and to renewal-state reporting.
  • CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — identifies the service contract and its modifier, forming the business key used to join to OKS_HEADERS and related contract tables.
  • CHR_ID — the associated contract history record identifier, linking the interaction to the contract change history.
  • PARTY_ID — the party (customer or organization) involved in the interaction.
  • USER_ID — the application user who performed or triggered the interaction.
  • STATUS / TASK_NAME / TASK_RESULT — the processing status and the named task with its outcome, useful for workflow troubleshooting.
  • DESCRIPTION — free-text description of the interaction.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying business logic.
  • ID and ROW_ID — the primary identifier and physical row locator, exposed for direct record addressing.

Common Use Cases and Queries

The view is typically queried to report renewal activity, monitor contract interaction outcomes, and feed integration extracts. The following examples reflect the documented structure:

To list all interactions for a specific contract with their renewal status:

SELECT contract_number, contract_number_modifier, renewal_status, task_name, task_result, creation_date
FROM   oks_interaction_hist_v
WHERE  contract_number = :contract_number
ORDER BY creation_date DESC;

To summarize renewal statuses over a date range:

SELECT renewal_status, COUNT(*) 
FROM   oks_interaction_hist_v
WHERE  creation_date BETWEEN :start_date AND :end_date
GROUP BY renewal_status;

To join interaction history back to contract headers for customer-level reporting:

SELECT v.contract_number, v.renewal_status, h.customer_id
FROM   oks_interaction_hist_v v, oks_headers h
WHERE  v.contract_number = h.contract_number
AND    v.renewal_status = 'ACTIVE';

Because the view performs no filtering, queries should always constrain by contract number, date range, or renewal status to avoid scanning the full interaction history. For high-volume renewal reporting, indexing the base table on CONTRACT_NUMBER and CREATION_DATE yields the best plan.