Results for “edi_payment_format”

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

Overview

The JTF_PARTY_CONT_POINTS_V view, owned by the APPS schema, is a CRM Foundation (JTF) reporting and integration object that exposes contact point information for parties registered in the Trading Community Architecture (TCA) model. As stated in the ETRM documentation, the view "retrieves all contact points for parties without any restriction," meaning it applies no filtering by status, primary flag, contact point type, or telephone type. Every contact point row associated with an HZ_PARTIES record is returned.

Because it is defined as a simple join between HZ_PARTIES and HZ_CONTACT_POINTS, the view is predominantly used for ad hoc queries, custom reports, extracts, and integration staging where a flattened, denormalized party-to-contact-point record is required. It is present in both Oracle EBS 12.1.1 and 12.2.2 with an identical column list and VALID status in the APPS schema.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both reached through public synonyms:

• HZ_PARTIES (aliased PARTY) — the TCA party registry holding party identifiers, party numbers, names, and party type.
• HZ_CONTACT_POINTS (aliased CONT_POINT) — the TCA contact point table holding phone, email, URL, EDI, and other communication records.

The join is driven by the polymorphic owner columns on HZ_CONTACT_POINTS: CONT_POINT.OWNER_TABLE_ID = PARTY.PARTY_ID and CONT_POINT.OWNER_TABLE_NAME = 'HZ_PARTIES'. This restriction is what confines the result set to party-owned contact points, excluding contact points owned by other TCA entities such as organizations in other owner-table contexts. There is no outer join or NVL decoration; the view is an inner join, so only parties with at least one matching contact point are returned.

Key Columns

The view exposes the full contact point column set alongside party attributes.

• CONTACT_POINT_ID / PARTY_ID — primary key of the contact point and the owning party identifier; the join keys for downstream integration.
• PARTY_NUMBER, PARTY_NAME, PERSON_FIRST_NAME, PERSON_LAST_NAME, PARTY_TYPE — party identification and classification attributes carried over from HZ_PARTIES.
• CONTACT_POINT_TYPE — the TCA lookup classifying the record (for example PHONE, EMAIL, URL, EDI, WEB).
• TELEPHONE_TYPE — the lookup value further qualifying a phone contact point (for example business, home, mobile, fax). This is the column most often sought when users search for "telephone_type," and it is only meaningful when CONTACT_POINT_TYPE indicates a phone record.
• PHONE_NUMBER, PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_EXTENSION, PHONE_LINE_TYPE — the decomposed telephone attributes.
• EMAIL_FORMAT, EMAIL_ADDRESS, URL, WEB_TYPE — email and web contact details.
• STATUS, PRIMARY_FLAG — active/inactive state and primary-contact indicator; neither is filtered by the view.
• TIME_ZONE, BEST_TIME_TO_CONTACT_START, BEST_TIME_TO_CONTACT_END — contact preference attributes.
• EDI_* columns — EDI transaction handling, payment, and remittance attributes.
• ORIG_SYSTEM_REFERENCE — cross-reference to the originating source system.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — audit and concurrent program context.

Common Use Cases and Queries

Typical scenarios include party contact-point extracts, telephone directory reporting, data quality audits of TELEPHONE_TYPE values, and integration staging feeds. Because no restrictions are applied, callers must impose their own filters. The following query retrieves active primary phone contact points with their telephone type:

• SELECT party_id, party_number, party_name, contact_point_id, telephone_type, phone_country_code, phone_area_code, phone_number
• FROM apps.jtf_party_cont_points_v
• WHERE contact_point_type = 'PHONE'
• AND status = 'A'
• AND primary_flag = 'Y';

A second common pattern counts contact points by telephone type for a given party:

• SELECT telephone_type, COUNT(*) FROM apps.jtf_party_cont_points_v
• WHERE party_id = :p_party_id
• GROUP BY telephone_type;

When joining to other party-related views, ensure that CONTACT_POINT_ID is used as the unique key rather than party attributes, since a party may have multiple rows in this view. Indexing or filtering on PARTY_ID, CONTACT_POINT_ID, and CONTACT_POINT_TYPE is advisable for performance, as the view performs no internal restriction or predicate pushdown beyond the owner-table join condition.