Search Results update_plan_header




Overview
Explore in AI Chat

Overview

CSC_RELATIONSHIP_PLANS_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that governs the creation, maintenance, and deactivation of relationship plan headers within the Customer Care / TeleSales (CSC) relationship management domain. Relationship plans represent structured interaction strategies applied to customers, contacts, or agents as part of a customer-relationship or telesales engagement model. The package body (source file cscprlpb.pls) encapsulates the business logic required to build and modify those plan headers and to retire them when they are no longer active. The package was originally authored in 1999 by dejoseph and subsequently extended for the 11.5.8 release cycle to support the CT/Agent-facing application, gaining a new END_USER_TYPE parameter across its conversion and header procedures. Because it is classified as a PUB package, its procedures form a supported programmatic interface intended to be called by other Oracle EBS components or customer extensions, rather than being reserved for internal package use.

Key Procedures and Functions

The package exposes three documented procedures, all of which are part of the supported public interface:

  • CREATE_PLAN_HEADER — Creates a new relationship plan header record. It accepts the plan attributes supplied by the caller and persists a plan definition that can subsequently be assigned and administered. As noted in the package history, this procedure was extended for 11.5.8 to include the END_USER_TYPE parameter, allowing the caller to distinguish the end-user context (for example, the CT or agent-facing application).
  • UPDATE_PLAN_HEADER — Modifies an existing relationship plan header. It applies changes to the same set of plan attributes handled by CREATE_PLAN_HEADER and likewise carries the END_USER_TYPE parameter added in the 11.5.8 uptake. This procedure is the supported path for maintaining plan definitions after initial creation.
  • DISABLE_PLAN — Deactivates a relationship plan so that it is no longer available for active use. Rather than deleting the plan record, the procedure performs a controlled disable operation, preserving the plan's history and referential integrity while removing it from active selection. This is the procedure most directly associated with the user search term disable_plan, and it is the supported means of retiring a plan through the public API.

A private conversion routine, convert_columns_to_rec_type, supports these procedures by translating a public CSC_RELATIONSHIP_PLANS record — which may contain either descriptive values or internal identifiers — into a fully resolved private record with all values converted to IDs. This routine is internal to the package body and is not part of the public interface.

Tables Accessed

The package operates against the CSC_RELATIONSHIP_PLANS record structure, which corresponds to the relationship plan header entity. Two supporting tables are documented as referenced through APPS synonyms:

  • FND_LOOKUP_VALUES — The Oracle Application Object Library flexfield lookup table. It is used to resolve and validate lookup-coded values (such as plan types, statuses, or end-user types) maintained as Oracle EBS lookups, converting stored codes to their internal identifiers during the conversion and validation steps.
  • PLITBLM — A PL/SQL index-by table (associative array) type used internally for bulk parameter storage and manipulation. The package history records that NOCOPY changes were made in November 2002, indicating that the PLITBLM structure is passed by reference to improve performance when handling collections of plan data.

No other tables are documented as referenced by this package in the ETRM metadata.

Usage Notes

CSC_RELATIONSHIP_PLANS_PUB is invoked programmatically wherever relationship plan headers must be created, changed, or retired. Typical callers include Customer Care and TeleSales forms, concurrent programs that seed or migrate plan definitions, and custom code extending the CT/Agent-facing application. Because CREATE_PLAN_HEADER, UPDATE_PLAN_HEADER, and DISABLE_PLAN are documented public procedures, they are the correct entry points for custom integrations; the private conversion routine and internal PLITBLM handling should not be called directly.

Callers must be aware of the release-specific interface. In Oracle EBS 11.5.8 and later releases (including 12.1.1 and 12.2.2), the header procedures require the END_USER_TYPE parameter added for the CT/Agent-facing application; code written against pre-11.5.8 signatures will not compile or execute correctly. The package depends on FND_LOOKUP_VALUES for lookup resolution, so callers should ensure the relevant lookup types are configured and active before invoking it. Finally, DISABLE_PLAN should be preferred over any attempt to delete plan records directly, as it preserves plan history and maintains the integrity of downstream references. In 12.2.2, the same public interface remains available under the APPS schema with no documented signature changes beyond those introduced at 11.5.8.