Search Results validate_media_type

Overview

APPS.IEX_SEND_FFM_PVT is a private (PVT-classified) PL/SQL package body in the Oracle E-Business Suite Collections application. Its stated purpose is "Calling Fulfillment" — it coordinates the dispatch of customer-facing output (letters, dunning correspondence, statements) to the fulfillment channels defined for a collection transaction. The package body source header identifies the file as iexvffmb.pls (version 120.4) and records creation on 20-MAR-2001 by CLCHANG. Typical of IEX private APIs, it is not intended to be called directly by external consumers; it is a subordinate worker invoked by the public IEX collection packages, which manage the user-facing API contract, message list lifecycle, and transaction boundaries.

The naming convention (IEX_SEND_FFM_PVT) places it within the Collections (IEX) family of fulfillment-related modules, where it bridges collection content records to the delivery mechanisms — e-mail, printer, fax, and file path — that correspond to the media type configured against each recipient.

Key Procedures and Functions

• VALIDATE_MEDIA_TYPE — Validates the media type and associated delivery attributes for each row in a content table passed in by the caller. The procedure declares local variables for the media type, e-mail address, printer, fax number, and file path, then iterates over the incoming collection (a CONTENT_TBL_TYPE associative array) to confirm that the destination information required by each row's media type is present and consistent. It initializes the FND message list when requested, sets the API return status to success on entry, and writes diagnostic output through IEX_DUNNING_PVT.WRITELOG. On validation failure it signals the standard FND_API error return status and populates the message count and message data out parameters so the calling API can surface the error. This is the procedure surfaced by a search for "validate_media_type".
• SEND_FFM — Performs the fulfillment dispatch itself, taking validated content and routing it to the appropriate delivery channel. It is the action counterpart to VALIDATE_MEDIA_TYPE; the validation pass protects it from malformed destination data.

Neither procedure is documented with a published parameter list; callers should rely on the public IEX collection APIs rather than invoking these entry points directly.

Tables Accessed

The only table documented against this package through APPS synonyms is PLITBLM. In Oracle EBS this is the PL/SQL message table used to hold messages produced and consumed by FND_MSG_PUB within server-side APIs. Its presence confirms that the package participates in the standard FND message-list mechanism: errors and warnings raised during media type validation are stored in the message table and retrieved by the caller for display or logging, rather than being written to ad hoc output. No application data tables are documented as directly accessed, indicating that content is supplied entirely through the CONTENT_TBL_TYPE parameter and that any persistence of the fulfillment request is handled elsewhere in the collection call stack.

Usage Notes

This package is invoked internally by one other package (the documented referrer), which acts as its public entry point. It is not exposed to Oracle Forms or concurrent programs directly; no form or concurrent program short name is registered against it. In Oracle EBS 12.1.1 and 12.2.2, private collection packages of this type are called synchronously within the transaction of the public API, so any exception must be handled by the caller through the X_RETURN_STATUS / X_MSG_COUNT / X_MSG_DATA convention. Customizations should call the public IEX API and never reference IEX_SEND_FFM_PVT by name, since the private package is subject to change between patches and is not covered by Oracle's API compatibility guarantee.