SAP FMEUF_PREPARE_CORRECTION Function Module for Certification run. correction
FMEUF_PREPARE_CORRECTION is a standard fmeuf prepare correction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Certification run. correction 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 fmeuf prepare correction FM, simply by entering the name FMEUF_PREPARE_CORRECTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMEUF_CERTIFICATION_RUN
Program Name: SAPLFMEUF_CERTIFICATION_RUN
Main Program: SAPLFMEUF_CERTIFICATION_RUN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMEUF_PREPARE_CORRECTION 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 'FMEUF_PREPARE_CORRECTION'"Certification run. correction.
EXPORTING
IT_FMEUF_DOC = "Table with Header Fields from BKPF
I_PAYDT_FROM = "Payment date (from)
I_PAYDT_TO = "Payment date (to)
I_RT_OPERA = "Range Table type for Operation
I_CURR = "Currency Key
I_CRTPR = "Certification Procedure
I_PHASE = "Certification Phase
I_TAX_HAND = "Tax Handling Type
I_RT_BUKRS = "Range Table type for Company Code
IMPORTING
ET_CORRECTION_LIST = "Table Type for Processing the Certification Run
ET_REVERSED_DOCS = "List of reversed documents
CHANGING
CT_ITEMS_TO_BE_CORRECTED = "Table Type for Processing the Certification Run
CT_MSG = "Table for messages
EXCEPTIONS
CUSTOMIZING_NOT_MAINTAINED = 1
IMPORTING Parameters details for FMEUF_PREPARE_CORRECTION
IT_FMEUF_DOC - Table with Header Fields from BKPF
Data type: FMEUF_T_BKPFOptional: No
Call by Reference: Yes
I_PAYDT_FROM - Payment date (from)
Data type: DATUMOptional: No
Call by Reference: Yes
I_PAYDT_TO - Payment date (to)
Data type: DATUMOptional: No
Call by Reference: Yes
I_RT_OPERA - Range Table type for Operation
Data type: FMEUF_RT_OPERAOptional: No
Call by Reference: Yes
I_CURR - Currency Key
Data type: WAERSOptional: No
Call by Reference: Yes
I_CRTPR - Certification Procedure
Data type: FMEUF_CRTPROptional: No
Call by Reference: Yes
I_PHASE - Certification Phase
Data type: FMEUF_PHASEOptional: No
Call by Reference: Yes
I_TAX_HAND - Tax Handling Type
Data type: FMEUF_TAX_HANDOptional: No
Call by Reference: Yes
I_RT_BUKRS - Range Table type for Company Code
Data type: FMEUF_RT_BUKRSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FMEUF_PREPARE_CORRECTION
ET_CORRECTION_LIST - Table Type for Processing the Certification Run
Data type: FMEUF_T_FMEUF_EXP_RUNOptional: No
Call by Reference: Yes
ET_REVERSED_DOCS - List of reversed documents
Data type: FMEUF_T_AWITEMKEYOptional: No
Call by Reference: Yes
CHANGING Parameters details for FMEUF_PREPARE_CORRECTION
CT_ITEMS_TO_BE_CORRECTED - Table Type for Processing the Certification Run
Data type: FMEUF_T_FMEUFEXPOptional: No
Call by Reference: Yes
CT_MSG - Table for messages
Data type: FMEUF_T_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
CUSTOMIZING_NOT_MAINTAINED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMEUF_PREPARE_CORRECTION 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_it_fmeuf_doc | TYPE FMEUF_T_BKPF, " | |||
| lv_et_correction_list | TYPE FMEUF_T_FMEUF_EXP_RUN, " | |||
| lv_ct_items_to_be_corrected | TYPE FMEUF_T_FMEUFEXP, " | |||
| lv_customizing_not_maintained | TYPE FMEUF_T_FMEUFEXP, " | |||
| lv_ct_msg | TYPE FMEUF_T_MSG, " | |||
| lv_i_paydt_from | TYPE DATUM, " | |||
| lv_et_reversed_docs | TYPE FMEUF_T_AWITEMKEY, " | |||
| lv_i_paydt_to | TYPE DATUM, " | |||
| lv_i_rt_opera | TYPE FMEUF_RT_OPERA, " | |||
| lv_i_curr | TYPE WAERS, " | |||
| lv_i_crtpr | TYPE FMEUF_CRTPR, " | |||
| lv_i_phase | TYPE FMEUF_PHASE, " | |||
| lv_i_tax_hand | TYPE FMEUF_TAX_HAND, " | |||
| lv_i_rt_bukrs | TYPE FMEUF_RT_BUKRS. " |
|   CALL FUNCTION 'FMEUF_PREPARE_CORRECTION' "Certification run. correction |
| EXPORTING | ||
| IT_FMEUF_DOC | = lv_it_fmeuf_doc | |
| I_PAYDT_FROM | = lv_i_paydt_from | |
| I_PAYDT_TO | = lv_i_paydt_to | |
| I_RT_OPERA | = lv_i_rt_opera | |
| I_CURR | = lv_i_curr | |
| I_CRTPR | = lv_i_crtpr | |
| I_PHASE | = lv_i_phase | |
| I_TAX_HAND | = lv_i_tax_hand | |
| I_RT_BUKRS | = lv_i_rt_bukrs | |
| IMPORTING | ||
| ET_CORRECTION_LIST | = lv_et_correction_list | |
| ET_REVERSED_DOCS | = lv_et_reversed_docs | |
| CHANGING | ||
| CT_ITEMS_TO_BE_CORRECTED | = lv_ct_items_to_be_corrected | |
| CT_MSG | = lv_ct_msg | |
| EXCEPTIONS | ||
| CUSTOMIZING_NOT_MAINTAINED = 1 | ||
| . " FMEUF_PREPARE_CORRECTION | ||
ABAP code using 7.40 inline data declarations to call FM FMEUF_PREPARE_CORRECTION
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