Results for “salesforce_id”

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

Overview

The view AS_SALESGROUP_SUB_V is an Oracle E-Business Suite (EBS) Sales Foundation (AS) object owned by the APPS schema. It is documented in ETRM for both 12.1.1 and 12.2.2 as a VALID database view. Its stated purpose is to expose all first-level sub-groups belonging to the JTF Resource Manager hierarchy. Rather than returning the entire resource group tree, the view filters the denormalized group table so that only those group records flagged as immediate children (that is, first-level, non-rolled-up descendants) of a sales group are returned.

In EBS reporting and integration terms, the view provides a light, presentation-ready projection of the sales organization's direct sub-groups. It joins the denormalized resource group table to the group usages and the translatable group names, so consumers receive a sales-qualified group list enriched with language-specific names. Because AS_SALESGROUP_SUB_V is a view and not a table, it carries no storage of its own and simply materializes at query time from its base objects. This makes it well suited to concurrent-program extracts, OBIEE/BI Publisher datasets, and custom API or interface logic requiring the immediate children of a given sales group.

Underlying Base Objects

The ETRM metadata identifies three referenced base objects, all accessed through synonyms in the APPS schema:

• JTF_RS_GROUPS_DENORM (referenced as a SYNONYM) — the denormalized resource group table, aliased as JGD. It supplies the group identifier, the parent group identifier, the immediate-parent flag, and the active date range.
• JTF_RS_GROUP_USAGES (SYNONYM) — the group usage table, aliased as JGU. It restricts results to groups whose usage is SALES.
• JTF_RS_GROUPS_TL (SYNONYM) — the translatable group names table, aliased as JGT. It supplies the language-specific GROUP_NAME.

The joins are: JGU.GROUP_ID = JGD.GROUP_ID with JGU.USAGE = 'SALES'; JGT.GROUP_ID = JGD.GROUP_ID with JGT.LANGUAGE = USERENV('LANG'). The rows are further constrained by JGD.IMMEDIATE_PARENT_FLAG = 'Y', which is the mechanism that limits the view to first-level sub-groups.

Key Columns

• SALESFORCE_ID — selected as a literal NULL, retained for interface compatibility with salesforce-oriented consumers. It does not carry a source value.
• SALES_GROUP_ID — the group identifier, sourced from JGD.GROUP_ID. Identifies the sub-group itself.
• PARENT_GROUP_ID — the parent group identifier, sourced from JGD.PARENT_GROUP_ID. This is the key column for the searched term "parent_group_id" and defines the immediate parent of each returned sub-group.
• START_DATE_ACTIVE — start of the group's active period, from JGD.START_DATE_ACTIVE.
• END_DATE_ACTIVE — end of the group's active period, from JGD.END_DATE_ACTIVE.
• GROUP_NAME — the translatable, language-specific name of the group, from JGT.GROUP_NAME.

Common Use Cases and Queries

Typical scenarios include enumerating the direct sub-groups under a specific sales group, driving territory or assignment lookups, and resolving group names in the session language. Because the view exposes PARENT_GROUP_ID, it is frequently linked back to a parent sales group to build two-level hierarchies.

• Retrieve direct sub-groups for a given parent:
  SELECT sales_group_id, parent_group_id, group_name FROM apps.as_salesgroup_sub_v WHERE parent_group_id = :p_parent_group_id;
• List all first-level sales sub-groups currently active:
  SELECT sales_group_id, group_name FROM apps.as_salesgroup_sub_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);
• Join to a parent resource group to display the parent and child names in the same row, using PARENT_GROUP_ID as the join key.

Consumers should note that the view returns only groups flagged with IMMEDIATE_PARENT_FLAG = 'Y' and usage 'SALES', so it should not be expected to return deeper hierarchy levels or non-sales resource groups.