SAP DAP_FGDT_UPDATE Function Module for Database Insert in Update Task
DAP_FGDT_UPDATE is a standard dap fgdt update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Database Insert in Update Task 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 dap fgdt update FM, simply by entering the name DAP_FGDT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMRC
Program Name: SAPLRMRC
Main Program: SAPLRMRC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function DAP_FGDT_UPDATE 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 'DAP_FGDT_UPDATE'"Database Insert in Update Task.
EXPORTING
I_UPDTASK = "
TABLES
I_TAB_KO = "
I_TAB_OLD_KOET = "
I_TAB_OLD_ABEST = "
I_TAB_OLD_OPTI = "
I_TAB_OLD_BEWEG = "
* I_TAB_OLD_COMBEWEG = "RM: DB Table BEWEG Extended Category of Primary Transaction
I_TAB_OLD_FML = "
I_TAB_OLD_HIER = "
I_TAB_KOET = "
I_TAB_ABEST = "
I_TAB_OPTI = "
I_TAB_BEWEG = "
* I_TAB_COMBEWEG = "RM: DB Table BEWEG Extended Category of Primary Transaction
I_TAB_FML = "
I_TAB_HIER = "
I_TAB_OLD_KO = "
IMPORTING Parameters details for DAP_FGDT_UPDATE
I_UPDTASK -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DAP_FGDT_UPDATE
I_TAB_KO -
Data type: JBRDBKOOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_KOET -
Data type: JBRDBKOETOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_ABEST -
Data type: JBRDBABESTOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_OPTI -
Data type: JBRDBOPTIOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_BEWEG -
Data type: JBRDBBEWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_COMBEWEG - RM: DB Table BEWEG Extended Category of Primary Transaction
Data type: JBRDBCOMBEWEGOptional: Yes
Call by Reference: Yes
I_TAB_OLD_FML -
Data type: JBRDBFMLOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_HIER -
Data type: JBRDBHIEROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_KOET -
Data type: JBRDBKOETOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_ABEST -
Data type: JBRDBABESTOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OPTI -
Data type: JBRDBOPTIOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_BEWEG -
Data type: JBRDBBEWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_COMBEWEG - RM: DB Table BEWEG Extended Category of Primary Transaction
Data type: JBRDBCOMBEWEGOptional: Yes
Call by Reference: Yes
I_TAB_FML -
Data type: JBRDBFMLOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_HIER -
Data type: JBRDBHIEROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_OLD_KO -
Data type: JBRDBKOOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DAP_FGDT_UPDATE 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_i_tab_ko | TYPE STANDARD TABLE OF JBRDBKO, " | |||
| lv_i_updtask | TYPE BOOLE-BOOLE, " | |||
| lt_i_tab_old_koet | TYPE STANDARD TABLE OF JBRDBKOET, " | |||
| lt_i_tab_old_abest | TYPE STANDARD TABLE OF JBRDBABEST, " | |||
| lt_i_tab_old_opti | TYPE STANDARD TABLE OF JBRDBOPTI, " | |||
| lt_i_tab_old_beweg | TYPE STANDARD TABLE OF JBRDBBEWEG, " | |||
| lt_i_tab_old_combeweg | TYPE STANDARD TABLE OF JBRDBCOMBEWEG, " | |||
| lt_i_tab_old_fml | TYPE STANDARD TABLE OF JBRDBFML, " | |||
| lt_i_tab_old_hier | TYPE STANDARD TABLE OF JBRDBHIER, " | |||
| lt_i_tab_koet | TYPE STANDARD TABLE OF JBRDBKOET, " | |||
| lt_i_tab_abest | TYPE STANDARD TABLE OF JBRDBABEST, " | |||
| lt_i_tab_opti | TYPE STANDARD TABLE OF JBRDBOPTI, " | |||
| lt_i_tab_beweg | TYPE STANDARD TABLE OF JBRDBBEWEG, " | |||
| lt_i_tab_combeweg | TYPE STANDARD TABLE OF JBRDBCOMBEWEG, " | |||
| lt_i_tab_fml | TYPE STANDARD TABLE OF JBRDBFML, " | |||
| lt_i_tab_hier | TYPE STANDARD TABLE OF JBRDBHIER, " | |||
| lt_i_tab_old_ko | TYPE STANDARD TABLE OF JBRDBKO. " |
|   CALL FUNCTION 'DAP_FGDT_UPDATE' "Database Insert in Update Task |
| EXPORTING | ||
| I_UPDTASK | = lv_i_updtask | |
| TABLES | ||
| I_TAB_KO | = lt_i_tab_ko | |
| I_TAB_OLD_KOET | = lt_i_tab_old_koet | |
| I_TAB_OLD_ABEST | = lt_i_tab_old_abest | |
| I_TAB_OLD_OPTI | = lt_i_tab_old_opti | |
| I_TAB_OLD_BEWEG | = lt_i_tab_old_beweg | |
| I_TAB_OLD_COMBEWEG | = lt_i_tab_old_combeweg | |
| I_TAB_OLD_FML | = lt_i_tab_old_fml | |
| I_TAB_OLD_HIER | = lt_i_tab_old_hier | |
| I_TAB_KOET | = lt_i_tab_koet | |
| I_TAB_ABEST | = lt_i_tab_abest | |
| I_TAB_OPTI | = lt_i_tab_opti | |
| I_TAB_BEWEG | = lt_i_tab_beweg | |
| I_TAB_COMBEWEG | = lt_i_tab_combeweg | |
| I_TAB_FML | = lt_i_tab_fml | |
| I_TAB_HIER | = lt_i_tab_hier | |
| I_TAB_OLD_KO | = lt_i_tab_old_ko | |
| . " DAP_FGDT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM DAP_FGDT_UPDATE
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 BOOLE FROM BOOLE INTO @DATA(ld_i_updtask). | ||||
Search for further information about these or an SAP related objects