Results for “ams_person_dm_source_v”

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

Overview

The view AMS_PERSON_DM_SOURCE_V is an Oracle E-Business Suite database object owned by the APPS schema and registered as VALID. It belongs to the AMS (Marketing) product family and is documented in ETRM for releases 12.1.1 and 12.2.2. The view exposes a filtered, person-oriented projection of Oracle Marketing's data-mining source records stored in AMS_DM_SOURCE. Its defining SELECT statement joins AMS_DM_SOURCE to HZ_PARTIES (Oracle Trading Community Architecture) and restricts the result set to parties whose STATUS equals 'A' (active) and whose PARTY_TYPE equals 'PERSON'. Consequently, the view returns only data-mining source rows associated with active individual (person) parties, excluding organizations and inactive records. This makes it a reporting and integration surface for marketing analytics, lead scoring, and model-based segmentation scoped to natural persons.

Underlying Base Objects

Two referenced base objects are documented for this view (each exposed through a synonym in the APPS schema):

• AMS_DM_SOURCE — the core data-mining source table holding source identifiers, model metadata, scoring outputs, and standard WHO columns.
• HZ_PARTIES — the TCA party master, used here solely as a filter source to qualify records to active person parties via PARTY_ID.

The join predicate is ADS.PARTY_ID = HP.PARTY_ID, combined with the filter conditions HP.STATUS = 'A' and HP.PARTY_TYPE = 'PERSON'. Because the view is not updatable in the documented form and applies an inner join, rows in AMS_DM_SOURCE that lack a matching active person party are suppressed.

Key Columns

The view exposes eighteen columns. The most significant include:

• SOURCE_ID — primary key of the underlying data-mining source record.
• MODEL_TYPE — identifies the analytic model category associated with the record.
• PARTY_ID — the TCA party identifier for the scored person.
• TARGET_VALUE, SCORE_RESULT, CONFIDENCE, CONTINUOUS_SCORE — model scoring outputs used for ranking and segmentation.
• CREATED_BY_NAME, LAST_UPDATED_BY_NAME, LAST_UPDATE_LOGIN_NAME — these are the columns relevant to the user's search for created_by_name. Notably, they are aliases in the view text: ADS.CREATED_BY is aliased as CREATED_BY_NAME, ADS.LAST_UPDATED_BY as LAST_UPDATED_BY_NAME, and ADS.LAST_UPDATE_LOGIN as LAST_UPDATE_LOGIN_NAME.
• Standard audit columns also present: LAST_UPDATE_DATE, CREATION_DATE, OBJECT_VERSION_NUMBER, ARC_USED_FOR_OBJECT, USED_FOR_OBJECT_ID.

A critical implementation caveat applies to the "name" columns. Despite the _NAME suffix, they are aliases of numeric ID columns, not resolved display names. To obtain an actual user name for created_by_name, applications must join to FND_USER (for example, FND_USER.USER_ID = AMS_PERSON_DM_SOURCE_V.CREATED_BY_NAME).

Common Use Cases and Queries

Typical scenarios include listing model scores for active person parties, auditing record ownership, and feeding downstream marketing analytics. A basic query is:

SELECT source_id, party_id, model_type, score_result, confidence FROM apps.ams_person_dm_source_v;

To resolve created_by_name to a usable value, join with FND_USER:

SELECT v.source_id, v.party_id, u.user_name AS created_by_user FROM apps.ams_person_dm_source_v v, apps.fnd_user u WHERE v.created_by_name = u.user_id;

Filtering on score thresholds or dates follows the same pattern. Because the view already enforces the active person party restriction, callers should avoid assuming completeness of AMS_DM_SOURCE; organizations and inactive parties are intentionally excluded.