Search Results get_winners

Overview

JTY_ASSIGN_BULK_PUB is a public PL/SQL API in the Oracle E-Business Suite Territory Management (Territory Assignment Engine, TAE) module. Its documented purpose is to retrieve winning territories or territory resources for bulk transaction objects. In other words, given a set of transactional records, the package evaluates the applicable territory assignment rules and determines which territories—and which resources within those territories—qualify as "winners" for each transaction. The package is owned by APPS and classified as a public (PUB) API, meaning Oracle exposes it for supported customer and partner integration use rather than as an internal-only implementation detail. It is registered in ETRM at version 12.1.1 and 12.2.2, with a source header timestamp indicating an origin in 2005; the metadata reflects the package as documented for release 12.2.2.

The API is oriented toward bulk or multi-level processing. Its documented procedures explicitly note support for "MULTI-NUM MULTI-LEVEL PROCESSING," indicating that it can traverse multi-level territory hierarchies and evaluate winners at several levels of the territory tree in a single invocation.

Key Procedures and Functions

The documented interface exposes four procedures and functions:

• GET_WINNERS — The primary entry point associated with the user search term "get_winners." It returns the winning territories or territory resources for the bulk transaction objects being processed. As the headline API of the package, it encapsulates the core winner-selection logic.
• PROCESS_LEVEL_WINNERS — Processes winners at an intermediate level of the territory hierarchy. Its documented parameters indicate it accepts target and parent level table identifiers, upper and lower level-from-root bounds, a matches target, a source identifier, a run mode, a date-effective flag, a return status, and a worker identifier. This structure supports parallel or segmented evaluation across territory levels.
• PROCESS_FINAL_LEVEL_WINNERS — Handles the final (leaf) level of the territory hierarchy, completing the winner determination once intermediate levels have been evaluated. Its parameters mirror those of the level-processing procedure, with level-five target table handling.
• COLLECT_TRANS_DATA — Collects or assembles transaction data required for territory evaluation before winners are determined. This supports the bulk nature of the API, gathering the input set that the winner-processing routines subsequently evaluate.

Parameter lists above are summarized from the documented specification excerpt; no undocumented parameters should be assumed.

Tables Accessed

The package reads and writes a range of TAE and territory metadata tables through APPS synonyms. The core territory definition and qualification tables include JTF_TERR_ALL (territory definitions), JTF_QUAL_TYPES_ALL (qualification types), JTF_TAE_QUAL_PRODUCTS and JTY_TAE_ATTR_PRODUCTS_SQL (qualification and attribute product mappings), JTF_TERR_QTYPE_USGS_ALL (territory qualification usage), and the territory resource tables JTF_TERR_RSC_ALL and JTF_TERR_RSC_ACCESS_ALL, which underpin resource-level winner determination. Transaction and usage-program context is provided by JTY_TRANS_USG_PGM_DETAILS and JTY_TRANS_USG_PGM_SQL. The package also references JTY_CHANGED_TERRS, JTY_DEA_ATTR_PRODUCTS, and JTY_DEA_ATTR_PRODUCTS_SQL for change tracking and attribute-driven evaluation. Utility references include AD_DDL and ALL_TAB_COLUMNS, indicating dynamic SQL construction and metadata inspection at runtime.

Usage Notes

JTY_ASSIGN_BULK_PUB is a public API typically invoked programmatically rather than interactively. It is referenced by twelve other packages, confirming its role as a shared service within the territory assignment engine and its use during bulk territory assignment runs for transaction objects. Because it supports multi-number, multi-level processing and accepts a worker identifier and run mode, it is suited to concurrent or parallelized processing scenarios where large transaction volumes must be evaluated against multi-level territory hierarchies. Custom code integrating TAE should call the documented GET_WINNERS entry point or the level-processing procedures in the prescribed sequence (collect transaction data, process intermediate levels, then process final-level winners), respecting the returned status and date-effective semantics. As a PUB API, it remains the supported surface over the underlying TAE internals.