Search Results iex_filter_pub_w




Overview
Explore in AI Chat

Overview

APPS.IEX_FILTER_PUB_W is the public wrapper package for the Oracle Advanced Collections (IEX) filter engine. Its principal business role is to create, validate, and maintain the filter definitions that drive Collections strategies, scoring, and work queue selection. Filter records determine which delinquent accounts, customers, or transactions are included in a particular collections process, such as a dunning or strategy assignment run.

The package follows the Oracle E-Business Suite PL/SQL API convention: a wrapper package (_W) exposes a stable public signature that internally delegates to the underlying entity package (IEX_FILTER_PUB) and enforces FND_API return status, message stack, and initialization semantics. Source header information (iexwfils.pls 120.1) indicates the file belongs to the Collections filter subsystem and was last revised in Release 11i/12.0 lineage before being carried forward to 12.1.1 and 12.2.2.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P2 — Bulk data transfer helper that copies a JTF_NUMBER_TABLE collection into the internal universe_ids nested table type defined in IEX_FILTER_PUB. It is used to marshal a list of universe (filter criterion set) identifiers from OAF/Java or middle-tier calls into the PL/SQL API.
  • ROSETTA_TABLE_COPY_OUT_P2 — The inverse of the above, copying the internal universe_ids collection back out to a JTF_NUMBER_TABLE for consumption by the calling Java or OAF layer.
  • VALIDATE_FILTER — Performs validation logic against an inbound set of filter attribute values without persisting the record. It returns a duplicate-status indicator (x_dup_status), standard API return status, and message count/data fields. This allows callers to detect duplicate or conflicting filter definitions prior to insert.
  • CREATE_OBJECT_FILTER — Creates a new filter record in the Collections filter repository. It accepts a version number, initialization and commit flags, an out parameter carrying the newly generated filter identifier, and an ordered set of overloaded positional attributes (numeric, character, and date) using FND_API missing-value sentinels as defaults. The procedure returns the standard x_return_status, x_msg_count, and x_msg_data diagnostics plus a duplicate status.
  • UPDATE_OBJECT_FILTER — Updates an existing filter record identified by the corresponding attribute set. Like the create routine it supports explicit commit control and returns the standard FND_API diagnostic outputs.

Tables Accessed

The documented table reference is PLITBLM, accessed via its APPS synonym. PLITBLM is a generic PL/SQL interim (temporary/generated) table used by Oracle APIs for table-handler and bulk processing operations. The filter API does not work directly with the base filter table through this package; instead the procedural entity logic in IEX_FILTER_PUB performs the actual DML and the wrapper exposes it through the public API surface.

Usage Notes

This package is normally invoked from the Oracle Collections middle-tier (OAF/Java) when a user creates or maintains a filter from the Collections administration UI, and from batch processing that programmatically defines filters for strategy execution. Because the procedure parameters use overloaded positional names (p1_a0 … p1_a16, p3_a0 … p3_a13) rather than descriptive identifiers, callers must reference the documented parameter sequence precisely; the numeric default 0-1962.0724 is the FND_API missing-number sentinel. Custom code should always pass p_init_msg_list and p_commit explicitly and inspect x_return_status before proceeding.

Changes should never be made directly to the underlying filter tables; all modifications must flow through CREATE_OBJECT_FILTER or UPDATE_OBJECT_FILTER so that validation, duplicate detection, and message-stack handling are preserved. The package is documented as referenced by zero other packages, so it is effectively a top-level integration point rather than an internal dependency.