Search Results amv_search_pvt




Overview
Explore in AI Chat

Overview

AMV_SEARCH_PVT is an internal (private) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle Marketing / Advanced Marketing (AMV) module and underpins the search and discovery capabilities used to locate marketing content, repositories, and repository areas. In the Oracle EBS architecture the AMV product family supports the storage, categorization, and retrieval of marketing collateral, and AMV_SEARCH_PVT provides the runtime search engine logic that services these operations.

The package is classified as PVT, meaning it is a private implementation package not intended for direct invocation by external or customer code. It exposes its functionality to other AMV packages, which act as the public API layer. The dependency metadata confirms that AMV_SEARCH_PVT calls into AMV_CATEGORY_PVT, AMV_UTILITY_PVT, and AMV_U_ACCESS, and that it is referenced by eight other packages, indicating it is a central, reused component of the AMV search subsystem. No external object in the database references it directly, reinforcing its private status.

Key Procedures and Functions

The documented API surface comprises four named program units:

  • FIND_REPOSITORIES — Locates and returns the set of repositories available to a search operation, respecting the caller's access rights. It gives the search subsystem its top-level scope by determining which repositories the user or process is permitted to query.
  • FIND_REPOSITORY_AREAS — Resolves the areas (subdivisions) within a given repository, refining the scope of a subsequent content search. Repository areas typically correspond to logical groupings of marketing items such as categories or channels.
  • CONTENT_SEARCH — The core search routine that queries marketing items based on the criteria assembled by the calling layer and returns matching content. It is the principal business function of the package and drives the results returned to the requester.
  • BUILD_IMT_STRING — Constructs a dynamically generated SQL statement, known in Oracle documentation as an IMT (intermedia text) string. This string is used by the dynamic SQL machinery (DBMS_SQL) to execute the actual content query, allowing flexible, runtime-assembled search predicates.

The procedure contract details, including parameter lists, are not reproduced in the ETRM metadata and should be obtained from the actual package source or the Oracle ETRM repository before any extension or custom integration.

Tables Accessed

Per the documented dependencies, the package references the following tables and resources via APPS synonyms:

  • AMV_U_ACCESS — An access-control table used to enforce user and role visibility over repositories and marketing items, ensuring search results honor security restrictions.
  • DBMS_SQL — The Oracle-supplied dynamic SQL package, used to parse, execute, and fetch results from the runtime-built IMT query string.
  • PLITBLM — The Oracle-supplied PL/SQL table index-by binary integer package, used for collection/array handling within the search logic.

The broader dependency list also shows access to JTF_AMV_ITEMS_VL and the AMV_C_CATEGORIES_VL and AMV_C_CHANNELS_VL views, which supply the marketing item content together with its category and channel attributes. Temporary working sets are held in AMV_TEMP_IDS and AMV_TEMP_NUMBERS, which act as transient collections during repository and content resolution.

Usage Notes

AMV_SEARCH_PVT is a private package and is not meant to be called directly from forms, concurrent programs, or customer-written code. It is invoked internally by the higher-level AMV packages that present search functionality to the user, typically through the Oracle Marketing application forms and the corresponding public APIs. Because it uses dynamically constructed SQL executed through DBMS_SQL, its behavior depends on the IMT string assembled by BUILD_IMT_STRING and on the access filters derived from AMV_U_ACCESS.

Customizations that require changes to search behavior should be made at the public AMV API layer rather than by modifying or overriding AMV_SEARCH_PVT, since the package is documented, proprietary, and subject to change across releases. Database administrators and developers troubleshooting search results, performance, or access issues may inspect it, but any direct invocation or extension carries upgrade risk and should be avoided in production environments.