SAP ISU_DB_EGER_FETCH_LOS Function Module for INTERNAL: Read Device Depending on Lot Using Fetch









ISU_DB_EGER_FETCH_LOS is a standard isu db eger fetch los 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 Device Depending on Lot Using Fetch 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 eger fetch los FM, simply by entering the name ISU_DB_EGER_FETCH_LOS into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DB_EGER_FETCH_LOS 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_EGER_FETCH_LOS'"INTERNAL: Read Device Depending on Lot Using Fetch
EXPORTING
X_LOT = "Sample Lot
* X_AB = SY-DATUM "From-date
* X_BIS = SY-DATUM "To Date
* X_PACKAGESIZE = 500 "
* X_CLOSE = ' ' "

IMPORTING
Y_COUNT = "Number of Hits
Y_V_EGER = "
Y_CLOSED = "Indicator

TABLES
* T_V_EGER = "

EXCEPTIONS
NOT_FOUND = 1 NOT_QUALIFIED = 2
.



IMPORTING Parameters details for ISU_DB_EGER_FETCH_LOS

X_LOT - Sample Lot

Data type: LOS
Optional: No
Call by Reference: Yes

X_AB - From-date

Data type: V_EGER-AB
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

X_BIS - To Date

Data type: V_EGER-BIS
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

X_PACKAGESIZE -

Data type: I
Default: 500
Optional: Yes
Call by Reference: Yes

X_CLOSE -

Data type: REGEN-KENNZX
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_DB_EGER_FETCH_LOS

Y_COUNT - Number of Hits

Data type: REGEN-MAXCOUNT
Optional: No
Call by Reference: Yes

Y_V_EGER -

Data type: V_EGER
Optional: No
Call by Reference: Yes

Y_CLOSED - Indicator

Data type: REGEN-KENNZX
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISU_DB_EGER_FETCH_LOS

T_V_EGER -

Data type: V_EGER
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)

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_EGER_FETCH_LOS 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_lot  TYPE LOS, "   
lv_y_count  TYPE REGEN-MAXCOUNT, "   
lt_t_v_eger  TYPE STANDARD TABLE OF V_EGER, "   
lv_not_found  TYPE V_EGER, "   
lv_x_ab  TYPE V_EGER-AB, "   SY-DATUM
lv_y_v_eger  TYPE V_EGER, "   
lv_not_qualified  TYPE V_EGER, "   
lv_x_bis  TYPE V_EGER-BIS, "   SY-DATUM
lv_y_closed  TYPE REGEN-KENNZX, "   
lv_x_packagesize  TYPE I, "   500
lv_x_close  TYPE REGEN-KENNZX. "   SPACE

  CALL FUNCTION 'ISU_DB_EGER_FETCH_LOS'  "INTERNAL: Read Device Depending on Lot Using Fetch
    EXPORTING
         X_LOT = lv_x_lot
         X_AB = lv_x_ab
         X_BIS = lv_x_bis
         X_PACKAGESIZE = lv_x_packagesize
         X_CLOSE = lv_x_close
    IMPORTING
         Y_COUNT = lv_y_count
         Y_V_EGER = lv_y_v_eger
         Y_CLOSED = lv_y_closed
    TABLES
         T_V_EGER = lt_t_v_eger
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_QUALIFIED = 2
. " ISU_DB_EGER_FETCH_LOS




ABAP code using 7.40 inline data declarations to call FM ISU_DB_EGER_FETCH_LOS

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 AB FROM V_EGER INTO @DATA(ld_x_ab).
DATA(ld_x_ab) = SY-DATUM.
 
 
 
"SELECT single BIS FROM V_EGER INTO @DATA(ld_x_bis).
DATA(ld_x_bis) = SY-DATUM.
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_y_closed).
 
DATA(ld_x_packagesize) = 500.
 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_close).
DATA(ld_x_close) = ' '.
 


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!