Results for “cn_pay_groups_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CN_PAY_GROUPS_ALL is a transactional configuration table in the Oracle Incentive Compensation (CN) module, owned by the CN schema. It stores pay group definitions, where a pay group is defined as a set of pay periods within a pay calendar. Pay groups determine the frequency of payment for a salesperson, making this table a foundational element of the compensation disbursement cycle. Each row represents a discrete pay group that can be assigned to participants and referenced by pay runs.

From a Data Vault modeling perspective, the heuristic classification of CN_PAY_GROUPS_ALL is hub-leaning. This suggests the table behaves primarily as a durable reference of business entities (pay groups) keyed by an immutable identifier, with descriptive attributes that could be modeled as a satellite in a pure Data Vault construction. Its multi-org structure, evidenced by the ORG_ID column and the composite unique index CN_PAY_GROUP_U1 (PAY_GROUP_ID, ORG_ID), reinforces its role as a stable, org-scoped reference entity rather than a high-volatility transactional link.

Key Information Stored

The table contains 33 documented columns. The surrogate primary key is PAY_GROUP_ID, enforced through the CN_PAY_GROUPS_PK constraint. A business-key candidate is captured by the unique index CN_PAY_GROUP_U1, which combines PAY_GROUP_ID and ORG_ID, reflecting the multi-organization architecture of EBS 12.1.1 and 12.2.2.

• PAY_GROUP_ID — surrogate primary key uniquely identifying each pay group.
• NAME — user-facing name of the pay group.
• PERIOD_SET_NAME / PERIOD_SET_ID — identifies the accounting period set associated with the pay calendar.
• PERIOD_TYPE / PERIOD_TYPE_ID — defines the period frequency (for example, monthly, semi-monthly, weekly) that governs payment cadence.
• START_DATE / END_DATE — effective date range for the pay group definition.
• PAY_GROUP_DESCRIPTION — free-text description of the pay group.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting row-level data security.
• ORG_ID — operating unit identifier enabling multi-org partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework for concurrent update control.
• ATTRIBUTE1 through ATTRIBUTE15 — DFF (Descriptive Flexfield) columns for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include validating pay group configuration before running incentive compensation pay runs, reporting on payment frequency by operating unit, and joining to pay runs to trace which pay group drove a given disbursement.

Example — list active pay groups for an operating unit:

• SELECT pay_group_id, name, period_type, start_date, end_date FROM cn.cn_pay_groups_all WHERE org_id = :p_org_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

Example — count pay runs per pay group:

• SELECT g.name, COUNT(*) FROM cn.cn_pay_groups_all g, cn.cn_payruns_all r WHERE g.pay_group_id = r.pay_group_id GROUP BY g.name;

Related Objects

• CN_PAYRUNS_ALL — references CN_PAY_GROUPS_ALL via PAYRUNS_ALL.PAY_GROUP_ID = CN_PAY_GROUPS_ALL.PAY_GROUP_ID; links each pay run to its governing pay group.
• CN_SRP_PAY_GROUPS_ALL — references CN_PAY_GROUPS_ALL via SRP_PAY_GROUPS_ALL.PAY_GROUP_ID; associates salespersons with pay groups.
• FND_SECURITY_GROUPS — referenced by CN_PAY_GROUPS_ALL.SECURITY_GROUP_ID; provides data security grouping.
• FND_ORG_ASSIGNMENTS / HR_OPERATING_UNITS — logically related through ORG_ID for operating unit context.
• CN_SRP_* participant tables — indirectly linked through CN_SRP_PAY_GROUPS_ALL for participant-to-pay-group resolution.