Results for “linked_flag”

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

Overview

The OKS_SUBSCR_ELEMENTS_V view is a reporting and integration artifact within the Oracle E-Business Suite OKS – Service Contracts module. It resides in the APPS schema and is documented as VALID in ETRM for both release 12.1.1 and 12.2.2. The object is a pass-through view whose stated purpose is to expose the contents of the subscription elements table in a stable, named form for consumption by forms, concurrent programs, public APIs, and custom extensions.

Subscription elements represent the individual priced or tracked components that make up a subscription line on a service contract. Each row links a subscription element to its governing subscription header (via OSH_ID) and, where applicable, to a contract line (DNZ_CLE_ID) and contract header (DNZ_CHR_ID). Because the view mirrors the base table column-for-column rather than joining additional entities, it functions primarily as an abstraction layer that shields downstream code from direct dependencies on OKS_SUBSCR_ELEMENTS.

Underlying Base Objects

Per the documented metadata, the view is defined solely over the synonym OKS_SUBSCR_ELEMENTS (resolving to the underlying APPS table of the same name, aliased SCES). No outer joins, lookups, or translated columns are present. The projection preserves the base ROWID as ROW_ID and carries the primary key column ID unchanged.

• OKS_SUBSCR_ELEMENTS – the single referenced base object; source of every exposed column.
• ROW_ID – SCES.ROWID, retained for row-level addressing and DML against the base table.
• No aggregations, filters, or DISTINCT qualifiers are applied, so row cardinality matches the base table exactly.

Key Columns

• ID – Primary identifier of the subscription element row.
• OSH_ID – Foreign key to the subscription header. This is the column most commonly used to retrieve all elements belonging to a given subscription, and is the term most frequently used in ad hoc searches.
• DNZ_CHR_ID / DNZ_CLE_ID – Contract header and contract line identifiers that contextualize the subscription within the service contract structure.
• LINKED_FLAG – Indicates whether the element is linked to an order or upstream entity.
• SEQ_NO – Ordering sequence of the element within its subscription.
• AMOUNT, QUANTITY, UOM_CODE – Commercial attributes of the element (priced amount, quantity, and unit of measure).
• START_DATE / END_DATE – Effective period of the element.
• OM_INTERFACE_DATE – Timestamp indicating when the element was interfaced to Order Management.
• ORDER_HEADER_ID / ORDER_LINE_ID – References to the associated OM sales order header and line.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the underlying framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reconciliation of subscription elements against OM orders, reporting of active subscription components by contract, and integration extracts. When querying, note that the view returns unprocessed base data, so date and status filtering must be applied by the caller.

SELECT ose.id,
       ose.osh_id,
       ose.dnz_cle_id,
       ose.seq_no,
       ose.amount,
       ose.quantity,
       ose.uom_code,
       ose.start_date,
       ose.end_date,
       ose.order_header_id,
       ose.order_line_id
  FROM apps.oks_subscr_elements_v ose
 WHERE ose.osh_id = :p_osh_id
 ORDER BY ose.seq_no;

A second frequent pattern retrieves all elements associated with a contract line for reconciliation against Order Management interface data:

SELECT ose.id, ose.linked_flag, ose.om_interface_date
  FROM apps.oks_subscr_elements_v ose
 WHERE ose.dnz_cle_id = :p_cle_id
   AND ose.om_interface_date IS NULL;