Search Results create_case_definitions




Overview
Explore in AI Chat

Overview

The PL/SQL package body APPS.IEX_CASE_DEFINITIONS_PVT belongs to the Oracle E-Business Suite Advanced Collections (IEX) module and is classified as a Private (PVT) API package. Its principal responsibility is to encapsulate the create, update, and delete operations that govern case definitions. A case definition is the configurable template that determines how a collections case — the primary work object used by collections agents to manage delinquent customer accounts — is constructed, including its associated attributes, statuses, and behavior. By exposing these maintenance operations through a disciplined private API layer, the package shields callers from the underlying DML on the base tables and enforces the EBS API programming standards, including recording-based parameter passing, message list initialization, savepoint management, and compatibility checking.

The package body declares the standard constants G_PKG_NAME and G_FILE_NAME and uses FND_LOG.G_CURRENT_RUNTIME_LEVEL for debug-level logging through IEX_DEBUG_PUB.LogMessage. Each public procedure also declares an internal API name and version constant, which is validated against the expecting caller's version through FND_API.Compatible_API_Call, raising FND_API.G_EXC_UNEXP when versions are incompatible.

Key Procedures and Functions

  • CREATE_CASE_DEFINITIONS — Creates a new case definition record. It accepts a case definition record type along with standard API control parameters (API version, initialization of the message list, commit flag, and validation level), and returns the newly generated case definition identifier together with standard return status, message count, and message data outputs.
  • UPDATE_CASE_DEFINITIONS — Updates an existing case definition. This is the procedure referenced by the search term "update_case_definitions." It modifies the definition's maintained attributes while preserving the object version number used for optimistic locking.
  • DELETE_CASE_DEFINITIONS — Removes an existing case definition, typically subject to the standard validation and referential checks enforced by the API before the delete is committed.

The package likely also contains internal helper routines used by these three public procedures, but only the three procedures above are documented in the ETRM metadata.

Tables Accessed

The package operates against the base table IEX_CASE_DEFINITIONS, which stores the case definition header records, and its sequence-backed primary key generator IEX_CASE_DEFINITIONS_S. Cursor c2 selects IEX_CASE_DEFINITIONS_S.nextval from DUAL to obtain a new primary key value before insertion. The identifier is then returned to the caller through the X_CASE_DEFINITION_ID output parameter. All references are made through APPS synonyms.

Usage Notes

As a PVT API, IEX_CASE_DEFINITIONS_PVT is not intended to be invoked directly by external consumers. It is referenced by two other packages within the IEX product, which provide the public interface layer. The procedures follow the standard EBS API lifecycle: a savepoint is established at the start of each procedure, API compatibility is validated, the message list is optionally initialized, validation is performed based on the requested validation level, DML is executed, and the outcome is reported through the return status and message outputs. Custom code that needs to maintain case definitions should call the corresponding public API rather than this private package body to ensure correct transaction and message handling. The package body source is identified by the header revision iexvcdfb.pls 120.1, indicating it is a core, shipped Oracle object rather than a customer extension.