Results for “cn_calc_sub_validation_u1”

10 results




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

Overview

The table CN.CN_CALC_SUB_VALIDATIONS_ALL is an Oracle E-Business Suite compensation (CN) schema object that stores the compensation plan validation results produced by the calculation process. As stated in the ETRM metadata, it "contains the compensation plan validation result generated by calculation process." It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is registered in FND Design Data as CN.CN_CALC_SUB_VALIDATIONS_ALL. The object is owned by the CN schema and holds status VALID across EBS 12.1.1 and 12.2.2.

Because the record is keyed by a combination of CALC_SUB_BATCH_ID and COMP_PLAN_ID, the heuristic Data Vault classification is that of a standalone object. In modeling terms, it functions closest to a link or satellite, capturing a point-in-time validation outcome per calculation batch and compensation plan rather than acting as a durable business entity hub.

Key Information Stored

The table exposes ten documented columns. The most significant are:

The table carries no single surrogate primary key column in the documented schema; instead, the unique index CN_CALC_SUB_VALIDATION_U1 on columns (CALC_SUB_BATCH_ID, COMP_PLAN_ID) serves as the business-key candidate that guarantees uniqueness.

Common Use Cases and Queries

Typical usage centers on diagnosing calculation outcomes — identifying which compensation plans in a given calculation batch produced validation results and how many resources were affected. A common query returns validation summary by batch:

SELECT v.CALC_SUB_BATCH_ID, v.COMP_PLAN_ID, v.AFFECTED_REPS
FROM   CN.CN_CALC_SUB_VALIDATIONS_ALL v
WHERE  v.CALC_SUB_BATCH_ID = :batch_id;

Reporting use cases include reconciling calculation batches to plans, auditing which plans threw validations, and producing affected-resource counts for downstream remediation. The presence of SECURITY_GROUP_ID means hosted-mode queries must filter by the applicable security group.

Related Objects

These relationships make the table a join point between calculation batches and compensation plans, enabling validation reporting aligned to both batch runs and plan configurations.