Search Results start_workflow_process

Overview

JTF_TTY_CATCHALL_WORKFLOW is an APPS-owned PL/SQL package that supports territory-management driven workflow initiation within Oracle E-Business Suite release 12.1.1 and 12.2.2. Its name reflects its function: a "catch-all" mechanism that evaluates territory assignment data and launches an Oracle Workflow process for records that fall outside normal routing logic. The package belongs to the JTF (Oracle Application Object Library / CRM Foundation) product family, specifically the territory management subsystem (TTY = territory). It carries an ETRM classification of OTHER, indicating it is not a formal public API but is nevertheless referenced by other application code.

The package was created on 15 December 2002 (per its header comment) and has remained stable, with the last recorded source revision dated 02 June 2005. This stability across the 12.1.1 and 12.2.2 releases indicates it continues to serve its original design purpose without functional change.

Key Procedures and Functions

The package exposes three documented procedures:

• PROCESS_CATCH_ALL_REC — The primary entry point. It processes a "catch-all" record, determining whether a given party, location, or territory access qualifies for workflow initiation. It returns a return status and error message to the caller via output parameters, allowing calling code to detect and handle failures.
• GET_WORKFLOW_DETAILS — Accepts a territory group identifier and retrieves the associated workflow item type and workflow process name. This procedure decouples the configuration (which workflow to start for a given territory group) from the initiation logic, allowing administrators to change workflow assignments through territory setup rather than code changes.
• START_WORKFLOW_PROCESS — The procedure most relevant to the search term "start_workflow_process." It invokes the Oracle Workflow engine to launch a process, accepting an item type, a workflow process name, and a workflow parameter record. The parameter record (workflow_param_rec_type) carries access ID, name, postal code, state, territory group ID, and party ID, supplying the workflow with the context needed to route and execute subsequent activities.

Tables Accessed

The package reads and writes a defined set of territory, party, and location tables through APPS synonyms:

• AS_TERRITORY_ACCESSES, AS_LEADS_ALL, AS_SALES_LEADS — Territory access definitions and lead records subject to catch-all routing.
• JTF_TTY_TERR_GROUPS, JTF_TERR_ALL — Territory group and territory definitions, used to resolve territory-specific workflow configuration.
• JTF_TTY_WORKFLOW_S — The territory workflow setup table, which stores the item type and process name mappings returned by GET_WORKFLOW_DETAILS.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS — Party, site, and address data used to populate workflow parameters (party ID, postal code, state).
• DUAL — Used for single-row lookups and validation queries.

Usage Notes

JTF_TTY_CATCHALL_WORKFLOW is typically invoked indirectly rather than by end users. It is called from other PL/SQL packages (one referencing package is documented) and may be triggered by territory assignment processing or lead management logic. Because the package launches Oracle Workflow processes, its execution generates workflow notifications and item history visible in the Workflow Administrator responsibility. Developers integrating with this package should call START_WORKFLOW_PROCESS only after first obtaining valid configuration through GET_WORKFLOW_DETAILS. Given its classification as OTHER rather than a public API, custom code should treat the package as internal and validate compatibility before relying on it across release upgrades.