Results for “old_service_end_date”

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

Overview

OKS_INST_HIST_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Service Contracts (OKS) module. It exposes historical transaction information for installed base instances — the customer product and service assets tracked by Oracle Service Contracts. The view presents a denormalized, DISTINCT-filtered projection of the underlying history detail table, allowing concurrent programs, concurrent reports, and integration interfaces to retrieve a consolidated audit trail of changes applied to an installed base instance without joining directly to the transactional detail table. In EBS 12.1.1 and 12.2.2 the view carries a VALID status in the ETRM repository, confirming its continued availability across both release lines. Because it surfaces both the previous ("OLD_") and current state attributes associated with a transaction, it is particularly useful for point-in-time analysis of contract, service line, and subline changes.

Underlying Base Objects

The view is defined over a single base object, OKS_INST_HIST_DETAILS, which is referenced through a SYNONYM. The view text is a straightforward SELECT DISTINCT over the columns listed in the ETRM metadata, with no joins, unions, or alternative table references. This means all filtering, aggregation, and time-based logic must be supplied by the consuming query. The DISTINCT qualifier is significant: the underlying detail table may contain duplicate rows across certain transaction scenarios, and the view screens those out to present one row per unique combination of instance, transaction date, transaction type, and related attribute values.

Key Columns

• INS_ID — Identifier of the installed base instance whose history is being tracked.
• TRANSACTION_DATE / TRANSACTION_TYPE — When and what kind of change occurred (for example, transfers or terminations).
• SYSTEM_ID — System reference associated with the instance history record.
• INSTANCE_QTY_OLD / INSTANCE_AMT_OLD — Prior quantity and amount values on the instance before the transaction.
• OLD_CONTRACT_ID, OLD_CONTRACT_START_DATE, OLD_CONTRACT_END_DATE — Prior contract header reference and its effective date range.
• OLD_SERVICE_LINE_ID, OLD_SERVICE_START_DATE, OLD_SERVICE_END_DATE — Prior service line on the contract.
• OLD_SUBLINE_ID, OLD_SUBLINE_START_DATE, OLD_SUBLINE_END_DATE — Prior subline on the contract; this is the column most frequently searched for by users investigating the old_subline_id attribute.
• SUBLINE_DATE_TERMINATED — Date the prior subline was terminated, if applicable.
• OLD_CUSTOMER — Prior customer associated with the instance.
• OLD_K_STATUS — Prior knowledge/status flag used by Service Contracts processing.
• TRANSFER_OPTION — Indicates the transfer behavior applied during the transaction.

Common Use Cases and Queries

Typical scenarios include auditing subline transfers, reconstructing the service coverage history of an asset at a given point in time, and feeding data warehouses or reconciliation reports. A frequent query retrieves all historical subline changes for a given instance:

• SELECT INS_ID, TRANSACTION_DATE, TRANSACTION_TYPE, OLD_SUBLINE_ID, OLD_SUBLINE_START_DATE, OLD_SUBLINE_END_DATE, SUBLINE_DATE_TERMINATED FROM APPS.OKS_INST_HIST_V WHERE INS_ID = :p_ins_id ORDER BY TRANSACTION_DATE;
• SELECT OLD_SUBLINE_ID, COUNT(*) FROM APPS.OKS_INST_HIST_V WHERE TRANSACTION_TYPE = 'TRANSFER' GROUP BY OLD_SUBLINE_ID;
• SELECT INS_ID, OLD_CONTRACT_ID, OLD_SERVICE_LINE_ID, OLD_SUBLINE_ID FROM APPS.OKS_INST_HIST_V WHERE TRANSACTION_DATE BETWEEN :p_from AND :p_to;

Because the view performs no filtering, always constrain by INS_ID or transaction date range to control result size, and join to OKS_K_HEADERS or related contract tables only when header-level descriptions are required.