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

Function ISU_DB_EPRINTACT_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_EPRINTACT_SELECT'".
EXPORTING
* X_ACTIONNO = "
* X_OBJ_TYPE = "
* X_OBJ_KEY = "
* X_FORMCLASS = "Form Class
* X_CAMPAIGN = "IS-U: Marketing Campaign
* X_ACTUAL = "
* X_MAX_ROWS = 500 "
IMPORTING
Y_COUNT = "Number of Hits
TABLES
* XT_OBJ_TYPE = "
* XT_OBJ_KEY = "
* XT_FORMCLASS = "
* YT_EPRINTACT = "No.of hits
EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2
IMPORTING Parameters details for ISU_DB_EPRINTACT_SELECT
X_ACTIONNO -
Data type: EPRINTACT-ACTIONNOOptional: Yes
Call by Reference: No ( called with pass by value option)
X_OBJ_TYPE -
Data type: EPRINTACT-OBJ_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_OBJ_KEY -
Data type: EPRINTACT-OBJ_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
X_FORMCLASS - Form Class
Data type: EPRINTACT-FORMCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
X_CAMPAIGN - IS-U: Marketing Campaign
Data type: EPA_MARKETING_CAMPAIGN_EXTERNOptional: Yes
Call by Reference: No ( called with pass by value option)
X_ACTUAL -
Data type: RFGEN-ACTUALOptional: Yes
Call by Reference: No ( called with pass by value option)
X_MAX_ROWS -
Data type: RFGEN-MAXCOUNTDefault: 500
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_DB_EPRINTACT_SELECT
Y_COUNT - Number of Hits
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISU_DB_EPRINTACT_SELECT
XT_OBJ_TYPE -
Data type: EFG_RANGESOptional: Yes
Call by Reference: No ( called with pass by value option)
XT_OBJ_KEY -
Data type: EFG_RANGESOptional: Yes
Call by Reference: No ( called with pass by value option)
XT_FORMCLASS -
Data type: EFG_RANGESOptional: Yes
Call by Reference: No ( called with pass by value option)
YT_EPRINTACT - No.of hits
Data type: EPRINTACTOptional: 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)
Copy and paste ABAP code example for ISU_DB_EPRINTACT_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: | ||||
| lv_y_count | TYPE SY-TABIX, " | |||
| lv_not_found | TYPE SY, " | |||
| lv_x_actionno | TYPE EPRINTACT-ACTIONNO, " | |||
| lt_xt_obj_type | TYPE STANDARD TABLE OF EFG_RANGES, " | |||
| lt_xt_obj_key | TYPE STANDARD TABLE OF EFG_RANGES, " | |||
| lv_x_obj_type | TYPE EPRINTACT-OBJ_TYPE, " | |||
| lv_system_error | TYPE EPRINTACT, " | |||
| lv_x_obj_key | TYPE EPRINTACT-OBJ_KEY, " | |||
| lt_xt_formclass | TYPE STANDARD TABLE OF EFG_RANGES, " | |||
| lv_x_formclass | TYPE EPRINTACT-FORMCLASS, " | |||
| lt_yt_eprintact | TYPE STANDARD TABLE OF EPRINTACT, " | |||
| lv_x_campaign | TYPE EPA_MARKETING_CAMPAIGN_EXTERN, " | |||
| lv_x_actual | TYPE RFGEN-ACTUAL, " | |||
| lv_x_max_rows | TYPE RFGEN-MAXCOUNT. " 500 |
|   CALL FUNCTION 'ISU_DB_EPRINTACT_SELECT' " |
| EXPORTING | ||
| X_ACTIONNO | = lv_x_actionno | |
| X_OBJ_TYPE | = lv_x_obj_type | |
| X_OBJ_KEY | = lv_x_obj_key | |
| X_FORMCLASS | = lv_x_formclass | |
| X_CAMPAIGN | = lv_x_campaign | |
| X_ACTUAL | = lv_x_actual | |
| X_MAX_ROWS | = lv_x_max_rows | |
| IMPORTING | ||
| Y_COUNT | = lv_y_count | |
| TABLES | ||
| XT_OBJ_TYPE | = lt_xt_obj_type | |
| XT_OBJ_KEY | = lt_xt_obj_key | |
| XT_FORMCLASS | = lt_xt_formclass | |
| YT_EPRINTACT | = lt_yt_eprintact | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| SYSTEM_ERROR = 2 | ||
| . " ISU_DB_EPRINTACT_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DB_EPRINTACT_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 TABIX FROM SY INTO @DATA(ld_y_count). | ||||
| "SELECT single ACTIONNO FROM EPRINTACT INTO @DATA(ld_x_actionno). | ||||
| "SELECT single OBJ_TYPE FROM EPRINTACT INTO @DATA(ld_x_obj_type). | ||||
| "SELECT single OBJ_KEY FROM EPRINTACT INTO @DATA(ld_x_obj_key). | ||||
| "SELECT single FORMCLASS FROM EPRINTACT INTO @DATA(ld_x_formclass). | ||||
| "SELECT single ACTUAL FROM RFGEN INTO @DATA(ld_x_actual). | ||||
| "SELECT single MAXCOUNT FROM RFGEN INTO @DATA(ld_x_max_rows). | ||||
| DATA(ld_x_max_rows) | = 500. | |||
Search for further information about these or an SAP related objects