Results for “formatting_function_flag”

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

Overview

JTF_TERR_VALUES_DESC_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 – CRM Foundation product family and is a component of the Oracle Territory Management (Territory Manager) infrastructure. The view presents territory qualifier values alongside decoded, human-readable descriptions, so that numeric identifiers, IDs, and low-level value-set codes stored in the base territory tables are surfaced as meaningful text for reporting, integration, and user-interface consumption.

The view text is dominated by calls to the JTF_TERRITORY_PVT package, specifically the GET_TERR_VALUE_DESC function, which resolves the raw value columns into display strings. Which description logic is applied to a given row depends on the qualifier's DISPLAY_TYPE as recorded in the usage definition (for example CHAR, DEP_2FIELDS_1CHAR_1ID, or INTEREST_TYPE). Because of this dependency, the view is a presentation-layer object rather than a normalized data source.

The "currency_desc" search term is typically associated with this object because territory qualifiers can be built on currency value sets. When the underlying value set resolves to currency codes, the decoded description exposes the currency name or code in a readable form through the same GET_TERR_VALUE_DESC mechanism. This makes JTF_TERR_VALUES_DESC_V a common target for queries that require a descriptive label for a territory value rather than its internal ID.

Underlying Base Objects

The documented base objects referenced by the view are:

• JTF_TERR_VALUES_ALL (SYNONYM) – the primary source of territory qualifier value rows, aliased as JTVA in the view text. It supplies value IDs, comparison operators, low/high character and number values, ID used flags, interest type IDs, and audit columns.
• JTF_TERR_QUAL (SYNONYM) – the territory qualifier definition, providing the qualifier context for each value row via TERR_QUAL_ID.
• JTF_QUAL_USGS (SYNONYM) – the qualifier usage definition, aliased as JQU. It supplies DISPLAY_TYPE, CONVERT_TO_ID_FLAG, COLUMN_COUNT, DISPLAY_SQL1, and DISPLAY_SQL2, which drive the DECODE branches in the view.
• JTF_TERR_CNR_GROUPS (SYNONYM) – territory qualifier group definitions used within the broader territory model.
• JTF_TERRITORY_PVT (PACKAGE) – the PL/SQL API package whose GET_TERR_VALUE_DESC function performs the actual decoding of stored values into descriptive text.

The view therefore joins value rows to their qualifier usage metadata and applies the package function per row, rather than relying on a simple table join. This design centralizes display logic in the package and keeps the view consistent with Territory Manager runtime behavior.

Key Columns

• TERR_VALUE_ID – primary identifier of the territory value row.
• TERR_QUAL_ID – foreign key to the qualifier definition that the value belongs to.
• INCLUDE_FLAG / COMPARISON_OPERATOR – control how the value participates in territory qualification logic.
• LOW_VALUE_CHAR / HIGH_VALUE_CHAR – the raw stored character range values; LOW_VALUE_CHAR_DESC and HIGH_VALUE_CHAR_DESC are their decoded equivalents.
• LOW_VALUE_NUMBER / HIGH_VALUE_NUMBER – numeric counterparts of the range values.
• LOW_VALUE_CHAR_ID – the underlying ID used when a value is stored by reference (relevant to ID_USED_FLAG handling).
• VALUE_SET – identifies the value set from which the values derive; currency-based qualifiers are resolved here.
• INTEREST_TYPE_ID / INTEREST_TYPE and PRIMARY_INTEREST_CODE_ID / PRIMARY_INTEREST_CODE – interest-related qualifiers and their decoded labels.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is most often used to produce readable territory qualifier reports and to validate which values are attached to a territory or qualifier. A typical query joins the view to JTF_TERR_QUAL on TERR_QUAL_ID and filters by qualifier name or value set:

• Listing all values for a currency qualifier: SELECT terr_value_id, low_value_char, low_value_char_desc FROM jtf_terr_values_desc_v WHERE value_set = :currency_value_set;
• Joining to qualifier metadata: SELECT q.terr_qual_id, q.name, v.low_value_char_desc, v.high_value_char_desc FROM jtf_terr_qual q, jtf_terr_values_desc_v v WHERE q.terr_qual_id = v.terr_qual_id;
• Finding ranges by comparison operator: select rows where COMPARISON_OPERATOR indicates BETWEEN or equals, using LOW_VALUE_NUMBER and HIGH_VALUE_NUMBER to bracket numeric qualifiers.

Because decoded columns are populated by a PL/SQL function, queries that return large result sets can incur performance costs; filtering by TERR_QUAL_ID or VALUE_SET before selecting decoded columns is recommended for reporting and integration extracts.