Search Results csc_customized_plans




Overview

The CSC_CUSTOMIZED_PLANS table is a core data object within the Oracle E-Business Suite Customer Care (CSC) module. It serves as the central repository for storing the association between a customer and a specific service or support plan that has been tailored to their requirements. This table is fundamental for managing customer entitlements, service contracts, and support agreements, enabling organizations to track which customized plans are assigned to which customers or customer accounts. Its role is to maintain the critical link between the master plan definition and the party or account that subscribes to it, forming a key component of the service lifecycle management functionality in EBS.

Key Information Stored

While the provided metadata does not list all columns, the documented foreign key relationships explicitly identify the most critical fields. The primary key column, ID, uniquely identifies each customer-plan association record. The table stores three essential foreign key references: PLAN_ID links to the CSC_PLAN_HEADERS_B table, identifying the specific plan template or definition. PARTY_ID references the HZ_PARTIES table, associating the plan with an individual or organization in the Trading Community Architecture (TCA) model. CUST_ACCOUNT_ID references the HZ_CUST_ACCOUNTS table, allowing the plan to be linked at the more granular customer account level. This structure supports flexible assignment of customized plans to either a party or a specific account.

Common Use Cases and Queries

A primary use case is generating reports on customer entitlements to determine service eligibility. Support agents frequently query this table to verify a customer's active, customized support plan when logging a service request. Another common scenario is analyzing plan adoption by customer segment. Sample SQL patterns often involve joins to the related TCA tables to retrieve customer names and details. For example, a basic query to list all customized plans with customer information would be:

  • SELECT ccp.id, ccp.plan_id, ph.plan_name, hp.party_name, hca.account_number FROM csc_customized_plans ccp, csc_plan_headers_b ph, hz_parties hp, hz_cust_accounts hca WHERE ccp.plan_id = ph.plan_id AND ccp.party_id = hp.party_id AND ccp.cust_account_id = hca.cust_account_id(+);

Data from this table is also crucial for integration with other modules like Service Contracts (OKS) and Depot Repair (CSD).

Related Objects

The table maintains documented foreign key relationships with several key EBS entities, as per the provided metadata. These relationships are critical for data integrity and application logic:

  • CSC_PLAN_HEADERS_B: Joined via CSC_CUSTOMIZED_PLANS.PLAN_ID. This is the master definition table for service plans.
  • HZ_PARTIES: Joined via CSC_CUSTOMIZED_PLANS.PARTY_ID. This TCA table stores the master record for a person or organization.
  • HZ_CUST_ACCOUNTS: Joined via CSC_CUSTOMIZED_PLANS.CUST_ACCOUNT_ID. This TCA table stores specific customer account information linked to a party.

As the child table in these relationships, CSC_CUSTOMIZED_PLANS depends on the existence of records in these parent tables. Its primary key, CSC_CUSTOMIZED_PLANS_PK (ID), is likely referenced by other child tables within the CSC module, such as those storing plan details or service line items.