Search Results name_suffix

Overview

JTF_PARTY_CUSTOMERS_V is an Oracle E-Business Suite view owned by the APPS schema and delivered as part of the JTF – CRM Foundation product. It presents consolidated party information drawn from the TCA (Trading Community Architecture) registry, exposing both person and organization records in a single denormalized structure. The view is defined over HZ_PARTIES, and depending on the value of PARTY_TYPE, it draws additional attributes from either HZ_ORGANIZATION_PROFILES (for organizations) or HZ_PERSON_PROFILES (for persons). This design allows CRM applications, reporting tools, and integration interfaces to retrieve party demographics, classification data, and profile attributes without writing custom unions or joins against the underlying TCA tables. The view holds a VALID status and is available in both EBS 12.1.1 and 12.2.2. Because it exposes descriptive and demographic attributes—not transactional balances—it is typically used for customer master lookups, list-of-values definitions, data warehousing extracts, and personalization of CRM screens. The attribute and global attribute columns propagated from HZ_PARTIES preserve the DFF (descriptive flexfield) context, enabling downstream consumers to apply the same flexfield semantics used on the base table.

Underlying Base Objects

The documented base objects referenced by the view are HZ_PARTIES, HZ_ORGANIZATION_PROFILES, and HZ_PERSON_PROFILES, all accessed through APPS synonyms. HZ_PARTIES is the driving table and supplies the universally applicable columns: PARTY_ID, PARTY_NUMBER, PARTY_TYPE, PARTY_NAME, KNOWN_AS, the person name components, STATUS, ORIG_SYSTEM_REFERENCE, SIC_CODE, CUSTOMER_KEY, URL, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus the attribute and global attribute flexfield segments. Organization-specific attributes are sourced from HZ_ORGANIZATION_PROFILES: ANALYSIS_FY, FISCAL_YEAREND_MONTH, EMPLOYEES_TOTAL, CURR_FY_POTENTIAL_REVENUE, NEXT_FY_POTENTIAL_REVENUE, TAX_REFERENCE, YEAR_ESTABLISHED, ORGANIZATION_NAME_PHONETIC, INTERNAL_FLAG, and LINE_OF_BUSINESS. Person-specific attributes are sourced from HZ_PERSON_PROFILES: DATE_OF_BIRTH, PERSON_TITLE, PERSON_FIRST_NAME_PHONETIC, PERSON_LAST_NAME_PHONETIC, PERSONAL_INCOME, GENDER, and MARITAL_STATUS. The effective join is driven by PARTY_TYPE, so organization columns are populated only for organization parties and person columns only for person parties; the remaining columns are null for the other type.

Key Columns

• PARTY_ID / PARTY_NUMBER – Primary identifier and human-readable party number; the standard foreign key targets for downstream tables.
• PARTY_TYPE – Determines whether organization or person profile columns are meaningful.
• PARTY_NAME, KNOWN_AS, person name components – Name rendering attributes for both party types.
• CUSTOMER_KEY, ORIG_SYSTEM_REFERENCE – Cross-system and legacy identifiers used in data migration and integration mapping.
• SIC_CODE, LINE_OF_BUSINESS, EMPLOYEES_TOTAL, YEAR_ESTABLISHED, TAX_REFERENCE – Organization classification and firmographic attributes.
• PERSONAL_INCOME, DATE_OF_BIRTH, GENDER, MARITAL_STATUS, PERSON_TITLE – Person demographic attributes, including personal_income, which originates from HZ_PERSON_PROFILES.
• ANALYSIS_FY, FISCAL_YEAREND_MONTH, CURR_FY_POTENTIAL_REVENUE, NEXT_FY_POTENTIAL_REVENUE – Organization financial profiling data.
• ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–15, ATTRIBUTE_CATEGORY – Descriptive flexfield segments inherited from HZ_PARTIES.
• STATUS, ROWID, WHO columns – Record state and audit metadata.

Common Use Cases and Queries

Typical usage includes customer LOVs, CRM dashboards, and reporting extracts that require a single query returning both person and organization parties. A common query returning person parties with income data is:

• SELECT party_id, party_number, party_name, personal_income, gender, marital_status FROM jtf_party_customers_v WHERE party_type = 'PERSON' AND personal_income IS NOT NULL;
• SELECT party_id, party_name, sic_code, employees_total, curr_fy_potential_revenue FROM jtf_party_customers_v WHERE party_type = 'ORGANIZATION' AND internal_flag = 'N';
• SELECT party_number, party_name, party_type FROM jtf_party_customers_v WHERE UPPER(party_name) LIKE 'ACME%';

Because person profile columns such as PERSONAL_INCOME are null for organization parties, filters should always constrain PARTY_TYPE when demographic columns are referenced. The view is read-only and should not be used as a DML target; inserts and updates must be performed against the underlying HZ_PARTIES, HZ_PERSON_PROFILES, and HZ_ORGANIZATION_PROFILES tables through the supported TCA APIs.