Search Results csc_plan_lines




Overview
Explore in AI Chat

Overview

The CSC_PLAN_LINES table is a core data object within the Oracle E-Business Suite Customer Care (CSC) module. It functions as the detail repository for plan templates, which are high-level service or support agreements defined in the CSC_PLAN_HEADERS_B table. This table is essential for managing the granular components, rules, or line items that constitute a complete service plan template. Its role is to store the specific conditions, terms, and details that are applied when a plan is instantiated for a customer, thereby enabling the configuration of complex, multi-line service offerings within the application.

Key Information Stored

While the full column list is not provided in the metadata, the documented foreign key relationships and primary key indicate the critical data elements. The primary identifier for each plan line is the LINE_ID column. Each line is associated with a parent plan template via the PLAN_ID column, which links to CSC_PLAN_HEADERS_B. A significant column is CONDITION_ID, which establishes a relationship with the OKC_CONDITION_HEADERS_B table from the Oracle Contracts Core module. This link is crucial, as it allows plan lines to incorporate formal contractual terms, conditions, and business rules defined in the OKC tables, integrating service plan logic with the enterprise's contract management framework.

Common Use Cases and Queries

Primary use cases involve the creation, inquiry, and reporting of service plan details. Application users typically interact with this data through the Oracle Customer Care front-end forms for maintaining plan templates. Technically, common operations include querying all lines for a specific plan for validation or auditing purposes, and extracting plan details for integration with downstream systems. A typical reporting query would join to the header table to provide context.

Sample SQL Pattern:
SELECT cpl.*
FROM csc.csc_plan_lines cpl
WHERE cpl.plan_id = :p_plan_id
ORDER BY cpl.line_id;

Another critical use case is analyzing the contractual conditions attached to plan lines, requiring a join to the OKC conditions table via the CONDITION_ID to retrieve the associated rule text or logic.

Related Objects

The table maintains defined relationships with other key EBS objects, primarily through foreign key constraints:

  • CSC_PLAN_HEADERS_B: This is the parent table. The relationship is defined as CSC_PLAN_LINES.PLAN_ID → CSC_PLAN_HEADERS_B. This join is fundamental for retrieving the header information for any plan line detail.
  • OKC_CONDITION_HEADERS_B: This table, from the Contracts Core module, stores condition headers. The relationship is defined as CSC_PLAN_LINES.CONDITION_ID → OKC_CONDITION_HEADERS_B. This link integrates service plan specifics with the broader contractual and legal terms managed within Oracle Contracts.

The primary key constraint CSC_PLAN_LINES_PK on LINE_ID ensures the uniqueness of each record within this detail table.