Results for “as_territory_groups”

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

Overview

AS_TERRITORY_GROUPS is a Sales Foundation (AS) view in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata classifies the object explicitly as Obsolete. Its stated purpose is to expose "Territory groups (multi-org)," the organizational construct that allowed multiple territory definitions to be grouped and evaluated together under Oracle Territory Manager. The view is a multi-org–secured, org-filtered projection over the base table AS_TERRITORY_GROUPS_ALL, meaning the underlying data model separates records in a single "ALL" table and applies an operating-unit filter at the view level.

Two facts govern any practical engagement with this object. First, the ETRM record states "Not implemented in this database." The view may exist as a stub, may not be created at all, or may be present in a database where the base table is empty. Second, the owner is not documented and no referenced base objects are recorded. In a live 12.1.1 or 12.2.2 instance, the presence and population of AS_TERRITORY_GROUPS therefore cannot be assumed. Its historical role was reporting and integration: allowing concurrent programs, forms, and downstream extracts to read territory-group definitions restricted to the session's current operating unit without writing the multi-org predicate themselves.

Underlying Base Objects

The view text shows a single source: AS_TERRITORY_GROUPS_ALL. The ETRM metadata, however, lists no documented referenced base objects and does not identify an owner. The view is obsolete, so the "ALL" table and the view were retired together as Oracle Territory Manager evolved. No other table, synonym, or subquery appears in the definition; it is a straightforward column projection plus a WHERE clause.

That WHERE clause is the canonical multi-org filter used throughout pre–MOAC (Multi-Org Access Control) EBS code:

WHERE NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) = NVL(TO_NUMBER(DECODE(...)),-99)

It reads the first ten bytes of CLIENT_INFO, conventionally the current organization ID, and matches it against ORG_ID, substituting -99 when either side is null. Because the view is obsolete, it is best treated as a read-only artifact rather than a foundation for new development; current territory functionality is delivered through successor objects and the Territory Manager APIs.

Key Columns

• TERRITORY_GROUP_ID — Primary key identifying the territory group.
• NAME — User-visible group name.
• DESCRIPTION — Free-text description of the group.
• ACCESS_TYPE — Classification controlling how the group is accessed or evaluated.
• ENABLED_FLAG — Status indicator; determines whether the group is active.
• NUM_WINNERS — Number of winning territories permitted for the group, a territory-manager ranking attribute.
• ORG_ID — Operating unit owning the row; drives the multi-org filter.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard fifteen flex columns plus category, available for customer-specific extensions.

The column list is essentially the full "ALL" table surface, with no joins, derivations, or lookup translations applied.

Common Use Cases and Queries

Because the view is obsolete and not guaranteed to be implemented, its realistic use is investigative: confirming whether legacy territory-group data remains after upgrade, reconciling historical extracts, or auditing customizations written against the pre-12.x territory model. Any query should first test existence and set the operating unit context correctly, since the multi-org predicate depends on CLIENT_INFO.

• List enabled groups for the current operating unit: SELECT TERRITORY_GROUP_ID, NAME, ACCESS_TYPE, NUM_WINNERS FROM AS_TERRITORY_GROUPS WHERE ENABLED_FLAG = 'Y' ORDER BY NAME;
• Audit recently changed groups: SELECT TERRITORY_GROUP_ID, NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM AS_TERRITORY_GROUPS ORDER BY LAST_UPDATE_DATE DESC;
• Inspect flex-field usage: SELECT TERRITORY_GROUP_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM AS_TERRITORY_GROUPS WHERE ATTRIBUTE_CATEGORY IS NOT NULL;

The ETRM note that the view is "Not implemented in this database" means results may be empty or the object absent. For new work, use the supported successor territory objects and the Territory Manager APIs instead of AS_TERRITORY_GROUPS.