Results for “odm_model_util”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ODM_MODEL_UTIL is a utility package in the Oracle Data Mining (ODM) schema that supports the Oracle E-Business Suite data mining and predictive modeling infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the ODM schema hosts the database-side components that enable advanced analytics, scoring, and model management integrated with EBS applications and Oracle Advanced Analytics. The package provides foundational type definitions, constants, and exception handling used throughout the ODM model management layer.
The package is delivered in wrapped (obfuscated) form, consistent with Oracle's practice of protecting proprietary data mining internals. It functions as an internal infrastructure utility rather than an end-user API, exposing a shared vocabulary of object name subtypes, data type constants, and enumerated error conditions to other ODM packages. Its presence in SYS with a UTIL classification reflects its role as a low-level building block referenced by higher-level modeling procedures.
Key Procedures and Functions
The documented metadata does not enumerate individual procedures or functions for this package (0 documented entries). The excerpt instead reveals an extensive declaration section, which is the package's primary contribution to the ODM codebase:
- Subtypes and domain types: SCHEMA_OBJECT_NAME_TYPE, TABLE_NAME_TYPE, VIEW_NAME_TYPE, INDEX_NAME_TYPE, SEQUENCE_NAME_TYPE, COLUMN_NAME_TYPE, COLUMN_TRUNC_NAME_TYPE, COLUMN_DATA_TYPE, DBLINK_NAME_TYPE, MINING_TASK_ID_TYPE, UNIQUE_OBJECT_ID_TYPE, CONNECT_STRING_TYPE, SQL_STATEMENT_TYPE, MESSAGE_TEXT_TYPE, TRACE_STATEMENT_TYPE, and ERROR_STACK_TYPE. These standardize identifiers and SQL text across model operations.
- Collection types: COLUMN_LIST_TYPE (VARRAY of 1000), TABLE_NAME_LIST_TYPE, and PARTITION_LIST_TYPE, used to pass multi-element lists of columns, tables, and partitions into model routines.
- Constants: Data type markers such as C_DT_NUMBER, C_DT_VARCHAR2, C_DT_CHAR, and C_DT_DATE; attribute-use constants C_AT_COMPUTE and C_AT_ESTIMATE; and length limits such as C_LONG_SQL_STATEMENT_LENGTH (256) and C_MAX_ERROR_STRING_LEN (62).
- Exception definitions: PRAGMA EXCEPTION_INIT bindings for errors numbered 20000 through 20013, covering invalid input, missing or duplicate tables, empty tables, missing or reserved columns, column-count and distinctness violations, invalid connections, Oracle model errors, and unevaluable models.
Tables Accessed
The wrapped source references ALL_TAB_COLUMNS and its DATA_TYPE and TYPE pseudo-columns, indicating that the package inspects the data dictionary to validate column names, resolve data types, and build metadata descriptors for mining operations. The excerpt does not document direct persistent table reads or writes; identifier values (for example, table and column name types) are consumed by the package and passed to dependent routines rather than stored by this unit itself.
Usage Notes
ODM_MODEL_UTIL is invoked internally by ODM modeling packages, not directly from EBS forms or concurrent programs. The metadata records that it is referenced by thirteen other packages, confirming its role as a shared dependency for model creation, scoring, and maintenance code. Because its body is wrapped and its objects are owned by SYS, customization is neither supported nor advisable; extensions should be implemented in custom schemas that call the supported Oracle Data Mining PL/SQL API. In EBS deployments where Oracle Advanced Analytics is licensed and configured, these utilities are loaded during database setup and are transparent to the application user, executing whenever data mining models are built, refreshed, or applied.