Results for “as_territories_v”

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

Overview

AS_TERRITORIES_V is a Sales Foundation (AS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, reporting-friendly projection of territory definitions held in the JTF_TERR table, joined to territory-to-qualifier-type usage information. Its principal purpose is to expose territories together with the descriptive name of their associated qualifier type (for example, a geography, product, or customer qualifier), so that reporting, concurrent programs, and integration interfaces can resolve a territory without traversing the underlying qualifier-usage model directly.

The view is documented as VALID and is catalogued under the ETRM repository. Because it is a view rather than a table, it stores no data of its own; all values are derived at query time from the referenced base objects.

Underlying Base Objects

The documented base objects referenced by AS_TERRITORIES_V are JTF_TERR (synonym), JTF_QUAL_TYPES (view), JTF_QUAL_TYPE_USGS (view), JTF_TERR_QTYPE_USGS (synonym), and the FND_GLOBAL package. The core join links JTF_TERR to JTF_TERR_QTYPE_USGS on TERR_ID, then to JTF_QUAL_TYPE_USGS on QUAL_TYPE_USG_ID, with JTF_QUAL_TYPES supplying the qualifier-type description via QUAL_TYPE_ID. The relationship to FND_GLOBAL is standard for a territory view, since territory security and the current user context are resolved through that package.

Critically, the joins to JTF_TERR_QTYPE_USGS and JTF_QUAL_TYPE_USGS are outer joins (indicated by the (+) operator), so a territory is still returned when no qualifier-type usage row exists. The predicate QUALTYPEUSG.SOURCE_ID = -1001 restricts the usage rows to a specific seeded source, meaning only usage records tied to that source contribute a qualified-type description. Territories without a matching usage therefore appear with a null qualifier description.

Key Columns

The view exposes the full audit envelope from JTF_TERR: ROW_ID, TERR_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. Territory detail columns include NAME, DESCRIPTION, ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE, which together define the territory's identity and its active date range. Fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) are passed through unchanged for extensibility. The final derived column carries the qualifier-type DESCRIPTION from JTF_QUAL_TYPES, providing the human-readable classification of the territory's associated qualifier type.

Common Use Cases and Queries

Typical uses include listing enabled, currently effective territories for a given sales organization, driving territory-based security checks, and feeding territory master data into downstream reporting or CRM synchronization. Because the view already resolves the qualifier-type description, it avoids repeated joins in ad hoc reports. A representative query is:

• SELECT terr_id, name, description, enabled_flag, start_date_active, end_date_active, qual_type_description FROM as_territories_v WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• SELECT name, qual_type_description FROM as_territories_v WHERE terr_id = :p_terr_id;

When filtering or joining on qualifier types, note that the description column may be null for territories whose usage rows fall outside SOURCE_ID = -1001; consumers requiring a guaranteed qualifier classification should query JTF_TERR_QTYPE_USGS directly. Overall, AS_TERRITORIES_V remains a lightweight, read-only access point for territory metadata across the AS module.