Search Results cn_period_sets_all

Overview

The CN_PERIOD_SETS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Incentive Compensation module (CN). Its primary role is to store master definitions for period sets, which are fundamental to the calculation and processing of compensation plans. As indicated by the ETRM documentation, this table is specifically utilized by the Oracle Sales Compensation (OSC) engine. The system-generated PERIOD_SET_ID serves as the unique identifier for a logical grouping of accounting or compensation periods, enabling the structured scheduling of plan calculations, quota assignments, and payment processing cycles. Its "ALL" suffix signifies it is a multi-organization enabled table, capable of storing data for multiple operating units.

Key Information Stored

Based on the provided metadata and standard EBS design patterns for such entities, the table's central column is the PERIOD_SET_ID. This is a system-generated numeric primary key that uniquely identifies each period set definition. While the explicit column list is not detailed in the excerpt, typical related columns in a period set master table would include:

• PERIOD_SET_ID: The unique identifier (Primary Key).
• NAME: The user-defined name for the period set (e.g., 'Monthly Calendar', 'Quarterly Fiscal').
• DESCRIPTION: A detailed explanation of the period set's purpose.
• START_DATE / END_DATE: Defines the active date range for the period set.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard EBS audit columns.
• ORG_ID: The operating unit identifier, supporting the multi-org structure.

Common Use Cases and Queries

This table is primarily referenced for setup validation, troubleshooting, and reporting on the foundational period structures in Incentive Compensation. Common scenarios include verifying existing period sets before creating new compensation plans or periods, and diagnosing issues related to period-driven processes. A typical query retrieves the master list of period sets, often joined to related period detail tables.

Sample Query: Retrieving all active period sets for a specific operating unit. SELECT period_set_id, name, description, start_date, end_date FROM cn_period_sets_all WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate) AND org_id = :org_id ORDER BY name;

Reporting Use Case: This table serves as a key dimension in reports analyzing plan performance across different time cycles, allowing compensation administrators to map transactional data (like earnings) to the correct period set structure.

Related Objects

The primary documented relationship for CN_PERIOD_SETS_ALL is via its primary key constraint, CN_PERIOD_SETS_PK, on the PERIOD_SET_ID column. This key is almost certainly referenced by foreign key constraints in child tables that store the detailed periods belonging to each set. While not listed in the brief excerpt, standard related objects in the CN schema would include:

• CN_PERIODS_ALL: The most critical related table. It would contain individual period records (e.g., JAN-2024, FEB-2024) that belong to a period_set_id defined in CN_PERIOD_SETS_ALL.
• CN_QUOTA_ASSIGNMENTS: Likely references period_set_id to assign quotas to specific period cycles.
• CN_COMP_PLANS: May reference a period_set_id to define the calculation frequency for a compensation plan.
• Oracle Sales Compensation (OSC) Engine Objects: Various internal OSC packages and calculation workflows will query this table to determine the valid period structure for processing.

Joins to these related tables typically use CN_PERIOD_SETS_ALL.PERIOD_SET_ID = <child_table>.PERIOD_SET_ID.