Search Results fem_mp_process_args_t

Overview

FEM_MULTI_PROC_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Enterprise Tax, Risk, and Management (ETRM) / Enterprise Performance Foundation product family, which supplies the underlying infrastructure for Enterprise Planning and Budgeting, Profitability Manager, and related applications. The package provides the parallel-processing orchestration framework used by FEM engines. Its central responsibility is to decompose a large analytical workload into data slices, launch one or more concurrent sub-requests to process those slices in parallel, and consolidate status and error messages back into the parent request. The package is classified as OTHER in the ETRM registry, indicating it is an internal infrastructure component rather than a published open interface, but it is actively referenced by eleven other packages and is therefore central to the runtime behavior of FEM engine execution.

Key Procedures and Functions

• MASTER — the controlling entry point. It initializes an engine run, resolves the object catalog and process options, derives the data slice definition, and drives the overall multi-process lifecycle, including submission of the parallel sub-requests and final consolidation.
• SUB_REQUEST — the worker entry point executed by each spawned concurrent request. It processes the data slice assigned to that request and reports results back to the master execution.
• GET_DATA_SLICE — retrieves or materializes the data slice assigned to a given worker, drawing from the slice definition stored in the multi-process metadata tables.
• POST_DATA_SLICE — persists slice-level results or status after a worker completes its portion of the workload.
• POST_SUBREQ_MESSAGES — consolidates log and message output raised by sub-requests, routing them through FND_MSG_PUB and FND_LOG so they appear on the parent concurrent request log.
• DELETE_DATA_SLICES — performs cleanup of slice rows after a run completes or is terminated, preventing stale partitioning metadata from affecting subsequent executions.

The package additionally depends internally on FEM_ENGINES_PKG for engine-level control flow and invokes dynamic PL/SQL via DBMS_DESCRIBE, DBMS_UTILITY, and DBMS_SESSION to resolve and execute the configured step method for each slice.

Tables Accessed

The package reads and writes the FEM multi-process metadata tables. FEM_MP_DATA_SLICES and FEM_MP_DATA_SLICE_COLS hold the slice definitions and the column-level partitioning rules that determine how work is divided. FEM_MP_OBJ_STEP_METHODS stores the PL/SQL entry point associated with each engine step, while FEM_MP_PROCESS_ARGS_T and FEM_MP_PROCESS_CTL_T are collection-like structures used to pass runtime arguments and control flags. FEM_MP_PROCESS_OPTIONS holds tuning parameters such as degree of parallelism. FEM_OBJECT_CATALOG_B identifies the FEM objects participating in the run. Concurrent processing integration relies on FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS, with FND_REQUEST, FND_GLOBAL, and FND_CONCURRENT supplying submission and context APIs. Dictionary views ALL_TAB_COLUMNS and USER_SYNONYMS, plus PLITBLM, support dynamic SQL generation and argument parsing.

Usage Notes

FEM_MULTI_PROC_PKG is not intended for direct invocation by end users or custom extensions. It is called by the FEM engine framework—primarily through FEM_ENGINES_PKG—when a process is configured to run in parallel. The fem_mp_process_args_t type that prompted the search is the argument structure passed into the master and sub-request processing path, and it should be treated as an internal contract that may change without notice. Because the package submits and monitors concurrent requests, invocation normally occurs from a concurrent program context. Customizations should avoid calling these procedures directly; instead, configure parallelism through the standard FEM engine and process option setups. Any diagnostic work involving this package should focus on the concurrent request log, since POST_SUBREQ_MESSAGES consolidates worker output there.