Results for “create_terr_qualtype_usage”

10 results




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

Overview

APPS.JTF_TERRITORY_PVT (defined with the AUTHID CURRENT_USER directive) is the core territory manager private API for Oracle EBS. Its stated purpose is to serve as a public API for inserting territory-related information into the JTF tables, providing the specifications for PL/SQL records and tables along with the private territory-related APIs used by the Territory Manager and dependent modules. This package underpins the management of territory hierarchies, territory qualifiers, usages, and territory values — the structures that drive territory-based assignment and access across CRM and related applications.

The package header identifies it explicitly as a private API ("This package is for private use"). It is hierarchically under the ETRM (Enterprise Territory Management) subsystem and is exposed to other internal packages rather than to end-user extendable code. The search term get_terr_value_desc relates to territory value descriptions; the package maintains the underlying territory value data through its CREATE_TERR_VALUE / UPDATE_TERR_VALUE / DELETE_TERR_VALUE routines, and description retrieval for a territory value is performed against the JTF_TERR_VALUES structure this package manages.

Key Procedures and Functions

The documented interface exposes 51 procedures/functions. The principal groups are:

The package additionally supports territory duplication (Gen_Duplicate_Territory), concurrent copy handling (Concurrent_Copy_Territory, Write_Log, Conc_Req_Copy_T), overlap checking, and unique validation routines, per the package history.

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

Usage Notes

JTF_TERRITORY_PVT is a private, internal API. It is typically invoked from the ETRM/territory management forms, from territory duplication and concurrent copy programs, and by other internal packages (the metadata indicates it is referenced by 7 other packages). Custom code should not call it as a supported extension point; supported integration normally occurs through the higher-level territory public APIs. When debugging territory value description behavior, note that value descriptions are resolved from JTF_TERR_VALUES, and entitlement/security rules govern visibility of these records.