Results for “bis_sales_groups_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIS_SALES_GROUPS_V is a BIS (Applications BIS) view that exposes sales group assignments for the currently logged-in Oracle EBS user. Its purpose is to return the set of sales groups for which the session user qualifies either as a sales team member (via AS_SALESFORCE) or as an enabled sales group manager (via AS_SALES_GROUPS.MANAGER_PERSON_ID). The view is therefore a security and personalization construct rather than a general-purpose transactional view: it derives its row set from the identity of the runtime user, obtained through FND_PROFILE.VALUE_WNPS('USER_ID').
Because the row filter is bound to the current session, the view is typically used by Oracle Sales/TeleSales and related BIS components to constrain list of values, dashboards, and reporting queries to the sales groups a user is entitled to see. The ETRM metadata notes that the object is “Not implemented in this database,” indicating that in the documented instance the view is defined in the application data model but not deployed, so queries against it in that environment would fail until the underlying product installs it. In Oracle EBS 12.1.1 and 12.2.2 the object is shipped with the AS (Sales Foundation) schema objects even though it is catalogued under BIS.
Underlying Base Objects
The view is defined over the following base tables and API:
AS_SALES_GROUPS— the sales group definition table, supplyingSALES_GROUP_ID,NAME,MANAGER_PERSON_ID,ENABLED_FLAG,START_DATE_ACTIVE, andEND_DATE_ACTIVE.AS_SALESFORCE— the sales force/team assignment table, joined toAS_SALES_GROUPSonSALES_GROUP_IDand carryingEMPLOYEE_PERSON_ID.FND_USER— used to translate the current user to an employee (EMPLOYEE_ID).FND_USER_RESP_GROUPS— supplies theRESPONSIBILITY_IDassociated with the user, enabling responsibility-scoped filtering downstream.FND_PROFILE.VALUE_WNPS('USER_ID')— the profile API that returns the current session user ID.
The metadata lists no additional referenced base objects, and the documented owner is blank. The view text is composed of two UNION branches: the first returns sales groups where the user is a member of the sales force and is not currently an enabled manager of that same person; the second returns sales groups the user manages, restricted to enabled groups whose active date range includes the current date. The effective join path is user → employee → sales force or manager → sales group, filtered by the session user ID from the profile value.
Key Columns
- ID — the
SALES_GROUP_ID, converted to character withTO_CHAR. This is the value typically bound to a list of values or lookup. - VALUE — the sales group
NAME, the display text returned alongside the ID. - RESPONSIBILITY_ID — the responsibility associated with the current user via
FND_USER_RESP_GROUPS, allowing callers to further scope results by responsibility.
Common Use Cases and Queries
The predominant use case is entitlement-driven list of values and reporting: a form or BI Publisher report queries the view to populate a sales group picker with only those groups the logged-in user may access. A representative query follows.
SELECT id, value, responsibility_id FROM apps.bis_sales_groups_v ORDER BY value;
To scope output to a single responsibility, add a predicate on RESPONSIBILITY_ID. To validate membership for a specific group, filter on ID. Because the view resolves the user from session context, it should be queried from within an EBS session, or with the USER_ID profile set through FND_PROFILE.PUT when executed by a concurrent program or integration process.
The search term “as_salesforce” maps directly to the AS_SALESFORCE base table referenced in the view, confirming that user queries for sales force membership are satisfied through this view’s first UNION branch.
-
View: BIS_SALES_GROUPS_V 12.1.1
Not implemented in this database·Explore BIS module →
-
View: BIS_SALES_GROUPS_V 12.2.2
Not implemented in this database·Explore BIS module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1