Results for “doc_source_object_name”

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

Overview

BIC_INTERACTIONS_V is a read-only database view associated with the BIC (Customer Intelligence) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. BIC Customer Intelligence is designated as obsolete within the EBS application portfolio, meaning it is no longer actively developed or supported, though its underlying schema objects may still be present in installations that were upgraded from earlier releases or that carried the module forward.

The view consolidates interaction records captured by the JTF Interaction History framework (JTF_IH_*) with party and account information from the BIC party model (BIC_PARTIES_V). Its purpose is to present a flattened, reporting-friendly projection of customer interactions, enriched with decoded lookup descriptions for outcome, reason, and result codes, and with the document source object reference exposed through the DOC_SOURCE_OBJECT_NAME column. This column links an interaction to the originating business document (for example, a service request, order, or campaign activity), which is why a search for "doc_source_object_name" surfaces this view in the ETRM repository.

The view is explicitly defined WITH READ ONLY, so it cannot be used as a DML target; it serves exclusively as a query surface for reporting, ad hoc analysis, and integration extracts.

Underlying Base Objects

The ETRM documentation records no separately documented base objects for this view, but its defining text identifies the following referenced tables and views:

• JTF_IH_INTERACTIONS (I) — the primary interaction header table, supplying INTERACTION_ID, START_DATE_TIME, PARTY_ID, and the outcome, reason, and result identifiers.
• JTF_IH_ACTIVITIES (A) — the interaction activity table, supplying DOC_SOURCE_OBJECT_NAME, CUST_ACCOUNT_ID, and CUST_ORG_ID. It is outer-joined to the interaction header on INTERACTION_ID.
• BIC_PARTIES_V (P) — the BIC party view, supplying CUSTOMER_NAME and ACCOUNT_NUMBER, joined to activities on CUST_ACCOUNT_ID.
• JTF_IH_OUTCOMES_TL (O), JTF_IH_REASONS_TL (R), and JTF_IH_RESULTS_TL (S) — the translated lookup tables that decode the outcome, reason, and result identifiers into their SHORT_DESCRIPTION values. Each is outer-joined against the interaction header.

The join structure therefore hinges on CUST_ACCOUNT_ID as the linking key between the BIC party model and the JTF interaction activity records, with the interaction header acting as the driving row.

Key Columns

• CUSTOMER_NAME / ACCOUNT_NUMBER — the party name and account identifier from BIC_PARTIES_V, providing the customer context for each interaction.
• INTERACTION_ID — the unique identifier of the interaction header record; the primary correlation key for drilling into JTF_IH_INTERACTIONS.
• START_DATE_TIME — the timestamp at which the interaction began; the standard basis for date-range filtering and trend reporting.
• PARTY_ID — the party identifier recorded on the interaction, which may differ from the account-level party resolved through BIC.
• OUTCOME_ID / REASON_ID / RESULT_ID — the raw numeric lookup identifiers stored on the interaction header.
• OUTCOME / REASON / RESULT — the decoded SHORT_DESCRIPTION values from the corresponding _TL tables, suitable for direct display in reports.
• DOC_SOURCE_OBJECT_NAME — the name of the source business object that generated or is associated with the interaction activity; the key column for tracing interactions back to their originating document.
• CUST_ACCOUNT_ID / CUST_ORG_ID — the account and operating unit context carried on the activity record.

Common Use Cases and Queries

Typical usage centers on interaction analytics and linkage of interaction history to source documents. A representative query retrieves recent interactions for a given account with decoded dispositions:

• SELECT customer_name, account_number, interaction_id, start_date_time, outcome, reason, result, doc_source_object_name FROM bic_interactions_v WHERE account_number = :account AND start_date_time >= :from_date ORDER BY start_date_time DESC;
• SELECT doc_source_object_name, COUNT(*) FROM bic_interactions_v GROUP BY doc_source_object_name ORDER BY 2 DESC; — profiling interaction volume by originating document type.
• SELECT outcome, COUNT(*) FROM bic_interactions_v WHERE start_date_time BETWEEN :start AND :end GROUP BY outcome; — disposition trending for a reporting period.

Because the view is read-only and retains the outer-join semantics of its definition, rows may appear with null outcome, reason, or result descriptions where no lookup value exists. Consumers should account for these nulls in aggregates and displays. Given the obsolete status of BIC Customer Intelligence, use of this view should be limited to existing reporting obligations; new development should target supported interaction-history objects directly.