Search Results build_imt_string

Overview

APPS.AMV_SEARCH_PVT_W is the public wrapper package for the AMV (Advanced Marketing / Marketing Verdict) Search private API in Oracle E-Business Suite. It belongs to the Oracle Marketing (AMS/AMV) family of modules and exposes a Rosetta-style generated interface that allows the internal PL/SQL implementation package, AMV_SEARCH_PVT, to be invoked from Java, JSP, or any tier that communicates through JDBC and strongly-typed table parameters rather than native PL/SQL collections.

The package's core business purpose is to drive search behavior across marketing repositories and their associated areas. It resolves which repositories and repository areas are relevant, executes a content search, and supports the construction of informational matching text used by the search engine. In Oracle EBS 12.1.1 and 12.2.2, this package remains part of the standard APPS schema installation, with its header traceable to the 2005 development cycle (amvwsers.pls 120.2). It is classified as an OTHER API, meaning it is not a documented business-facing interface but a support/wrapper artifact.

Key Procedures and Functions

The documented interface contains eighteen procedures, dominated by the auto-generated Rosetta table copy routines and a smaller set of functional entry points.

• ROSETTA_TABLE_COPY_IN_P0 / COPY_OUT_P0 — marshal character data between the calling tier's JTF_VARCHAR2_TABLE_4000 and the internal amv_char_varray_type.
• ROSETTA_TABLE_COPY_IN_P1 / COPY_OUT_P1 — marshal numeric data between JTF_NUMBER_TABLE and the internal amv_number_varray_type.
• ROSETTA_TABLE_COPY_IN_P5 / COPY_OUT_P5 — convert repository-area data, pairing a number table with a 100-character varchar2 table into amv_area_varray_type.
• ROSETTA_TABLE_COPY_IN_P7 / COPY_OUT_P7 — convert repository search results via amv_searchrep_varray_type, combining four varchar2/number arrays.
• ROSETTA_TABLE_COPY_IN_P9 / COPY_OUT_P9 — convert combined search/area result sets through amv_searchara_varray_type, the widest conversion pair in the package.
• ROSETTA_TABLE_COPY_IN_P11 / COPY_OUT_P11 — additional marshalling pair for a further typed collection.
• ROSETTA_TABLE_COPY_IN_P13 / COPY_OUT_P13 — additional marshalling pair for a further typed collection.
• FIND_REPOSITORIES — returns the set of marketing repositories matching the caller's search criteria.
• FIND_REPOSITORY_AREAS — returns the areas (subdivisions) belonging to identified repositories.
• CONTENT_SEARCH — performs the actual content-level search across the selected repository areas.
• BUILD_IMT_STRING — constructs the informational matching text (IMT) string used in repository search processing. This is the procedure most frequently referenced by developers searching for build_imt_string, typically to understand or debug how search match text is assembled before being passed to the content search logic.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM. This is a standard Oracle Applications infrastructure table associated with PL/SQL IMT (informational matching text) processing. Its presence here aligns directly with the BUILD_IMT_STRING routine, indicating that the package reads supporting metadata from PLITBLM when assembling IMT strings prior to invoking the content search. The repository, area, and search result structures are conveyed through the typed varrays rather than by direct base-table access within the wrapper, since the wrapper delegates substantive work to AMV_SEARCH_PVT.

Usage Notes

AMV_SEARCH_PVT_W is not intended for direct invocation from Oracle Forms or concurrent programs. It is a generated interoperability wrapper: the underscore-prefixed "_W" suffix and the Rosetta conversion routines identify it as the Java-facing layer above AMV_SEARCH_PVT. Typical invocation occurs from Oracle Marketing web-tier Java code, JSP pages, or OAF-based marketing search screens, where a JDBC callable statement binds the JTF array types and the wrapper translates them into native PL/SQL varrays.

Because the package is referenced by one other package and classified as OTHER, customizations should treat it as an internal dependency rather than a supported extension point. Developers investigating BUILD_IMT_STRING should note that the procedure exists to prepare matching text consumed by CONTENT_SEARCH; altering its behavior, or calling it directly outside the packaged sequence of FIND_REPOSITORIES, FIND_REPOSITORY_AREAS, and CONTENT_SEARCH, risks inconsistent search results. Standard practice is to invoke the higher-level search flow and inspect debug output rather than to call BUILD_IMT_STRING in isolation.