Results for “jtf_terr_cnr_group_values”

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

Overview

JTF_TERR_CNR_GROUP_VALUES is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the actual values assigned to territory qualifier groups. Within the Oracle Territory Manager (also referred to as ETRM, the Enterprise Territory Management engine), territory definitions are decomposed into qualifiers and grouping constructs. The CNR (Conjunctive Normal Rule) framework represents qualifiers as groups, where each group carries one or more comparison values. This table is the physical store for those values, enabling the territory engine to evaluate whether a given customer, prospect, or resource satisfies a territory's qualification criteria during territory assignment and qualification runs.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. It records descriptive attributes attached to a parent grouping entity, which functionally behaves as the key hub or link, while the value rows carry the changing descriptive detail. This classification should be treated as a modeling suggestion rather than an enforced constraint, since the table also exposes its own surrogate primary key and foreign-key relationships.

Key Information Stored

The table is owned by the JTF schema and, per the documented 12.2.2 physical schema, contains 15 columns. The most significant are summarized below.

• CNR_GROUP_VALUE_ID — surrogate primary key, defined by the constraint JTF_TERR_CNR_GROUP_VALUES_PK and also backed by the unique index JTF_TERR_CNR_GROUP_VALUES_U1. It uniquely identifies each value row.
• CNR_GROUP_ID — foreign key referencing JTF_TERR_CNR_GROUPS.CNR_GROUP_ID. It is the principal business-key candidate linking each value to its parent qualifier group.
• COMPARISON_OPERATOR — the operator applied when the qualifier is evaluated, such as equality, range, or set membership.
• LOW_VALUE_CHAR and HIGH_VALUE_CHAR — the character representations of the low and high bounds of the assigned value or value range.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date window during which the qualifier value is considered active.
• SECURITY_GROUP_ID — foreign key referencing FND_SECURITY_GROUPS, supporting multi-tenant and operating-unit security filtering.
• ORG_ID — the operating unit or organization context for the row.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording creation and last modification metadata.

Common Use Cases and Queries

Territory administrators and developers query this table to inspect, audit, or troubleshoot the values behind a territory qualifier. A typical diagnostic joins the value rows to their parent groups to reconstruct the effective qualification rule.

• Retrieve all active values for a given group: SELECT * FROM JTF.JTF_TERR_CNR_GROUP_VALUES WHERE CNR_GROUP_ID = :group_id AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Join values to the parent group and its territory definition in JTF_TERR_CNR_GROUPS to profile rule complexity per territory.
• Audit rows modified after a point in time using LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER.
• Filter by SECURITY_GROUP_ID or ORG_ID when generating operating-unit-scoped reports.
• Reconcile comparison operators and low/high value pairs to validate that range-based qualifiers are correctly bounded.

Related Objects

• JTF_TERR_CNR_GROUPS — the parent table referenced through CNR_GROUP_ID; the primary join partner for reconstructing qualifier definitions.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, providing row-level security context.
• JTF_TERR_CNR_GROUP_VALUES_PK / JTF_TERR_CNR_GROUP_VALUES_U1 — the primary key constraint and unique index enforcing row identity on CNR_GROUP_VALUE_ID.
• Territory qualifier and territory definition tables in the JTF schema — depend transitively on these values when the territory engine evaluates assignment rules.
• Oracle Territory Manager concurrent programs and the territory qualification APIs — consume this data at runtime to qualify customers and resources against defined territories.