Search Results use_organizer_for_query_find




Overview
Explore in AI Chat

Overview

QP_AM_UTIL is a small utility package in the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite, owned by the APPS schema. Its name and contents indicate that it supports the "Attribute Manager" (AM) and "Organizer" components used within Oracle Advanced Pricing and its related setup and query frameworks. Rather than encapsulating complex business logic, the package body functions as a configuration and capability probe: each function returns a fixed value that tells the calling code whether a particular feature or subsystem is considered available or enabled in the current installation. This pattern is common in EBS where feature flags are centralized so that dependent code can be upgraded or shipped to behave consistently across environments without embedding conditional compilation or hard-coded checks at every call site.

Key Procedures and Functions

The documented package exposes two public functions. Both are simple value-returning utilities:

  • ATTRMGR_INSTALLED (documented in the source excerpt as Attrmgr_Installed) — a public utility function that returns a status value indicating whether the Attribute Manager installation is present. In the documented body it unconditionally returns the string literal 'Y'. This constitutes a feature-detection flag that callers can query to determine whether Attribute Manager functionality should be treated as installed. Its classification is UTIL, confirming it performs no transactional work.
  • USE_ORGANIZER_FOR_QUERY_FIND — a public utility function that returns 'Y', indicating that the Organizer component should be used for query-find behavior. The ETRM listing normalizes the names as TO and USE_ORGANIZER_FOR_QUERY_FIND; TO corresponds to the ATTRMGR_INSTALLED entry in the source header. No parameter lists are documented, and none should be assumed; these are zero-argument functions returning VARCHAR2.

Tables Accessed

The documented metadata records no tables referenced via APPS synonyms. This is consistent with the source text: the package body is a compilation unit whose functions contain only a BEGIN/RETURN/END block, returning literal constants. It therefore performs no SELECT, INSERT, UPDATE, or DELETE against any database object, and it holds no state between calls. Because there is no data access, the package has no dependency on the FND or QP tables and cannot raise NO_DATA_FOUND or DML-related exceptions from table access.

Usage Notes

QP_AM_UTIL is described as being referenced by one other package, indicating a narrow dependency footprint within Oracle Advanced Pricing. In practice, such utility packages are invoked from PL/SQL callers — typically forms-based or OAF-based Advanced Pricing setup and query screens — where the calling code needs a lightweight, deterministic answer to a capability question. When a user searches for "attrmgr_installed," the most likely intent is to understand why a certain Advanced Pricing feature behaves as if the Attribute Manager is present. The documented source answers this directly: the function always returns 'Y', so any code path gated on Attrmgr_Installed will always take the "installed" branch regardless of environment. The same applies to Use_Organizer_for_Query_Find. Because the returns are constant, these functions are effectively hard-wired feature flags rather than true runtime detection. Customizations or diagnostics that expect dynamic detection should not rely on these functions for genuine conditional logic. For version and configuration auditing, administrators should treat QP_AM_UTIL as a stub-style utility whose behavior is fixed across 12.1.1 and 12.2.2.