SAP EA_GHO_EXTRACT_QUANT_TEXT Function Module for GET MEDIUMS FOR NET ID









EA_GHO_EXTRACT_QUANT_TEXT is a standard ea gho extract quant text 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 MEDIUMS FOR NET ID 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 ea gho extract quant text FM, simply by entering the name EA_GHO_EXTRACT_QUANT_TEXT into the relevant SAP transaction such as SE37 or SE38.

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



Function EA_GHO_EXTRACT_QUANT_TEXT 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 'EA_GHO_EXTRACT_QUANT_TEXT'"GET MEDIUMS FOR NET ID
EXPORTING
I_REQUNR = "Request Number for Creation of BI Extraction Order
* I_DSOURCE = "InfoSource
* I_MAXSIZE = "Maximum number of table entries in extraction API interface
* I_INITFLAG = "Flag: Callup of the extraction APIs for initialization
* I_UPDMODE = "Mode of data update (Full, Delta, etc.)

TABLES
* E_T_DATA = "EXTERNAL STR - PROD NET ID
I_T_SELECT = "
I_T_FIELDS = "

EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
.



IMPORTING Parameters details for EA_GHO_EXTRACT_QUANT_TEXT

I_REQUNR - Request Number for Creation of BI Extraction Order

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

I_DSOURCE - InfoSource

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

I_MAXSIZE - Maximum number of table entries in extraction API interface

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

I_INITFLAG - Flag: Callup of the extraction APIs for initialization

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

I_UPDMODE - Mode of data update (Full, Delta, etc.)

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

TABLES Parameters details for EA_GHO_EXTRACT_QUANT_TEXT

E_T_DATA - EXTERNAL STR - PROD NET ID

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

I_T_SELECT -

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

I_T_FIELDS -

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

EXCEPTIONS details

NO_MORE_DATA -

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

ERROR_PASSED_TO_MESS_HANDLER -

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

Copy and paste ABAP code example for EA_GHO_EXTRACT_QUANT_TEXT 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_e_t_data  TYPE STANDARD TABLE OF GHO_S_NW_QUANT_EXTRACT_SPRAS, "   
lv_i_requnr  TYPE SRSC_S_IF_SIMPLE-REQUNR, "   
lv_no_more_data  TYPE SRSC_S_IF_SIMPLE, "   
lv_i_dsource  TYPE SRSC_S_IF_SIMPLE-DSOURCE, "   
lt_i_t_select  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_SELECT, "   
lv_error_passed_to_mess_handler  TYPE SRSC_S_IF_SIMPLE, "   
lv_i_maxsize  TYPE SRSC_S_IF_SIMPLE-MAXSIZE, "   
lt_i_t_fields  TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_FIELDS, "   
lv_i_initflag  TYPE SRSC_S_IF_SIMPLE-INITFLAG, "   
lv_i_updmode  TYPE SRSC_S_IF_SIMPLE-READONLY. "   

  CALL FUNCTION 'EA_GHO_EXTRACT_QUANT_TEXT'  "GET MEDIUMS FOR NET ID
    EXPORTING
         I_REQUNR = lv_i_requnr
         I_DSOURCE = lv_i_dsource
         I_MAXSIZE = lv_i_maxsize
         I_INITFLAG = lv_i_initflag
         I_UPDMODE = lv_i_updmode
    TABLES
         E_T_DATA = lt_e_t_data
         I_T_SELECT = lt_i_t_select
         I_T_FIELDS = lt_i_t_fields
    EXCEPTIONS
        NO_MORE_DATA = 1
        ERROR_PASSED_TO_MESS_HANDLER = 2
. " EA_GHO_EXTRACT_QUANT_TEXT




ABAP code using 7.40 inline data declarations to call FM EA_GHO_EXTRACT_QUANT_TEXT

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 REQUNR FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_requnr).
 
 
"SELECT single DSOURCE FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_dsource).
 
"SELECT single T_SELECT FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_t_select).
 
 
"SELECT single MAXSIZE FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_maxsize).
 
"SELECT single T_FIELDS FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_t_fields).
 
"SELECT single INITFLAG FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_initflag).
 
"SELECT single READONLY FROM SRSC_S_IF_SIMPLE INTO @DATA(ld_i_updmode).
 


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!