Results for “submit_ffm_request”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ASO_FFM_INT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Application Object Library infrastructure supporting Oracle Order Management and its related fulfillment integrations. The package name associates it with the ASO product family (Order Capture and Order Management) and the "FFM" prefix, which in EBS commonly denotes "Flexfields Mapping" or fulfillment-related integration logic. In practice, ASO_FFM_INT provides the server-side integration layer used to submit and coordinate fulfillment requests generated from Oracle Order Management into downstream fulfillment systems.
As a foundational integration package, ASO_FFM_INT is designed to be invoked from other ASO-level packages rather than directly from the user interface. The ETRM metadata classifies it as a valid object with an API classification of "OTHER," indicating it is a supporting utility package rather than a standalone public API. It depends on the standard Oracle Application Framework utilities, including FND_API for standard API return status handling and SYS.STANDARD for core PL/SQL constructs.
Key Procedures and Functions
The documented interface exposes one procedure:
- SUBMIT_FFM_REQUEST — This is the primary entry point of the package. Its purpose is to submit a fulfillment request from within Oracle Order Management to the fulfillment integration layer. It encapsulates the logic required to initiate the request, likely including validation of the calling context, assembly of request parameters, and invocation of the downstream request submission mechanism. Because no parameter list is documented in the ETRM metadata, consumers should reference the actual package specification in the APPS schema for the authoritative signature.
Given the package's integration role, SUBMIT_FFM_REQUEST typically returns a standard FND_API.G_RET_STS status and may populate error/exception structures when the request cannot be submitted. The presence of FND_API as a dependency confirms that the package follows Oracle's standard API error-handling conventions rather than raising unhandled exceptions to the caller.
Tables Accessed
The documented table reference for ASO_FFM_INT is:
- PLITBLM — accessed via an APPS synonym. PLITBLM is a standard Oracle EBS temporary/collection-style table used to pass tabular data between PL/SQL program units. In the context of fulfillment request submission, ASO_FFM_INT uses this table to buffer the set of records that constitute the fulfillment request before the request is submitted to the target system. This pattern allows the package to assemble multi-row data without relying on persistent business tables, keeping the integration transient and reducing contention on core Order Management tables.
No other persistent tables are documented as being referenced through APPS synonyms, which reinforces that ASO_FFM_INT acts as a thin integration shim rather than a data-maintenance package.
Usage Notes
ASO_FFM_INT is not intended to be called directly from Oracle Forms or concurrent programs. The ETRM dependency information shows it is referenced by ASO_FFM_INT itself and by ASO_ORDER_INT, confirming that it is consumed internally by the broader Order Management integration stack. ASO_ORDER_INT is the higher-level orchestration package that drives order integration flows, and it delegates fulfillment request submission to ASO_FFM_INT.SUBMIT_FFM_REQUEST.
Typical invocation therefore occurs when an order is processed and the fulfillment integration must be triggered — for example, during order booking, order release to fulfillment, or an associated workflow. Customizations that need to submit a fulfillment request programmatically should call the parent ASO_ORDER_INT routine where one exists, or invoke ASO_FFM_INT.SUBMIT_FFM_REQUEST only after confirming the required context has been established. As with all ASO packages, any custom call should include standard FND_API exception handling and should be validated against the target release (12.1.1 or 12.2.2) because signatures may differ between versions. Because ETRM documents only a single procedure and a single table, developers must inspect the live package specification in the APPS schema for the complete interface before building dependencies on it.
-
PACKAGE: APPS.ASO_FFM_INT 12.2.2
-
PACKAGE: APPS.ASO_FFM_INT 12.1.1
-
PACKAGE: APPS.ASO_FFM_INT 12.1.1
-
PACKAGE: APPS.ASO_FFM_INT 12.2.2