Search Results iex_case_objects_n1

Overview

IEX.IEX_CASE_OBJECTS is a transactional table in the Oracle E-Business Suite Advanced Collections (IEX) module. It records the individual elements—or "objects"—that make up a Collections case. A case is a container that groups related receivables, invoices, contracts, and customer interactions into a single unit of work managed by a collections agent. IEX_CASE_OBJECTS provides the physical linkage between a case header (in IEX_CASES_ALL_B) and the underlying business entities it consolidates, using a generic object-code/object-id pairing that allows the table to reference heterogeneous record types without dedicated foreign key columns.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone rather than a pure hub, link, or satellite. It behaves as a link-like associative structure: the unique business key (OBJECT_CODE, OBJECT_ID) plus the CAS_ID represent a relationship between a case and the object being collected. Implementers designing a warehouse layer should treat the (OBJECT_CODE, OBJECT_ID) pair as a business key and CAS_ID as a foreign key into the case hub.

Key Information Stored

The table is owned by the IEX schema, stores its rows in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is documented with 35 columns in the 12.2.2 physical schema. The most significant columns are:

• CASE_OBJECT_ID – Surrogate primary key (IEX_CASE_OBJECTS_PK) and the target of the unique index IEX_CASE_OBJECTS_U2.
• OBJECT_CODE – VARCHAR2(30) discriminator identifying the type of business entity, for example 'CONTRACTS' or 'INVOICE'. When combined with OBJECT_ID it forms the unique business key IEX_CASE_OBJECTS_U1.
• OBJECT_ID – Primary key value of the referenced entity; for a contract or invoice case element, this holds that entity's primary key.
• CAS_ID – Foreign key to IEX_CASES_ALL_B, identifying the parent case.
• ACTIVE_FLAG – Indicates whether the case-element association is currently active.
• ORG_ID – Multi-org operating unit identifier supporting MOAC security.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS controlling row-level access.
• COLLECTIONS_ACTION – Stores the collections action associated with the case element.
• DELINQUENCY_STATUS – Delinquency classification for the referenced item.
• OBJECT_VERSION_NUMBER – Standard HTML front-end optimistic locking column.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent Program "Who" columns identifying the last program to update the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments for customer-defined information.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns.

Supporting indexes include IEX_CASE_OBJECTS_N1 on CAS_ID and IEX_CASE_OBJECTS_N2 on OBJECT_ID, both non-unique and residing in APPS_TS_TX_IDX.

Common Use Cases and Queries

The table is frequently queried to list all elements of a case or to find every case that references a particular invoice or contract. A typical lookup enumerates case elements by case identifier:

SELECT case_object_id, object_code, object_id, active_flag
FROM iex.iex_case_objects
WHERE cas_id = :p_case_id AND active_flag = 'Y';

A reverse lookup identifies which case contains a given invoice, using the unique business key index IEX_CASE_OBJECTS_U1:

SELECT cas_id, case_object_id
FROM iex.iex_case_objects
WHERE object_code = 'INVOICE' AND object_id = :invoice_id;

Reporting use cases include building delinquency rollups by joining to IEX_CASES_ALL_B for case attributes, driving correspondence generation per case element, and reconciling collections actions back to source receivables. Because OBJECT_CODE is polymorphic, reports must filter on the specific object type before joining to the corresponding source table.

Related Objects

The documentation identifies the case header as the principal parent and lists the "Who" and security objects referenced through foreign keys:

• IEX.IEX_CASES_ALL_B – Joined via CAS_ID = IEX_CASES_ALL_B.CASE_ID; provides case header attributes such as status and owner.
• FND_SECURITY_GROUPS – Joined via SECURITY_GROUP_ID; governs row-level security for multi-org and MOAC.
• FND_CONCURRENT_REQUESTS – Referenced by REQUEST_ID to identify the concurrent program instance.
• FND_APPLICATION – Referenced by PROGRAM_APPLICATION_ID.
• FND_CONCURRENT_PROGRAM – Referenced by PROGRAM_ID.
• AR.AR_INVOICES_ALL and OE/OKE contract tables – Resolved indirectly through the OBJECT_CODE/OBJECT_ID business key rather than a declared foreign key.

Because the object references are polymorphic, any application logic that consumes case elements must resolve OBJECT_CODE before joining to the target entity. Note that the ETRM commentary for OBJECT_CODE references a sequence number allocated for a Collections case, which is a documentation artifact; functionally the column stores the entity-type discriminator.