SAP EXIT_RFEBBE00_001 Function Module for User Exit Conversion Program (CODA (Belgium) -> Multicash)
EXIT_RFEBBE00_001 is a standard exit rfebbe00 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Exit Conversion Program (CODA (Belgium) -> Multicash) 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 exit rfebbe00 001 FM, simply by entering the name EXIT_RFEBBE00_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XF01
Program Name: SAPLXF01
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_RFEBBE00_001 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 'EXIT_RFEBBE00_001'"User Exit Conversion Program (CODA (Belgium) -> Multicash).
EXPORTING
I_NBVWZ = "Maximum Amount of Reference Data
I_C1 = "CODA Record 1 (Bank ID and Statement Number)
I_AGKTO = "Customer/Vendor Bank Account
I_AGBNK = "Customer/Vendor Bank Key
IMPORTING
E_AGKTO = "Customer/Vendor Bank Account
E_AGBNK = "Customer/Vendor Bank Key
TABLES
T_C21 = "Clearing Data for Line Item
T_C22 = "Note to Payee Reference Records for Line Item
T_C23 = "
T_C31 = "
T_C32 = "
T_C33 = "
T_C4 = "
T_VWZ = "
IMPORTING Parameters details for EXIT_RFEBBE00_001
I_NBVWZ - Maximum Amount of Reference Data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_C1 - CODA Record 1 (Bank ID and Statement Number)
Data type: FBEC_10_EBOptional: No
Call by Reference: No ( called with pass by value option)
I_AGKTO - Customer/Vendor Bank Account
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_AGBNK - Customer/Vendor Bank Key
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_RFEBBE00_001
E_AGKTO - Customer/Vendor Bank Account
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_AGBNK - Customer/Vendor Bank Key
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_RFEBBE00_001
T_C21 - Clearing Data for Line Item
Data type: FBEC_21_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C22 - Note to Payee Reference Records for Line Item
Data type: FBEC_22_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C23 -
Data type: FBEC_23_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C31 -
Data type: FBEC_31_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C32 -
Data type: FBEC_32_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C33 -
Data type: FBEC_33_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_C4 -
Data type: FBEC_40_EBOptional: No
Call by Reference: No ( called with pass by value option)
T_VWZ -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_RFEBBE00_001 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_t_c21 | TYPE STANDARD TABLE OF FBEC_21_EB, " | |||
| lv_e_agkto | TYPE FBEC_21_EB, " | |||
| lv_i_nbvwz | TYPE FBEC_21_EB, " | |||
| lv_i_c1 | TYPE FBEC_10_EB, " | |||
| lt_t_c22 | TYPE STANDARD TABLE OF FBEC_22_EB, " | |||
| lv_e_agbnk | TYPE FBEC_22_EB, " | |||
| lt_t_c23 | TYPE STANDARD TABLE OF FBEC_23_EB, " | |||
| lv_i_agkto | TYPE FBEC_23_EB, " | |||
| lt_t_c31 | TYPE STANDARD TABLE OF FBEC_31_EB, " | |||
| lv_i_agbnk | TYPE FBEC_31_EB, " | |||
| lt_t_c32 | TYPE STANDARD TABLE OF FBEC_32_EB, " | |||
| lt_t_c33 | TYPE STANDARD TABLE OF FBEC_33_EB, " | |||
| lt_t_c4 | TYPE STANDARD TABLE OF FBEC_40_EB, " | |||
| lt_t_vwz | TYPE STANDARD TABLE OF FBEC_40_EB. " |
|   CALL FUNCTION 'EXIT_RFEBBE00_001' "User Exit Conversion Program (CODA (Belgium) -> Multicash) |
| EXPORTING | ||
| I_NBVWZ | = lv_i_nbvwz | |
| I_C1 | = lv_i_c1 | |
| I_AGKTO | = lv_i_agkto | |
| I_AGBNK | = lv_i_agbnk | |
| IMPORTING | ||
| E_AGKTO | = lv_e_agkto | |
| E_AGBNK | = lv_e_agbnk | |
| TABLES | ||
| T_C21 | = lt_t_c21 | |
| T_C22 | = lt_t_c22 | |
| T_C23 | = lt_t_c23 | |
| T_C31 | = lt_t_c31 | |
| T_C32 | = lt_t_c32 | |
| T_C33 | = lt_t_c33 | |
| T_C4 | = lt_t_c4 | |
| T_VWZ | = lt_t_vwz | |
| . " EXIT_RFEBBE00_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_RFEBBE00_001
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