Search Results terr_rsc

Overview

The APPS.JTF_TERR_TRIGGER_HANDLERS package body implements the private trigger-handling API layer for the Oracle E-Business Suite Territory Manager, part of the Foundation/CRM (Joint Task Force) technology stack shipped with EBS 12.1.1 and 12.2.2. Its stated purpose in the package header is to define territory trigger handlers — that is, the internal logic that fires in response to insert, update, and delete activity against core territory tables. The package is classified under ETRM as OTHER and is documented as a private API, meaning it is not intended as a public extension point but is invoked indirectly by the Territory Manager's own DML paths.

A significant design constraint is recorded in the package history: transaction capture is restricted so that "only transactions for sales will be recorded" (10/04/00, BUG 1423245/1423718). The handlers therefore selectively propagate changes into the change-tracking tables rather than mirroring every row operation. Earlier revisions also optimized the code (09/07/00) and corrected defect BUG 1410995, including the suppression of qual_type_usg_id in the update procedure and the cascading deletion of related change records when a territory changed record is deleted.

Key Procedures and Functions

The documented package exposes five procedures, each aligned to a specific territory table whose DML must be intercepted:

• TERRITORY_TRIGGER_HANDLER — Handles trigger activity for the primary territory table, JTF_TERR. It captures territory-level changes, including parent territory relationships, and is responsible for recording the corresponding entries in the change-tracking table.
• TERR_VALUES_TRIGGER_HANDLER — Handles trigger activity for JTF_TERR_VALUES, propagating changes to territory value rows so that downstream consumers see accurate qualifier/value state.
• TERR_RSC_TRIGGER_HANDLER — Handles trigger activity for JTF_TERR_RSC, the territory resource assignment table. This is the handler most closely associated with the search term terr_rsc, and it records resource-assignment changes against territories.
• TERR_QTYPE_TRIGGER_HANDLER — Handles trigger activity for qualifier-type usage, keyed to JTF_TERR_QTYPE_USGS and its related qualifier table JTF_TERR_QUAL.
• TERR_RSCACCESS_TRIGGER_HANDLER — Handles trigger activity for JTF_TERR_RSC_ACCESS, recording changes to resource access rights on territories.

Per the package history, old values as well as new values are recorded for territory party (TERR_PTY) transactions (10/06/00), and a request_id IS NULL predicate is applied across all SQL statements to isolate direct, interactive changes from concurrent-request-driven maintenance.

Tables Accessed

• JTF_CHANGED_TERR — The change-capture table that receives records generated by every handler; the history notes special on-delete behavior where either a delete record is added or an existing on-insert record is removed, together with cascading cleanup of all records relating to a deleted territory.
• JTF_TERR_RSC — Territory resource assignments; read and written to detect and record resource-level changes.
• JTF_TERR_RSC_ACCESS — Resource access rights; accessed by the resource-access handler.
• JTF_TERR_QUAL — Territory qualifiers, referenced in support of qualifier-type processing.
• JTF_TERR_USGS — Territory usages, referenced alongside qualifier handling.

All tables are accessed through APPS synonyms in the standard EBS manner.

Usage Notes

Because this is a private implementation package, it should not be called directly by custom code. It is invoked automatically by the database triggers or program units attached to the territory tables, and it propagates qualifying changes into JTF_CHANGED_TERR for consumption by Territory Manager's denormalization and refresh processes. The package is not referenced by any other documented package (referenced-by count of zero), confirming its role as a terminal handler layer. When diagnosing issues around the search term terr_rsc — such as stale territory resource assignments or missing change records — the TERR_RSC_TRIGGER_HANDLER procedure and the JTF_TERR_RSC/JTF_CHANGED_TERR pair are the primary objects to inspect. Because DML in concurrent request context is filtered by the request_id IS NULL condition, bulk territory maintenance run via concurrent programs may not generate the same change records as interactive updates, a behavior worth accounting for during data reconciliation.