SAP ABI_UPDATE_DB Function Module for Update AIDLOG and AIDIDDATA
ABI_UPDATE_DB is a standard abi update db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update AIDLOG and AIDIDDATA 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 abi update db FM, simply by entering the name ABI_UPDATE_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABI_MAP
Program Name: SAPLABI_MAP
Main Program: SAPLABI_MAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ABI_UPDATE_DB 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 'ABI_UPDATE_DB'"Update AIDLOG and AIDIDDATA.
EXPORTING
IT_AIDLOG = "Auto-ID Infrastructure Log Table
* IT_IDDATA = "Auto-ID Infrastructure Log Table
EXCEPTIONS
OPEN_SQL_ERROR = 1
IMPORTING Parameters details for ABI_UPDATE_DB
IT_AIDLOG - Auto-ID Infrastructure Log Table
Data type: ABI_AIDLOG_TOptional: No
Call by Reference: Yes
IT_IDDATA - Auto-ID Infrastructure Log Table
Data type: ABI_AIDIDDATA_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
OPEN_SQL_ERROR - Open SQL Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ABI_UPDATE_DB 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_it_aidlog | TYPE ABI_AIDLOG_T, " | |||
lv_open_sql_error | TYPE ABI_AIDLOG_T, " | |||
lv_it_iddata | TYPE ABI_AIDIDDATA_T. " |
  CALL FUNCTION 'ABI_UPDATE_DB' "Update AIDLOG and AIDIDDATA |
EXPORTING | ||
IT_AIDLOG | = lv_it_aidlog | |
IT_IDDATA | = lv_it_iddata | |
EXCEPTIONS | ||
OPEN_SQL_ERROR = 1 | ||
. " ABI_UPDATE_DB |
ABAP code using 7.40 inline data declarations to call FM ABI_UPDATE_DB
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