Results for “ams_discoverer_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_DISCOVERER_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle Marketing (AMS) product family. It provides the internal implementation layer for Oracle Discoverer integration within Oracle E-Business Suite 12.1.1 and 12.2.2. Specifically, the package encapsulates the logic required to build, parameterize, encrypt, and execute search queries against Discoverer-based data sources registered in Oracle Marketing. It acts as the backend engine behind the public wrapper package AMS_DISCOVERER_PVT_W, which exposes the same functionality to forms, concurrent programs, and other calling code.

The package is classified as a PVT (private) API, meaning its procedures and functions are not intended for direct invocation by external or customer-developed code. Its responsibilities center on translating a user-defined search definition into a usable Discoverer URL or SQL string, applying the necessary security transformations, and persisting or retrieving the search configuration from the marketing transaction tables.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within this package:

• CREATE_DISCOVERER_URL — Constructs a fully qualified Discoverer URL from a stored search definition. This URL is used to launch the Discoverer workbook or query in the appropriate user context.
• EUL_TRIGGER$POST_SAVE_DOCUMENT — A trigger-style procedure invoked after a search document is saved. It performs post-save processing, ensuring the End User Layer (EUL) and related metadata remain synchronized with the saved document.
• SEARCH_SQL_STRING — Returns the SQL string associated with a given search definition. This function supplies the executable query text that underpins Discoverer-based searching.
• ENCRYPT_PARAM — Applies encryption to parameters passed through the Discoverer URL, protecting sensitive values (such as identifiers or user-supplied criteria) from exposure.
• BATCH_SEARCH_SQL — Produces or executes SQL suitable for batch search operations, supporting set-based processing rather than single-record interactive queries.

Tables Accessed

The package reads from and writes to several AMS tables and standard Oracle constructs via APPS synonyms:

• AMS_DISCOVERER_SQL — The primary table storing Discoverer SQL definitions. The package uses it to persist and retrieve the SQL text referenced by SEARCH_SQL_STRING, BATCH_SEARCH_SQL, and CREATE_DISCOVERER_URL.
• AMS_DISCOVERER_SQL_S — The sequence table used to generate unique identifiers for new rows inserted into AMS_DISCOVERER_SQL.
• AMS_LIST_SRC_TYPES — Provides source-type metadata that determines how the Discoverer query should be interpreted or where the underlying list data originates.
• DUAL — Used for scalar evaluations, such as validating expressions or returning single computed values.
• PLITBLM — The PL/SQL internal table type used for passing collections of parameters or values within the package's procedures.

Usage Notes

AMS_DISCOVERER_PVT is not called directly. It is invoked indirectly through the public wrapper AMS_DISCOVERER_PVT_W, which is referenced by the Oracle Marketing forms and other application components. The ETRM dependency listing also shows the package is referenced by IGS_PE_DYNAMIC_PERSID_GROUP, indicating a cross-product dependency with Oracle Student Systems in deployments that include that module.

Typical invocation paths include:

• Marketing forms that allow users to define, save, and run Discoverer-based searches.
• Concurrent or batch programs that execute stored search definitions in bulk.
• Internal framework code requiring an encrypted Discoverer URL or post-save document synchronization.

Because it is a private package, customizations should always target the public wrapper or documented AMS APIs rather than AMS_DISCOVERER_PVT directly. Its procedures are tightly coupled to the Discoverer EUL and the AMS_DISCOVERER_SQL schema, so any direct modification risks invalidating the package or breaking dependencies across products. The package has been validated as VALID in both 12.1.1 and 12.2.2, and its behavior is consistent across those releases.