Search Results csc_relationship_plans_pub




Overview
Explore in AI Chat

Overview

The APPS.CSC_RELATIONSHIP_PLANS_PUB package is a public (PUB) PL/SQL API within the Oracle E-Business Suite Customer Relationship Management (CRM) schema. It belongs to the customer relationship management foundation layer that manages customer plans associated with relationships tracked in the CSC (Customer Support/Service) modules. Its primary business purpose is to provide a stable, externally callable interface for creating, updating, and disabling relationship plan headers that describe the plans a customer or organization maintains in relation to other parties.

The package is classified as a public API, meaning it is intended to be invoked by external callers—other application modules, forms, concurrent programs, or custom extensions—rather than being restricted to internal use. It functions as a thin wrapper that delegates core business logic to the private implementation package APPS.CSC_CUST_PLANS_PVT, as confirmed by the dependency listing showing that CSC_RELATIONSHIP_PLANS_PUB references CSC_CUST_PLANS_PVT. This two-tier pattern (public wrapper over a private package) is a standard Oracle EBS design convention that isolates the callable interface from the internal processing logic.

The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, indicating it is a supported component across both release families. It is not referenced by any other packages, which suggests it is a leaf-level API called directly by user-facing or integration components rather than being invoked internally by other PL/SQL code.

Key Procedures and Functions

The ETRM metadata documents five callable program units, of which three are explicitly named procedures:

  • CREATE_PLAN_HEADER — Creates a new relationship plan header record. This procedure is invoked when a new plan is being established for a customer relationship and is responsible for validating and persisting the header-level attributes that define the plan.
  • UPDATE_PLAN_HEADER — Modifies an existing relationship plan header. Used when plan attributes need to be changed after initial creation, such as status changes, date adjustments, or descriptive updates.
  • DISABLE_PLAN — Logically deactivates a relationship plan. Rather than physically deleting the record, this procedure marks the plan as inactive, preserving referential and historical integrity consistent with EBS soft-delete conventions.

The metadata indicates five total program units are documented; the remaining entries are not individually named in the excerpt. No parameter lists are reproduced here, and parameter signatures should be confirmed against the live package specification in the target instance before use.

Tables Accessed

According to the documented metadata, the package references two tables through APPS synonyms:

  • FND_LOOKUP_VALUES — The Oracle Application Object Library lookup values table. It is read to validate or translate coded values such as plan types, statuses, or other flexfield-related codes used during plan processing.
  • PLITBLM — A PL/SQL index-by table type construct used for bulk processing and temporary storage of collections during API execution.

Actual insert, update, and delete operations against the underlying plan tables are performed by the subordinate CSC_CUST_PLANS_PVT package, which holds the data manipulation logic.

Usage Notes

CSC_RELATIONSHIP_PLANS_PUB is typically invoked from CRM application forms, from concurrent programs that process relationship plans in batch, or from custom PL/SQL integration code. Because it is a PUB API, it is the supported entry point for external callers and should be used in preference to calling CSC_CUST_PLANS_PVT directly, ensuring forward compatibility with Oracle upgrades. Callers should perform prerequisite setup, supply valid lookup codes present in FND_LOOKUP_VALUES, and handle the standard EBS API return conventions for success and error messaging.