Search Results jty_changed_dea_terrs_s

Overview

JTY_TERR_TRIGGER_HANDLERS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Oracle Territory Management (ETRM) module. Its business purpose is to provide centralized trigger-handling logic that synchronizes the territory definition base tables with the changed-territory staging tables used to drive territory assignment and denormalization processes. In Oracle EBS 12.1.1 and 12.2.2, territory definitions are maintained across several child tables (resources, usages, qualifiers, and associated resource access rows). Whenever one of these child structures is inserted, updated, or deleted, the change must be propagated to the JTY_CHANGED_TERRS denormalization queue so that downstream concurrent programs can recompute the affected territories.

The package encapsulates that propagation and is classified as an OTHER API object rather than a public business API. It exposes seven documented handler entry points that serve as the single point of control for territory change detection.

Key Procedures and Functions

The package body documents seven handler procedures/functions, each aligned to a specific territory sub-entity:

• TERRITORY_TRIGGER_HANDLER — Handles change events occurring at the master territory level, recording affected territory identifiers for downstream processing.
• TERR_VALUES_TRIGGER_HANDLER — Handles changes to territory value rows associated with a territory definition.
• TERR_RSC_TRIGGER_HANDLER — Handles changes to territory resource assignments.
• TERR_QTYPE_TRIGGER_HANDLER — Handles changes to territory qualifier type definitions.
• TERR_RSCACCESS_TRIGGER_HANDLER — Handles changes to resource access rows tied to a territory.
• TERR_QUAL_TRIGGER_HANDLER — Handles changes to territory qualifier rows.
• TERR_USGS_TRIGGER_HANDLER — Handles changes to territory usage rows.

Each handler consumes the affected row data and writes the corresponding territory into the appropriate changed-territory table. The package also references FND_MSG_PUB, indicating that it uses the standard Oracle Application Object Library message dictionary for raising or logging errors. Parameter lists are not documented here and should be verified against the live source.

Tables Accessed

The documented dependency list shows the package reading and writing the following APPS objects:

• JTF_TERR_QUAL, JTF_TERR_RSC_ALL, JTF_TERR_USGS_ALL — the territory qualifier, resource, and usage base tables read to identify the affected territory.
• JTY_CHANGED_TERRS and JTY_CHANGED_TERRS_S — the changed-territory table and its sequence, populated so that downstream denormalization can detect modified territories.
• JTY_CHANGED_DEA_TERRS and JTY_CHANGED_DEA_TERRS_S — the changed-territory variant used for the territory denormalization/assignment process, with its sequence.
• DUAL — used for singleton sequence or constant retrieval.

The user search term "jty_changed_terrs_s" corresponds directly to the sequence referenced in this dependency list, which the handlers use to generate primary keys for the changed-territory staging table.

Usage Notes

JTY_TERR_TRIGGER_HANDLERS is not referenced by any other database object according to the ETRM metadata; conversely, it is documented as referenced by seven other packages, reflecting its role as a shared utility layer invoked by trigger-generated calls or by the parent territory maintenance packages. Typical invocation points include database triggers on the JTF_TERR_* base tables and any custom code that programmatically modifies territory definitions. The package is executed implicitly during territory maintenance through the Territory Management forms UI and during territory denormalization concurrent programs, rather than being scheduled standalone. Because it directly manipulates the changed-territory staging tables, direct custom invocation should be avoided; instead, extensions should follow the standard territory maintenance flow so that the staging and sequence tables remain consistent.