Results for “oppr_to_order_cycle”

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

Overview

BIM_SUMV_SALES_CYCLE is a database view owned by the APPS schema within the Oracle E-Business Suite environment (12.1.1 / 12.2.2). It belongs to the BIM – Marketing Intelligence product family, now classified as obsolete. The view is registered as VALID in the data dictionary and functions as a consolidated read layer that joins the underlying summary tables to their associated dimension views. Its description is concise: "Joins the summary table to the dimension views."

In practical terms, the view presents sales cycle metrics (lead-to-order, lead-to-opportunity, and opportunity-to-order durations) enriched with descriptive dimension attributes such as media, marketing channel, market segment, and sales channel. Because these attributes are resolved through the BIM dimension views, the view delivers a denormalized result set suitable for direct reporting, dashboarding, or analytical integration without requiring callers to perform the multi-table joins themselves. The column most commonly associated with user searches for this object is SALES_CHANNEL_NAME, which supplies the human-readable sales channel descriptor.

Underlying Base Objects

The documented view metadata lists six referenced objects: three views and two synonyms plus a package:

• BIM_DIMV_MARKET_SGMTS (VIEW) – market segment dimension.
• BIM_DIMV_MEDIA_CHANNELS (VIEW) – media and channel dimension.
• BIM_DIMV_SALES_CHANNELS (VIEW) – sales channel dimension; source of SALES_CHANNEL_NAME.
• BIM_OPPR_CYCLE_SUMM (SYNONYM) – opportunity cycle summary table.
• BIM_SALES_CYCLE_SUMM (SYNONYM) – sales cycle summary table.
• FND_GLOBAL (PACKAGE) – referenced for session/context resolution.

The view definition is built as a UNION of two SELECT statements. The first reads from BIM_SALES_CYCLE_SUMM (aliased BSA) and populates LEAD_TO_ORDER_CYCLE and LEAD_TO_OPPR_CYCLE, setting OPPR_TO_ORDER_CYCLE to TO_NUMBER(NULL). The second reads from BIM_OPPR_CYCLE_SUMM (aliased BOP), populating only OPPR_TO_ORDER_CYCLE and nulling the two lead-cycle measures. Both branches join to the three dimension views on matching MEDIA_ID, CHANNEL_ID, MARKET_SEGMENT_ID, and SALES_CHANNEL_CODE keys.

Key Columns

• CAMPAIGN_ID, PERIOD_NAME, START_DATE, END_DATE – campaign identity and reporting period boundaries.
• MEDIA_ID, MEDIA_NAME, MEDIA_TYPE, MEDIA_TYPE_NAME – media dimension attributes.
• CHANNEL_ID, CHANNEL_NAME – marketing channel descriptors.
• MARKET_SEGMENT_ID, MARKET_SEGMENT_NAME – market segmentation attributes.
• GEOGRAPHY_CODE, SALES_CHANNEL_CODE – geographic and sales channel keys.
• SALES_CHANNEL_NAME – the descriptive name of the sales channel, resolved from BIM_DIMV_SALES_CHANNELS; a primary target for user queries.
• LEAD_TO_ORDER_CYCLE, LEAD_TO_OPPR_CYCLE, OPPR_TO_ORDER_CYCLE – numeric cycle-time measures.

Common Use Cases and Queries

Typical uses include cycle-time trend analysis, comparison of lead-to-order performance across sales channels, and export of enriched sales cycle data into BI dashboards. A representative query filtering on the sales channel name is:

SELECT campaign_id, period_name, sales_channel_name, lead_to_order_cycle, lead_to_oppr_cycle, oppr_to_order_cycle FROM apps.bim_sumv_sales_cycle WHERE sales_channel_name IS NOT NULL ORDER BY period_name;

Aggregate reporting by channel is equally straightforward:

SELECT sales_channel_name, AVG(lead_to_order_cycle) avg_l2o, AVG(oppr_to_order_cycle) avg_o2o FROM apps.bim_sumv_sales_cycle GROUP BY sales_channel_name;

Because the product is obsolete, queries should be limited to historical reporting and legacy integration scenarios.