Search Results resubmit_job

Overview

The APPS.JTF_FM_REQUEST_GRP package body is the core execution engine of the Oracle E-Business Suite Fulfillment Manager (JTF_FM) module, which governs the generation, queuing, transmitting, and tracking of outbound documents such as email, fax, and XML-based notifications. The package encapsulates the business logic that moves a fulfillment request from a simple request definition into an actionable job, routes that job to the correct delivery channel and server, and records the outcome in the fulfillment history tables. It is classified as a "Group" (GRP) API, meaning it exposes a broad collection of related public procedures rather than a single transactional interface, and it is referenced by approximately thirty other packages across the JTF, FND, and IBC schemas. The header comment (jtfgfmb.pls 120.11) indicates the file has been maintained since the early 11i release and remains functionally stable through 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twenty documented entry points spanning the full request lifecycle:

• START_REQUEST – creates and initializes a new fulfillment request record.
• SUBMIT_REQUEST, SUBMIT_PREVIEWED_REQUEST, SUBMIT_BATCH_REQUEST, and SUBMIT_MASS_REQUEST – enqueue requests for processing in single, preview, batch, or mass (high-volume) modes.
• RESUBMIT_REQUEST, RESUBMIT_JOB, and RESUBMIT_MALFORMED – re-drive requests or jobs that previously failed, stalled, or were rejected as malformed. RESUBMIT_JOB is the specific routine associated with the user's search term and is the re-entry point used to retry an existing job without rebuilding the request definition.
• CANCEL_REQUEST and NEW_CANCEL_REQUEST – withdraw a pending or active request.
• PAUSE_RESUME_REQUEST and NEW_PAUSE_RESUME_REQUEST – suspend and later continue in-flight processing.
• GET_CONTENT_XML and GET_MULTIPLE_CONTENT_XML – retrieve the rendered XML payload for one or many requests.
• SEND_REQUEST – performs the actual delivery handoff to the messaging transport.
• DETERMINE_REQUEST_PATH – resolves routing information such as the queue name based on server and request type.
• CORRECT_MALFORMED – repairs content that failed validation.
• REPLACE_TAG – a utility retained explicitly for backward compatibility (per Bug #1310227) that escapes XML metacharacters (&, <, >, ", ') and handles the FND miss-character sentinel.

Tables Accessed

The package reads and writes the Fulfillment Manager operational and audit tables, primarily through APPS synonyms:

• JTF_FM_REQUEST_CONTENTS and JTF_FM_REQUESTS_AQ – request body content and Advanced Queue staging.
• JTF_FM_INT_REQUEST_HEADER – the request header driving each job.
• JTF_FM_REQUEST_HISTORY_ALL and JTF_FM_REQUESTHISTID_S – immutable audit of request state transitions.
• JTF_FM_PROCESSED, JTF_FM_RESUBMITTED, and JTF_FM_CONTENT_FAILURES – tracking of completed, resubmitted, and failed items.
• JTF_FM_EMAIL_STATS and JTF_FM_QUERY_MES / JTF_FM_QUERIES_ALL – statistics and query lookups.
• JTF_AMV_ATTACHMENTS, IBC_CONTENT_ITEMS, and FND_LOBS/FND_LOBS_S – attachment and content-item resolution.

Usage Notes

JTF_FM_REQUEST_GRP is normally invoked indirectly. The Fulfillment Manager forms and the concurrent programs that schedule and dispatch fulfillment jobs call these procedures on the user's behalf; direct calls appear chiefly in custom extensions, workflow activities, and diagnostic scripts. Because it is a GRP-style API, no single transaction wraps the whole package — each procedure manages its own commit boundary and writes its own history rows. When troubleshooting, RESUBMIT_JOB is the recommended recovery path for a specific stuck job after correcting the underlying cause (for example via CORRECT_MALFORMED), whereas RESUBMIT_REQUEST rebuilds from the request definition.