SAP /FLDQ/PROCESS_BATCH_MATCH Function Module for handles the batch match process
/FLDQ/PROCESS_BATCH_MATCH is a standard /fldq/process batch match SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for handles the batch match process processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for /fldq/process batch match FM, simply by entering the name /FLDQ/PROCESS_BATCH_MATCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: /FLDQ/AD_RSADRINI
Program Name: /FLDQ/SAPLAD_RSADRINI
Main Program: /FLDQ/SAPLAD_RSADRINI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /FLDQ/PROCESS_BATCH_MATCH pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION '/FLDQ/PROCESS_BATCH_MATCH'"handles the batch match process.
EXPORTING
* IM_THRESH = "threshold value for batch match
* IM_RFCDEST = "Logical Destination (Specified in Function Call)
IM_CLEAN = "flag variable
IM_PKG_SIZE = "
IMPORTING
EX_ERROR_CODE = "batch id used by batch match
EX_RETURN_CODE = "batch id used by batch match
IMPORTING Parameters details for /FLDQ/PROCESS_BATCH_MATCH
IM_THRESH - threshold value for batch match
Data type: /FLDQ/AD_THRESHOLDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_RFCDEST - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_CLEAN - flag variable
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
IM_PKG_SIZE -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /FLDQ/PROCESS_BATCH_MATCH
EX_ERROR_CODE - batch id used by batch match
Data type: /FLDQ/AD_ERR_CODEOptional: No
Call by Reference: No ( called with pass by value option)
EX_RETURN_CODE - batch id used by batch match
Data type: /FLDQ/AD_ERR_CODEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /FLDQ/PROCESS_BATCH_MATCH Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_im_thresh | TYPE /FLDQ/AD_THRESHOLD, " | |||
| lv_ex_error_code | TYPE /FLDQ/AD_ERR_CODE, " | |||
| lv_im_rfcdest | TYPE RFCDEST, " | |||
| lv_ex_return_code | TYPE /FLDQ/AD_ERR_CODE, " | |||
| lv_im_clean | TYPE FLAG, " | |||
| lv_im_pkg_size | TYPE I. " |
|   CALL FUNCTION '/FLDQ/PROCESS_BATCH_MATCH' "handles the batch match process |
| EXPORTING | ||
| IM_THRESH | = lv_im_thresh | |
| IM_RFCDEST | = lv_im_rfcdest | |
| IM_CLEAN | = lv_im_clean | |
| IM_PKG_SIZE | = lv_im_pkg_size | |
| IMPORTING | ||
| EX_ERROR_CODE | = lv_ex_error_code | |
| EX_RETURN_CODE | = lv_ex_return_code | |
| . " /FLDQ/PROCESS_BATCH_MATCH | ||
ABAP code using 7.40 inline data declarations to call FM /FLDQ/PROCESS_BATCH_MATCH
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects