Results for “iex_case_contacts”

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

Overview

IEX_CASE_CONTACTS is a transaction table in the IEX (Collections) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It holds information about the contacts defined for a party playing a specific role in the collection process of a case. In the Advanced Collections module, a "case" represents a collections work item tracked against a customer or party, and each case may involve multiple contacts — collectors, customer contacts, guarantors, or other responsible parties — each associated with a defined role. IEX_CASE_CONTACTS stores these per-case contact assignments, linking a case to contact parties, addresses, and phone records.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. From a modeling perspective, this suggests the table functions less as a pure hub- or link-style entity and more as a self-contained association record — its only outgoing references are to IEX_CASES_ALL_B and FND_SECURITY_GROUPS, so it can be treated as a standalone collection-contact entity rather than a central hub or intersection link in a larger network.

Key Information Stored

The documented physical schema contains 34 columns. The most significant include:

• CAS_CONTACT_ID — the surrogate primary key (IEX_CASE_CONTACTS_PK) and the column defined by the unique index IEX_CASE_CONTACTS_U1; it uniquely identifies each case-contact record.
• CAS_ID — foreign key to IEX_CASES_ALL_B, identifying the parent collections case to which the contact belongs.
• CONTACT_PARTY_ID — the party identifier of the contact (typically referencing HZ_PARTIES), establishing who the contact is.
• ADDRESS_ID and PHONE_ID — optional references to the contact's address and phone records used for collections communication.
• PRIMARY_FLAG — indicates whether the contact is the primary contact for the case.
• ACTIVE_FLAG — denotes whether the assignment is currently active.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/multi-tenant data security.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle ADF/BC4J framework.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording which request last touched the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-column auditing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF (Descriptive Flexfield) extensibility columns.

Note that ADDRESS_ID and PHONE_ID are not documented as foreign keys in the supplied metadata, though they are conventionally associated with the contact's communication details.

Common Use Cases and Queries

Typical scenarios include identifying all contacts assigned to a case, determining the primary collector for a delinquent customer, and producing contact-role reporting for collections agents.

Example — list contacts for a case:

• SELECT cc.cas_contact_id, cc.contact_party_id, cc.primary_flag, cc.active_flag FROM iex.iex_case_contacts cc WHERE cc.cas_id = :cas_id AND cc.active_flag = 'Y';

Example — join to the parent case:

• SELECT c.case_number, cc.contact_party_id, cc.primary_flag FROM iex.iex_case_contacts cc JOIN iex.iex_cases_all_b c ON c.cas_id = cc.cas_id;

Reporting frequently filters on PRIMARY_FLAG to surface the single primary contact per case and on ACTIVE_FLAG to exclude superseded contacts.

Related Objects

• IEX_CASES_ALL_B — parent case table; joined via IEX_CASE_CONTACTS.CAS_ID = IEX_CASES_ALL_B.CAS_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for data security.
• HZ_PARTIES — implicit source of the contact identity via CONTACT_PARTY_ID.
• HZ_LOCATIONS / HZ_CONTACT_POINTS — conventional sources for ADDRESS_ID and PHONE_ID.
• IEX_CASE_CONTACTS_PK / IEX_CASE_CONTACTS_U1 — the primary key constraint and unique index on CAS_CONTACT_ID.