Search Results interaction_tbl_type

Overview

AML_INTERACTION_ENGINE is an Oracle EBS Applications (APPS) PL/SQL package that belongs to the Oracle Marketing (AMS/AML) product family. Its principal business function is to generate and manage sales or marketing "interactions" and interaction leads by correlating business events, parties, and sales-lead data captured across the CRM schema. The package header, shipped under the file amlitens.pls (version 115.1, dated 2003/10/22), is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner.

From a functional standpoint, the interaction engine drives the automated creation of lead and activity records that link a party to a business event, supporting campaign execution, telemarketing, and lead qualification workflows in Oracle Marketing and Oracle Sales. The engine is intended to run against a rolling window of recent activity, defined by the public constant G_LOOKBACK_DAYS NUMBER := 30, which limits processing to data captured within the preceding 30 days.

Key Procedures and Functions

The package exposes a single documented routine:

• RUN_INTERACTION_ENGINE — The main entry point that executes the interaction engine logic. It returns the standard concurrent-program output parameters (error buffer and return code) and accepts debug and trace mode flags to control diagnostics during execution. The procedure orchestrates the identification of business events and the generation of interaction and lead records.

The specification also declares supporting public constructs used by the routine:

• INTERACTION_REC_TYPE — A record type holding an interaction identifier and party identifier.
• INTERACTION_TBL_TYPE — A PL/SQL associative-array (index-by) table of the above record type, used to accumulate interaction data in memory.
• Global variables — g_user_id, g_last_update_login, g_prog_appl_id, g_prog_id, and g_request_id, which carry audit and concurrent-program context.

Tables Accessed

The package reads and writes a broad set of CRM entities through APPS synonyms:

• AML_BUSINESS_EVENT_TYPES_B — Defines the business event types that qualify for interaction generation.
• AML_INTERACTION_LEADS — The primary target table where generated interaction leads are stored.
• AS_SALES_LEADS, AMS_ACT_PRODUCTS, AMS_SOURCE_CODES — Supply sales-lead, product, and source-code data used to qualify and enrich leads.
• AS_IMPORT_INTERFACE and AS_IMPORT_INTERFACE_S, AS_IMP_LINES_INTERFACE and AS_IMP_LINES_INTERFACE_S, AS_SL_IMP_BATCH_S — Sales-lead import interface tables consumed during processing.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_RELATIONSHIPS — TCA registry data resolving party identities, addresses, and relationships.
• JTF_IH_ACTIVITIES — Interaction-history activities associated with generated interactions.

Usage Notes

Because the package exposes a concurrent-program-style signature (ERRBUF, RETCODE, debug and trace flags), AML_INTERACTION_ENGINE is typically invoked from a registered Oracle EBS concurrent program, or scheduled through the standard request submission framework. It may also be called from custom PL/SQL code that provisions the global context variables (g_user_id, g_request_id, and related fields) before invoking RUN_INTERACTION_ENGINE. ETRM records show the package is referenced by zero other packages, indicating it functions as a standalone driver rather than a shared library. Given the 12.1.1 / 12.2.2 source line, implementers should treat the diagnostic parameters as the supported mechanism for troubleshooting runs.