Results for “customized_plan”

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

Overview

The CSC_PLAN_HEADERS_B table is a core transactional and configuration table within the CSC (Customer Care) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the header-level definitions for all plan templates and customized plan templates used by the Customer Care planning functionality. Each row represents a distinct plan, capturing the metadata, activation windows, profile-check bindings, and criteria that determine how a plan is applied to customer accounts and end users. Because the table is the parent of several dependent detail and translation tables, it functions as the anchor object for the CSC planning schema.

From a Data Vault modeling perspective, the FK structure heuristically classifies this table as hub-leaning. The PLAN_ID column acts as the business key around which related detail, audit, and translation satellites cluster, while a self-referencing foreign key on ORIGINAL_PLAN_ID links customized plans back to their source templates. This self-reference is a distinctive feature, enabling plan versioning and customization lineage within a single logical structure.

Key Information Stored

The table exposes 38 documented columns. The most operationally significant include:

• PLAN_ID — surrogate primary key (index CSC_PLAN_HEADERS_B_PK) that uniquely identifies each plan header.
• ORIGINAL_PLAN_ID — self-referencing FK identifying the template from which a customized plan derives.
• PLAN_GROUP_CODE — groups related plans for categorization and lookup.
• START_DATE_ACTIVE / END_DATE_ACTIVE — control the effective date range during which a plan is applicable.
• USE_FOR_CUST_ACCOUNT — flag indicating whether the plan applies to customer accounts.
• CUSTOMIZED_PLAN — flag distinguishing templates from customized instances.
• PROFILE_CHECK_ID — FK to CSC_PROF_CHECKS_B, linking plans to the profile check they enforce.
• RELATIONAL_OPERATOR, CRITERIA_VALUE_HIGH, CRITERIA_VALUE_LOW — define the comparison logic and thresholds applied during plan evaluation.
• SEEDED_FLAG — indicates whether the plan was seeded by Oracle or user-created.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS for multi-org / data security isolation.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrency control.
• ZD_EDITION_NAME — participates in the unique index CSC_PLAN_HEADERS_B_U1 (PLAN_ID, ZD_EDITION_NAME), a business-key candidate associated with editioning.

The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and 15 descriptive ATTRIBUTE columns provide audit and extensibility. The PLAN_ID plus ZD_EDITION_NAME combination is the documented unique key candidate; surrogate uniqueness is enforced by the PK alone.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving active plans for a given date, resolving customized plans to their templates, and auditing plan-to-profile-check bindings.

• List currently active customer-account plans:

  SELECT PLAN_ID, PLAN_GROUP_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE
  FROM   CSC.CSC_PLAN_HEADERS_B
  WHERE  USE_FOR_CUST_ACCOUNT = 'Y'
  AND    SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE;

• Trace customization lineage:

  SELECT c.PLAN_ID, c.ORIGINAL_PLAN_ID, t.PLAN_GROUP_CODE
  FROM   CSC.CSC_PLAN_HEADERS_B c, CSC.CSC_PLAN_HEADERS_B t
  WHERE  c.ORIGINAL_PLAN_ID = t.PLAN_ID;

• Join headers to profile checks for criteria reporting:

  SELECT h.PLAN_ID, p.PROFILE_CHECK_ID, h.RELATIONAL_OPERATOR,
         h.CRITERIA_VALUE_LOW, h.CRITERIA_VALUE_HIGH
  FROM   CSC.CSC_PLAN_HEADERS_B h, CSC.CSC_PROF_CHECKS_B p
  WHERE  h.PROFILE_CHECK_ID = p.PROFILE_CHECK_ID;

These patterns support plan eligibility reporting, security-group-scoped extracts, and reconciliation of template versus customized plan inventories.

Related Objects

The following dependent objects reference CSC_PLAN_HEADERS_B and are most relevant for joins and impact analysis:

• CSC_PLAN_HEADERS_TL — translation table, joined on PLAN_ID; supplies language-specific plan text.
• CSC_PLAN_LINES — detail lines, joined on PLAN_ID.
• CSC_CUST_PLANS and CSC_CUST_PLANS_AUDIT — customer-specific plan instances and audit history, joined on PLAN_ID.
• CSC_CUSTOMIZED_PLANS — customized plan records, joined on PLAN_ID.
• CSC_PROF_CHECKS_B — referenced via PROFILE_CHECK_ID, defining evaluation criteria.
• CSC_PLAN_HEADERS_B (self) — joined via ORIGINAL_PLAN_ID to resolve template ancestry.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.