Search Results txn_group_id




Overview
Explore in AI Chat

Overview

OKS_ENT_TXN_GROUPS_V is a Service Contracts (OKS) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of transaction groups that fall under a given coverage line, where a "transaction group" is modeled as a contract line of specific line styles residing beneath a coverage line. In practical terms, the view flattens the multi-level structure of a service contract — service line, coverage line, and the transaction group line beneath it — into a single denormalized row that joins coverage identity, business process classification, and effective dates together.

The view is primarily consumed by entitlement processing logic. The OKS_ENTITLEMENTS_PVT package, which resolves whether a given transaction is covered by a contract, relies on this shape of data to determine which transaction groups are valid within a coverage window. Because it presents coverage-to-transaction-group relationships with start and end dates, it is equally useful as a reporting source for coverage audits, contract line hierarchies, and integration extracts that need to publish covered business processes to external systems.

Underlying Base Objects

The documented base objects referenced by the view are OKC_K_LINES_B, OKC_K_ITEMS, OKS_K_LINES_B, OKX_BUS_PROCESSES_V, and the OKS_ENTITLEMENTS_PVT package. The view text joins OKC_K_LINES_B three times, aliased SV (service line), CV (coverage line), and KL (transaction group line, which supplies TXN_GROUP_ID from its ID column). The join path is SV.ID = CV.CLE_ID and CV.ID = KL.CLE_ID, establishing the parent-child chain from service line to coverage line to transaction group line. The predicate KL.LSE_ID IN (3, 16, 21) restricts the transaction group lines to the line styles that qualify as transaction groups.

OKC_K_ITEMS is joined on KL.ID = IT.CLE_ID, and the item's OBJECT1_ID1 and OBJECT1_ID2 columns are matched against OKX_BUS_PROCESSES_V to resolve the business process. The IDs are returned as BUSINESS_PROCESS_ID and the name as BUSINESS_PROCESS_NAME. OKS_K_LINES_B is documented as a referenced synonym, reflecting the OKS-side line structures that parallel the OKC contract lines. OKS_ENTITLEMENTS_PVT is the entitlement engine that consumes the same coverage and transaction group relationships at runtime.

Key Columns

  • TXN_GROUP_ID — Identifier of the transaction group line, sourced from OKC_K_LINES_B.ID for the qualifying line styles. This is the column most frequently searched by users.
  • COVERAGE_ID — Identifier of the parent coverage line (OKC_K_LINES_B.CLE_ID for the coverage alias).
  • BUSINESS_PROCESS_ID — Identifier of the business process associated with the transaction group, derived from OKX_BUS_PROCESSES_V.ID1.
  • BUSINESS_PROCESS_NAME — Descriptive name of that business process, useful for direct reporting without a further join.
  • START_DATE — Effective start date of the coverage line on which the transaction group depends.
  • END_DATE — Effective end date of the coverage line.
  • BILLING_PROFILE_ID — Exposed but populated as NULL in the view definition, retained for interface compatibility.

Common Use Cases and Queries

Typical uses include identifying every transaction group attached to a coverage, listing covered business processes for a contract, and validating entitlement windows during integration or reconciliation. A direct lookup by transaction group identifier is the most common access pattern:

  • SELECT txn_group_id, coverage_id, business_process_name, start_date, end_date FROM oks_ent_txn_groups_v WHERE txn_group_id = :p_txn_group_id;
  • SELECT coverage_id, txn_group_id, business_process_name FROM oks_ent_txn_groups_v WHERE coverage_id = :p_coverage_id;
  • SELECT txn_group_id, business_process_name FROM oks_ent_txn_groups_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Because BILLING_PROFILE_ID is always NULL, queries should not filter on it. For coverage evaluation requiring entitlement logic beyond the denormalized view, OKS_ENTITLEMENTS_PVT remains the authoritative source.