Results for “expense_ccid”

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

Overview

CN_RULES_ALL_B is a core configuration table in the Oracle E-Business Suite Incentive Compensation (CN) module. It stores the rules that drive revenue classification, and it functions as the primary input to the revenue classification generator. Each row defines a rule that determines how revenue is categorized and assigned during the compensation processing cycle, linking a rule to its parent ruleset, its target revenue class, and its position within the ruleset hierarchy.

The table resides in the CN schema and, in ETRM 12.2.2, is documented with 16 columns. It is multi-organization aware through ORG_ID and is protected by row-level security via SECURITY_GROUP_ID. Based on the foreign key topology, the heuristic Data Vault classification is hub-leaning. In a Data Vault model this table would be treated as a hub, with RULE_ID as the business key and the descriptive attributes distributed to satellites; this is a modeling suggestion only and does not reflect the physical design of the EBS table itself.

Key Information Stored

The most significant attributes include:

• RULE_ID — the surrogate identifier for the rule and the leading column of the primary key.
• RULESET_ID — foreign key to CN_RULESETS_ALL_B, identifying the ruleset to which the rule belongs.
• REVENUE_CLASS_ID — foreign key to CN_REVENUE_CLASSES_ALL, indicating the revenue classification the rule produces.
• ORG_ID — the operating unit context, making the rule applicable only within that organization.
• RULE_LEVEL — indicates the rule's position or tier within the ruleset hierarchy.
• PACKAGE_ID — references the associated package used when the rule is generated or executed.
• EXPENSE_CCID and LIABILITY_CCID — accounting flexfield identifiers used to post the expense and liability sides of the classification result.
• ZD_EDITION_NAME — supports the editioning/archive mechanism used in 12.2 online patching.
• SECURITY_GROUP_ID — controls which users or responsibilities can access the row.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

The documented unique indexes are CN_RULES_ALL_B_UK (RULE_ID, RULESET_ID, ORG_ID), CN_RULES_ALL_B_UK2 (RULE_LEVEL), and CN_RULES_PK (RULE_ID); the physical 12.2.2 schema also documents CN_RULES_ALL_B_U1 (RULE_ID, RULESET_ID, ORG_ID, ZD_EDITION_NAME). These columns serve as the business-key candidates. Note that CN_RULES_PK and CN_RULES_ALL_B_UK both lead with RULE_ID, so RULE_ID is the effective surrogate key while RULESET_ID and ORG_ID provide the scoping context.

Common Use Cases and Queries

The table is typically queried when diagnosing why a particular transaction was classified into a given revenue class, when reviewing or auditing a ruleset's configuration, and when generating classification results. A common pattern joins the rule to its parent ruleset and revenue class:

• SELECT r.RULE_ID, r.RULESET_ID, r.REVENUE_CLASS_ID, r.RULE_LEVEL FROM CN_RULES_ALL_B r WHERE r.ORG_ID = :org_id AND r.RULESET_ID = :ruleset_id ORDER BY r.RULE_LEVEL;
• SELECT r.RULE_ID, s.RULESET_NAME, c.REVENUE_CLASS_NAME FROM CN_RULES_ALL_B r, CN_RULESETS_ALL_B s, CN_REVENUE_CLASSES_ALL c WHERE r.RULESET_ID = s.RULESET_ID AND r.REVENUE_CLASS_ID = c.REVENUE_CLASS_ID;
• SELECT COUNT(*) FROM CN_RULES_ALL_B WHERE ZD_EDITION_NAME IS NULL AND SECURITY_GROUP_ID = :sg_id;

Reporting use cases include listing all active rules by organization, identifying rules without an associated revenue class, and reconciling rule counts against ruleset definitions. Because the table is editioned, queries against 12.2 environments should generally filter on the current edition. Multi-org filters on ORG_ID are mandatory for correct results when more than one operating unit is configured.

Related Objects

The most significant related objects and join columns are:

• CN_RULESETS_ALL_B — referenced by CN_RULES_ALL_B.RULESET_ID; defines the ruleset that owns each rule.
• CN_REVENUE_CLASSES_ALL — referenced by CN_RULES_ALL_B.REVENUE_CLASS_ID; defines the classification target.
• FND_SECURITY_GROUPS — referenced by CN_RULES_ALL_B.SECURITY_GROUP_ID; enforces access control.
• CN_ATTRIBUTE_RULES_ALL — references this table via RULE_ID, RULESET_ID, and ORG_ID; stores attribute-level rule conditions.
• CN_RULES_HIERARCHY_ALL — references this table via RULE_ID and PARENT_RULE_ID, capturing the parent-child rule structure.
• CN_RULE_ATTR_EXPRESSION_ALL — references this table via RULE_ID; holds attribute expressions attached to a rule.

Together these objects form the revenue classification rule model, with CN_RULES_ALL_B acting as the central hub from which attribute rules, hierarchy relationships, and expressions derive their context.