Results for “num_qualifiers”

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

Overview

AS_TERRITORY_TYPES_ALL is a Sales Foundation (AS) table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines territory types — the classification records that group and categorize territories used by territory assignment, sales force management, and qualifier-driven routing. ETRM documents the object as obsolete to JTF Territory Core, meaning that in current releases the functional territory engine has largely migrated to the JTF (CRM Foundation) territory tables. The AS table is retained primarily for backward compatibility, historical data, and upgrade paths rather than for new functional configuration.

Under the heuristic Data Vault classification derived from its foreign key topology, AS_TERRITORY_TYPES_ALL is satellite-leaning. It carries descriptive and status attributes for a territory type and points outward to a parent territory group through TERRITORY_GROUP_ID, rather than acting as a pure intersection (link) or as an independent hub of business keys. Treat this classification as a modeling suggestion for analytical or warehouse designs: the territory type identifier behaves as a durable key, while attributes such as ENABLED_FLAG, ACCESS_TYPE, and RANK describe state that can change over time.

Key Information Stored

The table exposes 32 documented columns. The most operationally significant are:

• TERRITORY_TYPE_ID — surrogate primary key and the column backing AS_TERRITORY_TYPES_ALL_PK. It is also the documented unique index AS_TERRITORY_TYPES_U1 candidate, so it serves simultaneously as the physical identifier and a business-key candidate.
• NAME — the user-visible territory type name; combined with ORG_ID it forms unique index AS_TERRITORY_TYPES_U2, making (NAME, ORG_ID) the strongest documented business-key candidate.
• ORG_ID — the operating unit or organization context, required for multi-org partitioning of the same type name.
• TERRITORY_GROUP_ID — foreign key to AS_TERRITORY_GROUPS_ALL, placing the type within a territory group hierarchy.
• ENABLED_FLAG and ACCESS_TYPE — status and access semantics controlling whether the type is active and how it may be used.
• ROLLUP_FLAG, RANK, and NUM_QUALIFIERS — indicate rollup behavior, ordering/priority of the type, and the count of qualifiers attached to it.
• DESCRIPTION — free-text explanation of the territory type.
• INTERNAL_UPGRADE_TERRTYPE_ID — an internal column supporting upgrade mapping between legacy AS territory types and the successor JTF model.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — plus the ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns.

Common Use Cases and Queries

Typical usage centers on validating territory configuration, reconciling legacy AS territory data during a JTF migration, and feeding sales-territory reporting. A basic lookup by primary key:

• SELECT * FROM as_territory_types_all WHERE territory_type_id = :p_id;

Enforcing the multi-org business key:

• SELECT territory_type_id, name, enabled_flag FROM as_territory_types_all WHERE name = :p_name AND org_id = :p_org_id;

Joining to the parent territory group to list types with their group and qualifier count:

• SELECT tt.name type_name, tt.num_qualifiers, tg.name group_name FROM as_territory_types_all tt, as_territory_groups_all tg WHERE tt.territory_group_id = tg.group_id AND tt.enabled_flag = 'Y';

Reporting scenarios include auditing enabled versus disabled types, identifying types with zero qualifiers, and cross-referencing INTERNAL_UPGRADE_TERRTYPE_ID against JTF territory core records during an upgrade validation. Because the table is documented as obsolete, new development should query JTF territory tables; AS reads are appropriate for legacy reconciliation only.

Related Objects

• AS_TERRITORIES_ALL — references this table via TERRITORY_TYPE_ID; each territory is classified by a territory type.
• AS_TERR_TYPE_QUALIFIERS — references this table via TERRITORY_TYPE_ID; holds the qualifiers that restrict a territory type.
• AS_TERRITORY_GROUPS_ALL — referenced by this table through TERRITORY_GROUP_ID; provides the parent grouping of territory types.

The primary keys AS_TERRITORY_TYPES_ALL_PK, AS_TERRITORY_TYPES_PK, and the unique key AS_TERRITORY_TYPES_UK named in the documentation are all defined on TERRITORY_TYPE_ID or NAME, reinforcing the two documented business-key candidates. Downstream functional consumers should be validated against JTF territory core, since the AS objects are retained only for compatibility.