Search Results make_listentriesavailable

Overview

IEC_RECORD_FILTER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Channel Revenue Management (IEC/AMS) product family. The package encapsulates the server-side logic that governs Record Filter Views — dynamically constructed database views used to query marketing and trade promotion records according to user-defined filter criteria. It is declared with AUTHID CURRENT_USER, meaning that dynamic SQL executed within the package (notably the DDL that creates and drops views) runs under the privileges of the invoking session, which allows a filter view to be created in a schema the caller is authorized to modify.

The package is designated Private ("PVT"), so it is not intended as a public extension point; it is invoked internally by other Channel Revenue Management packages and forms to synthesize, refresh, and tear down record filter views on demand. The underlying source header (IECRECFS.pls, version 115.3, 2003/08/22) indicates the package has been stable since the early 11i lineage and is carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions:

• MAKE_LISTENTRIESAVAILABLE — Reinstates list entries that had been marked with a "do not use" (DNU) reason by setting the DO_NOT_USE_FLAG to 'N' in IEC_G_RETURN_ENTRIES, and updates the associated report counts to reflect their renewed availability. Parameters include the list header identifier, the DNU reason code, a commit flag, and a return status.
• GET_RECORDFILTERVIEW — Returns the name of a record filter view after verifying that the view exists and creating it if necessary. It accepts a record filter identifier and a source-type view name, returning the view name and an out return code.
• RECREATE_RECORDFILTERVIEW — Drops and rebuilds a record filter view, typically invoked when the underlying filter definition or source view structure changes.
• DROP_RECORDFILTERVIEW — Removes an existing record filter view. This is the routine associated with the user's search term "drop_recordfilterview."
• GET_RECORDFILTERSOURCETYPE — Resolves the source object type (and thus the base view) that a given record filter is built upon.
• APPLY_RECORDFILTER — Applies a saved record filter definition, orchestrating view creation through GET_RECORDFILTERVIEW.
• CANCEL_RECORDFILTER — Cancels an active filter, releasing the associated view and resources.
• CANCEL_RECORDFILTERFORLIST — Cancels filtering for an entire list, providing a bulk cleanup path for all filters tied to a given list header.

Tables Accessed

• AMS_LIST_HEADERS_ALL — Validates and resolves the marketing list header that owns the filter and its entries.
• IEC_G_RETURN_ENTRIES — Stores list return entries; the DO_NOT_USE_FLAG and count columns are updated by MAKE_LISTENTRIESAVAILABLE.
• ALL_VIEWS — Confirms whether a filter view already exists before creation, supporting GET_RECORDFILTERVIEW.
• FND_ORACLE_USERID — Used to resolve valid Oracle schema/user identities when creating views dynamically.
• IEC_G_MKTG_ITEM_CC_TZS — Provides marketing item time-zone seed data referenced during filter evaluation.
• DBMS_SQL and PLITBLM — PL/SQL-supplied packages leveraged for dynamic SQL parsing and execution of the DDL/DML that creates and drops views.

Usage Notes

Because IEC_RECORD_FILTER_PVT is a private package, it should not be called directly from custom code. It is invoked indirectly through Oracle Forms, concurrent programs, and the two dependent packages reported in the ETRM metadata, whenever a user defines, applies, or clears a record filter within the marketing/trade promotion UI. The critical operational caveat concerns DROP_RECORDFILTERVIEW: filter views are physical database objects, and dropping them improperly can leave dangling references in user interfaces or in saved filter definitions. During cloning or schema migration between 12.1.1 and 12.2.2, unresolved filter views may require rebuilding through RECREATE_RECORDFILTERVIEW or cleanup via CANCEL_RECORDFILTER/CANCEL_RECORDFILTERFORLIST. Customizations should target the public APIs that wrap this package rather than calling it directly.