Results for “use_to_name_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_TERR_QUAL_ALL is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the qualifiers used to define a territory. Territories in Oracle Territory Manager are not stored as flat attribute lists; each territory is expressed as a set of qualification rules that determine which customers, prospects, or transactions fall inside the boundary. JTF_TERR_QUAL_ALL is the object that records each of those qualifier definitions and binds it to a parent territory, making it the structural backbone of territory rule definition and, by extension, of territory-based assignment and routing.
The object is owned by the JTF schema and is documented as VALID in ETRM 12.2.2 with 15 physical columns. Its primary key is TERR_QUAL_ID, enforced by the JTF_TERR_QUAL_ALL_PK constraint, and a unique index JTF_TERR_QUAL_U1 on (TERR_QUAL_ID, ORG_ID) provides the multi-org aware business-key candidate. Under the heuristic Data Vault classification mined from the foreign-key structure, the table leans toward a satellite: it carries descriptive, rule-level attributes about a parent entity rather than acting as a standalone hub or a pure many-to-many link. This classification should be treated as a modeling suggestion rather than an enforced design constraint.
Key Information Stored
The column set divides into a surrogate identifier, business keys, qualifier configuration attributes, and standard EBS audit/security columns.
- TERR_QUAL_ID — surrogate primary key, generated for each qualifier row and referenced by downstream territory value and reporting structures.
- TERR_ID — foreign key to JTF_TERR_ALL; identifies the territory to which the qualifier belongs. This is the primary drill-down path from a territory definition to its rules.
- QUAL_USG_ID — foreign key to JTF_QUAL_USGS_ALL; identifies the qualifier usage, that is, the specific attribute or usage being qualified (for example, a geography, industry, or account attribute usage).
- QUALIFIER_MODE — controls how the qualifier operates within the territory expression, typically expressing include or exclude semantics.
- OVERLAP_ALLOWED_FLAG — indicates whether qualifiers in this territory may overlap, affecting eligibility and deduplication behavior during assignment.
- USE_TO_NAME_FLAG — governs whether the qualifier participates in the generated territory name.
- GENERATE_FLAG — controls whether the qualifier is used when the territory is generated or compiled.
- ORG_ID — the operating unit context, part of the JTF_TERR_QUAL_U1 unique index and the basis for multi-org filtering.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
- OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-column audit trail.
Common Use Cases and Queries
Typical usage centers on auditing and reconstructing territory definitions: identifying which qualifiers are active for a territory, confirming whether overlap or generation flags are set correctly, and reconciling territory membership against the values stored in JTF_TERR_VALUES_ALL. A representative query joins the qualifier rows back to their parent territory:
SELECT q.TERR_QUAL_ID, q.TERR_ID, q.QUAL_USG_ID, q.QUALIFIER_MODE, q.OVERLAP_ALLOWED_FLAG, q.GENERATE_FLAG FROM JTF.JTF_TERR_QUAL_ALL q WHERE q.TERR_ID = :terr_id AND q.ORG_ID = :org_id;- Join to JTF_TERR_ALL for the territory name and status:
... FROM JTF_TERR_QUAL_ALL q, JTF_TERR_ALL t WHERE q.TERR_ID = t.TERR_ID AND q.ORG_ID = t.ORG_ID; - Join to JTF_QUAL_USGS_ALL to resolve the human-readable qualifier usage:
... FROM JTF_TERR_QUAL_ALL q, JTF_QUAL_USGS_ALL u WHERE q.QUAL_USG_ID = u.QUAL_USG_ID; - Count qualifiers per territory to detect overly complex or empty rules:
SELECT TERR_ID, COUNT(*) FROM JTF_TERR_QUAL_ALL GROUP BY TERR_ID;
Reporting uses include territory rule inventories, migration validation before and after upgrades to 12.2.2, and impact analysis when a qualifier usage is retired.
Related Objects
The foreign-key relationships define the object's immediate neighborhood:
- JTF_TERR_ALL — parent territory definition; joined on JTF_TERR_QUAL_ALL.TERR_ID.
- JTF_QUAL_USGS_ALL — qualifier usage master; joined on QUAL_USG_ID.
- JTF_TERR_VALUES_ALL — child table holding the actual qualifier values; references JTF_TERR_QUAL_ALL.TERR_QUAL_ID and is the principal dependent object.
- FND_SECURITY_GROUPS — security group master; joined on SECURITY_GROUP_ID.
- JTF_TAE_RPT_STAGING_OUT — staging output table that also references TERR_QUAL_ID, used in territory assignment reporting flows.
Together these objects form the territory definition stack: JTF_TERR_ALL supplies the container, JTF_TERR_QUAL_ALL supplies the rule header, JTF_TERR_VALUES_ALL supplies the rule values, and the qualifier usage and security group tables supply the supporting master data.
-
Stores the qualifiers that used to define a territory.
-
Stores the qualifiers that used to define a territory.
-
View: JTF_TERR_QUALIFIERS_V 12.1.1
This shows the qualifiers used to define a territory.
APPS.JTF_TERR_QUALIFIERS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_QUAL_TYPES·Explore JTF module →
-
View: JTF_TERR_QUALIFIERS_V 12.2.2
This shows the qualifiers used to define a territory.
APPS.JTF_TERR_QUALIFIERS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_QUAL_TYPES·Explore JTF module →
-
View: JTF_TERR_QUAL 12.1.1
Same as JTF_TERR_QUAL_ALL table.
Not implemented in this database·Explore JTF module →
-
View: JTF_TERR_QUAL 12.2.2
Same as JTF_TERR_QUAL_ALL table.
Not implemented in this database·Explore JTF module →
-
VIEW: JTF.JTF_TERR_QUAL_ALL# 12.2.2
-
VIEW: JTF.JTF_TERR_QUAL_ALL# 12.2.2
-
TABLE: JTF.JTF_TERR_QUAL_ALL 12.2.2
-
TABLE: JTF.JTF_TERR_QUAL_ALL 12.1.1