Search Results assign_geo_terr




Overview

APPS.JTF_TTY_GEO_TERRGP is a PL/SQL package belonging to the Oracle Territory Management (formerly TeleSales / TTY) schema family within Oracle E-Business Suite. Its stated purpose, drawn from the package header comment (revision 120.2, last shipped 2005/09/23), is "For handling Geography Territor Groups, like delete, create, update." The package therefore provides the programmatic layer that governs how geography-based territory groups are constructed, maintained, and removed, and how the geography definitions inside those groups are propagated to the underlying territory and resource-assignment tables used by the territory engine.

The header carries an explicit restriction: "ORACLE INTERNAL USE ONLY: NOT for customer use." In the EBS 12.1.1 and 12.2.2 releases this package is classified as an OTHER API rather than a public, supported interface, meaning Oracle development owns its behavior and external callers do so at their own risk. It is not referenced by any other documented package, so it operates as a low-level utility invoked either by Oracle's own territory administration code or by the concurrent/forms layer that manages geography territory groups.

The package appears to sit between the high-level territory administration UI and the raw geography-to-territory mapping tables. Its procedures combine group-level operations (creating, deleting, and updating a geography territory group) with membership operations (attaching or detaching individual geographies) and with the downstream assignment of territories to resources.

Key Procedures and Functions

The documented interface exposes ten procedures. Naming and grouping below reflect the header comments; parameter signatures are intentionally omitted.

  • POPULATE_SELF_SRV_SCHEMA — Populates the self-service schema structures associated with a territory, presumably to keep the self-service (iStore/self-service territory) representations synchronized with the base territory definitions.
  • DELETE_TERRGP — Deletes a geography territory group identified by territory group ID. This is the procedure matched by the user's search term "delete_terrgp" and is the entry point for removing a group from the territory model.
  • ADD_GEO_TO_GRP — Adds a geography (or geography range) to an existing group, accepting a from/to geography range, an operator, a geography type, and a user ID for auditing.
  • CREATE_GRP_GEO_TERR — Creates the geography territory records for a newly defined geography territory group, effectively instantiating the group as a territory.
  • DELETE_GEOS_FROM_TERRS — Removes geographies from the territories that belong to a group, typically the bulk counterpart to individual detach operations.
  • DELETE_GEO_FROM_GRP — Removes geography membership from a group at the group level.
  • UPDATE_GEO_GRP_ASSIGNMENTS — Refreshes or recalculates the geography-to-group assignments when group definitions change.
  • ASSIGN_GEO_TERR — Assigns a geography territory to a resource, taking territory, resource, resource group, and resource role code to establish the ownership relationship.
  • DELETE_GEO_TERR_RSC — Removes a resource assignment from a geography territory.
  • REPLACE_GEO_TERR_RSC — Replaces the owner resource on a geography territory, added in 2004 for bug 3889970, supporting ownership hand-off without deleting and re-creating the assignment.

Collectively these procedures cover the create, update, delete, and assignment lifecycle described in the package PURPOSE comment.

Tables Accessed

Through APPS synonyms the package touches a mix of generic territory tables and TTY geography-specific tables. The JTF_TTY_GEO* family forms the core of its work:

Usage Notes

Because the package is marked internal-use-only and is not referenced by any other documented package, it is not intended for direct customer invocation. In practice it is reached from the Oracle Territory Manager forms and related administrative flows when an administrator defines, edits, or deletes a geography territory group, and from internal concurrent or API code that maintains self-service territory data. Customizations should avoid calling these procedures directly; the supported route for geography and territory maintenance is the published Territory Management API layer. Where direct access is unavoidable in 12.1.1 or 12.2.2, callers must supply the required IDs and user ID, handle the OUT return-status style conventions used by the underlying EBS API framework, and account for the fact that validation, audit, and change-tracking (JTF_TTY_NAMED_ACCT_CHANGES) are handled inside the package rather than by the caller.