Search Results x_case_definition_id

Overview

The APPS.IEX_CASE_DEFINITIONS_PKG package is a table-handler (CRUD) PL/SQL package belonging to the Oracle Advanced Collections (IEX) module of Oracle E-Business Suite. Its purpose is to encapsulate insert, update, lock, and delete operations against the IEX_CASE_DEFINITIONS table, which stores the definition records that govern how collection cases are configured and resolved within the Collections application. Case definitions control the rules by which strategies, deliverables, and case attributes are applied to delinquent customers.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, and is therefore intended for internal use inside the APPS environment. The header comment ($Header: iextcdfs.pls 120.0 2004/01/24) indicates this package has remained stable since its original 11i-era creation, and it is classified as an OTHER API rather than a public, supported interface.

Key Procedures and Functions

The ETRM metadata documents four procedures. The most critical is INSERT_ROW, the primary entry point used to create a new case-definition record. Its signature is dominated by the x_CASE_DEFINITION_ID primary key — the identifier the user searched for — followed by the case structure columns x_TABLE_NAME, x_COLUMN_NAME, x_COLUMN_VALUE, x_ACTIVE_FLAG, x_OBJECT_VERSION_NUMBER, and x_CAS_ID. It also carries the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), request/program auditing columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), and the fifteen DFF attribute columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–15).

UPDATE_ROW mirrors the insert signature minus the rowid parameter, updating an existing case definition identified by x_CASE_DEFINITION_ID. LOCK_ROW obtains a row-level lock on a definition for concurrency control during a transactional edit. DELETE_ROW removes a case definition by its identifier. Together these four procedures form a complete, DFF-enabled maintenance API for the table.

Tables Accessed

The single documented table is IEX_CASE_DEFINITIONS, accessed through its APPS synonym. Every procedure operates exclusively on this table: INSERT_ROW and UPDATE_ROW write the configuration columns and audit/DFF attributes; LOCK_ROW and DELETE_ROW act on the CASE_DEFINITION_ID key. No other table is referenced by the package according to the metadata.

Usage Notes

Because the API is classified OTHER and is controlled by the APPS schema, it is normally invoked indirectly rather than from custom code. Typical callers are the Collections setup forms and concurrent programs that maintain case-definition setup data. The package is referenced by one other package in the documented object map, indicating layered use within the Collections codebase. Direct invocation is generally limited to Oracle internal code or carefully controlled extensions; developers should obtain CASE_DEFINITION_ID values from the IEX_CASE_DEFINITIONS_S sequence and always populate the object version number and WHO columns to preserve optimistic locking and audit integrity.