Results for “p_itemset_item_table_name”

2 results




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

Overview

The ODM.ODM_ASSOCIATION_RULE_MODEL package body is a component of the Oracle Data Mining (ODM) option shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. ODM integrates Oracle Database data mining algorithms with EBS transactional data so that users can discover hidden patterns in purchasing, order management, CRM, and other operational datasets. This particular package implements the association rule model — the data mining model type that discovers co-occurrence relationships between items, the classic "market basket analysis" use case where the system learns that customers who buy item A frequently also buy item B.

The package is delivered wrapped, meaning its compiled source is obfuscated in the ETRM snapshot; only the declaration section names are visible. The ETRM metadata classifies it under owner ODM with API classification OTHER, indicating it is an internal implementation package rather than a public, documented API. It is not referenced by any other package and exposes no formally documented procedures, so it functions as a private worker module supporting the broader ODM mining framework.

Key Procedures and Functions

Because the body is wrapped, no public procedure or function signatures are published in the ETRM excerpt. However, the preserved identifier names reveal the internal decomposition of the package. Three named operations are present: BUILD, EVALUATE, and CREATE_EMPTY. These correspond to the standard lifecycle of an Oracle Data Mining model: build constructs and trains the model, evaluate scores it against a test dataset, and create_empty provisions a model skeleton without training. These are invoked through ODM's generic mining driver rather than called directly.

The naming constants C_PACKAGE_NAME, C_BUILD_NAME, C_EVALUATE_NAME, and C_CREATE_EMPTY_NAME are used to dispatch calls reflectively. A large block of C_*_NAME / P_* pairs maps parameter identifiers to their internal values, including training and testing table names, transaction and item column lists, minimum support, minimum confidence, maximum rule length, and evaluation percentage. A THROW_EXCEPTION helper centralizes error raising with location, exception number, up to four substitution variables, and a message text built from session details such as SYS_CONTEXT('userenv','session_user') and the session ID.

Tables Accessed

The package operates over a set of transient and persistent mining tables whose names are parameterized rather than hard-coded. Documented table-name parameters include P_TRAINING_TABLE_NAME, P_TESTING_TABLE_NAME, P_OLD_RULE_TABLE_NAME, P_ANTECEDENT_TABLE_NAME, P_ITEM_TABLE_NAME, P_ITEMSET_TABLE_NAME, P_ITEMSET_ITEM_TABLE_NAME, and P_RULE_TABLE_NAME. The RULE_TABLE holds the generated association rules along with their confidence and support measures; the ANTECEDENT_TABLE stores the left-hand side of each rule; the ITEmsET tables store frequent itemsets discovered during mining; and the ITEM_TABLE holds a flattened representation of the ITEM_ID universe.

Storage clauses are generated by C_SQL_SMALL_STORAGE and C_SQL_LARGE_STORAGE, and DDL fragments are assembled from the TABLE_NAME_TYPE, COLUMN_NAME_TYPE, and SEQUENCE_NAME_TYPE subtypes defined in ODM_MODEL_UTIL. Standard rule columns such as RULE_ID, CONFIDENCE, SUPPORT, ANTECEDENT_SUPPORT, CONSEQUENT_SUPPORT, and NUMBER_OF_ANTECEDENTS are used throughout.

Usage Notes

This package is not invoked by end users, Oracle Forms, or concurrent programs directly. It is called internally by the ODM mining engine when a user creates or evaluates an association rule model through the Oracle Data Miner interface or the EBS Data Mining workbench. The package requires an ODM-enabled database user with CREATE TABLE and CREATE SEQUENCE privileges because it materializes intermediate mining tables at runtime. Customizations that reference internal names such as BUILD, EVALUATE, or the C_*_NAME constants are unsupported and will be invalidated if Oracle reissues the wrapped body. Upgrades between 12.1.1 and 12.2.2 preserve the wrapped signature, so any external dependency on this package should be treated as fragile.