Search Results iex_send_ffm_pvt




Overview
Explore in AI Chat

Overview

IEX_SEND_FFM_PVT is a private PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Advanced Collections (IEX) module. The name reflects its purpose: it handles the sending of "FFM" communication, where FFM corresponds to the Fulfillment and Follow-up Messaging facility used to deliver collection-related correspondence such as dunning letters and other customer communications generated by the Collections work queue. The package is classified as a private (PVT) API, meaning it is intended for internal consumption by other EBS collection components rather than as a public interface exposed to external integrations or customer extensions.

The package sits within the messaging layer that bridges the Collections module and the Oracle Workflow notification infrastructure. When a collections agent or a scheduled process determines that a customer communication must be dispatched, the calling code invokes this package to validate the message format and hand the request to the underlying messaging group for actual transmission. Because it is a private package, its procedures are subject to change between releases and should not be called directly by custom code.

Key Procedures and Functions

Two procedures and functions are documented in the package metadata:

  • VALIDATE_MEDIA_TYPE — This program unit validates the media or delivery type associated with an outgoing message before transmission. It ensures that the requested communication medium (for example, the delivery channel configured for a dunning letter or follow-up message) is supported and correctly specified, thereby preventing invalid or unsupported transmission requests from reaching the messaging infrastructure.
  • SEND_FFM — This is the principal worker routine of the package. It assembles and submits the fulfillment and follow-up message for delivery through the Oracle Workflow / fulfillment messaging request group, passing the required request metadata so that the message is queued and dispatched to the recipient. It is the entry point through which the Dunning component initiates outbound customer communications.

These two units form a validate-then-send pattern: media type validation is performed first to guarantee a legitimate delivery channel, and the send routine performs the actual submission to the messaging framework.

Tables Accessed

According to the documented dependency metadata, the package references the table PLITBLM through an APPS synonym. PLITBLM is a standard EBS persistent structure used in conjunction with the fulfillment messaging infrastructure and typically stores or stages the message content and its associated delivery attributes. The package uses this table to persist message data required by the FFM request group before the message is submitted for transmission. In addition to this table dependency, the package does not itself define database structures; it operates on data prepared by higher-level collections processes.

Usage Notes

IEX_SEND_FFM_PVT is not a public API and should not be invoked directly from customer-written code. It is called internally by IEX_DUNNING_PVT, the dunning engine within Advanced Collections, and is also referenced by itself through internal package-body dependencies.

Its runtime dependency on JTF_FM_REQUEST_GRP indicates that message submission is delegated to the shared Oracle Fulfillment Management request group, which manages the queuing and delivery of workflow-based correspondence. Consequently, the package is exercised whenever a dunning letter or similar collection communication is generated and dispatched, most commonly during execution of the dunning concurrent program or when a collections agent releases a correspondence item from the work queue.

Because the API classification is PVT and status is VALID in ETRM, the package is maintained and supported by Oracle as part of the standard product. Custom solutions requiring similar outbound communication should use the supported public APIs, such as those in the collections and workflow interface layers, rather than calling this private package directly.