Search Results close_competitor_code

Overview

The view EDW_BIM_OPPR_OPRNTIES_LTC_IV belongs to the Oracle E-Business Suite Marketing Intelligence module, identified by the product code BIM. In Oracle EBS 12.1.1 and 12.2.2, this module is documented as obsolete, meaning it is retained only for backward compatibility and is not implemented in current installations. The view is an Enterprise Data Warehouse (EDW) extraction object whose name indicates a "LTC" (load-to-cache or incremental change capture) interface view, designed to expose opportunity data in a denormalized, flattened form suitable for bulk extraction into an external data warehouse or reporting layer.

The _IV suffix identifies the object as an interface view, a construct commonly used in Marketing Intelligence ETL pipelines to stage base table rows for downstream transformation. The view is defined as a simple projection over EDW_BIM_OPPR_OPRNTIES_LTC, adding a ROWID-derived surrogate key and remapping one attribute column into an OPERATION_CODE column, which is characteristic of change-data-capture extraction patterns that signal insert, update, or delete operations to a target system.

Underlying Base Objects

The ETRM metadata lists no referenced base objects and notes that the view is not implemented in the documented database. The view text, however, establishes its single documented dependency: the table or staging object EDW_BIM_OPPR_OPRNTIES_LTC. The view performs no joins, aggregations, or filters; it selects a fixed column list from that source object verbatim, with two exceptions. First, it exposes ROWID aliased as ROW_ID. Second, it selects USER_ATTRIBUTE5 a second time under the alias OPERATION_CODE, reusing a descriptive flexfield attribute column as an operational status flag.

Given the absence of documented base objects and the "Not implemented in this database" designation, the counterpart table should be treated as part of a Marketing Intelligence EDW schema that may be absent or deprecated in a given environment. The view therefore functions as a decoupling layer: extraction jobs reference the view, insulating them from any structural changes to the underlying LTC object.

Key Columns

• ROW_ID — the source ROWID, used as a unique row identifier for incremental processing.
• OPPORTUNITY_PK / OPPORTUNITY_PK_KEY — primary and foreign key references identifying the opportunity record.
• OPPORTUNITY_LEAD_ID / OPP_LEAD_NUMBER — identifiers and human-readable number for the opportunity or lead.
• NAME / OPP_DESCRIPTION — descriptive text for the opportunity.
• TOTAL_AMOUNT / CURRENCY_CODE / WIN_PROBABILITY — revenue, currency, and likelihood-of-win metrics supporting pipeline analysis.
• SALES_STAGE_ID / DECISION_DATE / CLOSE_REASON — sales-cycle attributes describing stage, expected decision timing, and outcome.
• CUSTOMER_ID / ADDRESS_ID / END_USER_CUSTOMER_NAME — customer and location context.
• CHANNEL_CODE / LEAD_SOURCE_CODE / SOURCE_PROMOTION_ID — source and channel attribution dimensions.
• CLOSE_COMPETITOR / CLOSE_COMPETITOR_CODE / CLOSE_COMPETITOR_ID — competitive outcome data.
• DELETED_FLAG / NO_OPP_ALLOWED_FLAG / DELETE_ALLOWED_FLAG — status and control flags governing deletion and opportunity eligibility.
• OPERATION_CODE — derived from USER_ATTRIBUTE5; signals the change operation for CDC extraction.
• USER_ATTRIBUTE1–5 / SECURITY_GROUP_ID / INSTANCE — flexfield attributes, data-security partitioning, and instance identification.

Common Use Cases and Queries

The principal use case is orchestrated extraction of opportunity data into an external warehouse, with OPERATION_CODE driving insert/update/delete handling. A representative query follows:

• Full extract: SELECT ROW_ID, OPPORTUNITY_PK, NAME, TOTAL_AMOUNT, CURRENCY_CODE, WIN_PROBABILITY, OPERATION_CODE FROM EDW_BIM_OPPR_OPRNTIES_LTC_IV;
• Pipeline summary: group by SALES_STAGE_ID and sum TOTAL_AMOUNT.
• Security-scoped extract: filter on SECURITY_GROUP_ID.

Because the object is obsolete and unimplemented, it should be used only for historical reference or migration validation against legacy Marketing Intelligence EDW interfaces.