Results for “open_flag”

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

Overview

The view APPS.AST_MYTEAM_SALESOPP_UWQ_REF_V is a TeleSales (AST) module database object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the APPS schema and carries a VALID status in the ETRM registry, indicating that the object is compiled and active in a standard installation. The name itself encodes its purpose: "MYTEAM" denotes a team-based sales hierarchy scope, "SALESOPP" references sales opportunities, and the "UWQ_REF" suffix identifies it as a reference view supporting a Universal Work Queue (UWQ) query used by the TeleSales work queue infrastructure.

Functionally, the view exposes the association between a lead (or opportunity record) and the sales team resources that have been granted access to it. It filters the access records to only those that are currently open. In Oracle TeleSales, the Universal Work Queue surfaces work items to agents based on assignments and access rights, and this view supplies the qualified lead-to-resource mapping that drives the "My Team" style work queue selection logic. Because it returns DISTINCT rows, the view de-duplicates the underlying access records, presenting one row per unique lead/resource/open-flag combination suitable for direct consumption by UWQ queries, concurrent programs, or custom reporting and integration layers.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: AS_ACCESSES_ALL, itself described as a VIEW. The definition is a straightforward projection with a filter, joining no other tables:

SELECT DISTINCT ACC.LEAD_ID, ACC.SALESFORCE_ID RESOURCE_ID, ACC.OPEN_FLAG
FROM AS_ACCESSES_ALL ACC
WHERE ACC.LEAD_ID IS NOT NULL AND ACC.OPEN_FLAG = 'Y'

AS_ACCESSES_ALL is the access-control foundation in the Oracle Sales/TeleSales data model, recording which resources (salesforce members) have access to which leads, opportunities, and related entities. Because the base object is itself a view over the underlying accesses schema, AST_MYTEAM_SALESOPP_UWQ_REF_V is a layered presentation object rather than a direct table projection. The dependency chain is therefore APPS view → AS_ACCESSES_ALL view → base accesses tables owned by the AS schema. Any change to the access records for a lead is immediately reflected in this view.

Key Columns

• LEAD_ID — The identifier of the lead (or opportunity) record to which access has been granted. The view suppresses rows where this is NULL, ensuring every returned row is tied to a valid lead.
• RESOURCE_ID — Exposed as an alias of ACC.SALESFORCE_ID, this is the salesforce resource granted access to the lead. It identifies the team member or resource to whom the work queue item is routed.
• OPEN_FLAG — The access status indicator. Only records with a value of 'Y' survive the filter, meaning the association is currently open and the resource retains active access to the lead.

Common Use Cases and Queries

The principal use case is Universal Work Queue selection in Oracle TeleSales, where the view provides the authoritative list of open lead/resource access pairs for team-scoped work queues. It also supports custom reporting that requires a clean, de-duplicated mapping of leads to their currently authorized resources.

A typical query lists all leads accessible to a given resource:

SELECT LEAD_ID, RESOURCE_ID
FROM   APPS.AST_MYTEAM_SALESOPP_UWQ_REF_V
WHERE  RESOURCE_ID = :p_resource_id;

To count open leads per resource for workload balancing:

SELECT RESOURCE_ID, COUNT(DISTINCT LEAD_ID) lead_count
FROM   APPS.AST_MYTEAM_SALESOPP_UWQ_REF_V
GROUP  BY RESOURCE_ID;

Because the view returns only records with OPEN_FLAG = 'Y', callers never need to reapply that predicate; the view is self-filtering and read-only, making it safe for integration and reporting use without risk of mutating the underlying access records.