Results for “import_interface_id”

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

Overview

AML_INTERACTION_LEADS is a table owned by the AMS schema within the Oracle E-Business Suite Marketing (AMS) module. It defines the relationship between interactions, responses, and sales leads, serving as the association layer that links marketing interactions to the leads they generate or influence. In EBS 12.1.1 and 12.2.2, this object is central to tracking the outcome of marketing activities — specifically, which interactions produced which leads.

Under the heuristic Data Vault classification derived from its foreign key structure, AML_INTERACTION_LEADS is modeled as a link table. This classification is a modeling suggestion: the table does not represent a business entity in its own right, but rather an associative relationship (a many-to-many bridge) connecting interactions, import interface records, and sales leads. The physical schema confirms 16 columns and two unique indexes, consistent with a relationship-table design.

Key Information Stored

The table's surrogate primary key is INTERACTION_LEAD_ID, enforced by the unique index AML_INTERACTION_LEADS_PK. This column uniquely identifies each interaction-to-lead association record.

• INTERACTION_LEAD_ID — The surrogate primary key (AML_INTERACTION_LEADS_PK); a system-generated identifier for the association row.
• INTERACTION_ID — Foreign key to JTF_IH_INTERACTIONS; identifies the marketing interaction (call, visit, campaign touch) that the record belongs to.
• SALES_LEAD_ID — Foreign key to AS_SALES_LEADS; identifies the sales lead linked to the interaction.
• IMPORT_INTERFACE_ID — Foreign key to AS_IMPORT_INTERFACE; identifies the import source or interface batch through which the record was loaded.
• SCORE — A numeric value representing the lead score or weighting assigned to the interaction-to-lead relationship, supporting lead qualification and ranking.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; supports multi-org / data-security partitioning of the record.
• CREATION_DATE, CREATED_BY — Standard audit columns capturing row insertion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J layer to detect concurrent updates.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program / request context columns identifying the batch process that created or last updated the row.

Two unique indexes are documented: AML_INTERACTION_LEADS_U1 on INTERACTION_LEAD_ID and AML_INTERACTION_LEADS_U2 on the composite (INTERACTION_ID, IMPORT_INTERFACE_ID, SALES_LEAD_ID). The U2 index is the business-key candidate, ensuring that a given interaction, import source, and lead combination is not duplicated.

Common Use Cases and Queries

Typical uses include lead attribution reporting, campaign ROI analysis, and tracing which interactions influenced a lead. A join across the three core foreign keys reconstructs the full relationship:

SELECT l.INTERACTION_LEAD_ID, i.INTERACTION_ID, s.SALES_LEAD_ID, l.SCORE
FROM AMS.AML_INTERACTION_LEADS l,
  JTF_IH_INTERACTIONS i, AS_SALES_LEADS s
WHERE l.INTERACTION_ID = i.INTERACTION_ID
  AND l.SALES_LEAD_ID = s.SALES_LEAD_ID;

To obtain the highest-scoring interactions per lead, query ordering by SCORE descending grouped by SALES_LEAD_ID. To audit batch-loaded associations, filter by IMPORT_INTERFACE_ID or REQUEST_ID. Security-group-aware queries should filter on SECURITY_GROUP_ID.

Related Objects

• JTF_IH_INTERACTIONS — joined via INTERACTION_ID; the parent interaction record.
• AS_SALES_LEADS — joined via SALES_LEAD_ID; the lead entity linked to the interaction.
• AS_IMPORT_INTERFACE — joined via IMPORT_INTERFACE_ID; the import/interface batch source.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs data visibility.
• AML_INTERACTION_LEADS_PK / _U1 / _U2 — the primary key and unique indexes enforcing integrity.