Search Results iex_case_objects

Overview

The IEX_CASE_OBJECTS table is a core transactional structure within the Oracle EBS Collections (Advanced Collections) module, owned by the IEX schema. It stores the individual elements, or "objects," that constitute a Collections case (CAS). A case in Advanced Collections typically aggregates one or more delinquent or disputed items belonging to a customer, and IEX_CASE_OBJECTS is the table that records which specific business objects are attached to that case. The documented description states that it holds information about the elements of a case and, by way of example, will hold an OBJECT_CODE of 'CONTRACTS' together with the corresponding object identifier.

Functionally, this table acts as the association layer between a Collections case header and the underlying operational entity (a contract, transaction, or other referenced object). Because a single case may reference multiple objects and an object may, under certain conditions, appear across cases, the table behaves like a junction or association structure. Applying heuristic Data Vault modeling, IEX_CASE_OBJECTS is best classified as a link table, since it resolves the many-to-many-style relationship between cases and the objects they contain, while carrying its own descriptive attributes such as collections action and delinquency status. It carries a foreign key to IEX_CASES_ALL_B via CAS_ID, reinforcing its role as a dependent component of the case aggregate.

Key Information Stored

Although the table is documented with 35 columns, the following are the most significant for functional and reporting purposes:

• CASE_OBJECT_ID — the surrogate primary key, uniquely identifying each row and enforced by the IEX_CASE_OBJECTS_PK constraint.
• CAS_ID — foreign key to IEX_CASES_ALL_B, linking the object to its parent Collections case.
• OBJECT_ID — the identifier of the referenced business object (for example, a contract identifier).
• OBJECT_CODE — the type or category of the referenced object; the documentation cites 'CONTRACTS' as an example value.
• COLLECTIONS_ACTION — the collections activity or action associated with the object within the case.
• DELINQUENCY_STATUS — the delinquency state recorded for the object.
• ACTIVE_FLAG — indicates whether the case-object association is currently active.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• ORG_ID — the operating unit, enabling multi-org security and reporting.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting data security partitioning.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording the process that created or updated the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for extensible client-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns.

Two unique indexes are documented: IEX_CASE_OBJECTS_U1 on (OBJECT_CODE, OBJECT_ID) and IEX_CASE_OBJECTS_U2 on (CASE_OBJECT_ID). These represent business-key candidates in addition to the surrogate primary key.

Common Use Cases and Queries

The most common requirement is to enumerate the objects attached to a case, or to find all cases associated with a given object. A representative query joins the case header to its objects:

• SELECT c.case_number, o.object_code, o.object_id, o.active_flag FROM iex_cases_all_b c, iex_case_objects o WHERE c.cas_id = o.cas_id;
• SELECT * FROM iex_case_objects WHERE object_code = 'CONTRACTS' AND object_id = :p_object_id;
• SELECT * FROM iex_case_objects WHERE cas_id = :p_cas_id AND active_flag = 'Y';

Collections analysts and reporting users rely on this table to build delinquency and collections-action reports, to reconcile the objects counted within a case, and to drive dashboards that summarize open cases by object type. Because ORG_ID is present, reporting queries should generally be scoped to the operating unit. The program audit columns also support tracing which concurrent program loaded or refreshed a given case-object association.

Related Objects

The following objects are most significant in relation to IEX_CASE_OBJECTS, grounded in the documented foreign-key relationships:

• IEX_CASES_ALL_B — the parent case header table; joined via IEX_CASE_OBJECTS.CAS_ID → IEX_CASES_ALL_B.CAS_ID. This is the primary dependency.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, governing data security access.
• IEX_CASES_ALL_TL — the translated (language) table for cases, commonly joined to retrieve case names and descriptions for reporting.
• IEX_CASE_FOLDERS / IEX_CASE_FOLDER_OBJECTS — folder-level structures that organize case content and frequently relate to the objects held here.
• FND_CONCURRENT_PROGRAMS — joins through PROGRAM_ID and PROGRAM_APPLICATION_ID for auditing the loading process.
• FND_USER — joins through CREATED_BY and LAST_UPDATED_BY for who-column auditing.
• IEX_CASE_OBJECTS_U1 / IEX_CASE_OBJECTS_U2 — the unique indexes enforcing business-key and primary-key uniqueness.

No public PL/SQL API is documented for this object in the supplied metadata; interaction typically occurs through the Advanced Collections application logic and concurrent programs rather than direct DML.