Results for “exclusive_flag”

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

Overview

BIL_DIMV_SALES_GROUPS is a read-only dimension view owned by the APPS schema within the BIL - Sales Intelligence product family of Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It presents a consolidated, reporting-friendly list of sales groups drawn from Oracle CRM resource group definitions, together with a placeholder row for a special "no value" lookup. The view exists to feed Sales Intelligence analytics, dimensional modeling, and downstream integrations that need a stable reference to sales groups for aggregating revenue, pipeline, and territory data. Because it is a dimension view, it flattens and standardizes attributes (IDs, group numbers, names, descriptions, and enablement state) so that BI Publisher reports, OBIEE extracts, and custom SQL can join to a single consistent source rather than querying the TCA/JTF resource tables directly.

Underlying Base Objects

The view is defined as a three-branch UNION/UNION ALL over the following documented base objects:

• JTF_RS_GROUPS_B — the base (language-independent) resource group table, supplying GROUP_ID, GROUP_NUMBER, START_DATE_ACTIVE, END_DATE_ACTIVE, and EXCLUSIVE_FLAG.
• JTF_RS_GROUPS_TL — the translation table providing GROUP_NAME and GROUP_DESC, filtered by LANGUAGE = USERENV('LANG').
• JTF_RS_GROUP_USAGES — the usage mapping table, filtered to USAGE = 'SALES' to restrict rows to sales groups only.
• FND_LOOKUPS — the standard lookup table, queried for LOOKUP_TYPE = 'BIL_VALUE_TYPE' with LOOKUP_CODE = '-999', providing a synthetic "unknown/none" sales group row.

The first UNION ALL branch returns sales groups that are currently active (with ENABLED_FLAG set to 'Y' when SYSDATE falls between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, SYSDATE)); the second branch returns sales groups outside their active window with ENABLED_FLAG 'N'. The final UNION branch appends the -999 placeholder row from FND_LOOKUPS.

Key Columns

• SALES_GROUP_ID — the group identifier (JTF_RS_GROUPS_B.GROUP_ID, or the numeric LOOKUP_CODE for the placeholder row).
• GROUP_NUMBER — the user-visible group number from the base table (or LOOKUP_CODE for the placeholder).
• NAME / DESCRIPTION — the translated group name and description.
• ENABLED_FLAG — 'Y' for currently active groups, 'N' for inactive or the placeholder row.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the group.
• EXCLUSIVE_FLAG — indicates whether the group is an exclusive (private) group. This is the attribute most relevant to the user's search term "exclusive_flag"; note that the placeholder row from FND_LOOKUPS is hard-coded as 'N'.
• ID / VALUE — a TO_CHAR of GROUP_ID and the group name, used as key-value pairs for List of Values and picklist rendering.

Common Use Cases and Queries

The view is typically used to enumerate sales groups for selection, filtering, or dimension joins, and to distinguish exclusive from shared groups. A representative query listing active, exclusive sales groups is:

• SELECT sales_group_id, group_number, name, exclusive_flag FROM apps.bil_dimv_sales_groups WHERE enabled_flag = 'Y' AND exclusive_flag = 'Y' ORDER BY name;
• SELECT sales_group_id, name FROM apps.bil_dimv_sales_groups WHERE exclusive_flag = 'N'; — returns shared and placeholder groups.
• SELECT id, value FROM apps.bil_dimv_sales_groups ORDER BY name; — populates an LOV or picklist via the ID/VALUE key-value pair columns.

Because the view is defined WITH READ ONLY and relies on organization-independent JTF resource tables, it is safe for ad-hoc reporting and integration extracts without risk of data modification. Filters on EXCLUSIVE_FLAG and ENABLED_FLAG are the most common predicates.