Search Results content_xml

Overview

JTF_FM_REQUEST_GRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that anchors the Foundation Message (FM) fulfillment and message-generation infrastructure used across ETRM and CRM modules. Its API classification is GRP (group), indicating that it exposes a cohesive set of related entry points rather than a discrete business entity service. The package is responsible for creating, submitting, tracking, and rendering fulfillment requests — the outbound communications such as e-mail, fax, and print documents that Oracle applications generate for customers and partners.

In Oracle EBS 12.1.1 and 12.2.2, JTF_FM_REQUEST_GRP centralizes request lifecycle management so that numerous AMS, ASO, AST, CS, IES, IEX, and OKL packages do not each implement their own message-dispatch logic. The package depends on FND_API for standard API error-handling and message-stack conventions, and it is referenced by more than thirty sibling packages, confirming its role as a shared utility layer within the fulfillment stack.

Key Procedures and Functions

The package publishes twenty documented procedures and functions that cover the full request lifecycle:

• Request initiation: START_REQUEST, SUBMIT_REQUEST, SUBMIT_PREVIEWED_REQUEST, SUBMIT_BATCH_REQUEST, and SUBMIT_MASS_REQUEST create and launch single, batch, or high-volume message requests.
• Request content: GET_CONTENT_XML and GET_MULTIPLE_CONTENT_XML assemble the rendered document body, while REPLACE_TAG substitutes merge-field tokens during content generation.
• Request control: CANCEL_REQUEST and NEW_CANCEL_REQUEST terminate active requests; PAUSE_RESUME_REQUEST and NEW_PAUSE_RESUME_REQUEST manage suspend and restart behavior.
• Retry and recovery: RESUBMIT_REQUEST, RESUBMIT_JOB, CORRECT_MALFORMED, and RESUBMIT_MALFORMED address failed or malformed dispatches.
• Routing: SEND_REQUEST, DETERMINE_REQUEST_PATH, and SEND_REQUEST with SEND_REQUEST’s companion logic select the delivery channel and processing path.

Collectively these entry points give callers uniform control over submission, rendering, cancellation, pause/resume, and error correction without directly manipulating the underlying request tables.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables that constitute the fulfillment request repository:

• JTF_FM_REQUEST_HISTORY_ALL and JTF_FM_REQUEST_CONTENTS store request history and generated content.
• JTF_FM_REQUESTS_AQ and JTF_FM_PROCESSED support the Advanced Queue and processed-record tracking used for asynchronous delivery.
• JTF_FM_RESUBMITTED, JTF_FM_CONTENT_FAILURES, and JTF_FM_EMAIL_STATS record resubmissions, content-generation failures, and e-mail delivery statistics.
• JTF_FM_INT_REQUEST_HEADER, JTF_FM_QUERIES_ALL, and JTF_FM_QUERY_MES hold request headers and query definitions.
• FND_LOBS and FND_LOBS_S store large binary attachments, while IBC_CONTENT_ITEMS and JTF_AMV_ATTACHMENTS supply media and attachment content.
• JTF_FM_REQUESTHISTID_S provides the sequence used to generate request history identifiers.

Usage Notes

JTF_FM_REQUEST_GRP is not typically invoked directly by end users. It is called programmatically by concurrent programs, Oracle Workflow activities such as JTF_FM_PROCESS_REQUEST_WF, and module packages including IEX_SEND_FFM_PVT, AMS_FULFILL_PVT, OKL_FULFILLMENT_PUB, and OKL_AM_UTIL_PVT. Users searching on OKL_AM_UTIL_PVT will encounter this package because lease and asset-fulfillment routines in the OKL schema delegate message dispatch to JTF_FM_REQUEST_GRP.

Because entry points comply with FND_API conventions, custom code should invoke them rather than perform direct DML on the underlying JTF_FM tables; this preserves queue integrity, auditing, and resubmission handling across 12.1.1 and 12.2.2 environments.