Search Results as_sl_imp_batch_s

Overview

APPS.AML_INTERACTION_ENGINE is a PL/SQL package body residing in the APPS schema that serves as the interaction-processing engine within the Oracle E-Business Suite Marketing and Sales Lead Management modules. Its primary business function is to evaluate, transform, and route inbound marketing interactions—including leads, activities, and imported lead batches—into the appropriate interaction records and downstream sales lead structures. The package acts as an orchestration layer that coordinates data captured from external import interfaces, party and party-site master data, resource/group constructs, and product or source classification, then applies business event logic to determine how each interaction should be categorized and stored.

The package is classified as an OTHER API within the ETRM metadata. At the time of documentation the package body carries a VALID status, indicating that it compiled cleanly against the referenced database objects. It is not referenced by any other database object, confirming that it is a top-level program invoked directly by concurrent processing or external callers rather than an internal helper package.

Key Procedures and Functions

• RUN_INTERACTION_ENGINE — The sole documented procedure in the package. It represents the main entry point for the interaction engine execution cycle, carrying out the batch evaluation of interaction and lead data. Based on the surrounding dependency footprint, this procedure is responsible for reading staged or imported interaction records, applying business event type rules, and propagating qualifying records into sales lead and interaction tables. The procedure is designed to run as a set-based batch operation rather than a single-record call, as evidenced by the heavy dependence on concurrent-processing facilities.

No parameter lists are documented in the ETRM metadata for this procedure; the description above is inferred strictly from the documented dependencies and the procedure name. Additional internal helper code exists within the package body, but only RUN_INTERACTION_ENGINE is catalogued as a public documented entry point.

Tables Accessed

The package references a broad set of base tables through APPS synonyms. Interaction and lead tables—AML_INTERACTION_LEADS, AML_BUSINESS_EVENT_TYPES_B, AS_SALES_LEADS, and AS_SL_IMP_BATCH_S—form the core read/write targets, holding incoming lead data, the business event type definitions that drive classification, and the sales-lead import batch identifiers. Interface and staging tables AS_IMPORT_INTERFACE, AS_IMPORT_INTERFACE_S, AS_IMP_LINES_INTERFACE, and AS_IMP_LINES_INTERFACE_S supply the inbound rows that the engine consumes and reconciles.

Trading Community Architecture tables HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS provide party and address context used to resolve and enrich interactors. Interaction history is captured in JTF_IH_ACTIVITIES and JTF_IH_INTERACTIONS. Resource and group structures—JTF_RS_GROUPS_B, JTF_RS_GROUP_MEMBERS, JTF_RS_GROUP_USAGES, JTF_RS_ROLES_B, JTF_RS_ROLE_RELATIONS, and JTF_RS_RESOURCE_EXTNS—support assignment and routing logic. Product and source classification draws on MTL_SYSTEM_ITEMS_B, AMS_ACT_PRODUCTS, and AMS_SOURCE_CODES. Supporting PL/SQL packages referenced include AS_SALES_LEAD_ENGINE_PVT, AS_SALES_LEAD_LINES_PKG, and AML_INTERACTION_LEADS_PKG, along with FND_API, FND_CONCURRENT, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, and FND_REQUEST, which together indicate a concurrently executed, message-logging, profile-driven batch process.

Usage Notes

AML_INTERACTION_ENGINE is typically invoked as a concurrent program or through custom batch scheduling, given its dependency on FND_CONCURRENT, FND_REQUEST, and FND_FILE. It is not referenced by other packages or forms, so it functions as a standalone processing engine. In the context of Oracle EBS 12.1.1 and 12.2.2, it is expected to be executed after lead import staging has been populated into the AS_IMP_* interface tables and batch identifiers exist in AS_SL_IMP_BATCH_S. The user search term "as_sl_imp_batch_s" aligns directly with this usage pattern: the batch key identifies which staged import run is to be processed by RUN_INTERACTION_ENGINE. Because the package is owned by APPS and documented as OTHER, any custom invocation should respect the standard concurrent request submission pattern and rely on FND_GLOBAL for session context.