Search Results update_cust_plans

Overview

APPS.CSC_CUST_PLANS_PUB is the public PL/SQL API for maintaining customer plan records stored in the CSC_CUST_PLANS table. It belongs to the Customer Care / Service (CSC) schema and forms part of Oracle EBS's customer relationship management footprint, specifically the component that tracks service plans, entitlements, or contractual coverage associated with a customer account. The package body header (cscpctpb.pls, version 115.13, dated 27-NOV-2002) documents its purpose explicitly: it "contains procedure to insert, update and delete records from CSC_CUST_PLANS table."

The package follows a thin public wrapper pattern. Its procedures accept a public API record, perform conversions and validations, and then delegate the actual database manipulation to a private API invoked at validation level 100 (FULL). This design isolates callers from internal structures and enforces completeness of validation. A notable design decision, recorded in the version history, is the removal of the cust_account_org reference in favor of TCA's decision to drop the org_id column from hz_cust_accounts, reflecting the package's integration with the Trading Community Architecture customer model.

Key Procedures and Functions

• CREATE_CUST_PLANS — Inserts a new customer plan record. Accepts the public record, converts any value-based attributes to their corresponding IDs, and forwards the request to the private API for full validation (level 100) before committing the row.
• UPDATE_CUST_PLANS — Modifies an existing customer plan. This is the procedure most commonly associated with the search term "update_cust_plans." It applies changes to CSC_CUST_PLANS and re-validates the record through the private API. As with all conversions in this package, IDs take precedence over values: if both an ID and a value are supplied for the same attribute, the ID is used, the value is ignored, and a warning message is generated.
• ENABLE_PLAN — Activates a customer plan, making it effective for downstream business processes.
• DISABLE_PLAN — Deactivates a customer plan without deleting it, preserving history while removing the plan from active use.
• DELETE_CUST_PLANS — Removes a customer plan record from CSC_CUST_PLANS through the same validated private API path.

Seven documented program units exist in total, including private conversion routines (public-to-private record translation for values-to-IDs mapping) and their supporting internals. The public procedures rely on the private API for all actual DML.

Tables Accessed

The primary table is CSC_CUST_PLANS, which holds the customer plan rows this package inserts, updates, deletes, and toggles via ENABLE_PLAN and DISABLE_PLAN. The package also interacts with TCA customer tables indirectly: the header history references HZ_CUST_ACCOUNTS and the obsolete CUST_ACCOUNT_ORG construct, confirming that plan records are keyed to a TCA customer account. Per the package comments, all table access occurs via APPS synonyms and through the private API rather than direct DML in the public layer.

Usage Notes

CSC_CUST_PLANS_PUB is the supported entry point for programmatic maintenance of customer plans; the ETRM metadata classifies it as a PUB API and shows no other packages referencing it, indicating it is called externally rather than internally by sibling CSC packages. Typical invocations include Oracle Forms in the Customer Care module, concurrent programs performing bulk plan maintenance, and custom PL/SQL extensions that need to create, modify, enable, disable, or delete customer plan records with full validation. The WHENEVER OSERROR EXIT FAILURE ROLLBACK directive added in the 26-11-2002 revision means the package must be used in a controlled session context — failed OS-level errors abort the session and roll back uncommitted work. Because the public procedures delegate to the private API at validation level 100, callers should expect strict validation and should honor the warning mechanism that reports fields where an ID suppressed a redundant value.