SAP ISU_SPEC_CASE_DEVICE_STATUS Function Module for
ISU_SPEC_CASE_DEVICE_STATUS is a standard isu spec case device status 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 spec case device status FM, simply by entering the name ISU_SPEC_CASE_DEVICE_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: E17A
Program Name: SAPLE17A
Main Program: SAPLE17A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_SPEC_CASE_DEVICE_STATUS 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_SPEC_CASE_DEVICE_STATUS'".
EXPORTING
X_BP = "
X_EQUNR = "Equipment Number
X_ZWNUMMER = "Register
* X_ADATREAL = "[JBP] Real Meter Reading Date
* X_ATIMREAL = "[JBP] Real Meter Reading Time
X_MASTERDATA = "
X_ABLBELNR = "Internal ID for meter reading document
X_KEYDATE = "Meter Reading Date Relevant to Billing
CHANGING
XY_DEV_STATE = "Device Status
TABLES
* XT_EABL_ALL = "Meter reading document
* XT_EABLG_ALL = "MR Reasons in MR Document
EXCEPTIONS
GENERAL_ERROR = 1
IMPORTING Parameters details for ISU_SPEC_CASE_DEVICE_STATUS
X_BP -
Data type: EABL-BPOptional: No
Call by Reference: Yes
X_EQUNR - Equipment Number
Data type: EABL-EQUNROptional: No
Call by Reference: Yes
X_ZWNUMMER - Register
Data type: EABL-ZWNUMMEROptional: No
Call by Reference: Yes
X_ADATREAL - [JBP] Real Meter Reading Date
Data type: EABL-ADATREALOptional: Yes
Call by Reference: Yes
X_ATIMREAL - [JBP] Real Meter Reading Time
Data type: EABL-ATIMREALOptional: Yes
Call by Reference: Yes
X_MASTERDATA -
Data type: ISU17_METERDOCU_MASTERDATAOptional: No
Call by Reference: Yes
X_ABLBELNR - Internal ID for meter reading document
Data type: EABL-ABLBELNROptional: No
Call by Reference: Yes
X_KEYDATE - Meter Reading Date Relevant to Billing
Data type: EABL-ADATOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISU_SPEC_CASE_DEVICE_STATUS
XY_DEV_STATE - Device Status
Data type: REABLD-DEV_STATEOptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_SPEC_CASE_DEVICE_STATUS
XT_EABL_ALL - Meter reading document
Data type: EABLOptional: Yes
Call by Reference: Yes
XT_EABLG_ALL - MR Reasons in MR Document
Data type: EABLGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
GENERAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_SPEC_CASE_DEVICE_STATUS 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_x_bp | TYPE EABL-BP, " | |||
| lt_xt_eabl_all | TYPE STANDARD TABLE OF EABL, " | |||
| lv_xy_dev_state | TYPE REABLD-DEV_STATE, " | |||
| lv_general_error | TYPE REABLD, " | |||
| lv_x_equnr | TYPE EABL-EQUNR, " | |||
| lt_xt_eablg_all | TYPE STANDARD TABLE OF EABLG, " | |||
| lv_x_zwnummer | TYPE EABL-ZWNUMMER, " | |||
| lv_x_adatreal | TYPE EABL-ADATREAL, " | |||
| lv_x_atimreal | TYPE EABL-ATIMREAL, " | |||
| lv_x_masterdata | TYPE ISU17_METERDOCU_MASTERDATA, " | |||
| lv_x_ablbelnr | TYPE EABL-ABLBELNR, " | |||
| lv_x_keydate | TYPE EABL-ADAT. " |
|   CALL FUNCTION 'ISU_SPEC_CASE_DEVICE_STATUS' " |
| EXPORTING | ||
| X_BP | = lv_x_bp | |
| X_EQUNR | = lv_x_equnr | |
| X_ZWNUMMER | = lv_x_zwnummer | |
| X_ADATREAL | = lv_x_adatreal | |
| X_ATIMREAL | = lv_x_atimreal | |
| X_MASTERDATA | = lv_x_masterdata | |
| X_ABLBELNR | = lv_x_ablbelnr | |
| X_KEYDATE | = lv_x_keydate | |
| CHANGING | ||
| XY_DEV_STATE | = lv_xy_dev_state | |
| TABLES | ||
| XT_EABL_ALL | = lt_xt_eabl_all | |
| XT_EABLG_ALL | = lt_xt_eablg_all | |
| EXCEPTIONS | ||
| GENERAL_ERROR = 1 | ||
| . " ISU_SPEC_CASE_DEVICE_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SPEC_CASE_DEVICE_STATUS
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 BP FROM EABL INTO @DATA(ld_x_bp). | ||||
| "SELECT single DEV_STATE FROM REABLD INTO @DATA(ld_xy_dev_state). | ||||
| "SELECT single EQUNR FROM EABL INTO @DATA(ld_x_equnr). | ||||
| "SELECT single ZWNUMMER FROM EABL INTO @DATA(ld_x_zwnummer). | ||||
| "SELECT single ADATREAL FROM EABL INTO @DATA(ld_x_adatreal). | ||||
| "SELECT single ATIMREAL FROM EABL INTO @DATA(ld_x_atimreal). | ||||
| "SELECT single ABLBELNR FROM EABL INTO @DATA(ld_x_ablbelnr). | ||||
| "SELECT single ADAT FROM EABL INTO @DATA(ld_x_keydate). | ||||
Search for further information about these or an SAP related objects