Results for “clli_code”

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

Overview

The view AMS_PERSON_LOCATIONS_V is a Marketing (AMS) module reporting and integration object in Oracle EBS 12.1.1 and 12.2.2. It exposes person-level location and address information drawn from the Oracle Trading Community Architecture (TCA) / Oracle Customers Online (HZ) schema. As the ETRM metadata notes, the object is not implemented in this database, meaning it is a seeded dictionary definition present in the application tier but only materialized when the relevant TCA and AMS code installations and dependencies are in place.

The view serves as a convenient, denormalized read interface over the person party model. Rather than requiring a developer or report author to join HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTIES, and FND_TERRITORIES_TL manually, AMS_PERSON_LOCATIONS_V presents the joined result set with the territory short name already resolved. This makes it useful for Marketing segmentation, list generation, campaign target extraction, and downstream integration where a flattened person-address record is required. Applications such as Oracle Marketing, Oracle Leads Management, and custom AMS extensions may reference this view when compiling contactable person records.

Underlying Base Objects

Although the ETRM metadata records no documented referenced base objects, the view text supplied in the excerpt clearly defines four underlying objects:

• HZ_LOCATIONS (HL) — the TCA location master, supplying address components.
• HZ_PARTY_SITES (HPS) — the association between a party and a location, filtered to STATUS = 'A' and ACTUAL_CONTENT_SOURCE = 'USER_ENTERED'.
• HZ_PARTIES (HP) — the party master, filtered to STATUS = 'A' and PARTY_TYPE = 'PERSON'.
• FND_TERRITORIES_TL (LANG) — the translated territory table, joined on the session language via USERENV('LANG').

The join condition is HL.LOCATION_ID = HPS.LOCATION_ID, with the party and territory joins applied on top. The view therefore returns only active, user-entered person locations where a valid country territory translation exists for the current language.

Key Columns

The view exposes the full set of location columns plus a resolved country name. Notably:

• LOCATION_ID — primary key of the underlying HZ location.
• COUNTRY and COUNTRY_NAME — the territory code and its translated short name.
• ADDRESS1 – ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, POSTAL_PLUS4_CODE — standard postal address elements.
• VALIDATED_FLAG, LIFE_CYCLE_STATUS, CONTENT_SOURCE_TYPE — address quality and provenance indicators.
• ADDRESS_EFFECTIVE_DATE / ADDRESS_EXPIRATION_DATE — validity windowing.
• LANGUAGE, TIME_ZONE — localization attributes.
• Granular address fields such as BUILDING, FLOOR, SUITE, ROOM, STREET, HOUSE_NUMBER, PO_BOX_NUMBER, DELIVERY_POINT_CODE, CLLI_CODE, DODAAC, SALES_TAX_GEOCODE — supporting international and delivery-specific addressing.
• LOC_HIERARCHY_ID — reference to the location hierarchy.

Common Use Cases and Queries

Typical uses include building Marketing target lists, validating contactable persons, and integrating person addresses into external systems. A representative query:

• SELECT location_id, country_name, city, state, postal_code FROM ams_person_locations_v WHERE country = 'US';
• SELECT location_id, address1, city, country_name FROM ams_person_locations_v WHERE validated_flag = 'Y';

Because the view filters on active persons and active party sites with user-entered content, it should be treated as a curated, active-record view rather than a full historical picture. For historical or inactive records, query the underlying HZ tables directly.