SAP FDM_COLL_INTERFACE_00001025 Function Module for
FDM_COLL_INTERFACE_00001025 is a standard fdm coll interface 00001025 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 fdm coll interface 00001025 FM, simply by entering the name FDM_COLL_INTERFACE_00001025 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDM_COLL_BTE01
Program Name: SAPLFDM_COLL_BTE01
Main Program: SAPLFDM_COLL_BTE01
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FDM_COLL_INTERFACE_00001025 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 'FDM_COLL_INTERFACE_00001025'".
EXPORTING
* I_BKDF = "Recurring entry data
TABLES
* T_AUSZ1 = "Items to Be Cleared
* T_BSEU = "
* T_RSGTAB = "Complete Table of Residual Items with Reasons
* T_RENUM = "Temporary and Final Posting Item Number for FI Document
* T_POSTAB = "Open Item Data for Clearing Transactions
* T_AUSZ2 = "
* T_AUSZ3 = "Clearing Information
T_BKP1 = "
T_BKPF = "Document Headers
T_BSEC = "One-Time Account Data
T_BSED = "Bill of Exchange Data
T_BSEG = "Document Line Items
T_BSET = "Tax Data
IMPORTING Parameters details for FDM_COLL_INTERFACE_00001025
I_BKDF - Recurring entry data
Data type: BKDFOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FDM_COLL_INTERFACE_00001025
T_AUSZ1 - Items to Be Cleared
Data type: AUSZ1Optional: Yes
Call by Reference: No ( called with pass by value option)
T_BSEU -
Data type: BSEUOptional: Yes
Call by Reference: No ( called with pass by value option)
T_RSGTAB - Complete Table of Residual Items with Reasons
Data type: IRSGTABOptional: Yes
Call by Reference: Yes
T_RENUM - Temporary and Final Posting Item Number for FI Document
Data type: IRENUMOptional: Yes
Call by Reference: Yes
T_POSTAB - Open Item Data for Clearing Transactions
Data type: AUSZ_INFOOptional: Yes
Call by Reference: Yes
T_AUSZ2 -
Data type: AUSZ2Optional: Yes
Call by Reference: No ( called with pass by value option)
T_AUSZ3 - Clearing Information
Data type: AUSZ_CLROptional: Yes
Call by Reference: No ( called with pass by value option)
T_BKP1 -
Data type: BKP1Optional: No
Call by Reference: No ( called with pass by value option)
T_BKPF - Document Headers
Data type: BKPFOptional: No
Call by Reference: No ( called with pass by value option)
T_BSEC - One-Time Account Data
Data type: BSECOptional: No
Call by Reference: No ( called with pass by value option)
T_BSED - Bill of Exchange Data
Data type: BSEDOptional: No
Call by Reference: No ( called with pass by value option)
T_BSEG - Document Line Items
Data type: BSEGOptional: No
Call by Reference: No ( called with pass by value option)
T_BSET - Tax Data
Data type: BSETOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FDM_COLL_INTERFACE_00001025 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_bkdf | TYPE BKDF, " | |||
| lt_t_ausz1 | TYPE STANDARD TABLE OF AUSZ1, " | |||
| lt_t_bseu | TYPE STANDARD TABLE OF BSEU, " | |||
| lt_t_rsgtab | TYPE STANDARD TABLE OF IRSGTAB, " | |||
| lt_t_renum | TYPE STANDARD TABLE OF IRENUM, " | |||
| lt_t_postab | TYPE STANDARD TABLE OF AUSZ_INFO, " | |||
| lt_t_ausz2 | TYPE STANDARD TABLE OF AUSZ2, " | |||
| lt_t_ausz3 | TYPE STANDARD TABLE OF AUSZ_CLR, " | |||
| lt_t_bkp1 | TYPE STANDARD TABLE OF BKP1, " | |||
| lt_t_bkpf | TYPE STANDARD TABLE OF BKPF, " | |||
| lt_t_bsec | TYPE STANDARD TABLE OF BSEC, " | |||
| lt_t_bsed | TYPE STANDARD TABLE OF BSED, " | |||
| lt_t_bseg | TYPE STANDARD TABLE OF BSEG, " | |||
| lt_t_bset | TYPE STANDARD TABLE OF BSET. " |
|   CALL FUNCTION 'FDM_COLL_INTERFACE_00001025' " |
| EXPORTING | ||
| I_BKDF | = lv_i_bkdf | |
| TABLES | ||
| T_AUSZ1 | = lt_t_ausz1 | |
| T_BSEU | = lt_t_bseu | |
| T_RSGTAB | = lt_t_rsgtab | |
| T_RENUM | = lt_t_renum | |
| T_POSTAB | = lt_t_postab | |
| T_AUSZ2 | = lt_t_ausz2 | |
| T_AUSZ3 | = lt_t_ausz3 | |
| T_BKP1 | = lt_t_bkp1 | |
| T_BKPF | = lt_t_bkpf | |
| T_BSEC | = lt_t_bsec | |
| T_BSED | = lt_t_bsed | |
| T_BSEG | = lt_t_bseg | |
| T_BSET | = lt_t_bset | |
| . " FDM_COLL_INTERFACE_00001025 | ||
ABAP code using 7.40 inline data declarations to call FM FDM_COLL_INTERFACE_00001025
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