Search Results submit_ffm_request

Overview

ASO_FFM_INT is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified in the ETRM as an OTHER (non-public) API. Its name indicates its role as an integration layer between Oracle Order Management / Oracle Advanced Pricing and the external "FFM" subsystem, which in EBS terminology corresponds to the fulfillment or freight/flexible-message processing service invoked through the JTF_FM_REQUEST_GRP dependency. In EBS 12.1.1 and 12.2.2, the package acts as a thin wrapper that assembles request parameters on behalf of calling modules and delegates the actual submission to the FFM request group, using the standard Oracle Application Object Library (AOL) messaging and API infrastructure.

The package is a supporting, internal component rather than a user-facing API. It relies on FND_API for the standard return-status convention, FND_MESSAGE and FND_MSG_PUB for message stack handling, and ASO_UTILITY_PVT for shared Order Capture utility logic. It is not referenced by any other database object, confirming its role as a leaf-level integration utility invoked directly by form logic or concurrent code.

Key Procedures and Functions

The ETRM documents a single entry point for this package body:

• SUBMIT_FFM_REQUEST — The sole documented procedure. It initiates an outbound FFM request by packaging the caller-supplied context and forwarding it to the FFM request mechanism represented by the JTF_FM_REQUEST_GRP dependency. The procedure returns its outcome through the conventional FND_API x_return_status, x_msg_count and x_msg_data parameters; message text is populated through FND_MSG_PUB and FND_MESSAGE. No parameter list is reproduced here, as the ETRM does not expose formal argument signatures.

Because only one procedure is documented, the package body should be understood as a narrowly scoped integration helper rather than a broad utility library. Any private helper routines present in the body are implementation details and are not part of the documented interface.

Tables Accessed

The documented table reference is PLITBLM, accessed through an APPS synonym. PLITBLM is the standard Oracle PL/SQL table used to hold VARCHAR2 values for the FND message stack and is typically populated when FND_MSG_PUB stores messages for later retrieval. Its presence in this package confirms that ASO_FFM_INT writes diagnostic or error messages into the AOL message stack rather than maintaining its own persistent logging table.

No application data tables (for example, order headers, lines, or pricing qualifiers) are documented as directly accessed by this package. Persistence of the actual FFM request and its results is therefore assumed to occur inside the downstream FFM service, not within ASO_FFM_INT itself.

Usage Notes

ASO_FFM_INT is an internal, non-public API. It is not intended to be called from customer extensions, and Oracle does not guarantee its signature across releases. Typical invocation paths in EBS 12.1.1 and 12.2.2 are:

• Internal Order Management or Oracle Advanced Pricing form handlers that need to dispatch an FFM request as part of order or quote processing.
• Concurrent program logic that batches request submission, using the FND_API return-status convention to detect failures and surface messages to the concurrent request log.
• Other Oracle-owned ASO packages; however, the ETRM records that ASO_FFM_INT is not referenced by any database object, so callers must be application-tier code rather than further PL/SQL wrappers.

Because the package depends on ASO_UTILITY_PVT and JTF_FM_REQUEST_GRP, it requires that Order Capture and the FFM request infrastructure are correctly installed and that the executing session has the required FND message-stack context. Developers troubleshooting FFM submission issues should inspect FND_MSG_PUB output and the concurrent request log rather than expecting a dedicated ASO_FFM_INT log table.