Search Results oks_med_prty_type

Overview

The OKS.OKS_SUBSCR_HEADER_B table is the master header table for subscription templates and instantiated subscriptions within the Oracle Service Contracts (OKS) module. A subscription template defines a reusable set of attributes that can be associated with subscription items; each template occupies a single row in this table. When a subscription contract line is created, the template is instantiated against that specific line, and the resulting instantiated subscription is also persisted in this same table. Templates are distinguished from instantiated records by the sentinel value of -1 in the DNZ_CHR_ID column. For instantiated rows, the corresponding contract header identifier and contract line identifier are stored in DNZ_CHR_ID and CLE_ID respectively.

The object resides in the APPS_TS_TX_DATA tablespace and carries 23 documented columns in the 12.2.2 schema. Based on the foreign-key topology mined from the ETRM metadata, this table exhibits a satellite-leaning Data Vault classification. In Data Vault modeling terms, it functions predominantly as a satellite attached to hubs such as contract lines and item instances, rather than as a hub or link in its own right.

Key Information Stored

The surrogate primary key is ID, enforced by the unique index OKS_SUBSCR_HEADER_B_U1 (ID, unique, APPS_TS_TX_IDX). This index is the documented unique business-key candidate. The most significant remaining columns include:

• CLE_ID — the contract line identifier; NULL for templates. Indexed non-uniquely by OKS_SUBSCR_HEADER_B_N2.
• DNZ_CHR_ID — the denormalized contract ID, retained for performance; holds -1 for templates.
• INSTANCE_ID — the item instance identifier; NULL for templates. Indexed by OKS_SUBSCR_HEADER_B_N3.
• SUBSCRIPTION_TYPE — user-definable, validated against FND_LOOKUPS lookup type OKS_SUB_TYPE.
• MEDIA_TYPE — validated against lookup type OKS_MED_PRTY_TYPE.
• ITEM_TYPE — item type for the subscription.
• STATUS — subscription status ('A'ctive or 'I'nactive).
• FREQUENCY — billing cadence ('Y'early, 'M'onthly, 'W'eekly, 'D'aily).
• FULFILLMENT_CHANNEL, OFFSET, and the ORIG_SYSTEM_*/UPG_ORIG_SYSTEM_* columns, which support fulfillment attributes and legacy/origin-system traceability during upgrades.
• Standard audit columns — OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID.

Common Use Cases and Queries

Typical reporting scenarios separate template definitions from instantiated subscriptions. To list all reusable templates:

SELECT id, subscription_type, frequency, status FROM oks.oks_subscr_header_b WHERE dnz_chr_id = -1;

To find the instantiated subscription for a specific contract header or line, join on DNZ_CHR_ID or CLE_ID:

SELECT b.id, b.cle_id, b.instantiation_dt FROM oks.oks_subscr_header_b b WHERE b.cle_id = :contract_line_id;

For item-instance-driven reporting, filter on INSTANCE_ID, which is indexed by OKS_SUBSCR_HEADER_B_N3. Operational users query this table to validate active subscriptions by joining to lookup views for SUBSCRIPTION_TYPE and MEDIA_TYPE, and to assess fulfillment configuration through FULFILLMENT_CHANNEL and OFFSET. Because the physical design favours template lookups on DNZ_CHR_ID = -1 and line lookups through CLE_ID, queries should include those predicates to leverage the available indexes.

Related Objects

• OKS.OKS_SUBSCR_PATTERNS — references this table via OSH_ID.
• OKS.OKS_SUBSCR_ELEMENTS — references this table via OSH_ID; stores the element-level attributes of each subscription.
• OKC.OKC_K_LINES_B — referenced by CLE_ID; the contract line owning the instantiated subscription.
• CSI.CSI_ITEM_INSTANCES — referenced by INSTANCE_ID; the item instance linked to the subscription.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for multi-org security.
• OKC_OKS_SUBSCRIPTIONS and related OKS service-contract APIs — used to create contract lines from subscription templates and instantiate header/element records.