Results for “jtf_terr_templates_nav”

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

Overview

JTF_TERR_TEMPLATES_NAV is an APPS-owned database view in Oracle EBS Release 12.1.1 and 12.2.2, belonging to the JTF – CRM Foundation product family. It functions as a UI Navigator view that defines the navigator tree structure used to render the relationship between territory templates and the territories created from those templates. In effect, the view materializes the hierarchy that the Territory Manager (or equivalent ETRM administrative UI) traverses when a user selects the "view by Templates" navigation option.

The view does not store data; it is a pure projection built from a UNION of three result sets, each producing a distinct level of the navigator tree: the root SOURCE level, the TEMPLATE level, and the TERRITORY level. Every branch of the UNION anchors on the constant ROOT_KEY value 'JTF_TERR_TEMP_ROOT' (returned as PARENT_NODE_KEY), which explains the common user search term jtf_terr_temp_root. This constant is the anchor key that ties all nodes of the template navigator to a single virtual root in the tree.

Underlying Base Objects

The documented referenced objects are FND_GLOBAL (package), JTF_NAV_NODE_TYPES_V (view), JTF_SOURCES (view), JTF_TERR (synonym), and JTF_TERR_USGS (synonym). The view text joins these as follows:

• JTF_NAV_NODE_TYPES_V (NT) — supplies NODE_TYPE, ICON_NAME, and ROOT_KEY for each navigator tree level. The predicates NT.ROOT_KEY = 'JTF_TERR_TEMP_ROOT' restrict the view to the territory-template tree only.
• JTF_SOURCES (S / JS) — supplies the SOURCE_ID and MEANING used to label and key the root source node.
• JTF_TERR (JTALL, JTALL2, T) — the territory definition table. JTALL rows with TEMPLATE_FLAG = 'Y' form template nodes; rows with TEMPLATE_FLAG = 'N' and a non-null TEMPLATE_TERRITORY_ID form child territory nodes. The self-join JTALL2 provides the child-count check that determines the leaf flag.
• JTF_TERR_USGS (JTU) — links territories to their owning source via SOURCE_ID, providing the PARENT_NODE_KEY for template nodes.

FND_GLOBAL is referenced for session context (such as ORG_ID and USER_ID) used implicitly by the underlying ETRM security and territory-access logic applied at runtime.

Key Columns

• LABEL — the display text of the node: SOURCE meaning, template name, or territory name.
• NODE_TYPE — the level identifier; values are 'SOURCE', 'TEMPLATE', and 'TERRITORY'.
• NODE_KEY — quoted string identifier for the node, built from SOURCE_ID or TERR_ID, used by the UI to resolve selection.
• ICON_NAME — the icon presented beside the node in the navigator.
• LEAF_FLAG — 'Y' indicates a terminal node. For templates it is computed with DECODE(COUNT(...)); territories and the source root are statically flagged.
• PARENT_NODE_TYPE — the parent level ('ROOT', 'SOURCE', or 'TEMPLATE'), establishing the tree edges.
• PARENT_NODE_KEY — the quoted key of the parent node; the root rows all carry 'JTF_TERR_TEMP_ROOT'.

Common Use Cases and Queries

Typical uses include diagnosing navigator rendering issues, validating template-to-territory parents, and extracting the tree for migration or auditing.

List all template nodes and their parents:

• SELECT label, node_key, parent_node_key FROM jtf_terr_templates_nav WHERE node_type = 'TEMPLATE' ORDER BY label;

Find territories generated from a specific template:

• SELECT label, node_key FROM jtf_terr_templates_nav WHERE node_type = 'TERRITORY' AND parent_node_key = '"12345"';

Locate the tree root and its immediate source nodes:

• SELECT label, node_type, node_key FROM jtf_terr_templates_nav WHERE parent_node_key = 'JTF_TERR_TEMP_ROOT';

Because the view is read-only and driven by the ROOT_KEY constant, query results reflect the live territory model and must respect ETRM data security applied through the underlying JTF_TERR access rules at runtime.