Search Results cn_pmtplan_pub




Overview
Explore in AI Chat

Overview

The APPS.CN_PMTPLAN_PUB package body is the public Application Programming Interface (API) layer of the Oracle E-Business Suite Channel Revenue Management (formerly Trade Management) payment plan module. Its primary business function is to provide a controlled, validated, and multi-organization–aware mechanism for creating, maintaining, and removing payment plans (CN_PMT_PLANS) used in channel partner compensation and rebate settlement processing. The PUBLIC designation signals that the package is intended to be called by external consumers — forms, concurrent programs, workflows, or custom extensions — as opposed to the private implementation package CN_PMTPLAN_PVT, which carries the actual business logic. This separation of public and private APIs is a standard Oracle EBS design pattern: the _PUB body orchestrates validation, message handling, logging, and transactional boundaries, then delegates to the _PVT counterpart.

Key Procedures and Functions

The documented API surface exposes three core procedures, all named following standard EBS DML verb conventions:

  • CREATE_PMTPLAN — Inserts a new payment plan record into the CN_PMT_PLANS table and its associated _S (sequence-generated primary key) table. It accepts plan attributes, performs validation, seeds the surrogate key, and returns the newly created identifier to the caller.
  • UPDATE_PMTPLAN — Modifies existing plan attributes on a persisted payment plan. It enforces concurrency and referential integrity checks before committing changes, and is typically invoked after a plan has been queried and edited in the Oracle Forms UI.
  • DELETE_PMTPLAN — Logically or physically removes a payment plan. Deletion typically includes business-rule validation to prevent removal of plans that are already referenced by downstream payment, claim, or settlement transactions.

The metadata reports a total of six documented procedures/functions; the excerpt lists the three principal DML operations. All three follow Oracle's error-stack convention, raising exceptions through FND_MSG_PUB and the standard FND_API result structure.

Tables Accessed

The package body reads and writes the following documented tables, accessed via APPS synonyms:

  • CN_PMT_PLANS / CN_PMT_PLANS_S — the payment plan header table and its sequence table; the primary DML targets for all three procedures.
  • CN_CREDIT_TYPES — validates the credit type associated with a plan.
  • CN_INTERVAL_TYPES and CN_INTERVAL_TYPES_ALL_TL — validate the payment interval and retrieve its translated description.
  • DUAL — used for scalar lookups and sequence fetches.

Dependencies further confirm use of CN_PMTPLAN_PVT (private logic), FND_API, FND_GLOBAL, FND_LOG, FND_MESSAGE, FND_MSG_PUB, and MO_GLOBAL for multi-org initialization — indicating the API is legal-entity/operating-unit aware.

Usage Notes

Although CN_PMTPLAN_PUB is not referenced by any other database object (zero incoming dependencies), it is invoked at runtime by the Channel Revenue Management payment plan maintenance form, by concurrent programs that generate or adjust payment plans in bulk, and by custom integrations requiring programmatic plan creation. Callers should initialize the multi-org context via MO_GLOBAL and invoke the API inside a standard FND_API transaction, checking the returned message list for errors. The absence of inbound dependencies and the user search term "cn_pmt_plans_s" suggests the package is commonly discovered through its underlying tables rather than direct package references.