Search Results create_strategy

Overview

APPS.IEX_STRATEGY_PVT is a private (PVT) PL/SQL package body in the Oracle E-Business Suite Collections module (Advanced Collections / IEX). It encapsulates the core create, update, and delete operations that manipulate collection strategy definitions, which are the rule-based configurations governing how delinquent customers are treated during the collections process. The private classification means the package is not intended to be called directly by external consumers; instead it provides the implementation layer used internally by its public counterparts and related IEX packages. As of ETRM 12.2.2, the package exposes three documented procedures: CREATE_STRATEGY, UPDATE_STRATEGY, and DELETE_STRATEGY. The file header (iexvstrb.pls, version 120.1.12010000.3) confirms it has been part of the IEX codebase since at least the 12.1.x release and remains current in 12.2.2.

Key Procedures and Functions

The package follows the standard Oracle EBS API programming conventions, including the FND_API compatibility check, the use of a savepoint (CREATE_STRATEGY_PVT), message-list initialization, and OUT NOCOPY status parameters. Each procedure follows this pattern.

• CREATE_STRATEGY — Inserts a new collection strategy record into IEX_STRATEGIES. It accepts a STRATEGY_Rec_Type record populated by the caller, verifies the API version against l_api_version_number (2.0), derives a primary key from the IEX_STRATEGIES_S sequence, and returns the generated strategy identifier in X_STRATEGY_ID along with the standard return status, message count, and message data outputs. The procedure also reads IEX_STRATEGY_TEMPLATES_B via an internal cursor (c3) to retrieve the strategy level associated with the supplied template.
• UPDATE_STRATEGY — Modifies the attributes of an existing strategy with optimistic locking (object_version_number) and returns updated status information. It is the counterpart to CREATE_STRATEGY for maintenance of existing definitions.
• DELETE_STRATEGY — Removes a strategy record, enforcing the standard API validation and error-handling framework so that related IEX objects are not left in an inconsistent state.

Tables Accessed

The package operates against the following APPS-synonym tables:

• IEX_STRATEGIES — The primary table holding strategy definitions; it is the target of INSERT, UPDATE, and DELETE operations and supplies the object_version_number used for concurrency control.
• IEX_STRATEGIES_S — The sequence source for the STRATEGY_ID primary key, referenced through the internal cursor c2 (SELECT IEX_STRATEGIES_S.nextval FROM dual).
• IEX_STRATEGY_TEMPLATES_B — Read via cursor c3 to obtain the strategy_level for the template identified by STRATEGY_TEMPLATE_ID in the input record, ensuring the new strategy inherits the correct hierarchical level.
• DUAL — Used solely as the sequence selection source.

Usage Notes

Because IEX_STRATEGY_PVT is a private package, it is invoked indirectly. ETRM records show it is referenced by seven other packages, which wrap it in public APIs or call it from Collections setup and administration flows. Typical invocation points include the Collections Strategy setup forms, concurrent programs that seed or migrate strategy data, and custom extensions built on the public IEX API layer. Developers writing custom code should not call IEX_STRATEGY_PVT directly; the supported entry point is the corresponding public package, which internally routes to this private implementation. Debug tracing is controlled through FND_LOG and the IEX_DEBUG_LEVEL profile, emitting messages via IEX_DEBUG_PUB.