Search Results cov_start_date

Overview

APPS.CS_CONTRACT_COVERAGES_V is a VALID view in the Oracle E-Business Suite Applications (APPS) schema, owned by APPS and registered in FND Design Data as CS.CS_CONTRACT_COVERAGES_V. It exposes contract coverage information drawn from the Oracle Service (CS) and Oracle Knowledge/Service entitlement (OKS) data model, presenting a denormalized projection that joins contract header attributes with the specific coverages, transaction groups, and business processes associated with a service contract. Because the view consolidates contract-level identifiers (such as ORG_ID, CONTRACT_ID, and CONTRACT_NUMBER) alongside coverage-level attributes (COVERAGE_ID, COVERAGE_NAME, COV_START_DATE, and COV_END_DATE), it is primarily intended for reporting, inquiry, and integration scenarios in which a single record must associate a coverage line with its parent service contract.

The view is documented as Internal and is annotated with an Oracle warning stating that access to Oracle applications data through this object is not supported except from standard Oracle Applications programs. It should therefore be treated as an internal, read-only construct used by Oracle application code and not as a supported public API. In Oracle EBS 12.1.1 and 12.2.2 this behavior is consistent, though the underlying OKS entitlement view definitions may differ slightly between releases.

Underlying Base Objects

The documented references for APPS.CS_CONTRACT_COVERAGES_V are:

• OKS_ENTITLEMENTS_PVT (PACKAGE)
• OKS_ENT_COVERAGES_V (VIEW)
• OKS_ENT_HEADERS_V (VIEW)
• OKS_ENT_TXN_GROUPS_V (VIEW)
• OKS_ENT_UTIL_PVT (PACKAGE)

Functionally, the view composes entitlement header, coverage, and transaction group information. OKS_ENT_HEADERS_V supplies the contract header context, including organization, contract identity, party, and contract active dates. OKS_ENT_COVERAGES_V supplies the coverage rows and their coverage active dates and names. OKS_ENT_TXN_GROUPS_V contributes transaction group linkage (TXN_GROUP_ID) and the related business process reference. The packages OKS_ENTITLEMENTS_PVT and OKS_ENT_UTIL_PVT are referenced utility APIs used by the entitlement model; they are not queried as data sources but are cited as dependencies of the view's defining logic. No direct base table names appear in the excerpted metadata, so all column semantics are described as inherited from these documented dependent objects.

Key Columns

• ORG_ID — Operating unit identifier; the multi-org partitioning attribute for the contract record.
• CONTRACT_ID / CONTRACT_NUMBER — Unique identifier and human-readable number of the service contract.
• PARTY_ID — The customer or party with whom the contract is held.
• CON_START_DATE_ACTIVE / CON_END_DATE_ACTIVE — The active date range of the contract itself; these are the columns referenced by queries searching for "con_start_date_active".
• BILL_TO_SITE_USE_ID / SHIP_TO_SITE_USE_ID — Site-use identifiers for the billing and shipping locations.
• PRICE_LIST_ID / CURRENCY_CODE — Pricing and currency context for the contract.
• COVERAGE_ID / COVERAGE_NAME — Identifier and descriptive name of the individual coverage.
• COV_START_DATE / COV_END_DATE — Effective date range for the specific coverage, distinct from the contract-level active dates.
• TXN_GROUP_ID / BUSINESS_PROCESS_ID — Transaction group and associated business process for the coverage.
• EXCEPTION_COVERAGE_FLAG — Indicates whether the coverage is an exception coverage.

Common Use Cases and Queries

A typical use is to locate contracts whose active start date falls within a reporting window, and to report the coverages attached to each. The following query selects contract and coverage timing information:

SELECT contract_number, party_id, con_start_date_active, con_end_date_active, coverage_name, cov_start_date, cov_end_date FROM apps.cs_contract_coverages_v WHERE con_start_date_active BETWEEN :p_start AND :p_end AND org_id = :p_org_id;

Because the view is documented as internal and unsupported for direct access, production integrations should prefer the supported OKS entitlement APIs. The view remains useful for diagnostic queries, data validation, and read-only reporting within a controlled environment.