Search Results jtf_tty_workflow_s

Overview

The APPS.JTF_TTY_CATCHALL_WORKFLOW package body is a component of the Oracle E-Business Suite CRM "TeleSales / Telephony" (JTF_TTY) infrastructure. It provides the server-side PL/SQL entry points used to route "catch-all" TeleSales activity records—leads, opportunities and territory-based assignments that are not handled by more specific routing rules—into an Oracle Workflow process. In effect, it acts as the bridge between the TeleSales data model (leads, parties, territories and workflow staging tables) and the Workflow engine (WF_ENGINE).

The package is classified as OTHER in the ETRM metadata, meaning it is an internal, non-public API rather than a documented extension point. It is owned by APPS and is currently VALID in both the 12.1.1 and 12.2.2 releases. Its principal role is to evaluate catch-all routing criteria, resolve the correct workflow definition, and initiate a workflow instance for the qualifying record. The presence of the dependency on JTF_TTY_WORKFLOW_S and JTF_TTY_WORKFLOW_POP_BIN_PVT confirms that it operates as part of the broader TeleSales workflow population and bin-management subsystem.

Key Procedures and Functions

Three documented program units make up the package body:

• PROCESS_CATCH_ALL_REC — The main driver procedure. It receives a candidate catch-all record, applies the routing/qualification logic, and determines whether the record proceeds into a workflow. It is the procedure most likely to be invoked by the TeleSales processing layer or a scheduled concurrent program.
• GET_WORKFLOW_DETAILS — A retrieval routine that resolves the workflow metadata required before an instance can be started, such as the workflow definition/item type and the associated parameters derived from the territory and lead data.
• START_WORKFLOW_PROCESS — Initiates the workflow instance. It calls WF_ENGINE to create and launch the workflow process for the qualified record, using the details assembled by GET_WORKFLOW_DETAILS.

Only the names and documented purposes are asserted here; the actual parameter signatures are not published in the ETRM extract and should not be assumed.

Tables Accessed

The package references the following tables through APPS synonyms:

• AS_LEADS_ALL, AS_SALES_LEADS — the base and sales-lead tables holding the candidate records subject to catch-all routing.
• AS_TERRITORY_ACCESSES, JTF_TERR_ALL, JTF_TTY_TERR_GROUPS — territory definitions, access rules and territory groups used to qualify the catch-all record.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS — Trading Community Architecture (TCA) party, site and location data used to resolve the customer context.
• JTF_TTY_WORKFLOW_S — the TeleSales workflow staging/settings table, which supplies workflow configuration.
• DUAL — used for single-row PL/SQL evaluations.

AS_ACCESSES_ALL also appears in the broader dependency list, consistent with territory access lookups.

Usage Notes

This package is an internal component and is not intended for direct customer invocation. It is typically reached indirectly: the TeleSales application logic or the workflow population process (JTF_TTY_WORKFLOW_POP_BIN_PVT) invokes PROCESS_CATCH_ALL_REC to evaluate records that fall through to catch-all routing, and the package then starts the appropriate workflow via START_WORKFLOW_PROCESS. Because it is not referenced by any other database object per the ETRM metadata (though one package is listed as a referencing package at runtime), customizations should treat it as a black box. Administrators troubleshooting missing TeleSales workflow notifications should inspect the JTF_TTY_WORKFLOW_S configuration and the Workflow runtime tables rather than modifying this package. Direct calls from custom code are strongly discouraged, as the package is not a supported public API in either 12.1.1 or 12.2.2.