Search Results jtf_tae_control_pvt




Overview
Explore in AI Chat

Overview

JTF_TAE_CONTROL_PVT is a private PL/SQL control package in the Oracle E-Business Suite Territory Management module (JTF / Oracle Trade Management foundation), declared with AUTHID CURRENT_USER and owned by APPS. Its documented purpose is to serve as the control layer for the JTF_TERR_AE (Territory Assignment Engine) packages. It analyses territory definition data before invoking the mass assignment cursor generator that performs the actual territory-to-entity assignments.

The package header carries the source identifier jtftaecs.pls 120.0 dated 2005/06/02, with an internal history recording creation by EIHSU on 02/10/2002, the addition of AE CONTROL and build_qual_rel_multiple on 02/12/2002, and the addition of a source parameter on 03/13/2002. Although the header comment block refers to the package as JTF_TAE_CONTROL_PUB, the actual object name is JTF_TAE_CONTROL_PVT, and it is classified as a PVT (private) API rather than a public API. It is referenced by four other packages in the territory assignment code path.

In practical terms, the package handles the preparatory, infrastructure-level work that must precede the computationally heavy territory assignment run: decomposing territory definitions into the transient tables the engine consumes, tuning the database session for the load, controlling logging on staging tables, and emitting diagnostic output.

Key Procedures and Functions

  • WRITE_LOG — Diagnostic logging procedure. Writes a message to the package's log output, used for tracing progress and errors during territory decomposition and assignment runs.
  • SET_TABLE_NOLOGGING — Accepts a table name and switches that table to NOLOGGING mode. This is a performance measure applied to the transient/staging tables used by the assignment engine, reducing redo generation during large bulk operations.
  • SET_SESSION_PARAMETERS — Accepts sort area size and hash area size values and applies them to the current database session, tuning memory allocation for the sort- and hash-intensive territory analysis that follows.
  • DECOMPOSE_TERR_DEFNS — The principal control procedure. It decomposes territory definitions prior to the mass assignment cursor generation. It exposes FND_API standard parameters (API version, initialization message list, commit flag, validation level, and the standard return status / message count / message data out parameters), together with an error buffer and return code for concurrent-program integration. It additionally accepts run mode, classification and transaction-selection flags, index generation control, and a source identifier and transaction identifier that scope the decomposition to a specific run.

The package also declares the package-level boolean G_DEBUG (initialised FALSE), which gates debug output.

Tables Accessed

The package operates against the territory and qualifier model tables (accessed through APPS synonyms), including JTF_TERR_QUAL_ALL, JTF_TERR_DENORM_RULES_ALL, JTF_TERR_QTYPE_USGS_ALL, JTF_QUAL_TYPE_USGS_ALL, JTF_QUAL_USGS_ALL, and the qualifier factor and product tables: JTF_TAE_QUAL_FACTORS and its _S shadow, JTF_TAE_QUAL_PRODUCTS and its _S shadow, JTF_TAE_QUAL_PROD_FACTORS and its _S shadow, and JTF_TAE_ANALYZE_TERR_S. These are read to resolve territory definitions, qualifier usage, and product-based qualifier factors, and written to the transient analysis and shadow tables consumed by the assignment engine.

It also relies on DBMS_SQL for dynamic SQL, DUAL for scalar evaluation, and UTL_FILE for file-based output, consistent with its logging and NOLOGGING/session-tuning responsibilities.

Usage Notes

Because this is a PVT package, it is not intended for direct invocation by customer code, forms, or concurrent programs. It is invoked internally by the public territory assignment APIs and by the four packages documented as referencing it. In Oracle EBS 12.1.1 and 12.2.2 the territory assignment engine is driven either from the Territory Manager administrative flows or, more commonly, from scheduled concurrent programs that perform mass territory assignment. The presence of ERRBUF and RETCODE parameters on DECOMPOSE_TERR_DEFNS indicates that this procedure is designed to run inside such a concurrent program context.

Customisations should call the corresponding public territory assignment API rather than JTF_TAE_CONTROL_PVT directly. Change control should treat the package as internal EBS infrastructure; its signatures and the tables it manipulates may change with patching, and the AUTHID CURRENT_USER declaration means runtime privileges are resolved against the invoking schema.