Search Results asbv_sales_groups

Overview

The view ASBV_SALES_GROUPS belongs to the AS – Sales Foundation product family within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is a reporting-oriented, read-only view that presents sales group definitions in a denormalized form suitable for extracts, concurrent programs, and integration interfaces. The trailing "BV" convention follows Oracle's standard naming pattern for business views layered over transactional foundation tables, indicating that the object is intended for consumption by forms, reports, and external systems rather than for direct DML.

The metadata notes that the view is not implemented in this database, meaning the object may exist only as a documented template or may be absent in a given environment. The view definition is nonetheless exposed so that integrators can understand the expected column layout. Because the query is declared WITH READ ONLY, any attempt to perform INSERT, UPDATE, or DELETE against the view will fail; all maintenance must be performed against the underlying table AS_SALES_GROUPS.

Underlying Base Objects

The ETRM documentation lists no separately documented base objects, but the embedded view text makes the dependency explicit: the view selects exclusively from AS_SALES_GROUPS, aliased as GRP. This table stores the master definition of sales groups used by Oracle Sales and related modules, including territory, compensation, and sales force hierarchies. The view does not join to any lookup, party, or HR table directly; instead it references lookups via a display parameter. The token _LA:GRP.ENABLED_FLAG:AS_LOOKUPS:FLAG:MEANING instructs the application framework to resolve the ENABLED_FLAG value against the AS_LOOKUPS lookup type (lookup type FLAG, meaning column MEANING), which yields a human-readable enabled/disabled label rather than the raw code. Similarly, the token _DF:AS:AS_SALES_GROUPS:GRP is a descriptive flexfield reference, indicating that the view exposes the sales group's descriptive flexfield context for that table.

Key Columns

• SALES_GROUP_NAME — the NAME of the sales group, providing the primary business identifier.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range governing when the group is active.
• "_LA:ENABLED" — the resolved enabled/disabled meaning derived from ENABLED_FLAG through AS_LOOKUPS.
• DESCRIPTION — free-text description of the group.
• ACCOUNTING_CODE — the accounting code associated with the sales group, used to align sales activity with general ledger accounting segments. This column is the target of the "accounting_code" search term.
• "_DF" — the descriptive flexfield placeholder for the sales group record.
• SALES_GROUP_ID — the unique primary key of the sales group.
• PARENT_SALES_GROUP_ID — self-referencing key enabling hierarchical sales group structures.
• MANAGER_PERSON_ID / MANAGER_SALESFORCE_ID — identifiers for the group's manager and associated sales force.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

This view is typically queried for reporting on sales organization structure, validating accounting codes, or feeding downstream systems. A representative query lists active groups with their accounting codes:

• SELECT sales_group_name, accounting_code, "_LA:ENABLED" FROM asbv_sales_groups WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Hierarchy traversal: query sales_group_id and parent_sales_group_id to reconstruct the sales group tree for org-chart reporting.
• Integration extracts: select the flexfield and audit columns to synchronize sales group data into external CRM or data-warehouse platforms.

Because the object is read-only and may not be implemented in all environments, developers should confirm its existence in the target schema before relying on it, falling back to AS_SALES_GROUPS directly where necessary.