Search Results source_first_name

Overview

The APPS.AST_LM_OPP_QUICK_SREP_V view is a denormalized reporting object within the Oracle EBS TeleSales (AST) module. It exposes a consolidated, read-only projection of opportunity records — represented internally as leads — joined with customer party information, sales stage and status lookups, sales channel lookups, and the assigned sales resource. The view is designed to support quick-search and quick-report ("QUICK_SREP") requirements, allowing TeleSales agents, sales managers, and reporting tools to retrieve opportunity data without navigating the full relational model of the AS_LEADS_ALL base table and its associated lookup and resource tables.

The object is owned by the APPS schema and is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its purpose is primarily reporting and integration: the flattened structure reduces join complexity for Business Intelligence Publisher reports, Oracle Discoverer worksheets, OAF-based quick-search pages, and custom concurrent programs. Since the view filters multilingual lookup tables using USERENV('LANG'), it inherently returns translated values appropriate to the session language.

Underlying Base Objects

The view is defined over the following documented base objects:

• AS_LEADS_ALL — the primary TeleSales opportunity/lead table, aliased as OPP. It provides lead identity, stage, status, channel, amount, probability, and date attributes.
• HZ_PARTIES — the Trading Community Architecture party table, aliased as PARTY, supplying the customer name and party type.
• AS_STATUSES_TL — the translated status lookup, joined on STATUS_CODE and language, yielding the STATUS meaning.
• AS_SALES_STAGES_ALL_TL — the translated sales stage lookup, supplying SALES_STAGE descriptions.
• OE_LOOKUPS — the Order Entry lookup view, restricted to LOOKUP_TYPE = 'SALES_CHANNEL', providing the CHANNEL meaning.
• AS_ACCESSES_ALL — the access/assignment table linking leads to sales resources, joined via SALESFORCE_ID.
• JTF_RS_RESOURCE_EXTNS — the resource extension table, aliased as SP, supplying RESOURCE_ID, SOURCE_FIRST_NAME, SOURCE_LAST_NAME, and SOURCE_NAME.

The joins enforce referential alignment across opportunity, party, lookup, access, and resource data, producing one row per opportunity-to-resource association.

Key Columns

The view exposes 27 columns. Identity and ownership columns include LEAD_ID, LEAD_NUMBER, CUSTOMER_ID, ORG_ID, and SOURCE_PROMOTION_ID. Descriptive attributes include CUSTOMER_NAME, PARTY_TYPE, ADDRESS_ID, OPPORTUNITY_NAME (aliased from DESCRIPTION), and PARENT_PROJECT.

Classification and state columns include SALES_STAGE_ID and SALES_STAGE, STATUS_CODE and STATUS, CHANNEL_CODE and CHANNEL, TOTAL_AMOUNT, WIN_PROBABILITY, and CLOSE_DATE (aliased from DECISION_DATE). Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

The columns relevant to the search term source_first_name are the resource-related columns RESOURCE_ID, SOURCE_FIRST_NAME, SOURCE_LAST_NAME, and SOURCE_NAME, all originating from JTF_RS_RESOURCE_EXTNS. SOURCE_FIRST_NAME represents the given name of the sales resource assigned to the opportunity, enabling filtering or display of opportunities by assigned agent.

Common Use Cases and Queries

Typical scenarios include agent-level pipeline reports, channel-by-stage summaries, and quick-search pages filtered by resource name. A representative query follows:

• SELECT lead_number, customer_name, sales_stage, status, channel, total_amount, source_first_name, source_last_name FROM apps.ast_lm_opp_quick_srep_v WHERE source_first_name = 'JOHN';
• SELECT sales_stage, channel, SUM(total_amount) FROM apps.ast_lm_opp_quick_srep_v GROUP BY sales_stage, channel;

Because the view resolves translations through USERENV('LANG'), consumers should ensure the reporting session's language context matches the intended output language.