Search Results jtf_terr_trigger_handlers




Overview
Explore in AI Chat

Overview

JTF_TERR_TRIGGER_HANDLERS is a private PL/SQL package in the APPS schema that forms part of the Joint Task Force (JTF) Territory Manager core infrastructure in Oracle E-Business Suite. Its stated purpose is to define and expose the trigger handler APIs for the JTF_TERR and JTF_TERR_VALUES tables — the base tables that hold territory definitions and the qualification values associated with each territory. The package is declared with AUTHID CURRENT_USER, meaning that all SQL statements within it execute under the privileges of the calling schema rather than the definer, which is a common convention for internal EBS APIs that must respect the invoker's security context and operating unit (ORG_ID) restrictions.

The package is classified as OTHER in the ETRM metadata, confirming that it is not a public, customer-facing API but an internal mechanism used by the territory management engine to synchronize derived and dependent data whenever a territory or its qualification values change. The header comments date the original creation to April 2000 (EIHSU), with the shipping version referenced as 115.12 (December 2002), placing this object squarely in the long-lived JTF foundation layer that persists across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes five documented trigger-handler procedures. Each follows the established EBS "trigger handler" pattern, receiving both old (o_ prefixed) and new (n_ prefixed) column values together with a trigger mode indicator, so that the same handler can service INSERT, UPDATE, and DELETE events uniformly.

  • TERRITORY_TRIGGER_HANDLER — Handles changes to the JTF_TERR table. It receives territory identity and operating unit context plus the old and new versions of territory attributes such as parent territory, effective dates, rank, and winner count, and applies the corresponding territory maintenance logic.
  • TERR_VALUES_TRIGGER_HANDLER — Handles changes to JTF_TERR_VALUES, carrying old and new qualification values including the qualifier reference, include flag, comparison operator, ID-used flag, and the low/high character and numeric value ranges that define a territory qualification line.
  • TERR_RSC_TRIGGER_HANDLER — Manages territory resource assignments, invoked when the resources linked to a territory are inserted, updated, or removed.
  • TERR_QTYPE_TRIGGER_HANDLER — Handles territory qualifier-type relationships, ensuring that qualifier usage remains consistent with the territory definition.
  • TERR_RSCACCESS_TRIGGER_HANDLER — Manages resource access entries associated with territories, propagating access-level changes that affect which resources can act within a given territory.

Tables Accessed

The package reads from and writes to several JTF tables through APPS synonyms. JTF_CHANGED_TERR acts as the change-tracking table, recording territories whose definitions have been modified so that dependent structures can be re-evaluated. JTF_TERR_QUAL stores the qualifier definitions that drive territory evaluation. JTF_TERR_RSC holds the resource-to-territory assignments, and JTF_TERR_USGS records territory usage or assignment relationships. These tables collectively represent the working set of territory metadata that must remain synchronized whenever a base territory or value row changes.

Usage Notes

This package is not intended for direct invocation by end users or typical customizations; the ETRM metadata records zero referencing packages, underscoring its role as a low-level internal handler. In practice it is invoked from database triggers or internal territory management routines that fire in response to DML against JTF_TERR and its related tables. Territory administration forms within Oracle Sales, Trade Management, and related modules, as well as concurrent programs that rebuild or re-evaluate territory assignments, indirectly exercise these handlers. Because the procedures are private and follow the trigger-handler convention, customizations should avoid calling them directly and instead operate through the supported territory management APIs, allowing the handlers to maintain JTF_CHANGED_TERR and related structures consistently.