Results for “jtf_terr”

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

Overview

JTF_TERR is a CRM Foundation (JTF) reporting view that presents territory definitions for multi-organization enabled Oracle E-Business Suite environments. In the 12.1.1 and 12.2.2 releases, territories are the core constructs used by Oracle Territory Manager (part of the CRM Foundation and shared by modules such as TeleSales, Sales Online, Service, and Trade Management) to partition customers, prospects, and resources into logical groups for assignment, qualification, and lead routing.

The view is not a physical table; it is a thin projection over the underlying JTF_TERR_ALL table, which holds the organization-specific (multi-org) territory records. Its purpose is to expose a denormalized, application-consistent read interface so that forms, concurrent programs, and reporting tools can query territory data without directly referencing the base table. The view also applies several translations and formatting rules—most notably the substitution of a catch-all territory name and description using FND_MESSAGE.GET_STRING when TERR_ID equals 1.

Per the documented ETRM metadata, this view is marked "Not implemented in this database," indicating that in certain environments the object may not be deployed or may have been superseded by other territory reporting objects. Administrators should verify its presence with a query against ALL_VIEWS before relying on it in custom code.

Underlying Base Objects

The view text is defined entirely over JTF_TERR_ALL, the multi-organization base table storing territory header information. No other base objects are documented in the ETRM metadata for this view. Because JTF_TERR_ALL is org-striped, the view inherits its ORG_ID column and multi-tenant behavior; a query issued in a specific operating unit context returns only territories belonging to that organization.

The projection is essentially a 1:1 mapping of columns, with two DECODE expressions that intercept the reserved catch-all territory (TERR_ID = 1) and replace its stored NAME and DESCRIPTION with localized strings returned by FND_MESSAGE.GET_STRING. This preserves the technical identity of the catch-all record while presenting a user-friendly label to downstream consumers.

• Base table: JTF_TERR_ALL (multi-org territory master)
• Referenced base objects documented: none beyond JTF_TERR_ALL
• Relationship: one row in JTF_TERR_ALL produces one row in JTF_TERR

Key Columns

The view exposes the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus concurrent request audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE). Functional columns include:

• TERR_ID – Primary identifier of the territory; value 1 designates the system catch-all.
• NAME / DESCRIPTION – Territory label and narrative; overridden for the catch-all record.
• ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE – Control the active window of the territory.
• PARENT_TERRITORY_ID – Establishes the territory hierarchy.
• TERRITORY_TYPE_ID – References the territory type (e.g., geography, product, resource).
• TEMPLATE_TERRITORY_ID, TEMPLATE_FLAG – Support territory templates and cloning.
• ESCALATION_TERRITORY_ID, ESCALATION_TERRITORY_FLAG – Define escalation routing.
• OVERLAP_ALLOWED_FLAG, RANK, NUM_WINNERS, NUM_QUAL – Govern qualification and winner selection logic.
• AUTO_ASSIGN_RESOURCES_FLAG – Indicates automatic resource assignment behavior.
• ORG_ID – Multi-organization discriminator.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include territory setup validation, listing active territories for an operating unit, and resolving the catch-all name during reporting. The following query returns enabled, currently active territories for the session organization:

• SELECT terr_id, name, description, org_id FROM jtf_terr WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• SELECT terr_id, name FROM jtf_terr WHERE parent_territory_id IS NULL ORDER BY name;
• SELECT terr_id, name, rank, num_winners FROM jtf_terr WHERE overlap_allowed_flag = 'Y';

Because the view does not filter by organization, custom SQL should always include a suitable ORG_ID predicate or rely on the Multi-Org views (such as JTF_TERR_VL or MO equivalents) where appropriate. Applications upgrading between 12.1.1 and 12.2.2 should confirm view availability, as the documented status "Not implemented" may reflect a specific database instance rather than a release-wide characteristic.