Results for “parent_project”

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

Overview

The view APPS.AST_MYTEAM_SALESOPP_UWQ_R_S_V is a reporting and integration object within the Oracle E-Business Suite TeleSales (AST) module. It is registered in the ETRM metadata repository with a status of VALID and is owned by the APPS schema. The naming convention, incorporating the UWQ (Universal Work Queue) and R_S_V (reporting/select view) tokens, indicates that this object is designed to supply the Universal Work Queue and associated TeleSales reporting components with a curated, denormalized projection of sales opportunity data belonging to a sales representative's team.

The view presents a distinct set of opportunity records joined to the resource-accesses that authorize a given salesforce resource to work them. Conceptually, it answers the question: "Which open opportunities are visible to the members of my team?" Because it emits a stable, flat structure, it functions as a convenient source for concurrent reports, OBIEE/BI Publisher extracts, and custom integrations that need opportunity and access information in a single row.

Underlying Base Objects

The documented ETRM metadata lists the following referenced base objects:

• AS_LEADS_ALL (SYNONYM) — the primary opportunity and lead entity in TeleSales. All opportunity-level attributes such as description, amounts, stage, decision date, and currency originate here.
• AS_ACCESSES_ALL (VIEW) — the access-control entity that maps a resource (salesforce representative) to a lead or opportunity, including the OPEN_FLAG that indicates whether the access record is currently active.

The view aliases AS_LEADS_ALL as OPP and AS_ACCESSES_ALL as ACC, joining them on OPP.LEAD_ID = ACC.LEAD_ID with the additional restrictive predicate ACC.OPEN_FLAG = 'Y'. Consequently, only opportunities with at least one active access row appear. The SELECT DISTINCT clause ensures that multiple access rows for the same lead do not produce duplicate opportunity records.

Key Columns

The projection deliberately surfaces both opportunity facts and resource authorization facts:

• LEAD_ID, LEAD_NUMBER — the primary identifier and human-readable number of the opportunity.
• DESCRIPTION, SALES_STAGE_ID, STATUS_CODE, WIN_PROBABILITY — descriptive attributes reflecting opportunity name, sales stage, status, and probability of win.
• TOTAL_AMOUNT, CURRENCY_CODE, CUSTOMER_BUDGET — financial sizing information.
• DECISION_DATE, DECISION_TIMEFRAME_CODE — the expected decision date and its associated timeframe code; the view exposes the code as DECISION_TIMEFRAME_CODE while emitting a constant NULL for DECISION_TIMEFRAME.
• PARTY_ID (aliased from CUSTOMER_ID), ORG_ID — the customer party and operating unit context.
• RESOURCE_ID (aliased from ACC.SALESFORCE_ID), RESOURCE_TYPE ('RS_INDIVIDUAL'), OBJECT_CODE ('OPPORTUNITY'), OPEN_FLAG — the access and routing metadata.

Common Use Cases and Queries

A typical usage is to retrieve all visible opportunities for a team resource within a decision window, filtering on the DECISION_TIMEFRAME_CODE the user searched for:

SELECT LEAD_NUMBER, DESCRIPTION, TOTAL_AMOUNT,
       CURRENCY_CODE, DECISION_DATE, DECISION_TIMEFRAME_CODE
FROM   APPS.AST_MYTEAM_SALESOPP_UWQ_R_S_V
WHERE  DECISION_TIMEFRAME_CODE = :p_timeframe
AND    RESOURCE_ID = :p_resource_id
ORDER BY DECISION_DATE;

Other common patterns include aggregating pipeline value by stage, joining PARTY_ID to customer master tables for account enrichment, and using RESOURCE_ID to drive Universal Work Queue assignment. Because the view already enforces OPEN_FLAG = 'Y', consumers avoid writing redundant access-control logic.