Results for “cust_account_org”

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

Overview

CSC_CUSTOMIZED_PLANS is a transactional table within the CSC (Customer Care) product family of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. The table records the association between a customized service or subscription plan definition and the specific customer entity to which that plan applies. In practical terms, it acts as the customer-facing instantiation layer of a plan: the plan template itself is mastered in CSC_PLAN_HEADERS_B, while CSC_CUSTOMIZED_PLANS captures which party and customer account hold that plan, along with the plan's lifecycle status and the concurrent program context that last touched the row.

The object is owned by the CSC schema and is documented as VALID in the ETRM repository. Its primary key is CSC_CUSTOMIZED_PLANS_PK, defined on the ID column, with a supporting unique index CSC_CUSTOMIZED_PLANS_U1 also on ID. From a heuristic Data Vault modeling perspective, the foreign key topology — four outbound references (PLAN_ID, PARTY_ID, CUST_ACCOUNT_ID, SECURITY_GROUP_ID) radiating from a single primary key — suggests a link classification rather than a hub or satellite. This is a modeling suggestion only; the table is a conventional normalized EBS entity, not a Data Vault artifact.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• ID — Surrogate primary key (CSC_CUSTOMIZED_PLANS_PK). Also carries the unique index CSC_CUSTOMIZED_PLANS_U1, making it the only documented business-key candidate. No alternate unique key on the natural customer/plan combination is documented.
• PLAN_ID — Foreign key to CSC_PLAN_HEADERS_B, identifying the plan header that has been customized for this customer.
• PARTY_ID — Foreign key to HZ_PARTIES, referencing the TCA party (person or organization) that owns or receives the customized plan.
• CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS, tying the plan to a specific customer account within the TCA model.
• CUST_ACCOUNT_ORG — Denormalized operating unit or organization context for the customer account, supporting multi-org filtering without a join.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level security and data partitioning across the CSC application.
• PLAN_STATUS_CODE — Lifecycle state of the customized plan (for example active, inactive, or terminated), driving eligibility and billing logic.
• REQUEST_ID — Concurrent request identifier that created or last updated the row, used for audit and batch traceability.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — Identify the concurrent program application and program responsible for the change.
• PROGRAM_UPDATE_DATE — Timestamp of the last programmatic update, complementing the WHO columns.

Common Use Cases and Queries

Typical scenarios include customer 360 reporting, plan entitlement checks, and reconciliation of customized plans against their parent plan headers. A common pattern joins the table to CSC_PLAN_HEADERS_B and the TCA tables:

• List all customized plans for a party: SELECT ccp.id, ccp.plan_id, ccp.plan_status_code FROM csc_customized_plans ccp WHERE ccp.party_id = :p_party_id;
• Retrieve plans with header detail: join csc_customized_plans ccp to csc_plan_headers_b ph ON ph.plan_id = ccp.plan_id.
• Account-level entitlement: join to hz_cust_accounts hca ON hca.cust_account_id = ccp.cust_account_id.
• Batch audit: filter on request_id or program_update_date to trace changes made by a specific concurrent request.
• Security-scoped extracts must include security_group_id to respect CSC row-level security.

Related Objects

• CSC_PLAN_HEADERS_B — joined via PLAN_ID; source of plan definitions.
• HZ_PARTIES — joined via PARTY_ID; supplies party identity.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; supplies account context.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs row-level access.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID; resolves the concurrent request details.
• FND_APPLICATION and FND_CONCURRENT_PROGRAMS — joined via PROGRAM_APPLICATION_ID and PROGRAM_ID for program metadata.