Search Results cn_pmt_plans_all




Overview

The CN_PMT_PLANS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Incentive Compensation module (CN). It serves as the master repository for all payment plan definitions. A payment plan is a fundamental construct that governs how compensation is calculated and disbursed to sales personnel. It defines the rules, schedules, and parameters for payments, directly linking sales performance, as tracked through credits, to monetary rewards. The table's "ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by the ORG_ID column to support complex enterprise structures. As the primary source of payment plan metadata, this table is integral to the configuration and execution of the compensation engine.

Key Information Stored

The table stores the defining attributes for each unique payment plan. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal critical data points. The primary key, PMT_PLAN_ID, uniquely identifies each plan. A significant foreign key, CREDIT_TYPE_ID, links the payment plan to a specific credit type defined in the CN_CREDIT_TYPES_ALL_B table. This establishes which category of sales transaction (e.g., new booking, renewal) the plan applies to. Other typical columns in such a table would include the plan name (NAME), a description (DESCRIPTION), effective start and end dates (START_DATE, END_DATE), the calculation method, payment frequency, and status. The ORG_ID column is essential for identifying the operating unit to which the plan belongs.

Common Use Cases and Queries

This table is central to administrative setup, operational reporting, and transactional processing. Common use cases include configuring compensation plans during implementation, generating lists of active plans for sales management, and auditing plan assignments. A typical reporting query would join to credit type and organization tables to provide a comprehensive view. For example, to list all active payment plans for a specific operating unit:

  • SELECT pp.name, pp.pmt_plan_id, ct.name credit_type, pp.start_date, pp.end_date
  • FROM cn_pmt_plans_all pp, cn_credit_types_all_b ct
  • WHERE pp.credit_type_id = ct.credit_type_id
  • AND pp.org_id = :org_id
  • AND SYSDATE BETWEEN pp.start_date AND NVL(pp.end_date, SYSDATE);

Data from this table is also frequently accessed by the compensation engine's calculation processes to determine the applicable rules when processing earned credits.

Related Objects

The CN_PMT_PLANS_ALL table sits at the center of a key data model within Incentive Compensation. Based on the documented foreign key relationships:

  • References (Outbound): The table references CN_CREDIT_TYPES_ALL_B via the CREDIT_TYPE_ID column. This join determines the type of sales credit to which the payment plan applies.
  • Referenced By (Inbound): The table is referenced by CN_SRP_PMT_PLANS_ALL via the PMT_PLAN_ID column. This is a critical mapping table that associates payment plans with specific sales resources (SRP), defining which plans are assigned to which salespeople.

This relationship chain—from credit type to payment plan to salesperson assignment—forms the backbone of the compensation rule hierarchy. Understanding these joins is essential for any data extraction or integration effort involving compensation plans.