Search Results csc_cust_plans_pvt
Overview
The APPS.CSC_CUST_PLANS_PVT package body is the private implementation layer of the Customer Plans API within Oracle E-Business Suite. It belongs to the Customer Care (CSC) product family and supports the storage, maintenance, and lifecycle management of customer-specific plans — records that associate a trading partner or customer organization with one or more plan headers defined in CSC_PLAN_HEADERS_B. In Oracle EBS 12.1.1 and 12.2.2, this package functions as the internal engine behind the public CSC_CUST_PLANS_PKG package, exposing the business logic used by callers while keeping cursor logic, validation, and DML statements private.
The package is documented with an API classification of PVT, confirming that it is intended for internal invocation rather than direct customer integration. Its dependency list includes FND_API, FND_MSG_PUB, FND_MESSAGE, FND_GLOBAL, and APP_EXCEPTION, indicating that all error handling, message stacking, and multi-org context resolution follow the standard Oracle Application Object Library (AOL) API conventions. The package is marked VALID and is referenced by three other database objects.
Key Procedures and Functions
The package body documents sixteen procedures and functions that together provide full CRUD and validation coverage for customer plan records:
- CREATE_CUST_PLANS — Creates a new customer plan association between a party and a plan header, applying default values and initial status.
- UPDATE_CUST_PLANS — Modifies an existing customer plan record, typically used for attribute and status changes.
- ENABLE_PLAN — Activates a customer plan, transitioning it to an active status.
- DISABLE_PLAN — Deactivates a customer plan without deleting the record.
- DELETE_CUST_PLANS — Removes a customer plan record from the repository.
- UPDATE_FOR_CUSTOMIZED_PLANS — Provides a controlled path to update plans that have been customized, respecting customization protection rules.
- GET_CUST_PLAN_ID — Retrieves the unique identifier for a customer plan based on its defining attributes.
- VALIDATE_CUST_PLAN_ID — Confirms that a supplied customer plan ID exists and is usable.
- VALIDATE_PLAN_ID — Verifies that a referenced plan header ID is valid.
- VALIDATE_PARTY_ID — Confirms that the party identifier corresponds to a valid record in
JTF_PARTIES_ALL_V. - VALIDATE_CUST_ACC_ORG_ID — Validates the customer account organization identifier associated with a plan.
- VALIDATE_MANUAL_FLAG — Ensures the manual flag indicator carries an allowed value.
- VALIDATE_PLAN_STATUS_CODE — Checks the plan status against the lookup values defined in
CSC_LOOKUPS. - VALIDATE_CSC_CUST_PLANS — Performs the consolidated validation routine invoked before insert or update operations.
The two remaining documented entries support wrapping and record-type handling consistent with the AOL API standard. Each routine uses FND_MSG_PUB for message stacking and raises APP_EXCEPTION on failure, allowing callers to surface user-friendly errors.
Tables Accessed
The package reads and writes the following base tables through APPS synonyms:
- CSC_CUST_PLANS — The primary customer plan table, holding the association between a party and a plan header along with status and flag attributes. This is the central DML target.
- CSC_PLAN_HEADERS_B — The plan header base table, referenced during validation and lookup of plan definitions.
- CSC_LOOKUPS — The lookup table used to validate status codes and flag values.
- PLITBLM — A standard Oracle Applications PL/SQL table indexed by binary_integer and positive, used internally for message and record buffering.
- JTF_PARTIES_ALL_V — A view used to confirm that a supplied party identifier resolves to a valid trading partner record.
The package also depends on CSC_CUST_PLANS_AUDIT_PKG, suggesting that audit trail records are written to companion audit tables during create, update, and delete operations.
Usage Notes
Because CSC_CUST_PLANS_PVT is a PVT package, it should not be invoked directly by custom code. Instead, callers should invoke the corresponding public package CSC_CUST_PLANS_PKG, which delegates to this private body after performing standard API wrapper duties. In Oracle EBS 12.1.1 and 12.2.2, this package is typically exercised by the Customer Care plan setup forms, by concurrent programs that mass-maintain customer plan assignments, and by other CSC product packages that need to resolve or validate customer plan data.
Custom integrations that require customer plan maintenance should reference the public API and rely on the FND_MSG_PUB message stack to retrieve error details. Direct DML against CSC_CUST_PLANS should be avoided, as the private validation and audit logic in this package enforces data integrity rules that bypassing it would circumvent. The package is not referenced by any database object, and its only external references flow through the public wrapper layer.
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_CUST_PLANS_PVT, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_PVT, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_CUST_PLANS_PVT, status:VALID,
-
PACKAGE: APPS.CSC_CORE_UTILS_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_CORE_UTILS_PVT, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_AUDIT_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_AUDIT_PKG, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_PKG, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_PKG, status:VALID,
-
PACKAGE: APPS.CSC_CORE_UTILS_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_CORE_UTILS_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
SYNONYM: APPS.CSC_PLAN_HEADERS_B
12.1.1
owner:APPS, object_type:SYNONYM, object_name:CSC_PLAN_HEADERS_B, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE: APPS.CSC_CUST_PLANS_AUDIT_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_CUST_PLANS_AUDIT_PKG, status:VALID,
-
PACKAGE: APPS.CSC_RELATIONSHIP_PLANS_PUB
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_RELATIONSHIP_PLANS_PUB, status:VALID,
-
PACKAGE: APPS.CSC_RELATIONSHIP_PLANS_PUB
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_RELATIONSHIP_PLANS_PUB, status:VALID,
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_CUST_PLANS_PUB, status:VALID,
-
PACKAGE: APPS.CSC_RELATIONSHIP_PLANS_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CSC_RELATIONSHIP_PLANS_PVT, status:VALID,
-
PACKAGE: APPS.CSC_RELATIONSHIP_PLANS_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CSC_RELATIONSHIP_PLANS_PVT, status:VALID,
-
SYNONYM: APPS.CSC_PLAN_HEADERS_B
12.2.2
owner:APPS, object_type:SYNONYM, object_name:CSC_PLAN_HEADERS_B, status:VALID,
-
SYNONYM: APPS.CSC_CUST_PLANS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:CSC_CUST_PLANS, status:VALID,
-
SYNONYM: APPS.CSC_CUST_PLANS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:CSC_CUST_PLANS, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.CSC_RELATIONSHIP_PLANS_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_RELATIONSHIP_PLANS_PVT, status:VALID,
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_CUST_PLANS_PUB, status:VALID,
-
PACKAGE BODY: APPS.CSC_RELATIONSHIP_PLANS_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_RELATIONSHIP_PLANS_PUB, status:VALID,
-
PACKAGE BODY: APPS.CSC_RELATIONSHIP_PLANS_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_RELATIONSHIP_PLANS_PUB, status:VALID,
-
PACKAGE BODY: APPS.CSC_RELATIONSHIP_PLANS_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CSC_RELATIONSHIP_PLANS_PVT, status:VALID,
-
VIEW: APPS.CSC_LOOKUPS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:CSC.CSC_LOOKUPS, object_name:CSC_LOOKUPS, status:VALID,
-
VIEW: APPS.CSC_LOOKUPS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:CSC.CSC_LOOKUPS, object_name:CSC_LOOKUPS, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_RELATIONSHIP_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
VIEW: APPS.JTF_PARTIES_ALL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_PARTIES_ALL_V, object_name:JTF_PARTIES_ALL_V, status:VALID,
-
PACKAGE: APPS.CSC_CUST_PLANS_PVT
12.2.2
-
APPS.CSC_CUST_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_CUST_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
VIEW: APPS.JTF_PARTIES_ALL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_PARTIES_ALL_V, object_name:JTF_PARTIES_ALL_V, status:VALID,
-
APPS.CSC_RELATIONSHIP_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_RELATIONSHIP_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_CUST_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
APPS.CSC_CUST_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
APPS.CSC_RELATIONSHIP_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
APPS.CSC_RELATIONSHIP_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
APPS.CSC_RELATIONSHIP_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_RELATIONSHIP_PLANS_PVT dependencies on CSC_CUST_PLANS_PVT
12.1.1
-
APPS.CSC_RELATIONSHIP_PLANS_PUB dependencies on CSC_CUST_PLANS_PVT
12.2.2
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PVT
12.1.1
-
PACKAGE BODY: APPS.CSC_CUST_PLANS_PVT
12.2.2
-
eTRM - CSC Tables and Views
12.1.1
description: Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown ,
-
APPS.CSC_CUST_PLANS_PVT dependencies on CSC_CUST_PLANS
12.1.1