Search Results chk_trx_factor

Overview

APPS.CN_CHK_PLAN_ELEMENT_PKG is a validation and lookup package within the Oracle E-Business Suite Incentive Compensation (CN) module. Its role is to validate the constituent elements of a compensation plan before they are persisted or processed, and to resolve the surrogate keys and derived attributes those elements depend on. The package operates under AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the calling schema rather than the package owner, which is consistent with its position as an internal validation utility invoked from the Incentive Compensation application layer.

The header comment ($Header: cnchkpes.pls 120.4 2005/09/14) and the revision note of 1999-07-19 indicate this is long-standing core EBS logic that has evolved with the product. The declared record type pe_rec_type (plan element record) shows the breadth of attributes the package reasons about: quota name, quota id, description, start and end periods, start and end dates, quota status, interval type, payee assignment and vesting flags, quota type, transaction group, target, payment amount, calculation formula, quota rule, credit type, and incentive type. Notably, several fields are initialized to the FND_API sentinel values g_miss_char, g_miss_num, and g_miss_date, which is the standard Oracle API convention for distinguishing "not supplied" from an explicit NULL.

Key Procedures and Functions

The package exposes 34 documented procedures and functions, which fall into two broad categories:

• Validation routines: VALID_RATE_TABLE, VALID_DISC_RATE_TABLE, VALIDATE_ORG_ID, VALID_REVENUE_CLASS, and CHK_TRX_FACTOR verify that referenced configuration such as rate schedules, discount rate tables, operating units, revenue classes, and transaction factors are valid and usable in the current context.
• Plan element checkers: CHK_DR_MAN_PE, CHK_REVENUE_QUOTA_PE, CHK_UNIT_QUOTA_PE, CHK_REVENUE_NON_QUOTA_PE, CHK_UNIT_NON_QUOTA_PE, and CHK_DISCOUNT_MARGIN_PE validate plan elements by incentive category — direct/management, revenue quota, unit quota, revenue non-quota, unit non-quota, and discount margin. These correspond to the plan element types supported by Incentive Compensation.
• Getter functions: GET_QUOTA_ID, GET_CALC_FORMULA_NAME, GET_CALC_FORMULA_ID, GET_CREDIT_TYPE, GET_INTERVAL_NAME, GET_QUOTA_RULE_ID, GET_UPLIFT_START_DATE, GET_QUOTA_RULE_UPLIFT_ID, and GET_RT_QUOTA_ASGN_ID resolve names to identifiers and derive dependent attributes such as uplift start dates and quota rule uplift identifiers.

Tables Accessed

The package reads and validates against the core Incentive Compensation configuration and assignment tables via APPS synonyms. CN_QUOTAS is the central entity, supplying quota definitions and the source columns for pe_rec_type; CN_QUOTA_RULES and CN_QUOTA_RULE_UPLIFTS supply rule and uplift configuration, and CN_QUOTA_ASSIGNS and CN_RT_QUOTA_ASGNS link quotas to payees and rate tables. CN_CALC_FORMULAS and CN_RT_FORMULA_ASGNS provide formula definitions and their rate-table assignments; CN_CREDIT_TYPES, CN_REVENUE_CLASSES, CN_INTERVAL_TYPES, and CN_TRX_FACTORS provide the classification and interval metadata used in validation. CN_RATE_SCHEDULES and CN_COMP_PLANS support plan-level and rate-level checks. PLITBLM (the Incentive Compensation plan element interface table) is referenced for bulk or interface-driven validation.

Usage Notes

This package is invoked primarily from the Incentive Compensation setup and plan element maintenance flows — typically the compensation plan and plan element forms — and from any batch process that stages plan elements through PLITBLM before committing them. Because it is referenced by 14 other packages, it also functions as a shared internal service layer for quota and formula resolution rather than as a standalone user-facing API (its ETRM classification is OTHER). The g_miss_date and g_miss_char conventions mean callers can pass partial records and rely on the checkers to validate only supplied attributes. The user search term "chk_miss_date_para" reflects this sentinel-driven design pattern. Customizations should call the getter and CHK_* routines rather than duplicating their lookup logic, since they encode the current validity rules for quotas, formulas, credit types, intervals, and uplifts.