Results for “object_filter_id”

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

Overview

IEX_OBJECT_FILTERS is a configuration table in the IEX (Collections) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the filter definitions that determine which customer, transaction, or other business objects are selected when a collections strategy or strategy template is executed. In practical terms, the table acts as a repository of reusable selection criteria; each row defines a named filter of a given type that operates against a specific object identifier, and collections strategies reference these rows to decide which delinquent accounts or items enter a given treatment path.

The ETRM-derived Data Vault classification for this object is standalone, meaning the mining process identified no inbound foreign keys from other tables into IEX_OBJECT_FILTERS itself. As a modeling suggestion, this implies the table behaves as a reference or lookup entity rather than a transactional hub or link; it holds definitional metadata that is then consumed by dependent strategy tables through outbound references.

Key Information Stored

The table contains 18 documented physical columns. The most significant are:

• OBJECT_FILTER_ID – The surrogate primary key, enforced by the IEX_OBJ_FILT_PK constraint. Every filter definition is uniquely identified by this value.
• OBJECT_FILTER_TYPE – Classifies the filter, distinguishing the kind of selection logic the row represents.
• OBJECT_FILTER_NAME – The user-facing name of the filter, used when administrators attach filters to strategies.
• OBJECT_ID – Identifies the specific business object (for example, a customer or transaction entity) against which the filter applies.
• SELECT_COLUMN – Holds the column reference used in the filter selection, driving which attribute is evaluated.
• ENTITY_NAME – Names the underlying entity or view supplying the data for the filter.
• ACTIVE_FLAG – Indicates whether the filter is currently enabled and available for use.
• OBJECT_VERSION_NUMBER – Supports optimistic locking and concurrency control during updates.
• ZD_EDITION_NAME – The editioning column introduced by EBS 12.2 online patching, enabling edition-based redefinition of the table across file system editions.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN capture the standard who-column audit trail.
• Concurrent program columns – PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE record the concurrent request context for batch maintenance.

The unique index IEX_OBJECT_FILTERS on (OBJECT_FILTER_ID, ZD_EDITION_NAME) is the documented business-key candidate, combining the surrogate key with the edition identifier. Note that in 12.2.2 the edition column extends all unique constraints, whereas 12.1.1 environments do not carry this column.

Common Use Cases and Queries

Typical usage centers on reviewing which filters exist, which are active, and how they are wired into strategies. A representative query lists active filters with their types and target entities:

SELECT object_filter_id, object_filter_name, object_filter_type,
       entity_name, object_id, active_flag
FROM   iex_object_filters
WHERE  active_flag = 'Y'
ORDER BY object_filter_name;

Administrators auditing strategy configuration join filters to the strategy templates that consume them:

SELECT stb.strategy_template_name, ofl.object_filter_name
FROM   iex_strategy_templates_b stb,
       iex_object_filters    ofl
WHERE  stb.object_filter_id = ofl.object_filter_id;

Reporting scenarios include inventorying filters by type, detecting orphaned or inactive filters that are still referenced by templates, and validating that every strategy template points to a valid filter row. Because the table is small and definitional, it is frequently joined into collection strategy diagnostics and post-patch validation reports.

Related Objects

The following objects are the most significant dependents and associated entities:

• IEX_STRATEGY_TEMPLATES_B – References IEX_OBJECT_FILTERS via OBJECT_FILTER_ID; join on stb.object_filter_id = ofl.object_filter_id.
• IEX_STRATEGY_TEMPLATE_GROUPS – Also references IEX_OBJECT_FILTERS via OBJECT_FILTER_ID, associating filters with template groupings.
• IEX_STRATEGIES / IEX_STRATEGY_TEMPLATES_TL – Related strategy definition tables that consume filter configuration alongside their translated template names.
• IEX_OBJ_FILT_PK – The primary key constraint defining the surrogate key on OBJECT_FILTER_ID.
• FND_CONCURRENT_REQUESTS – Correlates through PROGRAM_ID and REQUEST_ID for audit of batch maintenance.
• FND_APPLICATION – Resolves PROGRAM_APPLICATION_ID to the owning application.

In combination, these dependencies confirm IEX_OBJECT_FILTERS as a foundational reference table for collections strategy filtering across both 12.1.1 and 12.2.2 deployments.