Search Results update_strategy

Overview

IEX_STRATEGY_PVT is a private PL/SQL package within the Oracle E-Business Suite Collections (Advanced Collections / IEX) module. It encapsulates the core insert, update, and delete logic for Strategy records, which are the Collections work-item drivers that determine how delinquent customers are routed through collection activities, assignments, and follow-up actions. The package is classified as a private (PVT) API, meaning it is not intended to be called directly by external or customer-written code. Instead, it is designed to be invoked by its public counterpart package, IEX_STRATEGY_PUB, and by other internal IEX packages that orchestrate Collections processing.

The package is built around a single record type, STRATEGY_Rec_Type, which mirrors the full column definition of the IEX_STRATEGIES table, including identifiers such as STRATEGY_ID, STATUS_CODE, STRATEGY_TEMPLATE_ID, DELINQUENCY_ID, CUST_ACCOUNT_ID, PARTY_ID, WORK ITEM references, and standard WHO audit columns. The header reflects an automatic record-definition generation, indicating that the record is kept in alignment with the underlying table structure. The package also defines a default fetch size constant, G_DEFAULT_NUM_REC_FETCH, set to 30, used for bulk record retrieval in list-based operations.

Key Procedures and Functions

The documented procedures number three, all operating on the Strategy record type:

• CREATE_STRATEGY — Inserts a new strategy record into the IEX_STRATEGIES table, stamping it with the information passed in the STRATEGY_Rec_Type structure. It is the entry point through which a new collection strategy is instantiated for a given object (such as a customer, delinquency, or work item) and template.
• UPDATE_STRATEGY — Applies modifications to an existing strategy record. This is the procedure referenced by users searching for "update_strategy." It updates the mutable attributes of a strategy, including status code, score, template linkage, next work item, and checklist information, while preserving the primary key identifier. Because the package is private, UPDATE_STRATEGY should not be invoked directly from custom forms or concurrent programs; the public API layer or the Collections form should be used instead.
• DELETE_STRATEGY — Removes a strategy record, providing controlled cleanup of strategy data that is no longer required.

No parameter lists are documented in the available metadata and none should be assumed beyond the STRATEGY_Rec_Type structure they operate on.

Tables Accessed

All table access in the package is made through APPS synonyms, honoring EBS standards. The referenced tables are:

• IEX_STRATEGIES — The primary transactional table storing strategy records; the target of CREATE, UPDATE, and DELETE operations.
• IEX_STRATEGIES_S — The corresponding sequence (or security/intersection) object used to generate strategy identifiers or support dependent rows.
• IEX_STRATEGY_TEMPLATES_B — The base strategy template table, consulted to validate and resolve the template a strategy is based on.
• DUAL — Used for single-row lookups, sequence value validation, and similar utility queries.

Usage Notes

IEX_STRATEGY_PVT is referenced by seven other packages, confirming its role as a shared internal service. It is normally invoked indirectly: the Collections user interface (the IEX Strategy or Advanced Collections forms) and concurrent programs operate on the public package, which in turn delegates to this private package for persistence. The presence of the WHO audit columns and the PROGRAM/REQUEST columns in the record type indicates that the package participates in standard EBS audit and concurrent program context stamping.

Customization guidance is clear: developers should never call IEX_STRATEGY_PVT.CREATE_STRATEGY, UPDATE_STRATEGY, or DELETE_STRATEGY directly, because private APIs may change between releases and bypass business validation enforced in the public layer. When the term "update_strategy" appears in search results or documentation, it refers to the internal update routine that the IEX_STRATEGY_PUB public API uses to commit strategy changes. Any custom extension should route through the public API or the supported Collections forms to remain upgrade-safe across 12.1.1 and 12.2.2.