SAP ISIDE_GET_REQUIREMENT Function Module for GET Requirment for ESP Storage Location









ISIDE_GET_REQUIREMENT is a standard iside get requirement SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GET Requirment for ESP Storage Location 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 iside get requirement FM, simply by entering the name ISIDE_GET_REQUIREMENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: DE_ESP
Program Name: SAPLDE_ESP
Main Program: SAPLDE_ESP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ISIDE_GET_REQUIREMENT 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 'ISIDE_GET_REQUIREMENT'"GET Requirment for ESP Storage Location
  EXPORTING
   IT_VENDOR =  "Tabellentyp für Hilfe für Lieferanten
   I_PLANT =  "Werk
   I_LGORT =  "Lagerort
*  I_ESP =  "Kontonummer des Lieferanten bzw. Kreditors
   I_MATNR =  "Materialnummer
*  I_LICHA =  "Lieferantenchargennummer
*  IV_STARTDATE =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)
*  IV_ENDDATE =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

 IMPORTING
   ET_RETURN =  "Rückgabeparameter
   ET_REQUIRED_DATA =  "
.



IMPORTING Parameters details for ISIDE_GET_REQUIREMENT

IT_VENDOR - Tabellentyp für Hilfe für Lieferanten

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

I_PLANT - Werk

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

I_LGORT - Lagerort

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

I_ESP - Kontonummer des Lieferanten bzw. Kreditors

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

I_MATNR - Materialnummer

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

I_LICHA - Lieferantenchargennummer

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

IV_STARTDATE - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

IV_ENDDATE - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

EXPORTING Parameters details for ISIDE_GET_REQUIREMENT

ET_RETURN - Rückgabeparameter

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

ET_REQUIRED_DATA -

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

Copy and paste ABAP code example for ISIDE_GET_REQUIREMENT 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_et_return  TYPE ISI_BAPIRETURN1_TT, "   
lv_it_vendor  TYPE ISI_VENDOR_TT, "   
lv_i_plant  TYPE WERKS_D, "   
lv_et_required_data  TYPE ISI_ESP_RPM_TT, "   
lv_i_lgort  TYPE LGORT_D, "   
lv_i_esp  TYPE LIFNR, "   
lv_i_matnr  TYPE MATNR, "   
lv_i_licha  TYPE LICHN, "   
lv_iv_startdate  TYPE TIMESTAMP, "   
lv_iv_enddate  TYPE TIMESTAMP. "   

  CALL FUNCTION 'ISIDE_GET_REQUIREMENT'  "GET Requirment for ESP Storage Location
    EXPORTING
         IT_VENDOR = lv_it_vendor
         I_PLANT = lv_i_plant
         I_LGORT = lv_i_lgort
         I_ESP = lv_i_esp
         I_MATNR = lv_i_matnr
         I_LICHA = lv_i_licha
         IV_STARTDATE = lv_iv_startdate
         IV_ENDDATE = lv_iv_enddate
    IMPORTING
         ET_RETURN = lv_et_return
         ET_REQUIRED_DATA = lv_et_required_data
. " ISIDE_GET_REQUIREMENT




ABAP code using 7.40 inline data declarations to call FM ISIDE_GET_REQUIREMENT

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.

 
 
 
 
 
 
 
 
 
 


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!