Search Results load_rule_attributes

Overview

CN_IMP_RULE_PVT is a private PL/SQL package in the Oracle EBS Advanced Pricing / Channel Revenue Management (formerly Trade Management) schema, owned by APPS. It implements the server-side import engine that transfers rule data from the Oracle EBS interface (staging) tables into the production Channel Revenue Management rule schema. The package body header (source file cnvimrlb.pls) documents its central purpose: to move data from the staging table into CN_RULESETS, CN_RULES, CN_ATTRIBUTES, and CN_RULES_HIERARCHY. In practical terms it converts validated interface rows describing rulesets, rules, rule attributes, and hierarchy relationships into operable pricing and revenue-management rules. As a PVT package it is not a public API; it is called internally by the import concurrent program and by other CN import packages rather than directly by customers. The package is classified as Private in the ETRM repository and, according to the documented metadata, is referenced by zero other packages, confirming that its entry points are driven by concurrent program registration and internal invocation.

Key Procedures and Functions

• RULES_IMPORT — The private driver procedure. It accepts an interface header identifier and organization context, then coordinates the full import of a batch of rule interface lines. It initializes the package name and file constants, instantiates the import header record type from CN_IMP_HEADERS_PVT, and tracks processed and failed row counts. The source header explicitly states that it transfers data from the staging table into CN_RULESETS, CN_RULES, CN_ATTRIBUTES, and CN_RULES_HIERARCHY, and that its prerequisite is none.
• LOAD_RULES — Loads rule definitions from validated interface lines into the CN_RULES table, creating the rule records that are subsequently associated with their parent ruleset.
• LOAD_RULE_ATTRIBUTES — Loads the attributes attached to each imported rule into CN_ATTRIBUTES. This is the procedure most commonly referenced by the search term "load_rule_attributes," and it is the component responsible for populating rule-level attribute rows so that imported rules carry their qualifying and qualifying-value details.
• UPDATE_ON_ERROR — Handles error processing. When a line or rule fails validation or insertion, this procedure records the failure status and message against the interface line so the batch can be reviewed and corrected.
• UPDATE_IMP_LINES — Updates the CN_IMP_LINES staging rows with the final processing status, linking each line to its created production record or to its error condition.

Tables Accessed

The package reads and writes CN_IMP_HEADERS and CN_IMP_LINES, the interface header and line staging tables that supply the import batch and receive status updates. It inserts into and queries CN_RULESETS, CN_RULES, and CN_ATTRIBUTES, the core rule storage tables, and writes hierarchy links through CN_HIERARCHY_NODES, CN_HEAD_HIERARCHIES, and CN_DIM_HIERARCHIES. CN_OBJECTS and CN_REPOSITORIES provide object and repository metadata for the created rules. CN_PROCESS_AUDITS records processing audit information for each run. CN_REVENUE_CLASSES supplies revenue-classification references, and GL_CODE_COMBINATIONS is accessed to resolve accounting flexfield combinations used by rule attributes or qualifiers.

Usage Notes

CN_IMP_RULE_PVT is invoked indirectly. In a standard Oracle EBS 12.1.1 or 12.2.2 environment, rule data is loaded into the CN interface tables and the "Import Rules" concurrent program is submitted; that program calls RULES_IMPORT, which in turn invokes LOAD_RULES, LOAD_RULE_ATTRIBUTES, UPDATE_IMP_LINES, and UPDATE_ON_ERROR as the batch progresses. Because the package is private and the ETRM metadata records no dependent packages, custom code should not call it directly; instead, use the supported import concurrent program or the public CN import APIs that wrap it. When troubleshooting a "load_rule_attributes" failure, the relevant diagnostics are the status codes written back to CN_IMP_LINES and the audit rows in CN_PROCESS_AUDITS; correcting the offending interface lines and resubmitting the import is the standard remediation path.