Results for “jtf_terr_escalations_nav”

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

Overview

The JTF_TERR_ESCALATIONS_NAV view is a UI Navigator construct owned by the APPS schema and shipped with the JTF – CRM Foundation product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the navigator tree structure for the territory escalations escalating hierarchy. In practice, the view returns the row set a navigator region consumes to render a hierarchical tree of escalation territories, their parent territories, associated sources, node types, icons, and leaf flags. Rather than storing data, the view projects a tree-shaped result set from the underlying territory and navigator metadata tables so that a runtime navigator can expand nodes on demand.

Because it is a navigator backing object, it is encountered most often during ETRM (Enterprise Territory Management) analysis, CRM Foundation diagnostics, and troubleshooting of the Territory Manager escalation hierarchy UI. The view is marked VALID, so it may be queried directly by DBAs and developers, though its primary consumer is the navigator framework itself.

Underlying Base Objects

ETRM documentation for 12.2.2 identifies the following referenced base objects:

• JTF_NAV_NODE_TYPES_V (VIEW) – supplies NODE_TYPE, ICON_NAME, and ROOT_KEY metadata that drives node rendering and the JTF_TERR_ESC_ROOT root key.
• JTF_SOURCES (VIEW) – provides the source rows displayed at the top of the tree, keyed by SOURCE_ID and MEANING.
• JTF_TERR (SYNONYM) – the territory table; provides TERR_ID, NAME, ESCALATION_TERRITORY_FLAG, and the self-referencing ESCALATION_TERRITORY_ID that establishes the escalating hierarchy.
• JTF_TERR_USGS (SYNONYM) – links territories to sources via TERR_ID and SOURCE_ID.
• FND_GLOBAL (PACKAGE) – the standard EBS context package referenced for session/security context.

The view text is a three-way UNION ALL. The first branch emits the SOURCE nodes rooted at JTF_TERR_ESC_ROOT. The second emits ESCALATION nodes, restricting to territories where ESCALATION_TERRITORY_FLAG = 'Y' and joining JTF_TERR_USGS to JTF_SOURCES to attach the parent source. The third emits TERRITORY nodes, filtered on ESCALATION_TERRITORY_ID IS NOT NULL, with NODE_TYPE dynamically reclassified to 'ESCALATION' when the escalation flag is 'Y'. Each branch computes LEAF_FLAG from an outer join count against ESCALATION_TERRITORY_ID, yielding 'Y' when no child escalation exists.

Key Columns

• LABEL – display text for the node (source MEANING or territory NAME).
• NODE_TYPE – node classification: SOURCE, ESCALATION, or TERRITORY.
• NODE_KEY – quoted identifier for the node, derived from SOURCE_ID or TERR_ID.
• ICON_NAME – icon the navigator renders for the node.
• LEAF_FLAG – 'Y' when the node has no child escalation, otherwise 'N'.
• PARENT_NODE_TYPE – type of the parent node (ROOT, SOURCE, or ESCALATION).
• PARENT_NODE_KEY – quoted key of the parent node, resolving via ESCALATION_TERRITORY_ID.

Common Use Cases and Queries

Typical uses include validating escalation hierarchy configuration, tracing which territory escalates to which, and auditing source-to-territory associations. Because the user searched for escalation_territory_id, the column is central: it is the self-referencing foreign key in JTF_TERR that the view consumes to build PARENT_NODE_KEY and determine leaf status.

List escalation territories and their parents:

• SELECT label, node_type, node_key, parent_node_type, parent_node_key, leaf_flag FROM apps.jtf_terr_escalations_nav WHERE node_type = 'ESCALATION' ORDER BY label;

Identify leaf escalation nodes for UI diagnostics:

• SELECT node_key, label FROM apps.jtf_terr_escalations_nav WHERE leaf_flag = 'Y' AND node_type = 'TERRITORY';

Reconcile against the base hierarchy directly:

• SELECT terr_id, name, escalation_territory_id, escalation_territory_flag FROM apps.jtf_terr WHERE escalation_territory_id IS NOT NULL;

These queries support impact analysis before modifying escalation territories in Territory Manager and assist in confirming that the navigator tree reflects current ETRM setup.