Results for “line_start_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view OKS_COVDLEVEL_DETAILS_V belongs to the Service Contracts (OKS) module in Oracle E-Business Suite and resides in the APPS schema. Its documented purpose is to display the service details of a contract, including all covered levels. In practice, the view flattens the hierarchical relationship between a parent service line and its associated sub-lines into a single denormalized result set, allowing reporting tools and integrations to retrieve covered-level detail without navigating the underlying contract line hierarchy manually.

The view is particularly relevant to users who query the LINE_END_DATE column, which is exposed directly from the contract line entity. This makes the view a convenient source for reporting on service line expiry, entitlement windows, and renewal-relevant dates across all covered levels of a service contract. Because the view is defined over contract line data rather than transactional or billing data, it serves as a structural and descriptive reference rather than a financial ledger source.

Underlying Base Objects

The ETRM metadata documents three referenced base objects: OKC_K_LINES_B (a synonym), OKC_K_LINES_V (a view), and OKC_LINE_STYLES_V (a view). The view text joins these as follows:

• OKC_K_LINES_B (aliased SRV) provides the top-level service line. The predicate SRV.CLE_ID IS NULL restricts this alias to parent-level service lines.
• OKC_K_LINES_V (aliased KLIN) provides the covered detail lines, joined via SRV.ID = KLIN.CLE_ID, establishing the parent-to-child relationship.
• OKC_LINE_STYLES_V (aliased LSE) supplies the line style description, joined on LSE.ID = KLIN.LSE_ID.

A restriction limits results to line style IDs 7, 8, 9, 10, 11, 18, 25, and 35, which correspond to the service-related line styles recognized as covered levels. Only combinations satisfying all join and filter conditions appear in the result set.

Key Columns

• CONCATENATED_LINE_NUMBER — A composite identifier formed as SRV.LINE_NUMBER || '.' || KLIN.LINE_NUMBER, useful for displaying hierarchy in reports.
• LINE_NUMBER — The line number of the covered detail line (from KLIN).
• LINE_TYPE — The name of the line style, derived from LSE.NAME.
• LSE_ID — The line style identifier, constrained to the covered-level style set.
• LINE_REF — Corresponds to KLIN.COGNOMEN, the line reference or cognomen value.
• LINE_START_DATE — The effective start date of the covered line (KLIN.START_DATE).
• LINE_END_DATE — The end date of the covered line (KLIN.END_DATE); the primary column of interest for expiry analysis.
• LINE_STATUS — The status code of the line (KLIN.STS_CODE).
• LINE_AMOUNT — The negotiated price of the line (KLIN.PRICE_NEGOTIATED).
• ID, CHR_ID, DNZ_CHR_ID, CLE_ID — Internal identifiers linking the row to its contract header and parent line context.

Common Use Cases and Queries

A typical use case is identifying covered service lines that expire within a given window, which supports renewal campaigns and entitlement reporting. For example:

SELECT concatenated_line_number,
       line_number,
       line_type,
       line_start_date,
       line_end_date,
       line_status,
       line_amount
FROM   apps.oks_covdlevel_details_v
WHERE  line_end_date BETWEEN SYSDATE AND SYSDATE + 90
ORDER  BY line_end_date;

Another common scenario is reviewing all covered levels for a specific contract header by filtering on CHR_ID or DNZ_CHR_ID:

SELECT concatenated_line_number,
       line_type,
       line_status,
       line_end_date
FROM   apps.oks_covdlevel_details_v
WHERE  chr_id = :p_contract_id;

Because the view already resolves the parent-child line relationship and restricts to covered-level styles, it eliminates the need for custom joins between OKC_K_LINES_B, OKC_K_LINES_V, and OKC_LINE_STYLES_V, making it suitable for concurrent programs, BI Publisher reports, and inbound integrations that require contract service detail with associated end dates.