SAP FM_BL_CORRECTION_POST Function Module for Post correction to previous BL entries
FM_BL_CORRECTION_POST is a standard fm bl correction post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Post correction to previous BL entries 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 fm bl correction post FM, simply by entering the name FM_BL_CORRECTION_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_BLCORRECT
Program Name: SAPLFMFG_BLCORRECT
Main Program: SAPLFMFG_BLCORRECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_BL_CORRECTION_POST 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 'FM_BL_CORRECTION_POST'"Post correction to previous BL entries.
EXPORTING
I_LOT = "Budgetary Ledger Correction Lot Identifier
* I_INTERACTIVE = ' ' "Interactive mode: TRUE (='X') and FALSE (=' ')
I_T_ITEMS = "Table of data for Budgetary Ledger Correction
* I_PRM_D_ORIG = ' ' "Use original BUDAT etc: TRUE (='X') and FALSE (=' ')
* I_PRM_D_SPEC = "Use specified BUDAT etc: TRUE (='X') and FALSE (=' ')
* I_PRM_P_BLDT = "The specified Document Date in Document
* I_PRM_P_BUDT = "The specified Posting Date in the Document
* I_PRM_P_YEAR = "The specified Fiscal Year
* I_PRM_P_PERIOD = "The specified Fiscal Period
* I_TEST = 'X' "Test mode: TRUE (='X') and FALSE (=' ')
IMPORTING
E_T_RESULTS = "Table of processing results for BL correction/Results per lot
IMPORTING Parameters details for FM_BL_CORRECTION_POST
I_LOT - Budgetary Ledger Correction Lot Identifier
Data type: FMFG_CORR_LOTOptional: No
Call by Reference: No ( called with pass by value option)
I_INTERACTIVE - Interactive mode: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T_ITEMS - Table of data for Budgetary Ledger Correction
Data type: TFMFG_BLCORR_FIELDSOptional: No
Call by Reference: Yes
I_PRM_D_ORIG - Use original BUDAT etc: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PRM_D_SPEC - Use specified BUDAT etc: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PRM_P_BLDT - The specified Document Date in Document
Data type: BLDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PRM_P_BUDT - The specified Posting Date in the Document
Data type: BUDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PRM_P_YEAR - The specified Fiscal Year
Data type: GJAHROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PRM_P_PERIOD - The specified Fiscal Period
Data type: MONATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TEST - Test mode: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FM_BL_CORRECTION_POST
E_T_RESULTS - Table of processing results for BL correction/Results per lot
Data type: TFMFG_BLCORR_OUTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_BL_CORRECTION_POST 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_i_lot | TYPE FMFG_CORR_LOT, " | |||
| lv_e_t_results | TYPE TFMFG_BLCORR_OUT, " | |||
| lv_i_interactive | TYPE BOOLE_D, " SPACE | |||
| lv_i_t_items | TYPE TFMFG_BLCORR_FIELDS, " | |||
| lv_i_prm_d_orig | TYPE BOOLE_D, " SPACE | |||
| lv_i_prm_d_spec | TYPE BOOLE_D, " | |||
| lv_i_prm_p_bldt | TYPE BLDAT, " | |||
| lv_i_prm_p_budt | TYPE BUDAT, " | |||
| lv_i_prm_p_year | TYPE GJAHR, " | |||
| lv_i_prm_p_period | TYPE MONAT, " | |||
| lv_i_test | TYPE BOOLE_D. " 'X' |
|   CALL FUNCTION 'FM_BL_CORRECTION_POST' "Post correction to previous BL entries |
| EXPORTING | ||
| I_LOT | = lv_i_lot | |
| I_INTERACTIVE | = lv_i_interactive | |
| I_T_ITEMS | = lv_i_t_items | |
| I_PRM_D_ORIG | = lv_i_prm_d_orig | |
| I_PRM_D_SPEC | = lv_i_prm_d_spec | |
| I_PRM_P_BLDT | = lv_i_prm_p_bldt | |
| I_PRM_P_BUDT | = lv_i_prm_p_budt | |
| I_PRM_P_YEAR | = lv_i_prm_p_year | |
| I_PRM_P_PERIOD | = lv_i_prm_p_period | |
| I_TEST | = lv_i_test | |
| IMPORTING | ||
| E_T_RESULTS | = lv_e_t_results | |
| . " FM_BL_CORRECTION_POST | ||
ABAP code using 7.40 inline data declarations to call FM FM_BL_CORRECTION_POST
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.| DATA(ld_i_interactive) | = ' '. | |||
| DATA(ld_i_prm_d_orig) | = ' '. | |||
| DATA(ld_i_test) | = 'X'. | |||
Search for further information about these or an SAP related objects