Search Results con_start_date_active

Overview

CS_CONTRACT_COVERAGES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Service (CS) product family. Its documented purpose is to present a consolidated list of contracts and coverages available to the calling application or report. The view flattens the entitlement model, returning contract header attributes alongside coverage headers and the transaction groups associated with each coverage.

The view is defined as a UNION of two query branches. The first branch joins contract headers, coverages, and transaction groups on the coverage identifier and returns a literal flag of 'N'. The second branch performs the same join, but matches the transaction group coverage identifier against the coverage's exception coverage identifier and returns a literal flag of 'Y'. In both branches contract templates are explicitly excluded through the predicate HDR.CONTRACT_TEMPLATE_YN = 'N'. This design allows a single row set to distinguish standard coverage-to-transaction-group links from exception coverage links without requiring the consumer to write additional logic.

Because the view is a read-only construct that resolves active and terminated entitlement data across contract, coverage, and transaction group level, it is typically used as a data source for customer-facing inquiries, service entitlement validation, and downstream extracts rather than as a transactional interface.

Underlying Base Objects

The view is defined over the following documented objects:

• OKS_ENT_HEADERS_V (VIEW) — supplies the contract header, party, date, site, price list, and currency columns.
• OKS_ENT_COVERAGES_V (VIEW) — supplies the coverage identifier, coverage name, and coverage effective dates.
• OKS_ENT_TXN_GROUPS_V (VIEW) — supplies the transaction group identifier and business process identifier.
• OKS_ENTITLEMENTS_PVT (PACKAGE) — the entitlement engine package underpinning the OKS entitlement views.
• OKS_ENT_UTIL_PVT (PACKAGE) — the entitlement utility package supporting the same view family.

These dependencies confirm that CS_CONTRACT_COVERAGES_V does not read base tables directly; instead it layers interpretative logic on top of the OKS entitlement view family. Each underlying view applies its own date-effectivity and business-rule filtering, so the consumer inherits that logic without re-implementing it.

Key Columns

• ORG_ID — operating unit identifier, used for multi-org security and reporting partitioning.
• CONTRACT_ID / CONTRACT_NUMBER — internal and human-readable contract identifiers.
• PARTY_ID — the party that owns the contract.
• CON_START_DATE_ACTIVE / CON_END_DATE_ACTIVE — the active date range of the contract itself.
• BILL_TO_SITE_USE_ID / SHIP_TO_SITE_USE_ID — bill-to and ship-to site use references.
• PRICE_LIST_ID / CURRENCY_CODE — pricing list and currency context for the contract.
• COVERAGE_ID / COVERAGE_NAME — the coverage (entitlement) identifier and its descriptive name.
• COV_START_DATE / COV_END_DATE — the effective date range of the coverage line.
• TXN_GROUP_ID — the transaction group identifier linking the coverage to a set of transactions; this is the column users most frequently search on when reconciling coverage-to-transaction relationships.
• BUSINESS_PROCESS_ID — identifies the business process associated with the transaction group.
• EXCEPTION_COVERAGE_FLAG — a literal 'N' or 'Y' indicating whether the row originated from the standard coverage join or the exception coverage join.

Common Use Cases and Queries

A frequent scenario is locating every contract and coverage associated with a particular transaction group. Because TXN_GROUP_ID is exposed directly, the query is a simple filtered select:

SELECT contract_number, coverage_id, coverage_name, txn_group_id, business_process_id, exception_coverage_flag FROM cs_contract_coverages_v WHERE txn_group_id = :p_txn_group_id AND org_id = :p_org_id;

Other practical patterns include:

• Reporting all active coverages for a party, filtering on PARTY_ID and comparing SYSDATE against COV_START_DATE and COV_END_DATE.
• Isolating exception coverage linkages by adding WHERE exception_coverage_flag = 'Y'.
• Joining the view to service request or warranty reporting queries to validate that a transaction group falls within a contract's active window.
• Extracting contract and coverage data for downstream data warehouse loading, using ORG_ID as the security predicate.

Because the view already excludes contract templates and resolves both standard and exception paths, callers should not add their own template-exclusion logic; doing so risks implying that unreturned templates exist. All queries should include an ORG_ID predicate to satisfy multi-org access rules and to keep execution plans efficient against the underlying entitlement views.