Results for “person_iden_type”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_PARTIES_ALL_V is a CRM Foundation (JTF) view owned by the APPS schema and defined over party data maintained in the Trading Community Architecture (TCA). Its documented description states that it exposes "party information of the Caller, Customer and Relationship," which describes its role as a consolidated, read-oriented projection of party records used throughout the JTF stack — telephony, interaction history, scripted call flows, and CRM dashboards — where the identity of a caller, a customer, or a related party must be resolved and displayed. Because the object is a view rather than a table, it carries no storage of its own; it presents a stable, named interface over the underlying party entity so that dependent forms, concurrent programs, and OAF pages can reference party attributes without direct dependency on the full TCA table width. In Oracle EBS 12.1.1 and 12.2.2 the view remains VALID and is deployed identically, with the 12.2 online patching architecture preserving it as an APPS-owned, edition-enabled object.

Underlying Base Objects

The documented metadata records a single referenced base object: HZ_PARTIES, accessed through a synonym. HZ_PARTIES is the master TCA registry table holding one row per party — person, organization, or party group. JTF_PARTIES_ALL_V therefore inherits the grain, denormalized key structure, and DFF-enabled attribute columns of that table. The view text is a direct column-level projection of HZ_PARTIES: every column is passed through without joins or aggregation in the excerpt provided, meaning the view functions as a controlled, stable subset-and-alias layer over the base party table rather than a transformed dataset. This design shields JTF-consuming code from upstream column additions in HZ_PARTIES while exposing the descriptive flexfield and global descriptive flexfield segments (ATTRIBUTE1 through ATTRIBUTE24 and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE18) that CRM configurations rely on.

Key Columns

  • PARTY_ID — Primary key of the party record in TCA; the join key to HZ_PARTIES, HZ_CUST_ACCOUNTS, and JTF-related interaction tables.
  • PARTY_NUMBER — The user-visible, unique party number generated by TCA; used in CRM searches and customer-facing references.
  • PARTY_NAME — The formatted party name (person full name or organization name) presented in call center screens and reports.
  • PARTY_TYPE — Indicates PERSON, ORGANIZATION, or GROUP; governs which downstream attributes (e.g., person title, job) are meaningful.
  • VALIDATED_FLAG — Indicates whether the party has been validated by TCA, relevant to data-quality and duplicate-prevention reporting.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE24 — Descriptive flexfield context and segment values used to store site-specific party attributes.
  • GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE18 — Global DFF context and segments, typically reserved for localization and country-specific data.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and related audit/program columns for traceability.

Notably, the view does not expose person-specific attributes such as a title or job through its own columns; a consumer searching for "person_title" must join to HZ_PERSON_PROFILES, PER_PERSON_NAMES_F / PER_ALL_PEOPLE_F, or the relevant TCA person detail table on PARTY_ID to retrieve that attribute.

Common Use Cases and Queries

Typical scenarios include resolving a caller's identity during an inbound interaction, populating customer lookup lists in JTF-based forms, and auditing party validation status. A basic projection is straightforward:

  • SELECT party_id, party_number, party_name, party_type FROM jtf_parties_all_v WHERE party_type = 'PERSON';
  • SELECT party_id, party_number, party_name FROM jtf_parties_all_v WHERE validated_flag = 'Y' AND party_name LIKE :search_term;
  • Joining to the person profile to surface a person title: SELECT p.party_name, pp.person_title FROM jtf_parties_all_v p, hz_person_profiles pp WHERE p.party_id = pp.party_id;
  • Reading a configured flexfield segment: SELECT party_number, attribute_category, attribute1 FROM jtf_parties_all_v WHERE attribute_category = 'CUSTOMER_EXT';

Because the view is a passthrough over HZ_PARTIES, queries against it are subject to the same Org Access Control (MOAC) and security policies that protect the base table; report developers should therefore constrain or secure access appropriately and favor the view for read-only CRM reporting rather than for transactional updates.