Results for “as_imp_cnt_pnt_interface”

44 results




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

Overview

AS_IMP_CNT_PNT_INTERFACE is a staging and interface table owned by the OSM schema within the AS - Sales Foundation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold contact point information awaiting import into the application's production contact point model. Contact points in EBS comprise the communication channels associated with a party or owner record — e-mail addresses, web URLs, telephone numbers, telex numbers, and related attributes — and this table functions as the inbound boundary where such data is loaded, validated, and then consumed by concurrent programs that move records into the base contact point tables.

The object carries the status VALID and is catalogued in ETRM with 36 documented columns. From a data modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table is anchored to a parent import interface record and augments it with descriptive contact point attributes rather than acting as a pure hub or a many-to-many link resolver. This classification should be treated as a heuristic modeling suggestion rather than a declared design constraint.

Key Information Stored

The primary key is AS_IMP_CNT_PNT_INTERFACE_PK, defined on the surrogate column IMP_CNT_PNT_INTERFACE_ID. A unique index, AS_IMP_CNT_PNT_INTERFACE_U1, is also documented on the same column, confirming it as the sole business-key candidate among the documented indexes. The _PK suffix referenced in the user's search resolves directly to this constraint.

The most significant columns include:

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present.

Common Use Cases and Queries

Typical usage involves bulk loading contact point data from external systems and then running the import concurrent program that validates and promotes rows. Reporting queries frequently join the interface table to its parent import interface to track batch progress:

SELECT i.imp_cnt_pnt_interface_id,
       i.import_interface_id,
       i.contact_point_type,
       i.email_address,
       i.phone_number,
       i.primary_flag
FROM   osm.as_imp_cnt_pnt_interface i
WHERE  i.import_interface_id = :batch_id;

Error and duplicate detection is commonly performed by grouping on ORIG_SYSTEM_REFERENCE combined with OWNER_TABLE_NAME and OWNER_TABLE_ID, while primary-flag conflicts are surfaced by filtering on PRIMARY_FLAG and CONTACT_POINT_PURPOSE. Multi-org aware queries must filter by SECURITY_GROUP_ID.

Related Objects

  • AS_IMPORT_INTERFACE — parent table joined via IMPORT_INTERFACE_ID; governs the import batch context.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for data security partitioning.
  • HZ_CONTACT_POINTS — the base contact point table that staged rows are ultimately promoted into.
  • HZ_PARTIES — the party master providing PARTY_ID context.
  • AS_IMP_CNT_PNT_INTERFACE_PK / AS_IMP_CNT_PNT_INTERFACE_U1 — the primary key constraint and unique index over IMP_CNT_PNT_INTERFACE_ID.