SAP FM_UPDATE_VALID_COLLECT_EFDATA Function Module for Collect data from table EFDATA
FM_UPDATE_VALID_COLLECT_EFDATA is a standard fm update valid collect efdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Collect data from table EFDATA 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 update valid collect efdata FM, simply by entering the name FM_UPDATE_VALID_COLLECT_EFDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM_UPDATE_VALIDATION
Program Name: SAPLFM_UPDATE_VALIDATION
Main Program: SAPLFM_UPDATE_VALIDATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_UPDATE_VALID_COLLECT_EFDATA 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_UPDATE_VALID_COLLECT_EFDATA'"Collect data from table EFDATA.
EXPORTING
IV_ORGVG = "Business Transaction
IT_EFDATA = "Earmarked Fund Data for Commitment Interface
IMPORTING Parameters details for FM_UPDATE_VALID_COLLECT_EFDATA
IV_ORGVG - Business Transaction
Data type: COBK-ORGVGOptional: No
Call by Reference: Yes
IT_EFDATA - Earmarked Fund Data for Commitment Interface
Data type: FMEF_OIDATA_TTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_UPDATE_VALID_COLLECT_EFDATA 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_iv_orgvg | TYPE COBK-ORGVG, " | |||
| lv_it_efdata | TYPE FMEF_OIDATA_TT. " |
|   CALL FUNCTION 'FM_UPDATE_VALID_COLLECT_EFDATA' "Collect data from table EFDATA |
| EXPORTING | ||
| IV_ORGVG | = lv_iv_orgvg | |
| IT_EFDATA | = lv_it_efdata | |
| . " FM_UPDATE_VALID_COLLECT_EFDATA | ||
ABAP code using 7.40 inline data declarations to call FM FM_UPDATE_VALID_COLLECT_EFDATA
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.| "SELECT single ORGVG FROM COBK INTO @DATA(ld_iv_orgvg). | ||||
Search for further information about these or an SAP related objects