SAP ISU_DB_EWABILL_SELECT Function Module for INTERNAL: Read All Billing Factors of a Billing Category









ISU_DB_EWABILL_SELECT is a standard isu db ewabill 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 All Billing Factors of a Billing Category 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 ewabill select FM, simply by entering the name ISU_DB_EWABILL_SELECT into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DB_EWABILL_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_EWABILL_SELECT'"INTERNAL: Read All Billing Factors of a Billing Category
EXPORTING
* X_BILLTYPE = "
* X_MAXCOUNT = 0 "
* X_SORT = "Sorting ('K' = Key, ' ' = No Sorting)
* X_ACTUAL = "Consistent Data Version ('X' = Yes, ' ' = No)

IMPORTING
Y_COUNT = "Number of Hits
Y_OVERFLOW = "Overflow indicator
Y_EWABILL = "

TABLES
* T_EWABILL = "

EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2 NOT_QUALIFIED = 3
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEEWA_BILLING_001 Check Billing-Relevant Values in Waste Billing Category

IMPORTING Parameters details for ISU_DB_EWABILL_SELECT

X_BILLTYPE -

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

X_MAXCOUNT -

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

X_SORT - Sorting ('K' = Key, SPACE = No Sorting)

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

X_ACTUAL - Consistent Data Version ('X' = Yes, ' ' = No)

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

EXPORTING Parameters details for ISU_DB_EWABILL_SELECT

Y_COUNT - Number of Hits

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

Y_OVERFLOW - Overflow indicator

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

Y_EWABILL -

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

TABLES Parameters details for ISU_DB_EWABILL_SELECT

T_EWABILL -

Data type: EWA_BILL_RELEVNT
Optional: Yes
Call by Reference: Yes

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_EWABILL_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 REGEN-MAXCOUNT, "   
lv_not_found  TYPE REGEN, "   
lt_t_ewabill  TYPE STANDARD TABLE OF EWA_BILL_RELEVNT, "   
lv_x_billtype  TYPE EBILLTYPE, "   
lv_x_maxcount  TYPE REGEN-MAXCOUNT, "   0
lv_y_overflow  TYPE REGEN-OVERFLOW, "   
lv_system_error  TYPE REGEN, "   
lv_x_sort  TYPE REGEN-KZ_SORT, "   
lv_y_ewabill  TYPE EWA_BILL_RELEVNT, "   
lv_not_qualified  TYPE EWA_BILL_RELEVNT, "   
lv_x_actual  TYPE REGEN-ACTUAL. "   

  CALL FUNCTION 'ISU_DB_EWABILL_SELECT'  "INTERNAL: Read All Billing Factors of a Billing Category
    EXPORTING
         X_BILLTYPE = lv_x_billtype
         X_MAXCOUNT = lv_x_maxcount
         X_SORT = lv_x_sort
         X_ACTUAL = lv_x_actual
    IMPORTING
         Y_COUNT = lv_y_count
         Y_OVERFLOW = lv_y_overflow
         Y_EWABILL = lv_y_ewabill
    TABLES
         T_EWABILL = lt_t_ewabill
    EXCEPTIONS
        NOT_FOUND = 1
        SYSTEM_ERROR = 2
        NOT_QUALIFIED = 3
. " ISU_DB_EWABILL_SELECT




ABAP code using 7.40 inline data declarations to call FM ISU_DB_EWABILL_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 MAXCOUNT FROM REGEN INTO @DATA(ld_x_maxcount).
 
"SELECT single OVERFLOW FROM REGEN INTO @DATA(ld_y_overflow).
 
 
"SELECT single KZ_SORT FROM REGEN INTO @DATA(ld_x_sort).
 
 
 
"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!