Results for “module_type”

50+ results




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

Overview

CN_RULESETS_ALL_B is the base table in the Oracle E-Business Suite Incentive Compensation (CN) module that stores rulesets used for revenue classification rules. It resides in the CN schema and holds the header-level definition of each ruleset, which groups one or more classification rules (CN_RULES_ALL_B) into a logical unit that the Incentive Compensation engine evaluates against transaction data. The table carries a VALID status in the ETRM 12.1.1 / 12.2.2 documentation and comprises 18 documented columns. Users searching for the identifier "cn_rulesets_all_b_uk" are typically looking for the unique index that enforces the business key on this table.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. This suggests CN_RULESETS_ALL_B behaves primarily as a descriptive satellite attached to a business key composed of RULESET_ID and ORG_ID, with descriptive attributes such as status, date ranges, module type, and security group. It is not a pure hub, since it carries numerous descriptive and effective-dating columns.

Key Information Stored

The surrogate primary key is enforced through CN_RULESETS_PK on RULESET_ID alone, while the business-key candidate CN_RULESETS_ALL_B_UK is composed of RULESET_ID and ORG_ID. A second unique index, CN_RULESETS_ALL_B_U1 (RULESET_ID, ORG_ID, ZD_EDITION_NAME), supports edition-aware access, and CN_RULESETS_ALL_B_U2 (START_DATE, END_DATE, MODULE_TYPE, ORG_ID, ZD_EDITION_NAME) enforces temporal and module scoping.

Common Use Cases and Queries

Typical reporting and validation scenarios involve listing active rulesets by organization or joining rulesets to their constituent rules. The following pattern retrieves active rulesets effective in the current period:

  • SELECT ruleset_id, org_id, ruleset_status, start_date, end_date FROM cn_rulesets_all_b WHERE org_id = :p_org_id AND ruleset_status = 'ACTIVE' AND sysdate BETWEEN start_date AND NVL(end_date, sysdate+1);
  • Join to rules: SELECT r.ruleset_id, r.rule_id FROM cn_rulesets_all_b rs, cn_rules_all_b r WHERE rs.ruleset_id = r.ruleset_id AND rs.org_id = :p_org_id;
  • Resolve the destination column: SELECT rs.ruleset_id, o.object_name FROM cn_rulesets_all_b rs, cn_objects_all o WHERE rs.destination_column_id = o.object_id AND rs.repository_id = :p_repo_id;

These queries support revenue classification audits, ruleset maintenance reports, and interface validation between Incentive Compensation and downstream revenue recognition processes.

Related Objects

  • CN_RULES_ALL_B — child table; joins on RULESET_ID, holding individual rules belonging to each ruleset.
  • CN_REPOSITORIES_ALL — parent repository table joined on REPOSITORY_ID.
  • CN_OBJECTS_ALL — parent object table joined on DESTINATION_COLUMN_ID.
  • FND_SECURITY_GROUPS — security reference joined on SECURITY_GROUP_ID.
  • CN_RULESETS_ALL_TL — translation table (where present) supplying language-specific ruleset names.
  • CN_RULESETS_ALL_V — reporting view exposing ruleset data.

Together these objects form the configuration layer through which Incentive Compensation evaluates and classifies revenue transactions.