Search Results delete_strategy

Overview

APPS.IEX_STRATEGY_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Collections and Advanced Collections application module (IEX). It provides the core business logic for creating, maintaining, and removing collection strategy records against the IEX_STRATEGIES entity. A strategy in Advanced Collections represents an automated or user-driven plan that determines which delinquency action, work item, or task is delivered next for a customer account, party, or other object. The package encapsulates the low-level validation, sequencing, and DML operations required to keep collection strategy data consistent across the base table and its audit/shadow table.

The source header identifies the file as iexvstrs.pls (120.0.12010000.2, dated 2008/08/11), confirming this package has been part of the IEX schema since at least the 12.0 code line and remains present in both 12.1.1 and 12.2.2. Because the package is classified PVT, it is not intended as a public integration surface; instead it is consumed internally by the IEX public APIs, concurrent processing, and the Collections forms layer. The declaration of a package-level constant G_DEFAULT_NUM_REC_FETCH (30) and a comprehensive STRATEGY_Rec_Type record type — mirroring nearly every column of the underlying table, including OBJECT_VERSION_NUMBER, REQUEST_ID, and the JTF_OBJECT_TYPE/JTF_OBJECT_ID pairs — reflects a bulk-oriented, record-driven design typical of Oracle's seeded private APIs.

Key Procedures and Functions

• CREATE_STRATEGY — Inserts a new strategy row for a given object, validating referenced template and delinquency attributes and populating audit columns. It is the entry point for generating a strategy when a scoring or assignment process determines that a collection plan should be applied.
• UPDATE_STRATEGY — Modifies an existing strategy, including status transitions, score value changes, and reassignment of the next work item. This routine also supports object version number checking to detect concurrent modification.
• DELETE_STRATEGY — Removes a strategy record. This is the procedure most closely associated with the user's search term "delete_strategy," and it is the documented mechanism by which private API callers logically or physically clear a strategy from the collections data model.

Tables Accessed

• IEX_STRATEGIES — The primary transactional table holding active strategy instances. CREATE, UPDATE, and DELETE operate directly against this table.
• IEX_STRATEGIES_S — The companion shadow/audit table (Oracle's standard _S pattern) that stores the "old" values required for update history and for delete-safe auditing.
• IEX_STRATEGY_TEMPLATES_B — The template base table, read to validate that the STRATEGY_TEMPLATE_ID referenced by a new or updated strategy is valid and exists in the same operating context.
• DUAL — Used for single-row lookups, sequence retrieval, and control-flow validations within the package.

Usage Notes

IEX_STRATEGY_PVT is not called directly from end-user customizations; it is invoked by the IEX public API layer, by Advanced Collections concurrent programs that generate and refresh strategies, and by the Collections Agent/Collector forms when a user manually assigns, updates, or deletes a strategy from a work queue. The package is referenced by seven other packages, confirming it sits beneath a meaningful stack of dependent business logic. Because it is a PVT package, callers should interface through the corresponding public API rather than calling CREATE_STRATEGY, UPDATE_STRATEGY, or DELETE_STRATEGY directly, and any direct invocation must supply a fully populated STRATEGY_Rec_Type. Oracle's standard practice is that these procedures participate in the caller's transaction; commit and rollback are controlled at the public API or form level, not within this private package.