SAP ISU_DB_EABL_SELECT_BILL_ORDER Function Module for









ISU_DB_EABL_SELECT_BILL_ORDER is a standard isu db eabl select bill order 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 eabl select bill order FM, simply by entering the name ISU_DB_EABL_SELECT_BILL_ORDER into the relevant SAP transaction such as SE37 or SE38.

Function Group: EL24
Program Name: SAPLEL24
Main Program: SAPLEL24
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_DB_EABL_SELECT_BILL_ORDER 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_EABL_SELECT_BILL_ORDER'"
  EXPORTING
   X_ANLAGE =  "Installation
   X_ABRVORG =  "
   X_ADATSOLL =  "Scheduled Meter Reading Date
*  X_ABLESGR =  "
*  X_PREPARED = 'X' "
*  X_INVALID = 'X' "
*  X_VALID = 'X' "
*  X_ACTUAL =  "

 IMPORTING
   Y_COUNT =  "
   Y_ANZEABL_PRE =  "
   Y_ANZEABL_ENT =  "
   Y_ANZEABLG =  "

TABLES
*  TY_EABL =  "
*  TY_EABLG =  "

EXCEPTIONS
   NOT_FOUND = 1    SYSTEM_ERROR = 2    NOT_QUALIFIED = 3
.



IMPORTING Parameters details for ISU_DB_EABL_SELECT_BILL_ORDER

X_ANLAGE - Installation

Data type: ETRG-ANLAGE
Optional: No
Call by Reference: No ( called with pass by value option)

X_ABRVORG -

Data type: ETRG-ABRVORG
Optional: No
Call by Reference: No ( called with pass by value option)

X_ADATSOLL - Scheduled Meter Reading Date

Data type: ETRG-ADATSOLL
Optional: No
Call by Reference: No ( called with pass by value option)

X_ABLESGR -

Data type: EABLG-ABLESGR
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PREPARED -

Data type: REGEN-KENNZX
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_INVALID -

Data type: REGEN-KENNZX
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_VALID -

Data type: REGEN-KENNZX
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_ACTUAL -

Data type: REGEN-ACTUAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_DB_EABL_SELECT_BILL_ORDER

Y_COUNT -

Data type: REGEN-MAXCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

Y_ANZEABL_PRE -

Data type: REGEN-MAXCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

Y_ANZEABL_ENT -

Data type: REGEN-MAXCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

Y_ANZEABLG -

Data type: REGEN-MAXCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISU_DB_EABL_SELECT_BILL_ORDER

TY_EABL -

Data type: EABL
Optional: Yes
Call by Reference: No ( called with pass by value option)

TY_EABLG -

Data type: EABLG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_FOUND - Record does not exist

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 -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_DB_EABL_SELECT_BILL_ORDER 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_ty_eabl  TYPE STANDARD TABLE OF EABL, "   
lv_y_count  TYPE REGEN-MAXCOUNT, "   
lv_x_anlage  TYPE ETRG-ANLAGE, "   
lv_not_found  TYPE ETRG, "   
lt_ty_eablg  TYPE STANDARD TABLE OF EABLG, "   
lv_x_abrvorg  TYPE ETRG-ABRVORG, "   
lv_system_error  TYPE ETRG, "   
lv_y_anzeabl_pre  TYPE REGEN-MAXCOUNT, "   
lv_x_adatsoll  TYPE ETRG-ADATSOLL, "   
lv_not_qualified  TYPE ETRG, "   
lv_y_anzeabl_ent  TYPE REGEN-MAXCOUNT, "   
lv_x_ablesgr  TYPE EABLG-ABLESGR, "   
lv_y_anzeablg  TYPE REGEN-MAXCOUNT, "   
lv_x_prepared  TYPE REGEN-KENNZX, "   'X'
lv_x_invalid  TYPE REGEN-KENNZX, "   'X'
lv_x_valid  TYPE REGEN-KENNZX, "   'X'
lv_x_actual  TYPE REGEN-ACTUAL. "   

  CALL FUNCTION 'ISU_DB_EABL_SELECT_BILL_ORDER'  "
    EXPORTING
         X_ANLAGE = lv_x_anlage
         X_ABRVORG = lv_x_abrvorg
         X_ADATSOLL = lv_x_adatsoll
         X_ABLESGR = lv_x_ablesgr
         X_PREPARED = lv_x_prepared
         X_INVALID = lv_x_invalid
         X_VALID = lv_x_valid
         X_ACTUAL = lv_x_actual
    IMPORTING
         Y_COUNT = lv_y_count
         Y_ANZEABL_PRE = lv_y_anzeabl_pre
         Y_ANZEABL_ENT = lv_y_anzeabl_ent
         Y_ANZEABLG = lv_y_anzeablg
    TABLES
         TY_EABL = lt_ty_eabl
         TY_EABLG = lt_ty_eablg
    EXCEPTIONS
        NOT_FOUND = 1
        SYSTEM_ERROR = 2
        NOT_QUALIFIED = 3
. " ISU_DB_EABL_SELECT_BILL_ORDER




ABAP code using 7.40 inline data declarations to call FM ISU_DB_EABL_SELECT_BILL_ORDER

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 ANLAGE FROM ETRG INTO @DATA(ld_x_anlage).
 
 
 
"SELECT single ABRVORG FROM ETRG INTO @DATA(ld_x_abrvorg).
 
 
"SELECT single MAXCOUNT FROM REGEN INTO @DATA(ld_y_anzeabl_pre).
 
"SELECT single ADATSOLL FROM ETRG INTO @DATA(ld_x_adatsoll).
 
 
"SELECT single MAXCOUNT FROM REGEN INTO @DATA(ld_y_anzeabl_ent).
 
"SELECT single ABLESGR FROM EABLG INTO @DATA(ld_x_ablesgr).
 
"SELECT single MAXCOUNT FROM REGEN INTO @DATA(ld_y_anzeablg).
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_prepared).
DATA(ld_x_prepared) = 'X'.
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_invalid).
DATA(ld_x_invalid) = 'X'.
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_valid).
DATA(ld_x_valid) = 'X'.
 
"SELECT single ACTUAL FROM REGEN INTO @DATA(ld_x_actual).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!