SAP ISU_DB_EZUZ_SELECT Function Module for INTERNAL: Read EZUZ (Mass Access)
ISU_DB_EZUZ_SELECT is a standard isu db ezuz select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Read EZUZ (Mass Access) 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 isu db ezuz select FM, simply by entering the name ISU_DB_EZUZ_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: E70U
Program Name: SAPLE70U
Main Program: SAPLE70U
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DB_EZUZ_SELECT 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_EZUZ_SELECT'"INTERNAL: Read EZUZ (Mass Access).
EXPORTING
* X_LOGIKZW = "Logical register number
* X_ZUART = "
* X_LOGIKNR2 = "
* X_AB = '19000101' "From-date
* X_BIS = '99991231' "To Date
IMPORTING
Y_COUNT = "Number of Hits
Y_EZUZ = "Device allocations at register level
TABLES
* T_EZUZ = "Device allocations at register level
* T_EZUZ_OLD = "
* T_EZUZ_KEY = "
EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2 NOT_QUALIFIED = 3
IMPORTING Parameters details for ISU_DB_EZUZ_SELECT
X_LOGIKZW - Logical register number
Data type: EZUZ-LOGIKZWOptional: Yes
Call by Reference: No ( called with pass by value option)
X_ZUART -
Data type: EZUZ-ZUARTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_LOGIKNR2 -
Data type: EZUZ-LOGIKNR2Optional: Yes
Call by Reference: No ( called with pass by value option)
X_AB - From-date
Data type: EZUZ-ABDefault: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_BIS - To Date
Data type: EZUZ-BISDefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_DB_EZUZ_SELECT
Y_COUNT - Number of Hits
Data type: REGEN-MAXCOUNTOptional: No
Call by Reference: No ( called with pass by value option)
Y_EZUZ - Device allocations at register level
Data type: EZUZOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_DB_EZUZ_SELECT
T_EZUZ - Device allocations at register level
Data type: EZUZOptional: Yes
Call by Reference: No ( called with pass by value option)
T_EZUZ_OLD -
Data type: EZUZOptional: Yes
Call by Reference: No ( called with pass by value option)
T_EZUZ_KEY -
Data type: EZUZOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No Object Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR - Other Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_QUALIFIED - Input Parameters Are not Qualified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DB_EZUZ_SELECT 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_t_ezuz | TYPE STANDARD TABLE OF EZUZ, " | |||
| lv_y_count | TYPE REGEN-MAXCOUNT, " | |||
| lv_not_found | TYPE REGEN, " | |||
| lv_x_logikzw | TYPE EZUZ-LOGIKZW, " | |||
| lv_y_ezuz | TYPE EZUZ, " | |||
| lv_x_zuart | TYPE EZUZ-ZUART, " | |||
| lt_t_ezuz_old | TYPE STANDARD TABLE OF EZUZ, " | |||
| lv_system_error | TYPE EZUZ, " | |||
| lt_t_ezuz_key | TYPE STANDARD TABLE OF EZUZ, " | |||
| lv_x_logiknr2 | TYPE EZUZ-LOGIKNR2, " | |||
| lv_not_qualified | TYPE EZUZ, " | |||
| lv_x_ab | TYPE EZUZ-AB, " '19000101' | |||
| lv_x_bis | TYPE EZUZ-BIS. " '99991231' |
|   CALL FUNCTION 'ISU_DB_EZUZ_SELECT' "INTERNAL: Read EZUZ (Mass Access) |
| EXPORTING | ||
| X_LOGIKZW | = lv_x_logikzw | |
| X_ZUART | = lv_x_zuart | |
| X_LOGIKNR2 | = lv_x_logiknr2 | |
| X_AB | = lv_x_ab | |
| X_BIS | = lv_x_bis | |
| IMPORTING | ||
| Y_COUNT | = lv_y_count | |
| Y_EZUZ | = lv_y_ezuz | |
| TABLES | ||
| T_EZUZ | = lt_t_ezuz | |
| T_EZUZ_OLD | = lt_t_ezuz_old | |
| T_EZUZ_KEY | = lt_t_ezuz_key | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| SYSTEM_ERROR = 2 | ||
| NOT_QUALIFIED = 3 | ||
| . " ISU_DB_EZUZ_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_EZUZ_SELECT
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 MAXCOUNT FROM REGEN INTO @DATA(ld_y_count). | ||||
| "SELECT single LOGIKZW FROM EZUZ INTO @DATA(ld_x_logikzw). | ||||
| "SELECT single ZUART FROM EZUZ INTO @DATA(ld_x_zuart). | ||||
| "SELECT single LOGIKNR2 FROM EZUZ INTO @DATA(ld_x_logiknr2). | ||||
| "SELECT single AB FROM EZUZ INTO @DATA(ld_x_ab). | ||||
| DATA(ld_x_ab) | = '19000101'. | |||
| "SELECT single BIS FROM EZUZ INTO @DATA(ld_x_bis). | ||||
| DATA(ld_x_bis) | = '99991231'. | |||
Search for further information about these or an SAP related objects