Results for “ste_code”

1 result




Overview
Explore in AI Chat

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

Overview

The OKI_RENEW_RELS_V view is a Contracts Intelligence (OKI) reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the relationship between renewed (source) contracts and contract lines and the renewing (target) contracts and lines that supersede them. The view is owned by the APPS schema and holds VALID status in a standard installation.

The view is created specifically to surface renewal lineage: for each renewal operation recorded in Oracle Contracts (OKC), it links the originating contract header and line to the resulting contract header and line, and it exposes the workflow status code and status type code for each of the four entities involved. This makes it a convenient source for reports and integrations that must trace which contract superseded which, and at what workflow state, without reconstructing the renewal relationship from the OKC operation tables directly.

Because the view joins the OKC operation instance and line tables to the header and line base tables, it effectively presents a denormalized "renewal map" usable in SQL-based reporting, Oracle Discoverer workbooks, BI Publisher data sets, and custom interfaces. The user search term "ste_code" corresponds directly to the view's status type columns, which resolve the STE_CODE values from OKC_STATUSES_B.

Underlying Base Objects

The view is defined over ten OKC tables. The renewal relationship itself is derived from OKC_CLASS_OPERATIONS, which is filtered to operations where OPN_CODE is 'RENEWAL' or 'REN_CON' (renewal and renewal-connection), and OKC_OPERATION_INSTANCES, which records the instances of those operations. OKC_OPERATION_LINES supplies the specific line-level links, restricted to PORT_FLAG = 'P' (processed) rows, and provides the SUBJECT_CHR_ID, SUBJECT_CLE_ID, OBJECT_CHR_ID, and OBJECT_CLE_ID columns that bind the four contract entities together.

Contract data is retrieved from OKC_K_HEADERS_B (aliased TCHR for the target/renewed header and SCHR for the source/renewing header) and OKC_K_LINES_B (TCLE and SCLE respectively). Four instances of OKC_STATUSES_B (TSTS1, TSTS2, SSTS1, SSTS2) resolve the header and line status codes into their status type codes. The documented metadata lists no referential base objects beyond this view text; the effective dependency set is these ten OKC tables.

Key Columns

The STE_CODE columns are the status type values that group individual status codes into broader categories (for example, Active, Terminated, and similar OKC groupings). These are typically what consumers filter or group by when analyzing renewal progress.

Common Use Cases and Queries

Typical scenarios include renewal audit reporting, contract lifecycle analytics, and downstream interfaces that must propagate renewal relationships into data warehouses or third-party systems. A representative query lists all renewal pairs with their status types:

  • SELECT SOURCE_HEADER_ID, SOURCE_LINE_ID, SOURCE_CHR_STATUS_TYPE, SOURCE_CLE_STATUS_TYPE, TRGT_HEADER_ID, TRGT_LINE_ID, TRGT_CHR_STATUS_TYPE, TRGT_CLE_STATUS_TYPE FROM APPS.OKI_RENEW_RELS_V;
  • Filtering by status type to isolate only renewals in a particular state, for example WHERE SOURCE_CHR_STATUS_TYPE = :p_ste_code.
  • Joining to OKC_K_HEADERS_V or OKC_K_LINES_B on the header/line IDs to retrieve contract numbers and descriptions for a complete renewal report.

Because the view is read-only and pre-joins the OKC operation and status tables, it is the preferred starting point for any query that must relate renewed and renewing contracts without writing the underlying multi-table join explicitly.