Search Results gt_v




Overview

IEC_RECORD_FILTER_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a Private (PVT) API. Its business function is to support the Trade Management (formerly Oracle Advanced Marketing / AMS) "record filter" capability, which determines which marketing list entries and customer records are eligible for selection during campaign, list, and territory processing. The package provides the internal engine behind record filtering: it constructs and manages database views over source record queries, applies filter criteria, and controls the availability of list entries that have been flagged as "do not use." Because the package is private, it is not intended for direct customer invocation; it is called by its parent public packages and by concurrent processing.

Key Procedures and Functions

The package exposes eight documented procedures and functions. All are private helpers invoked by higher-level record-filter APIs.

  • MAKE_LISTENTRIESAVAILABLE — Restores list entries that carry a specified "do not use" reason code by setting the DO_NOT_USE_FLAG to 'N' in IEC_G_RETURN_ENTRIES. Report counts are updated to reflect the newly available entries. Parameters include a list header identifier, a do-not-use reason code, and a commit indicator, with a return status output.
  • GET_RECORDFILTERVIEW — Retrieves the name or definition of the database view that materializes a record filter's source records.
  • RECREATE_RECORDFILTERVIEW — Rebuilds the record filter view, typically after the underlying filter criteria or source query have changed.
  • DROP_RECORDFILTERVIEW — Removes an existing record filter view from the data dictionary.
  • GET_RECORDFILTERSOURCETYPE — Returns the source type associated with a record filter, identifying the underlying record source that the filter operates against.
  • APPLY_RECORDFILTER — Applies a record filter to the source data, producing the filtered set of records used by downstream list and campaign processing.
  • CANCEL_RECORDFILTER — Reverses or cancels an applied record filter operation.
  • CANCEL_RECORDFILTERFORLIST — Cancels record filter processing scoped to a specific marketing list.

Tables Accessed

The package reads and writes the following objects, referenced through APPS synonyms:

  • IEC_G_RETURN_ENTRIES — The principal working table. The DO_NOT_USE_FLAG column is updated here by MAKE_LISTENTRIESAVAILABLE.
  • AMS_LIST_HEADERS_ALL — Provides marketing list header context, linking filter operations to a specific list.
  • IEC_G_MKTG_ITEM_CC_TZS — Territory/assignment data supporting record source determination.
  • FND_ORACLE_USERID — Queried by the private Get_AppsSchemaName function to resolve the APPS schema name (ORACLE_USERNAME where READ_ONLY_FLAG = 'U').
  • ALL_VIEWS — Used to verify existence of record filter views before creation or drop operations.
  • DBMS_SQL and PLITBLM — Dynamic SQL and PL/SQL table utilities employed to build and manipulate the generated filter views at runtime.

Usage Notes

Because IEC_RECORD_FILTER_PVT is a private package, it is invoked internally by two other packages rather than by end users or custom code. Typical invocation paths include marketing list maintenance forms and the concurrent programs that process list entries, where MAKE_LISTENTRIESAVAILABLE is called when a user reverses a do-not-use decision and APPLY_RECORDFILTER/CANCEL_RECORDFILTER are driven during filter execution. The package embeds an internal Log procedure that delegates errors to IEC_OCS_LOG_PVT.LOG_INTERNAL_PLSQL_ERROR, populating the package-global g_error_msg; unexpected errors are re-raised as fnd_api.g_exc_unexpected_error. The record filter views it creates and drops are dynamically generated, so DBMS_SQL and ALL_VIEWS are central to its operation. Customizations should target the public wrapper packages rather than this private body, since its interface is not guaranteed across EBS 12.1.1 and 12.2.2.