Search Results oks_subscr_elements_u1

Overview

OKS.OKS_SUBSCR_ELEMENTS is a transactional table in the Oracle Service Contracts (OKS) schema that stores the fulfillment schedule of a subscription line. It is populated for tangible subscriptions only, and one row is created for each expected subscription fulfillment. For example, a one-year contract line using a subscription item fulfilled monthly generates twelve rows, one per monthly fulfillment. The fulfillment schedule is populated at contract creation time, and the Subscription Fulfillment concurrent program subsequently populates order details after successfully creating an order for a specific record. When both ORDER_HEADER_ID and ORDER_LINE_ID are present, an order has been created for that schedule element and Oracle Service Contracts regards it as fulfilled.

From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification. The table is anchored to OKS_SUBSCR_HEADER_B through the OSH_ID foreign key, and its payload columns (dates, quantities, amounts, fulfillment state) describe the changing condition of that parent, which is characteristic of satellite behavior rather than an independent hub.

Key Information Stored

The surrogate primary key is ID, enforced by the unique index OKS_SUBSCR_ELEMENTS_U1 and the primary key constraint OKS_SUBSCR_ELEMENTS_PK. ID is documented as the primary identifier. The primary business-key candidate is also the ID column based on the unique index documentation; the remaining indexes, DNZ_CLE_ID (N1) and OSH_ID (N2), are nonunique access paths rather than business keys.

• OSH_ID — Identifier of the subscription header the element belongs to; foreign key to OKS_SUBSCR_HEADER_B.ID.
• DNZ_CHR_ID — Denormalized contract ID, retained for query performance.
• DNZ_CLE_ID — Denormalized contract line ID; indexed nonuniquely for line-level retrieval.
• LINKED_FLAG — Set to 'Y' by the Service Contracts Instance Relationship program once the parent-child IB instance relationship is established.
• SEQ_NO — Sequence number of the fulfillment element within the schedule.
• START_DATE, END_DATE — Effective window for the individual fulfillment.
• AMOUNT, QUANTITY, UOM_CODE — Priced and quantified fulfillment values.
• ORDER_HEADER_ID, ORDER_LINE_ID — Populated by the Subscription Fulfillment program once an order exists for the element.
• OM_INTERFACE_DATE — Timestamp of the order management interface activity for the row.
• OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) support concurrency control, multi-org security, and auditability.

Common Use Cases and Queries

Typical reporting identifies unfulfilled schedule elements, tracks fulfillment progress by contract line, and reconciles Service Contracts schedules against Order Management orders.

• Unfulfilled elements: SELECT id, osh_id, seq_no, start_date FROM oks_subscr_elements WHERE order_header_id IS NULL;
• Fulfillment counts per contract line: SELECT dnz_chr_id, dnz_cle_id, COUNT(*) FROM oks_subscr_elements GROUP BY dnz_chr_id, dnz_cle_id;
• Order linkage verification: join ORDER_HEADER_ID and ORDER_LINE_ID to OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.
• Instance relationship status: filter on LINKED_FLAG = 'Y' to confirm IB parent-child linkage.

Related Objects

• OKS_SUBSCR_HEADER_B — referenced via OKS_SUBSCR_ELEMENTS.OSH_ID to its ID column.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — order records created by the Subscription Fulfillment concurrent program.
• OKS_SUBSCR_LINES — contract line context associated with DNZ_CLE_ID.
• Service Contracts Instance Relationship concurrent program and the Subscription Fulfillment concurrent program, which populate LINKED_FLAG and order IDs respectively.