Search Results person_pre_name_adjunct




Overview
Explore in AI Chat

Overview

AMS_LT_PERSON_DETAILS_V is an APPS-owned database view within the Oracle E-Business Suite marketing product family (AMS — Marketing). It is documented as a data source view whose purpose is to retrieve information about business-to-consumer (B2C) contacts. In the ETRM metadata for release 12.2.2 the object is registered with a status of VALID and is cataloged as a VIEW under the APPS schema, the standard owner for shared, cross-module database objects in Oracle EBS.

Functionally, the view acts as a flattened, read-only projection of person-type party records, exposing name, title, salutation, contact, address, and firmographic attributes in a single denormalized structure. Its "LT" naming convention and the presence of categorization columns such as CATEGORY_CODE and REFERENCE_USE_FLAG indicate that it is intended as a list-management or list-treatment data source, allowing marketing users to build target lists, personalization tokens, and campaign audiences from B2C contact data without joining the full normalized Trading Community Architecture (TCA) model. Because it selects only active person parties, it is well suited to operational marketing reporting and integration extracts.

Underlying Base Objects

Per the documented view text, the sole referenced base object is HZ_PARTIES, exposed in the APPS schema as a synonym. The view is defined as a straightforward SELECT over that table with two hard-coded filter predicates: STATUS = 'A' (active parties only) and PARTY_TYPE = 'PERSON' (individuals, not organizations or groups). The view therefore inherits the TCA party model's authoritative identity and contact columns and does not perform any joins to HZ_PERSON_PROFILES, HZ_LOCATIONS, or HZ_CONTACTS in the excerpted definition; the contact and address columns are drawn directly from HZ_PARTIES. Because the definition is a simple projection over a single base object, no aggregation or set operators are involved, and row counts mirror the qualifying HZ_PARTIES rows.

Key Columns

Given the user's search term "person_title", the most directly relevant column is PERSON_TITLE, which carries the party's professional or courtesy title (for example, Mr., Ms., Dr.), complemented by PERSON_ACADEMIC_TITLE for academic credentials and SALUTATION for the formatted greeting. Person name components are exposed individually: PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_PRE_NAME_ADJUNCT, PERSON_MIDDLE_NAME, and PERSON_NAME_SUFFIX, alongside PARTY_NAME (the concatenated display name) and KNOWN_AS. Identity and reference columns include PARTY_ID, PARTY_NUMBER, ORIG_SYSTEM_REFERENCE, CUSTOMER_KEY, TAX_REFERENCE, JGZZ_FISCAL_CODE, and DUNS_NUMBER_C.

Common Use Cases and Queries

Typical scenarios include building B2C target lists for campaigns, supplying personalization values to marketing templates, and extracting person contact data for downstream analytics. The filter on PARTY_TYPE = 'PERSON' means organization parties are excluded automatically, so no additional predicate is required for consumer-only extracts.

Retrieve titled contacts for a mailing list:

  • SELECT party_id, party_name, person_first_name, person_last_name, person_title, email_address FROM ams_lt_person_details_v WHERE person_title IS NOT NULL;

Filter by fiscal analysis period and revenue potential:

  • SELECT party_number, party_name, analysis_fy, curr_fy_potential_revenue, next_fy_potential_revenue FROM ams_lt_person_details_v WHERE analysis_fy = :p_fy ORDER BY next_fy_potential_revenue DESC;

Identify high-value consumers by order history:

  • SELECT party_id, party_name, total_num_of_orders, total_ordered_amount, last_ordered_date FROM ams_lt_person_details_v WHERE total_num_of_orders > 0 ORDER BY total_ordered_amount DESC;

Because the view is a synonym-backed projection, queries benefit from indexing on HZ_PARTIES primary and alternate keys; PARTY_ID remains the reliable join key back to TCA for any attributes not exposed here.