Results for “doc_source_object_name”

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

Overview

BIC_ACTIVITIES_V is a reporting view that belongs to the BIC – Customer Intelligence product family within Oracle E-Business Suite. In the ETRM metadata supplied for release 12.2.2, BIC is flagged as (Obsolete), and the view is documented with the note "Not implemented in this database." Consequently, BIC_ACTIVITIES_V does not exist as a queryable object in current 12.1.1 or 12.2.2 environments and should be treated as a historical artifact rather than a supported integration point. Its documented purpose was to flatten interaction and activity records from the Interaction History (JTF_IH) schema and join them to customer, outcome, reason, result, and resource reference data, producing a single denormalized row per interaction activity. In the reporting and integration model of EBS, such views typically served as the data source for Customer Intelligence dashboards, activity analytics, and extract programs that needed human-readable descriptions rather than raw foreign key identifiers. Because the owning product is obsolete, no new development should depend on this view; the equivalent live data is available directly from the JTF_IH base tables and their translations.

Underlying Base Objects

The documented ETRM metadata states that no base objects are formally owned or registered for this view, which is consistent with an obsolete object that was never deployed. The view text, however, reveals the objects it was defined over. The primary driving tables are JTF_IH_ACTIVITIES (aliased A) and JTF_IH_INTERACTIONS (aliased I), linked on INTERACTION_ID with an outer join from activities to the parent interaction. Customer identification is supplied by BIC_PARTIES_V (aliased P), joined on CUST_ACCOUNT_ID. Reference descriptions are resolved through three translation tables: JTF_IH_OUTCOMES_TL (O), JTF_IH_REASONS_TL (R), and JTF_IH_RESULTS_TL (S), each outer-joined on its respective ID. Resource detail is provided by JTF_RS_RESOURCE_DTLS_VL (E), outer-joined on RESOURCE_ID. The join to JTF_IH_INTERACTIONS means an activity row survives even when its parent interaction is absent, while outcome, reason, result, and resource attributes return null when no matching reference row exists.

Key Columns

• CUSTOMER_NAME and ACCOUNT_NUMBER – Party name and account number sourced from BIC_PARTIES_V.
• INTERACTION_ID – Identifier linking the activity to its parent interaction record.
• START_DATE_TIME – Timestamp of the interaction, used for activity chronology and period reporting.
• OUTCOME_ID, REASON_ID, RESULT_ID – Foreign keys to the Interaction History reference tables.
• RESOURCE_ID and RESOURCE_NAME – Identifier and display name of the agent or resource that handled the activity.
• DOC_SOURCE_OBJECT_NAME – The source object descriptor used to trace the document or record that originated the activity; this column is the basis for the "doc_source_object_name" search term associated with this view.
• CUST_ACCOUNT_ID and CUST_ORG_ID – Customer account and operating unit identifiers used for partitioning and security filtering.
• OUTCOME, REASON, RESULT – Translated short descriptions resolved from the _TL tables.
• PHONE – Contact telephone number of the resource.

Common Use Cases and Queries

A typical consumer of this view counted or listed activities per customer, broken down by outcome, reason, or handling resource. A representative query, valid wherever the view remains deployed, might read:

SELECT CUSTOMER_NAME, ACCOUNT_NUMBER, INTERACTION_ID, START_DATE_TIME, RESOURCE_NAME, OUTCOME, REASON, RESULT FROM BIC_ACTIVITIES_V WHERE START_DATE_TIME >= :p_from_date ORDER BY START_DATE_TIME DESC;

Analysts searching for the doc_source_object_name would narrow results to activities originating from a specific document source, for example: SELECT INTERACTION_ID, DOC_SOURCE_OBJECT_NAME, CUSTOMER_NAME FROM BIC_ACTIVITIES_V WHERE DOC_SOURCE_OBJECT_NAME = :p_source;. Because the object is obsolete, equivalent queries should be rewritten against JTF_IH_ACTIVITIES joined directly to the JTF_IH reference tables, replacing BIC_PARTIES_V with a current customer view such as HZ_CUST_ACCOUNTS_V. All such queries benefit from filtering on CUST_ACCOUNT_ID and date range to avoid full scans of the Interaction History tables.