Search Results jtf_terr_v




Overview
Explore in AI Chat

Overview

JTF_TERR_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the JTF product family, CRM Foundation, which supplies the shared territory management infrastructure used across Oracle CRM applications such as Oracle Sales, Oracle TeleSales, Oracle Service, and Oracle Marketing. The view exposes the full set of descriptive and control attributes associated with territory records, including territory identity, validity dates, hierarchical relationships, escalation settings, ranking, and territory type references.

Functionally, JTF_TERR_V presents a flattened, reporting-friendly projection of territory data. It is the object referenced by concurrent programs, CRM application inquiry screens, and custom integrations that need to resolve territory identifiers into human-readable names, validity windows, and assignment behavior flags without navigating the underlying transactional tables directly. Because the view is a pass-through definition, querying it returns the same rows as the base object with no additional filtering, joins, or aggregations applied by the database. This makes it suitable for both point lookups and set-based reporting.

The column PLANNED_FLAG is one of the exposed control attributes and is frequently the target of ad hoc queries, since it distinguishes territories created for planning or simulation purposes from those actively used in assignment processing.

Underlying Base Objects

According to documented ETRM metadata for 12.2.2, JTF_TERR_V is defined over a single referenced base object: the synonym JTF_TERR, which resolves to the APPS.JTF_TERR table. The view text is a straightforward SELECT of all forty-three columns from that base object, listing TERR_ID and the standard WHO columns first, followed by the territory attributes, the fifteen ATTRIBUTE flexible columns, and finally NUM_WINNERS.

No joins to JTF_TERR_TL or other territory-related tables appear in the documented definition, so the view does not by itself resolve translated territory names. Consumers requiring language-specific name resolution must join to the translation table on TERR_ID and LANGUAGE. Because the view is defined over a synonym rather than an explicit schema-qualified table, it inherits the standard APPS synonym layer used throughout EBS.

Key Columns

  • TERR_ID — Primary key of the territory record; the join key to all dependent territory tables such as JTF_TERR_TL, JTF_TERR_RESOURCES, and JTF_TERR_RANK_PREV.
  • NAME — User-visible territory name.
  • ENABLED_FLAG — Indicates whether the territory is currently enabled for use.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Validity window governing when the territory is in effect.
  • PLANNED_FLAG — Distinguishes planning or placeholder territories from operational territories. This is the column most commonly used to filter territory lists during reporting and simulation exercises.
  • PARENT_TERRITORY_ID — Self-referencing pointer establishing territory hierarchy.
  • TERRITORY_TYPE_ID — Foreign key to the territory type definition, which determines the criteria model in use.
  • TEMPLATE_TERRITORY_ID / TEMPLATE_FLAG — Identify the template used to create the territory and whether the record is itself a template.
  • ESCALATION_TERRITORY_ID / ESCALATION_TERRITORY_FLAG — Define escalation behavior when no resource in the territory can satisfy a transaction.
  • OVERLAP_ALLOWED_FLAG — Controls whether the territory may overlap with others for the same transaction.
  • RANK — Numeric precedence used during territory qualification.
  • AUTO_ASSIGN_RESOURCES_FLAG — Indicates whether resources are assigned automatically.
  • NUM_WINNERS — Limits the number of resources that may win a given transaction.
  • ORG_ID — Operating unit context for multi-org installations.
  • ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments available for customer extensions.

Common Use Cases and Queries

Typical usage includes territory list reports, data migration validation, integration extracts feeding external CRM or analytics platforms, and diagnostic queries during territory setup troubleshooting. A frequent requirement is to identify all active, non-planned territories within a given operating unit:

  • SELECT terr_id, name, enabled_flag, start_date_active, end_date_active, planned_flag FROM jtf_terr_v WHERE enabled_flag = 'Y' AND planned_flag = 'N' AND org_id = :p_org_id;
  • SELECT terr_id, name, parent_territory_id, rank, num_winners FROM jtf_terr_v WHERE territory_type_id = :p_type_id ORDER BY rank;
  • SELECT p.name parent_name, c.name child_name FROM jtf_terr_v c, jtf_terr_v p WHERE c.parent_territory_id = p.terr_id;

Where translated names are required, join jtf_terr_v to jtf_terr_tl on terr_id and filter by language. Because the view performs no filtering, always apply the appropriate ENABLED_FLAG, date, and ORG_ID predicates to avoid returning irrelevant planning records.