Results for “csc_plan_lines”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, CSC.CSC_PLAN_LINES is a Customer Care (CSC) module table that stores the individual plan line details belonging to plan templates persisted in CSC_PLAN_HEADERS_B. It functions as the child entity that expands each plan template (header) into one or more component lines, where each line associates a specific condition or entitlement defined in the Oracle Knowledge Center (OKC) schema. This parent-child structure supports subscription, service plan, and entitlement modeling used by Customer Care and its downstream service and contract flows.

Column-inventory metrics describe CSC_PLAN_LINES as a link table that connects it to related entities. Heuristically, this suggests the table behaves as a link/association between the plan header and the condition header, with a limited set of descriptive and administrative attributes. In a Data Vault model, PLAN_ID and CONDITION_ID would form the natural composite business key resolved to the surrogate LINE_ID.

Key Information Stored

The table contains 29 documented columns. The most significant are:

• LINE_ID — Surrogate primary key (CSC_PLAN_LINES_PK) uniquely identifying each plan line.
• PLAN_ID — Foreign key to CSC_PLAN_HEADERS_B, identifying the parent plan template.
• CONDITION_ID — Foreign key to OKC_CONDITION_HEADERS_B, specifying the condition/entitlement attached to the line.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data access control.
• SEEDED_FLAG — Indicates whether the line is a seeded (delivered) or user-defined record.
• APPLICATION_ID — Identifies the owning application context.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — DFF (Descriptive Flexfield) columns for extensible customer-defined data.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns for audit tracking.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching (Edition-Based Redefinition).

Two unique indexes define business-key candidates: CSC_PLAN_LINES_U1 (LINE_ID, ZD_EDITION_NAME) and CSC_PLAN_LINES_U2 (PLAN_ID, CONDITION_ID, ZD_EDITION_NAME). The latter enforces that a given condition appears only once per plan template, distinguishing the composite business key from the surrogate primary key.

Common Use Cases and Queries

Typical scenarios include retrieving all conditions attached to a plan template, reporting on seeded versus custom plan lines, and joining plan data to OKC condition details for entitlement analysis.

Sample query listing plan lines with their conditions:

• SELECT l.LINE_ID, l.PLAN_ID, l.CONDITION_ID, l.SEEDED_FLAG FROM CSC.CSC_PLAN_LINES l WHERE l.PLAN_ID = :plan_id;

Join to the OKC condition header for descriptive reporting:

• SELECT h.PLAN_ID, c.CONDITION_ID, c.NAME FROM CSC.CSC_PLAN_LINES l JOIN CSC.CSC_PLAN_HEADERS_B h ON l.PLAN_ID = h.PLAN_ID JOIN OKC.OKC_CONDITION_HEADERS_B c ON l.CONDITION_ID = c.CONDITION_ID;

Reporting often filters on SEEDED_FLAG = 'Y' to isolate Oracle-delivered plan lines, and on SECURITY_GROUP_ID to respect data partitioning.

Related Objects

The most significant related objects, per documented foreign keys and dependencies, include:

• CSC_PLAN_HEADERS_B — Parent plan template table; joined via CSC_PLAN_LINES.PLAN_ID.
• OKC_CONDITION_HEADERS_B — Condition/entitlement header; joined via CSC_PLAN_LINES.CONDITION_ID. This is the relationship surfaced by the user's search for okc_condition_headers_b.
• FND_SECURITY_GROUPS — Security group reference via SECURITY_GROUP_ID.
• CSC_PLAN_HEADERS_TL and OKC_CONDITION_HEADERS_TL — Translation tables typically paired with the _B base tables for multilingual reporting.
• CSC_PLAN_LINES_PK and the unique indexes CSC_PLAN_LINES_U1/U2 — Constraint objects that govern uniqueness and integrity.