Results for “program_application_id”

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

Overview

The OKX_QTE_LINE_RLSHPS_V view is a reporting and integration artifact within the Oracle E-Business Suite (EBS) Contracts Integration module, owned by the APPS schema. Its purpose is narrow and specific: it links one quote line to another and records the type of relationship that exists between them. In ETRM 12.1.1 and 12.2.2, this view is registered as a VALID database object of type VIEW, meaning it can be queried directly by reporting tools, concurrent programs, and external integration interfaces without requiring access to the underlying transactional table structure.

The view behaves as a projection layer over the quotation relationship data model. Rather than presenting new business logic, it exposes a curated, denormalized-in-name-only set of columns that map one-to-one with the base table, providing a stable, APPS-owned interface for downstream consumers. This design is consistent with standard EBS practice, where seeded views shield external callers from internal table changes and enforce row-level access through the APPS schema grants.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the single referenced base object for this view is:

• ASO_LINE_RELATIONSHIPS (referenced through a synonym)

The view text confirms a straightforward SELECT from ASO_LINE_RELATIONSHIPS, exposing fifteen columns verbatim. The synonym resolves to the underlying ASO (Order Capture / Quoting) base table, which is the physical store for line-level relationship records. Because the view definition contains no joins, filters, expressions, or aggregations, it functions as a pure pass-through: every row and column returned reflects the state of the base table at query time. Writers should note that a pass-through view of this type does not, by itself, enforce referential integrity or business rules — those are maintained by the ASO application logic and the base table constraints.

Key Columns

The view exposes the following columns, which carry the standard EBS audit and relationship semantics:

• LINE_RELATIONSHIP_ID — Primary identifier for each relationship record. This is the column most commonly matched by users searching for "line_relationship_id," as it uniquely keys the association.
• QUOTE_LINE_ID — The source quote line participating in the relationship.
• RELATED_QUOTE_LINE_ID — The target quote line to which the source is related.
• RELATIONSHIP_TYPE_CODE — Classifies the nature of the link (for example, a dependency or alternative relationship type), governing how the two lines interact.
• RECIPROCAL_FLAG — Indicates whether the relationship applies symmetrically to both lines in both directions.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which capture who created or last modified the record and through which concurrent program.

Common Use Cases and Queries

Typical uses include auditing quote line dependencies, building integration feeds to external configuration or order systems, and troubleshooting relationships surfaced by the OKX Contracts Integration flows. A representative query isolating all relationships for a given line is shown below:

SELECT line_relationship_id,
       quote_line_id,
       related_quote_line_id,
       relationship_type_code,
       reciprocal_flag
  FROM apps.okx_qte_line_rlshps_v
 WHERE quote_line_id = :p_quote_line_id;

To inspect the relationships of a specific relationship type, add a predicate on RELATIONSHIP_TYPE_CODE. For reconciliation against the base table, join the view back to ASO_LINE_RELATIONSHIPS on LINE_RELATIONSHIP_ID, recognizing that the view is a direct projection and should return identical results aside from any schema-level security policies applied to the view.