Search Results campaign_code




Overview
Explore in AI Chat

Overview

The AST_LS_OPP_SREP_ADV_V view is a reporting object belonging to the Oracle E-Business Suite TeleSales (AST) module. It presents a denormalized, report-ready projection of opportunity (lead) data, joining the core lead record to customer party information, sales stage and status lookups, sales representative details, primary contact information, and campaign source code data. Its name—"Opportunity Sales Representative Advanced View"—indicates that it is intended primarily for advanced opportunity and sales-representative reporting, exposing a wide attribute set in a single queryable object.

An important implementation note is recorded in the source metadata: this view is not implemented in this database. As such, the view serves as a documentation and reference artifact—its SQL text is preserved for analysis, customization guidance, and upgrade impact assessment, but it does not physically exist as a queryable object in the installation described by that metadata. This distinction is critical when diagnosing errors such as ORA-00942 (table or view does not exist) for customers who reference it directly.

Underlying Base Objects

The view is defined over six base objects, joined in a single flat SELECT:

  • AS_LEADS_ALL (aliased OPP) — the primary opportunity/lead record, driving most columns.
  • AS_LEAD_CONTACTS_ALL (aliased LEAD_CONTACT) — supplies the primary contact link; outer-joined to preserve leads without contacts.
  • AS_ACCESSES_ALL (aliased ACC) — the access table that maps the sales representative (person) to the lead.
  • PER_ALL_PEOPLE_F (aliased PER) — resolves the sales representative's first and last names.
  • HZ_PARTIES (aliased PARTY and PARTY_CONTACT) — supplies customer name, address components, and contact person names; the contact join is also outer.
  • AMS_SOURCE_CODES (aliased CAMP) — supplies the campaign source code; outer-joined.
  • AS_SALES_STAGES_ALL_VL (aliased ASS) and AS_STATUSES_VL (aliased AST) — value-list lookups translating stage and status identifiers into descriptive text.

Joins rely on LEAD_ID, CUSTOMER_ID/PARTY_ID, SALES_STAGE_ID, STATUS_CODE, SOURCE_PROMOTION_ID, and PERSON_ID. No base objects were separately documented in the ETRM metadata beyond those embedded in the view text.

Key Columns

Common Use Cases and Queries

Typical uses include opportunity funnel reporting by sales representative, campaign-influenced pipeline analysis (filtering on CAMPAIGN_CODE), and regional opportunity summaries. Example:

SELECT LEAD_NUMBER, CUSTOMER_NAME, SALES_STAGE, SALES_REP_LAST_NAME, CAMPAIGN_CODE, REVENUE_AMOUNT FROM AST_LS_OPP_SREP_ADV_V WHERE CAMPAIGN_CODE = '&campaign_code' ORDER BY REVENUE_AMOUNT DESC;

Because the view is documented as not implemented, substitute the constituent base tables if the view yields ORA-00942.