SAP ISU_DB_EWAOBJ_MULTI Function Module for
ISU_DB_EWAOBJ_MULTI is a standard isu db ewaobj multi 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 isu db ewaobj multi FM, simply by entering the name ISU_DB_EWAOBJ_MULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEWA_DB_ROBJ
Program Name: SAPLEEWA_DB_ROBJ
Main Program: SAPLEEWA_DB_ROBJ
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_EWAOBJ_MULTI 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 'ISU_DB_EWAOBJ_MULTI'".
EXPORTING
XT_OBJNR = "
* X_ERROR_NOT_FOUND = ' ' "
IMPORTING
YT_EWAOBJ = "
EXCEPTIONS
NOT_FOUND = 1 NOT_QUALIFIED = 2
IMPORTING Parameters details for ISU_DB_EWAOBJ_MULTI
XT_OBJNR -
Data type: EOBJNR_KEYOptional: No
Call by Reference: No ( called with pass by value option)
X_ERROR_NOT_FOUND -
Data type: KENNZXDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_DB_EWAOBJ_MULTI
YT_EWAOBJ -
Data type: T_EWAOBJOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NOT_QUALIFIED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_DB_EWAOBJ_MULTI 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_xt_objnr | TYPE EOBJNR_KEY, " | |||
| lv_not_found | TYPE EOBJNR_KEY, " | |||
| lv_yt_ewaobj | TYPE T_EWAOBJ, " | |||
| lv_not_qualified | TYPE T_EWAOBJ, " | |||
| lv_x_error_not_found | TYPE KENNZX. " SPACE |
|   CALL FUNCTION 'ISU_DB_EWAOBJ_MULTI' " |
| EXPORTING | ||
| XT_OBJNR | = lv_xt_objnr | |
| X_ERROR_NOT_FOUND | = lv_x_error_not_found | |
| IMPORTING | ||
| YT_EWAOBJ | = lv_yt_ewaobj | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NOT_QUALIFIED = 2 | ||
| . " ISU_DB_EWAOBJ_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_EWAOBJ_MULTI
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.| DATA(ld_x_error_not_found) | = ' '. | |||
Search for further information about these or an SAP related objects