Results for “source_code”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_IH_INTERACTIONS_CAMPAIGNS is a CRM Foundation (JTF) intersection table that links Interaction records to Campaign records within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the JTF schema and is documented with a status of VALID. Its purpose is to associate the individual customer touchpoints captured by the interaction subsystem with the marketing initiatives defined in the campaign model, enabling attribution analysis across the CRM stack.

Under a heuristic Data Vault classification mined from its foreign key structure, the table is modeled as a link entity. It carries no descriptive measures of its own; its role is to resolve a many-to-many relationship between two hubs (interactions and campaigns) while also recording the source through which the association was derived. Although the primary key constraint name is documented as JTF_IH_INTERACTIONS_CAMPAIG_PK, the unique index JTF_IH_INTERACTIONS_CAMPAIG_U1 covers only the INTERACTION_ID column, indicating that a given interaction maps to a single campaign row in this table.

Key Information Stored

The documented physical schema exposes 12 columns. The most significant are:

  • INTERACTION_ID — the foreign key to JTF_IH_INTERACTIONS; also serves as the sole business-key candidate via unique index JTF_IH_INTERACTIONS_CAMPAIG_U1 and forms part of the primary key constraint JTF_IH_INTERACTIONS_CAMPAIG_PK.
  • OBJECT_ID — identifier of the associated object within the interaction-campaign context.
  • OBJECT_TYPE — discriminator describing the type of object referenced by OBJECT_ID.
  • SOURCE_CODE_ID — foreign key to AMS_SOURCE_CODES, identifying the source attribution for the association.
  • SOURCE_CODE — denormalized source designation, typically carried alongside the source code identifier for reporting convenience.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org and data-security partitioning of the link row.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework to detect concurrent updates.
  • CREATED_BY / CREATION_DATE — standard WHO audit columns recording row creation.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns recording the last modification and the login context in which it occurred.

The surrogate primary key is the constraint JTF_IH_INTERACTIONS_CAMPAIG_PK, whose documented component is INTERACTION_ID. The remaining columns are descriptive and audit attributes rather than unique identifiers.

Common Use Cases and Queries

Typical reporting scenarios include measuring campaign influence on customer interactions, reconciling interaction volumes against campaign activity, and tracing source attribution for CRM analytics.

Joining the link to its parent tables is the most common access pattern:

  • Interactions for a campaign — join JTF_IH_INTERACTIONS_CAMPAIGNS to JTF_IH_INTERACTIONS on INTERACTION_ID to retrieve interaction details associated with a campaign object.
  • Source attribution — join SOURCE_CODE_ID to AMS_SOURCE_CODES to resolve the descriptive source name, enriched by the denormalized SOURCE_CODE column.
  • Security-filtered extracts — enforce SECURITY_GROUP_ID filtering when extracting data for delegated administrators or multi-org reporting.
  • Incremental loads — use LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to drive delta interfaces into a warehouse or data mart.

A representative pattern selects the campaign association for a given interaction by filtering on the business-key candidate INTERACTION_ID, which is fully covered by the unique index JTF_IH_INTERACTIONS_CAMPAIG_U1.

Related Objects

The following objects are the most significant dependencies, drawn from the documented foreign key relationships:

  • JTF_IH_INTERACTIONS — parent table; joined on JTF_IH_INTERACTIONS_CAMPAIGNS.INTERACTION_ID = JTF_IH_INTERACTIONS.INTERACTION_ID.
  • AMS_SOURCE_CODES — lookup table; joined on JTF_IH_INTERACTIONS_CAMPAIGNS.SOURCE_CODE_ID = AMS_SOURCE_CODES.SOURCE_CODE_ID.
  • FND_SECURITY_GROUPS — security reference table; joined on JTF_IH_INTERACTIONS_CAMPAIGNS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • AMS campaign tables (AMS_ACTIVE_CAMPAIGNS and related AMS objects) — campaign definitions resolved through OBJECT_ID and OBJECT_TYPE, which the link stores generically.

Applications that maintain or query this link should respect the unique constraint on INTERACTION_ID and populate the WHO audit columns through the standard OA Framework persistence layer to keep OBJECT_VERSION_NUMBER consistent across concurrent sessions.