Search Results jtf_fm_request_grp_wf




Overview
Explore in AI Chat

Overview

JTF_FM_REQUEST_GRP_WF is a PL/SQL package in the APPS schema that provides the workflow-facing wrapper for the Oracle E-Business Suite fulfillment request engine delivered through the JTF (Oracle Applications Foundation / Customer Relationship Management) product family. Its purpose is to expose the fulfillment request lifecycle to Oracle Workflow by way of callable workflow function activities. The package bridges the gap between a Workflow process definition and the underlying business logic held in JTF_FM_REQUEST_GRP, allowing a fulfillment process to be started, a request to be submitted, and a previously submitted request to be resubmitted entirely from within a running workflow.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is consistent with its role as a thin, invocable layer rather than a privileged bulk-processing routine. The source header dates the original implementation to early 2000, and the same interface has been carried forward into EBS 12.1.1 and 12.2.2 without signature changes.

Key Procedures and Functions

  • StartFulfillProcess — Starts the fulfillment workflow process. It accepts an API version, a commit flag, a validation level, the request content as XML, a request identifier, and a template identifier, and returns a status and a result value. This is the entry point used when a new fulfillment cycle must be launched for a given template.
  • submit_request — A workflow-standard callback whose sole documented purpose is to call JTF_FM_REQUEST_GRP.SUBMIT_REQUEST. It receives the usual Workflow function-activity parameters (item type, item key, activity identifier, function mode, and a result out parameter) and returns the outcome of the submission back to the workflow engine.
  • resubmit_request — The direct counterpart to submit_request, documented as calling JTF_FM_REQUEST_GRP.RESUBMIT_REQUEST. It follows the identical Workflow function-activity signature and is the routine invoked when a previously created fulfillment request needs to be re-driven. This is the procedure most closely associated with the search term "resubmit_request."

All three routines are thin delegations; no business logic is implemented inside this package itself.

Tables Accessed

The documented table references for this package are minimal. JTF_FM_WORKFLOW_S is the fulfillment workflow staging/state table through which request state is tracked and passed between the wrapper and the base fulfillment package; the presence of DUAL reflects simple single-row lookups such as sequence or constant retrieval performed during initialization of the workflow callbacks. No direct DML against base fulfillment request tables is documented here, since that work is performed by the delegated routines in JTF_FM_REQUEST_GRP.

Usage Notes

Because the procedures observe the standard Oracle Workflow function-activity signature (itemtype, itemkey, actid, funcmode, resultout), this package is not intended to be called directly from a form or from ad hoc custom code. It is referenced from Workflow process definitions as the function activity executed at the submit and resubmit steps of the fulfillment request process. Customizations that need to trigger a resubmission should normally invoke JTF_FM_REQUEST_GRP.RESUBMIT_REQUEST directly, or, where workflow context must be preserved, route the call through this wrapper. In EBS 12.1.1 and 12.2.2 the package is deployed and patched as part of the standard APPS schema; any modification would be overwritten by patching and is therefore not supported. The package is referenced by zero other documented packages, confirming its role as a leaf-level workflow interface rather than a reusable API.