Search Results edi_ece_tp_location_code

Overview

CSC_HZ_CONTACT_POINTS_V is a valid APPS-owned view in the Oracle E-Business Suite Customer Care (CSC) module, present in both release 12.1.1 and 12.2.2. It joins records from the Trading Community Architecture (TCA) tables HZ_CONTACT_POINTS and HZ_PARTIES to present contact point details alongside the associated party (customer) information. Its purpose within EBS reporting and integration is to provide a single consolidated source for retrieving telephone, email, URL, and EDI-related contact attributes together with party identifiers and name information, without requiring the caller to construct the underlying join.

The view is frequently referenced by Customer Care, order management, and outbound EDI extracts that must resolve a party's contact mechanism and location from the same query. Because the view exposes the EDI_ECE_TP_LOCATION_CODE column, it is particularly relevant to users searching for edi_ece_tp_location_code, which is the EDI trading-partner location identifier used in e-commerce gateway (ECE) processing.

Underlying Base Objects

The documented ETRM metadata lists two referenced base objects, both exposed as synonyms in the APPS schema:

• HZ_CONTACT_POINTS – the TCA entity that stores individual contact mechanisms (phone, email, URL, EDI) for a party.
• HZ_PARTIES – the TCA master entity holding party identity, number, name, and type.

The view's defining SQL selects CONT_POINT.ROWID and a broad set of columns from HZ_CONTACT_POINTS, joined to columns from HZ_PARTIES. The join predicate is CONT_POINT.OWNER_TABLE_ID = PARTY.PARTY_ID, meaning contact points are returned for parties recorded as their owner. This confines the view to party-owned contact points and mirrors the standard TCA ownership model. Because it is a simple two-table join with no aggregation, each row of the underlying HZ_CONTACT_POINTS record produces one row in the view.

Key Columns

The view exposes a wide column set. Among the most significant are:

• CONTACT_POINT_ID, ROWID – primary identifier and physical row locator for the contact point record.
• PARTY_ID, PARTY_NUMBER, PARTY_NAME, PARTY_TYPE – identifying attributes of the owning party.
• PERSON_FIRST_NAME, PERSON_LAST_NAME – person-name components when the party is a person.
• PHONE_NUMBER, PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_EXTENSION, PHONE_LINE_TYPE, TELEPHONE_TYPE – telephony attributes.
• EMAIL_ADDRESS, EMAIL_FORMAT, URL, WEB_TYPE – electronic contact attributes.
• CONTACT_POINT_TYPE, STATUS, PRIMARY_FLAG – classification and status of the contact point.
• EDI_TRANSACTION_HANDLING, EDI_ID_NUMBER, EDI_PAYMENT_METHOD, EDI_PAYMENT_FORMAT, EDI_REMITTANCE_METHOD, EDI_REMITTANCE_INSTRUCTION, EDI_TP_HEADER_ID, EDI_ECE_TP_LOCATION_CODE – EDI-specific attributes. EDI_ECE_TP_LOCATION_CODE holds the trading-partner location code used by the E-Commerce Gateway.
• ORIG_SYSTEM_REFERENCE, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – audit and concurrency columns inherited from the underlying table.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield segments.
• TIMEZONE_ID, TIME_ZONE, BEST_TIME_TO_CONTACT_START, BEST_TIME_TO_CONTACT_END – timing attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard audit columns.

One position in the select list is defined as NULL, and PARTY.COUNTRY is included from the party side.

Common Use Cases and Queries

Typical uses include locating a party's contact points by party number, extracting EDI location codes for gateway mappings, and building contact reports that combine party and contact details. The following examples illustrate representative queries:

• Retrieve EDI location codes for a party:
  SELECT party_number, party_name, edi_ece_tp_location_code FROM csc_hz_contact_points_v WHERE party_number = :p_party_number;
• List all email contact points for a party:
  SELECT party_id, party_name, email_address FROM csc_hz_contact_points_v WHERE party_id = :p_party_id AND contact_point_type = 'EMAIL';
• Select primary phone contacts:
  SELECT party_name, phone_number, telephone_type FROM csc_hz_contact_points_v WHERE primary_flag = 'Y';
• Resolve trading-partner header and location for ECE setup:
  SELECT edi_tp_header_id, edi_ece_tp_location_code, party_name FROM csc_hz_contact_points_v WHERE edi_ece_tp_location_code IS NOT NULL;

Because the view filters on party ownership, callers requiring non-party contact points must query HZ_CONTACT_POINTS directly. All queries should observe the standard EBS multi-org and security conventions applicable to TCA data.