Search Results ahm_odf_tab_columns_v

Overview

AHM_ODF_TAB_COLUMNS_V is a database view belonging to the AHM (Hosting Manager) product family within Oracle E-Business Suite. The ETRM documentation designates AHM as Obsolete, meaning the module is no longer actively maintained or shipped in current EBS releases, and the ETRM record explicitly notes that the view is "Not implemented in this database" in the reference environment. Despite this status, the object remains catalogued because it belonged to the legacy Hosting Manager schema and may persist in upgraded or custom installations that originated before the module was retired.

Functionally, the view exposes metadata about table columns managed by the Oracle Data File (ODF) framework used by Hosting Manager. It serves as a read-only dictionary layer over the underlying AHM_ODF_TAB_COLUMNS_H history/base table, presenting row-per-column definitions that describe the structure of tables registered within the AHM data model. In reporting and integration contexts it can be used to introspect the AHM repository catalog, drive dynamic SQL generation, or document the physical schema used by the obsolete Hosting Manager hosting-provisioning features.

Underlying Base Objects

According to the documented view text, the view is defined over a single base object:

• AHM_ODF_TAB_COLUMNS — the source table from which all projected columns are selected. The view is a straightforward projection with no joins, aggregations, or filters. The description elsewhere references AHM_ODF_TAB_COLUMNS_H, indicating the historical/tracking variant of the same column-catalog table.

No additional referenced base objects are documented. Because the view is a one-to-one projection over the base table, every row and column relationship in the view mirrors the base table exactly, making the view a convenient, stable access path that insulates consumers from direct dependence on the physical table name.

Key Columns

The view projects the following columns, which fall into several logical groups. The column most relevant to the user's interest, DATA_SCALE, defines the number of digits to the right of the decimal point for numeric columns registered in the AHM catalog.

• Identity and structure: COLUMN_ID, TABLE_ID, TABLE_NAME, COLUMN_NAME, COLUMN_SEQUENCE — identify each column and its owning table and ordinal position.
• Type and constraints: COLUMN_TYPE, LENGTH, NULLABLE, DATA_PRECISION, DATA_SCALE — describe the datatype, size, precision, scale, and nullability. DATA_PRECISION and DATA_SCALE are only meaningful for numeric types such as NUMBER.
• Default and translation: DEFAULT_VALUES, TRANSLATE, FKCOLUMN — capture defaults, translation flags, and foreign-key column linkage.
• Audit and concurrency: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS WHO columns plus optimistic locking.
• Concurrent program context: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — identify the concurrent request that created or modified the row.
• Additional identifiers: PATCH_ID, DB_ID — patch and database attribution keys.

Common Use Cases and Queries

Because AHM is obsolete, uses are typically limited to legacy migration, historical auditing, or documentation of pre-existing schemas. A typical query inspecting numeric precision and scale (the "data_scale" focus) is:

• Inspect numeric columns and their scale:
  SELECT table_name, column_name, column_type, data_precision, data_scale FROM ahm_odf_tab_columns_v WHERE data_scale IS NOT NULL ORDER BY table_name, column_sequence;
• List all columns for a given catalogued table:
  SELECT column_name, column_type, length, nullable FROM ahm_odf_tab_columns_v WHERE table_name = :p_table ORDER BY column_sequence;
• Trace recently modified definitions:
  SELECT table_name, column_name, last_updated_by, last_update_date FROM ahm_odf_tab_columns_v WHERE last_update_date > SYSDATE - 30;

These queries are read-only and safe against the view. As with all obsolete AHM objects, availability cannot be guaranteed in 12.1.1 or 12.2.2 instances, and confirmation against the data dictionary is advised before reliance.