Results for “value4_id”

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

Overview

JTF_TERR_VALUES_ALL is a table in the JTF schema (CRM Foundation) that stores the values assigned to territory qualifiers in Oracle E-Business Suite. Within the Territory Management (ETRM) subsystem, a territory is defined by a set of qualifiers, each of which describes a dimension (such as customer, product, or geography) against which the territory is evaluated. JTF_TERR_VALUES_ALL holds the actual comparison values that those qualifiers apply — for example, an account range, a currency, an interest code, or a product identifier. The table is therefore a core transactional store for territory definition and drives territory assignment, sales quota, and routing logic across the CRM and Trade Management modules.

Under a heuristic Data Vault classification mined from its foreign key structure, the table is satellite-leaning. It carries descriptive and operational attributes (comparison operators, flags, low/high values, currency) that attach to the parent qualifier hierarchy rather than forming an independent business entity. Modeling it as a satellite keyed to its qualifier parent is a reasonable design suggestion, while the primary surrogate key TERR_VALUE_ID preserves row-level identity.

Key Information Stored

• TERR_VALUE_ID — surrogate primary key defined by JTF_TERR_VALUES_ALL_PK; uniquely identifies each territory value row.
• TERR_QUAL_ID — foreign key to JTF_TERR_QUAL_ALL; links the value to its parent qualifier.
• INCLUDE_FLAG and COMPARISON_OPERATOR — define whether the value is inclusive or exclusive and the relational operator applied during evaluation.
• LOW_VALUE_CHAR, HIGH_VALUE_CHAR, LOW_VALUE_NUMBER, HIGH_VALUE_NUMBER — the low/high bounds for character and numeric comparison ranges.
• LOW_VALUE_CHAR_ID — reference identifier for the low character value.
• VALUE_SET and ID_USED_FLAG — identify the value set used and whether the value is expressed as an ID rather than a literal.
• INTEREST_TYPE_ID — foreign key to AS_INTEREST_TYPES_B, supporting interest-based qualifiers.
• PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID — codes for interest qualifier values.
• CURRENCY_CODE — currency associated with monetary comparison values.
• SECURITY_GROUP_ID (to FND_SECURITY_GROUPS) and CNR_GROUP_ID (to JTF_TERR_CNR_GROUPS) — enforce data security and group scoping.
• ORG_ID — multi-org operating unit context; combined with TERR_VALUE_ID in the unique index JTF_TERR_VALUES_U1, a business-key candidate.
• VALUE1_ID through VALUE4_ID and FIRST_CHAR — flexible descriptor columns for additional qualifier payloads.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework during concurrent updates.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard who-columns.

Common Use Cases and Queries

Territory value rows are typically retrieved by joining to the qualifier and territory hierarchy to reconstruct a complete territory definition. A common reporting pattern retrieves all values for a territory qualifier:

• Qualifier expansion — SELECT v.* FROM jtf_terr_values_all v WHERE v.terr_qual_id = :p_qual_id ORDER BY v.terr_value_id;
• Currency-scoped lookups — filter on CURRENCY_CODE where monetary ranges are defined.
• Security-filtered access — restrict by SECURITY_GROUP_ID to honor CRM data security.
• Change auditing — compare LAST_UPDATE_DATE against staging tables such as JTF_TAE_RPT_STAGING_OUT and JTF_CHANGED_TERR_ALL to identify newly assigned or modified territory values.
• Interest-based analysis — join to AS_INTEREST_TYPES_B on INTEREST_TYPE_ID for interest qualifier reporting.

Developers and integrators should treat TERR_VALUE_ID as the immutable row identifier and honor OBJECT_VERSION_NUMBER when writing concurrent updates.

Related Objects

• JTF_TERR_QUAL_ALL — parent qualifier table; joined on TERR_VALUE_ID.TERR_QUAL_ID = TERR_QUAL_ID.TERR_QUAL_ID.
• JTF_TERR_CNR_GROUPS — grouped value context; joined on CNR_GROUP_ID.
• AS_INTEREST_TYPES_B — interest type reference; joined on INTEREST_TYPE_ID.
• FND_SECURITY_GROUPS — security grouping; joined on SECURITY_GROUP_ID.
• JTF_CHANGED_TERR_ALL — records changed territory values; references TERR_VALUE_ID.
• JTF_TAE_RPT_STAGING_OUT — staging for territory assignment extraction; references TERR_VALUE_ID.
• Territory assignment engine and Territory Manager APIs, which consume these value rows during territory evaluation and assignment.