Search Results oks_inst_hist_details_v




Overview
Explore in AI Chat

Overview

The OKS_INST_HIST_DETAILS_V view is a reporting-layer object in the Oracle E-Business Suite Service Contracts (OKS) module, owned by the APPS schema. It exposes installation history detail records maintained by Oracle's Service Contracts and Install Base integration. In EBS 12.1.1 and 12.2.2, this view presents a denormalized, read-friendly projection of the OKS_INST_HIST_DETAILS table, allowing concurrent programs, forms, and custom reports to query installation transaction history without directly accessing the base table. The view is defined as a simple column rename/selection over its single base object, so it carries no aggregation or filtering logic. Its principal value lies in tracking changes to installed instances—quantity, amount, contract, service line, subline, customer, and status—captured at each transaction event.

Underlying Base Objects

The documented view metadata for ETRM 12.2.2 identifies a single referenced base object: the OKS_INST_HIST_DETAILS table, accessed through a synonym. The view text confirms this by selecting every visible column from the alias IHD, which is the synonym for OKS_INST_HIST_DETAILS. Because the view is a straightforward projection, its row cardinality equals that of the base table, and no joins to other entities (contracts, customers, service lines) are performed inside the view. Related descriptive data—such as the new customer name referenced by the NEW_CUSTOMER column—must be resolved by joining this view to the appropriate master tables, for example HZ_CUST_ACCOUNTS or the Install Base instance tables, at query time.

Key Columns

The view carries a wide set of paired old/new columns representing before-and-after state at each transaction, plus audit and version attributes. Notable columns include:

Common Use Cases and Queries

The view is used to audit installation history, to determine when an instance moved from one customer to another, and to reconcile service contract coverage changes. A typical query filtering on the new customer column is:

  • SELECT id, ins_id, transaction_date, transaction_type, old_customer, new_customer FROM oks_inst_hist_details_v WHERE new_customer = :customer_id ORDER BY transaction_date DESC;
  • Reports joining to HZ_CUST_ACCOUNTS on NEW_CUSTOMER to print customer names for transferred instances.
  • Concurrent programs extracting quantity and amount deltas between INSTANCE_QTY_OLD/NEW and INSTANCE_AMT_OLD/NEW.
  • Status-transition analysis using OLD_K_STATUS and NEW_K_STATUS together with SUBLINE_DATE_TERMINATED.

All queries should be schema-qualified as APPS and, in multi-org environments, constrained by SECURITY_GROUP_ID or the applicable MOAC policy.