Results for “iex_case_definitions”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The IEX_CASE_DEFINITIONS table is a core configuration and metadata object within the Oracle E-Business Suite Collections (IEX) module. It stores the identification criteria used to determine when and how a collection case is uniquely defined in the system. In Oracle Collections, a "case" represents a discrete collection scenario—such as a delinquent contract, a disputed invoice, or a customer-specific collection effort—and the rules that distinguish one case from another must be persisted so the application can consistently match incoming transactions to the correct case instance. IEX_CASE_DEFINITIONS serves this purpose by holding rows that describe which source table and column, and which value, participate in the case identity. For example, when a case pertains to a contract, the case may be uniquely identified by the combination of private label, bill-to address, currency, and vendor program ID. Each such criterion is represented as a row in this table.
From a data-modeling perspective, the mined metadata classifies IEX_CASE_DEFINITIONS as a standalone object (no heuristic hub, link, or satellite verdict was derived from its foreign-key structure). This classification should be treated as a modeling suggestion rather than an authoritative designation; in practice the table behaves as a dependency or attribute table anchored to the case entity through its CAS_ID foreign key, so it could equally be modeled as a satellite attached to the IEX_CASES_ALL_B hub.
Key Information Stored
The table spans 33 documented columns. The most significant are:
- CASE_DEFINITION_ID — the surrogate primary key, enforced by index IEX_CASE_DEFINITIONS_PK and also by unique index IEX_CASE_DEFINITIONS_U1. This is the single documented business-key candidate.
- CAS_ID — foreign key to IEX_CASES_ALL_B, linking each criterion row to its parent case.
- TABLE_NAME — the source table against which the criterion is evaluated.
- COLUMN_NAME — the specific column whose value defines the case identity.
- COLUMN_VALUE — the expected value (or value pattern) for that column.
- ACTIVE_FLAG — indicates whether the criterion is currently in effect.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org and security-group partitioning.
- OBJECT_VERSION_NUMBER — optimistic locking value used by the framework to detect concurrent updates.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the process that created or last refreshed the row.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for extensibility.
The surrogate key CASE_DEFINITION_ID is distinct from the business-key candidate on the same column; no composite unique constraint is documented across TABLE_NAME, COLUMN_NAME, and COLUMN_VALUE.
Common Use Cases and Queries
Typical scenarios include diagnosing why a case was or was not matched, auditing the criteria that define existing cases, and building configuration reports for the Collections implementation team.
- Retrieve all criteria for a given case:
SELECT d.table_name, d.column_name, d.column_value, d.active_flag
FROM iex_case_definitions d
WHERE d.cas_id = :p_case_id
ORDER BY d.case_definition_id;
- Locate cases defined against a specific source table or column:
SELECT d.cas_id, d.column_value
FROM iex_case_definitions d
WHERE d.table_name = :p_table AND d.column_name = :p_column AND d.active_flag = 'Y';
- Join to the case header for a full picture of contract-type cases:
SELECT c.case_number, d.column_name, d.column_value
FROM iex_case_definitions d, iex_cases_all_b c
WHERE d.cas_id = c.cas_id;
Reporting use cases include verifying that each ACTIVE_FLAG criterion is internally consistent, identifying dormant (inactive) definitions for cleanup, and confirming security-group segregation across legal entities.
Related Objects
The following objects are the most significant dependencies and references for IEX_CASE_DEFINITIONS, based on the documented FK/PK relationships:
- IEX_CASES_ALL_B — referenced via CAS_ID; the parent case header table and the primary join for any case-centric query.
- FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs access partitioning across operating units and organizations.
- IEX_CASES_ALL_TL — the translated case-name/description view commonly joined to IEX_CASES_ALL_B to render readable case identifiers in reports.
- IEX_CASE_FOLDERS and other IEX case-related entities that rely on the same case identity model.
- FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — joined through PROGRAM_ID and REQUEST_ID to trace which concurrent process populated each definition row.
- FND_APPLICATION — joined through PROGRAM_APPLICATION_ID for the concurrent program's owning application.
No public PL/SQL API is documented in the ETRM metadata for direct maintenance of this table; changes are generally performed through the Collections administrative forms or concurrent programs that manage case definitions.
-
Hold information about the criteria which is used to identify a case.For example , a case (if it is contract) is uniquely identified by the private label, bill_to_address,currency and vendor progaram id.
-
VIEW: APPS.IEX_CASES_V 12.1.1
-
VIEW: APPS.IEX_CASES_V 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2