Results for “release_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IEX_STRATEGIES is a core transaction table within the Oracle EBS Collections (IEX) module. It stores the collection strategies that drive the automated and semi-automated workflow of delinquent customer accounts. A "strategy" in the Collections context represents an assigned course of action—such as a defined sequence of collection activities, work items, or scoring rules—applied against a specific delinquent customer account, party, or object. Each row ties a strategy template to a concrete business entity, records the current lifecycle status, and captures the scoring or delinquency context that justified the assignment.

The table resides in the IEX schema and is registered as VALID against Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema in ETRM 12.2.2 contains 32 columns. Based on the FK structure mined from the metadata, the heuristic Data Vault classification for this object is standalone. From a modeling perspective this suggests IEX_STRATEGIES is best represented as an independent hub-like entity keyed by STRATEGY_ID, with its descriptive attributes (status, scores, dates, flags) behaving as satellite-style context rather than participating in a strict link table pattern. Its foreign keys to IEX_DELINQUENCIES_ALL, HZ_CUST_ACCOUNTS, and FND_SECURITY_GROUPS attach it to delinquency, trading-partner, and security-group dimensions without implying a many-to-many bridge between them.

Key Information Stored

The surrogate primary key of the table is STRATEGY_ID, which is also the sole documented unique index (IEX_STRATEGIES_U1), making it the primary business-key candidate for row identification. The remaining columns fall into several functional groups.

• Strategy definition: STRATEGY_TEMPLATE_ID identifies the reusable template from which the strategy instance was generated; STRATEGY_LEVEL and CHECKLIST_STRATEGY_ID further qualify scope and checklist behavior.
• Business object linkage: DELINQUENCY_ID, CUST_ACCOUNT_ID, PARTY_ID, CUSTOMER_SITE_USE_ID, OBJECT_TYPE, OBJECT_ID, JTF_OBJECT_TYPE, and JTF_OBJECT_ID together define which delinquency, customer, party, site, or JTF framework object the strategy targets.
• State and workflow: STATUS_CODE captures the current lifecycle state; NEXT_WORK_ITEM_ID points to the ensuing work item; USER_WORK_ITEM_YN indicates whether manual user intervention is required.
• Scoring and hold control: SCORE_VALUE stores the computed collection score; HOLD_START_DATE, HOLD_DAYS, and RELEASE_DATE govern holds placed on collection activity.
• Checklist indicators: CHECKLIST_YN and CHECKLIST_STRATEGY_ID flag checklist-based strategy execution.
• Standard audit and concurrency: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and the PROGRAM_* / REQUEST_ID columns support audit, concurrent request, and optimistic locking. ORG_ID and SECURITY_GROUP_ID enforce multi-org and security-group access control.

Common Use Cases and Queries

Typical reporting and operational scenarios include identifying all active strategies for a customer, reviewing strategies on held delinquencies, and measuring scoring distribution across the collection portfolio. A representative query joining IEX_STRATEGIES to its customer and delinquency parents follows:

• Active strategies per customer: SELECT s.strategy_id, s.cust_account_id, s.status_code, s.score_value FROM iex.iex_strategies s WHERE s.cust_account_id = :cust_account_id AND s.status_code = 'ACTIVE';
• Delinquency-driven review: join DELINQUENCY_ID to IEX_DELINQUENCIES_ALL to reconcile strategy assignment against delinquency balances.
• Hold monitoring: filter on HOLD_START_DATE, HOLD_DAYS, and RELEASE_DATE to find strategies currently suspended and due for release.
• Scoring analysis: aggregate SCORE_VALUE by STRATEGY_TEMPLATE_ID to evaluate template effectiveness.
• Security-scoped reporting: constrain by SECURITY_GROUP_ID and ORG_ID to respect access and operating-unit boundaries.

Related Objects

The following are the most significant objects related to IEX_STRATEGIES, drawn from its documented FK relationships:

• IEX_DELINQUENCIES_ALL — joined via IEX_STRATEGIES.DELINQUENCY_ID; the parent delinquency record the strategy addresses.
• HZ_CUST_ACCOUNTS — joined via IEX_STRATEGIES.CUST_ACCOUNT_ID; the trading-partner customer account.
• FND_SECURITY_GROUPS — joined via IEX_STRATEGIES.SECURITY_GROUP_ID; enforces data access security.
• Strategy template objects — referenced through STRATEGY_TEMPLATE_ID to define reusable strategy patterns.
• Collections work item objects — linked through NEXT_WORK_ITEM_ID to drive the follow-on activity queue.
• Checklist strategy objects — referenced through CHECKLIST_STRATEGY_ID for checklist-based execution paths.

These relationships confirm IEX_STRATEGIES as the operational bridge between delinquency detection, customer account context, and the Collections workflow engine across Oracle EBS 12.1.1 and 12.2.2.