Results for “ams_dm_model_test_v”

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

Overview

AMS_DM_MODEL_TEST_V is a database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AMS (Marketing) product family and holds a VALID status in both the 12.1.1 and 12.2.2 releases. Contrary to what its name might suggest, this object does not expose marketing data-mining model definitions, scoring output, or any analytical content. Per the documented ETRM metadata, it is explicitly described as a dummy view created to grant access to the ODM (Oracle Data Mining) schema.

Its role within EBS is therefore administrative rather than functional. Oracle Data Mining historically operated from a separate database schema, and cross-schema privilege grants in EBS are frequently implemented by exposing a minimal, harmless view in the APPS layer. This view acts as such a placeholder, providing a named object against which grants can be issued without exposing protected data. It presents no business information and is not used in standard marketing reporting, campaign analytics, or list-generation processes.

Underlying Base Objects

The view is defined with an extremely simple query: SELECT 1 DUMMY FROM DUAL. Its only referenced base object is the DUAL synonym, which resolves to the standard Oracle DUAL table. Because the projection is a literal constant rather than a column drawn from a table, the view is not dependent on any application table. It cannot return application data, and no joins, filters, or aggregations are involved.

This structure is deliberate. A view returning a constant is stable, cheap to compile, and immune to changes in underlying application tables. It fulfils its purpose as a privilege-granting vehicle while imposing negligible parsing or execution overhead.

Key Columns

The view exposes a single column, documented as follows:

• DUMMY — A numeric literal with the constant value 1 for every row returned. It carries no business meaning and exists only to satisfy the requirement that a view project at least one column. The column type is NUMBER.

No key, descriptive, or date-tracked columns exist. There is no relationship to AMS campaign, list, offer, or model entities, and no foreign keys, meaning the object cannot be used to derive or validate marketing data.

Common Use Cases and Queries

Because the view contains no application data, its uses are almost entirely technical and diagnostic. Typical scenarios include:

• Privilege verification: Confirming that a schema or user holds the expected grant on the ODM access path by selecting from the view.
• Connectivity and synonym checks: Testing that APPS-owned objects and public or private synonyms resolve correctly after cloning, patching, or a fresh installation.
• Object inventory and impact analysis: Locating the view in the data dictionary during upgrades or customisation reviews, and confirming it has no downstream dependencies.

A representative query is:

SELECT dummy FROM apps.ams_dm_model_test_v;

The statement returns a single row containing the value 1. To inspect the definition and owner, a DBA can query ALL_VIEWS or DBA_VIEWS for the view name, or ALL_DEPENDENCIES to confirm that only DUAL is referenced.

In summary, AMS_DM_MODEL_TEST_V is a deliberately minimal APPS view whose purpose is to support access grants for the Oracle Data Mining schema. It exposes one constant column, depends solely on DUAL, and should not be mistaken for a source of marketing model or campaign data in Oracle EBS 12.1.1 or 12.2.2.