Search Results create_mapping_rules

Overview

JTF_TTY_NA_WF is a private PL/SQL package owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. Its declared purpose is to reassign "Catch All" territories and create the appropriate named accounts. The package is part of the Oracle Trade Management / Territory Manager (JTF_TTY) family of components, which govern how sales territories, named accounts, and account qualification mappings are maintained within the CRM and Order-to-Cash flows.

The package was created on 13-Dec-2002 by ARPATEL (header jtftrwas.pls 120.0). It is explicitly documented as for PRIVATE USE ONLY, meaning Oracle does not publish it as a supported public API and its signature may change without notice. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the definer. The workflow-oriented name and the presence of a standard workflow callback signature (itemtype, itemkey, actid, funcmode, resultout) indicate that the package is designed to be invoked from an Oracle Workflow process, most likely for the business event that moves a "Catch All" territory's accounts into properly named accounts. Under the ETRM classification this object is catalogued as API classification OTHER, with four documented procedures and functions and no dependent packages referencing it.

Key Procedures and Functions

• AssignRep — The workflow callback. It follows the standard Oracle Workflow PL/SQL API convention with itemtype, itemkey, actid, funcmode, and a resultout output. Its role is to drive the assignment of a sales representative during the named-account / catch-all territory reassignment process, returning a workflow result.
• add_org_to_terrgp — Adds an organization (party/resource) to a territory group. It accepts territory group, reference account, party, resource, role code, user, resource group, lead keyword, and lead postal code inputs, and returns the resulting account identifier. It is the core routine that enrolls an organization into a territory group as part of named-account creation.
• create_mapping_rules — Accepts an account identifier, keyword, and postal code, and creates the qualification mapping rules that associate a named account with its territory qualification criteria. This is the procedure most relevant to the "create_mapping_rules" search, as it is the entry point for building account qualification mappings used by territory assignment.
• get_site_type_code — A function returning the site type code for a given party id, used to classify a customer site (for example, bill-to versus ship-to) when determining how an account should be mapped to a territory.

Tables Accessed

• JTF_TTY_NAMED_ACCTS / _S, JTF_TTY_NAMED_ACCT_RSC / _S — store named accounts and their assigned resources; these are the primary write targets of create_mapping_rules and add_org_to_terrgp.
• JTF_TTY_TERR_GRP_ACCTS / _S — holds the association between territory groups and accounts; updated when organizations are added to a territory group.
• JTF_TTY_ACCT_QUAL_MAPS / _S — holds account qualification mappings, the persistent form of the rules created by create_mapping_rules.
• JTF_TTY_ACCT_RSC_DN / _S — resource detail for named accounts.
• HZ_PARTIES and HZ_RELATIONSHIPS — read for party and relationship information used to resolve the organization and site being mapped.
• DUAL — used for scalar lookups.

Usage Notes

JTF_TTY_NA_WF is a private package and is not intended for direct invocation by customers. In practice it is invoked from Oracle Workflow by the AssignRep callback when a workflow process reassigns catch-all territory accounts, and indirectly through the Territory Manager configuration and the named-account maintenance flows. Custom code should avoid calling create_mapping_rules or add_org_to_terrgp directly because the package is documented as private and its behavior is subject to change; where equivalent public functionality is required, the supported JTF_TTY territory and HZ party APIs should be used instead. Because the package runs AUTHID CURRENT_USER, the caller must have the necessary privileges on the referenced JTF_TTY and HZ tables. No other packages reference it, confirming it is a leaf implementation detail of the territory reassignment workflow rather than a reusable public API.