Results for “person_interest_id”

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

Overview

AMS_PERSON_INTEREST_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered as VALID in the ETRM repository and belongs to the AMS (Marketing) product family. The view exposes information about a person's personal interests, drawing directly from the Oracle Trading Community Architecture (TCA) party model. Its practical purpose is to present a filtered, already-joined projection of interest data so that marketing applications, reports, and integrations can retrieve active person-level interests without re-implementing the underlying join logic.

Because the object is a view rather than a table, it holds no data of its own. All content is materialized at runtime from its underlying base objects. Users searching for the term "hz_person_interest" are typically looking for the HZ_PERSON_INTEREST base table; AMS_PERSON_INTEREST_V is the AMS-facing view derived from it and is the object most commonly referenced in Marketing reports and query tools.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• HZ_PERSON_INTEREST (SYNONYM) — the primary source of interest attributes and the object named in the view definition as alias HPI.
• HZ_PARTIES (SYNONYM) — the TCA party master, referenced as alias HP in the view definition and used to validate party status and type.

The defining query performs an inner join between HZ_PERSON_INTEREST and HZ_PARTIES on PARTY_ID, then applies two literal filter predicates: HP.STATUS = 'A' (active parties only) and HP.PARTY_TYPE = 'PERSON' (person parties only). As a result, the view returns one row per active person interest record, and interests belonging to inactive or non-person parties are excluded.

Key Columns

• PERSON_INTEREST_ID — the primary identifier of the interest record in HZ_PERSON_INTEREST.
• PARTY_ID — the TCA party identifier linking the interest to a specific person.
• INTEREST_NAME — the descriptive name of the interest recorded for the person.
• LEVEL_OF_INTEREST — the degree or intensity of the person's interest.
• LEVEL_OF_PARTICIPATION — the degree to which the person participates in the interest.
• INTEREST_TYPE_CODE — the classification code for the interest type.
• SUB_INTEREST_TYPE_CODE — a secondary, more granular classification of the interest.
• TEAM — the team associated with the interest record.
• SINCE — the date from which the interest has been held or recorded.

Common Use Cases and Queries

Typical use cases include marketing segmentation by personal interest, campaign target list generation, and operational reporting on a person's interests with their intensity and participation levels. Because the view enforces active-person filtering, it is well suited to queries where only current, valid person records should appear.

Basic retrieval for a specific party:

• SELECT person_interest_id, party_id, interest_name, level_of_interest, since FROM ams_person_interest_v WHERE party_id = :p_party_id;

Segmenting persons by interest type and participation:

• SELECT interest_type_code, sub_interest_type_code, COUNT(*) FROM ams_person_interest_v GROUP BY interest_type_code, sub_interest_type_code;

Filtering by level of participation for a campaign list:

• SELECT v.party_id, v.interest_name FROM ams_person_interest_v v WHERE v.level_of_participation = :p_level AND v.since <= SYSDATE;

All queries should qualify the view with the APPS schema (or rely on a synonym) and, in R12 environments, respect the operating unit and security context expected by the calling Marketing responsibility.