Search Results campaign_code




Overview
Explore in AI Chat

Overview

AS_OPPORTUNITY_LINES_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema and registered under the AS – Sales Foundation product family. It exposes the line-level detail of sales leads and opportunities maintained in AS_LEAD_LINES_ALL, enriched with descriptive attributes drawn from inventory, unit-of-measure, product hierarchy, and Oracle Marketing (AMS) source-code entities. The view is read-only by definition; it does not store data and its columns are derived at runtime from the join graph defined in its view text.

Its principal role is to provide a denormalized, query-friendly projection of opportunity lines for reporting, analytics, and integration. Rather than requiring report authors to resolve category concatenations, item key flexfield segments, UOM translations, and marketing campaign identifiers manually, the view presents these values as named columns. It is especially relevant to users searching for campaign_code, since the column CAMPAIGN_CODE is populated from AMS_P_SOURCE_CODES_V via the SOURCE_PROMOTION_ID foreign key on the lead line.

Underlying Base Objects

The view is defined over the following documented objects:

All joins other than the category hierarchy and the driving table itself are outer joins, so lead lines without a matching item, UOM, campaign, or offer record remain visible with null descriptive columns.

Key Columns

Common Use Cases and Queries

The view supports campaign attribution reporting, pipeline analysis by category or item, and extraction feeds into external CRM or BI platforms. A typical query filtering by campaign code is:

  • SELECT lead_line_id, lead_id, campaign_code, campaign_name, inventory_item_id, quantity, total_amount, forecast_date FROM as_opportunity_lines_v WHERE campaign_code = :p_campaign_code AND org_id = :p_org_id;
  • Aggregating pipeline value by campaign: SELECT campaign_code, SUM(total_amount), SUM(quantity) FROM as_opportunity_lines_v GROUP BY campaign_code;
  • Item-level demand extraction joining CONCATENATED_SEGMENTS and UNIT_OF_MEASURE_TL for order or forecast staging.
  • Category rollups using CONCATENATED_CAT_DESC for product management reporting.

Because the view is not indexed, filters on ORG_ID, LEAD_ID, and campaign columns should be applied to limit scan cost, and joins back to AS_LEAD_LINES_ALL on LEAD_LINE_ID can be used when additional base-table columns are required.