Search Results level_sequence

Overview

OKC_ANCESTRYS_V is a PL/SQL view owned by the APPS schema within the OKC – Contracts Core product family. It is a relatively thin projection layer defined directly over the OKC_ANCESTRYS table, and its stated purpose in the ETRM metadata is simply "View for table OKC_ANCESTRYS." Despite the absence of a descriptive business narrative, the object plays a meaningful role in the Contracts Core data model because OKC_ANCESTRYS stores the ancestor–descendant relationships that define the hierarchical structure of contract line entities (CLEs).

In Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed for reporting, integration extracts, and hierarchical navigation of contract structures. The view preserves the standard Oracle audit and concurrency columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER), which makes it suitable for interfaces that must respect optimistic locking or replicate data into external systems.

Underlying Base Objects

The documented source for the view definition is the OKC_ANCESTRYS table, accessed through the APPS.OKC_ANCESTRYS synonym. The view text performs a straightforward SELECT over that table, propagating every column without transformation, filtering, or join. This is confirmed by the metadata's single referenced base object (OKC_ANCESTRYS SYNONYM).

Because the view is a direct projection, it inherits the semantics, constraints, and indexing strategy of the base table. No additional tables are joined, so the view does not enrich the data with contract header or party attributes. Any such enrichment must be performed by the caller through explicit joins back to OKC_ANCESTRYS or to other Contracts Core entities.

Key Columns

• ROW_ID – The ROWID of the underlying OKC_ANCESTRYS row, exposed to support positioned updates and row identification during bulk processing.
• CLE_ID – The identifier of the contract line entity that participates in the relationship.
• CLE_ID_ASCENDANT – The identifier of the ancestor (parent) contract line entity, forming the hierarchical link.
• OBJECT_VERSION_NUMBER – Optimistic locking column used for concurrent update detection.
• LEVEL_SEQUENCE – The column the user searched for; it represents the ordinal position or depth sequence of the entity within its ancestry path, allowing ordered traversal of the hierarchy.
• CREATED_BY, CREATION_DATE – Standard audit attributes capturing who created the relationship record and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit attributes capturing the most recent modification details.

Common Use Cases and Queries

Typical uses include reconstructing contract hierarchy reports, extracting ancestry data into data warehouses, and validating parent–child relationships during data conversion. A representative query ordering by the level sequence is:

SELECT cle_id,
       cle_id_ascendant,
       level_sequence,
       creation_date
  FROM apps.okc_ancestrys_v
 WHERE cle_id = :p_cle_id
 ORDER BY level_sequence;

Because the view is unfiltered, callers should always apply a WHERE clause on CLE_ID or CLE_ID_ASCENDANT to limit result sets on large installations. Joins back to the base synonym remain valid when ROWID or full table semantics are required, and the standard audit columns should be preserved in any downstream interface to maintain traceability.