Search Results table_category




Overview
Explore in AI Chat

Overview

AHM_PRECOOK_JAVA_V is a database view belonging to the AHM - Hosting Manager product family, a module now classified as obsolete within the Oracle E-Business Suite. The view is defined as a filtered projection over AHM_APPS_CONFIGURATIONS, returning only those configuration rows whose TABLE_CATEGORY value corresponds to a lookup code registered under the lookup type AHM_PRECOOK_JAVA. In effect, it isolates the subset of table configurations that must be "precooked" through Java processing — specifically, tables that contain LONG columns. Because the Oracle EBS Java tier cannot process LONG datatypes through standard JDBC paths, such tables require special handling, and this view identifies exactly which table categories demand that treatment.

As reporting and integration metadata, the view presents a curated, environment-specific list of table categories. The ETRM 12.2.2 record notes that the view is not implemented (no rows) in the documented database and that no base objects are formally registered as owned or referenced. Nonetheless, its SQL text clearly targets AHM_APPS_CONFIGURATIONS and FND_LOOKUP_VALUES, making FND_LOOKUPS the semantic driver of its contents.

Underlying Base Objects

The view text joins two objects:

  • AHM_APPS_CONFIGURATIONS — the primary source of configuration rows, supplying the majority of the exposed columns including TABLE_ID, TABLE_CATEGORY, TABLE_NAME, and the standard WHO audit columns.
  • FND_LOOKUP_VALUES — the "view on FND_LOOKUPS," referenced in an inline subquery that restricts results to LOOKUP_TYPE = 'AHM_PRECOOK_AVA'. The subquery returns LOOKUP_CODE values, and the outer query keeps only configurations whose TO_CHAR(TABLE_CATEGORY) matches one of those codes.

The relationship is therefore a semi-join: AHM_APPS_CONFIGURATIONS is filtered against the set of precook-enabled lookup codes. No columns from FND_LOOKUP_VALUES appear in the projection; the lookups act purely as a validation mask. The ETRM metadata records no owned base objects and no referenced objects, so dependency details must be inferred from the embedded SQL rather than the registered data dictionary.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which table categories require Java precooking, validating hosting configurations after a patch or clone, and diagnosing LONG-column extraction failures by confirming whether the offending category is registered under the precook lookup.

SELECT table_category, table_name, application_id, last_update_date
FROM   ahm_precook_java_v
ORDER  BY table_category, table_name;

To correlate with the governing lookup values:

SELECT v.table_name, v.table_category, l.lookup_code, l.description
FROM   ahm_precook_java_v v,
       fnd_lookup_values l
WHERE  l.lookup_type = 'AHM_PRECOOK_JAVA'
AND    TO_CHAR(v.table_category) = l.lookup_code;

Because the module is obsolete and the view is documented as not implemented in the ETRM reference database, results may be empty; the query remains valid for environment-specific diagnostics where AHM configurations and lookup data are populated.