SAP FEB_GET_FOR_POST_PROCESSING Function Module for
FEB_GET_FOR_POST_PROCESSING is a standard feb get for post processing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 feb get for post processing FM, simply by entering the name FEB_GET_FOR_POST_PROCESSING into the relevant SAP transaction such as SE37 or SE38.
Function Group: NEW_FEBA
Program Name: SAPLNEW_FEBA
Main Program: SAPLNEW_FEBA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FEB_GET_FOR_POST_PROCESSING 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 'FEB_GET_FOR_POST_PROCESSING'".
EXPORTING
* IV_NEW_SELECTION = "
IMPORTING
EV_SINGLE_LINE = "
TABLES
ET_BS = "
ET_BS_ITEM = "
IMPORTING Parameters details for FEB_GET_FOR_POST_PROCESSING
IV_NEW_SELECTION -
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FEB_GET_FOR_POST_PROCESSING
EV_SINGLE_LINE -
Data type: BOOLE_DOptional: No
Call by Reference: Yes
TABLES Parameters details for FEB_GET_FOR_POST_PROCESSING
ET_BS -
Data type: FEBKOOptional: No
Call by Reference: Yes
ET_BS_ITEM -
Data type: FEBEPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FEB_GET_FOR_POST_PROCESSING 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: | ||||
| lt_et_bs | TYPE STANDARD TABLE OF FEBKO, " | |||
| lv_ev_single_line | TYPE BOOLE_D, " | |||
| lv_iv_new_selection | TYPE BOOLE_D, " | |||
| lt_et_bs_item | TYPE STANDARD TABLE OF FEBEP. " |
|   CALL FUNCTION 'FEB_GET_FOR_POST_PROCESSING' " |
| EXPORTING | ||
| IV_NEW_SELECTION | = lv_iv_new_selection | |
| IMPORTING | ||
| EV_SINGLE_LINE | = lv_ev_single_line | |
| TABLES | ||
| ET_BS | = lt_et_bs | |
| ET_BS_ITEM | = lt_et_bs_item | |
| . " FEB_GET_FOR_POST_PROCESSING | ||
ABAP code using 7.40 inline data declarations to call FM FEB_GET_FOR_POST_PROCESSING
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