EA_GHO_EXTRACT_PLANNED SAP Function module - Extract Measurement Data

EA_GHO_EXTRACT_PLANNED is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EA_GHO_EXTRACT_PLANNED into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EA_GHO_ANL_EXTRACTOR
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM EA_GHO_EXTRACT_PLANNED - EA GHO EXTRACT PLANNED

CALL FUNCTION 'EA_GHO_EXTRACT_PLANNED' "Extract Measurement Data
  EXPORTING
    i_requnr =                  " srsc_s_if_simple-requnr  Request Number for Creation of BI Extraction Order
*   i_dsource =                 " srsc_s_if_simple-dsource  Info Source
*   i_maxsize =                 " srsc_s_if_simple-maxsize  Maximum number of table entries in extraction API interface
*   i_initflag =                " srsc_s_if_simple-initflag  Flag: Callup of the extraction APIs for initialization
*   i_updmode =                 " srsc_s_if_simple-readonly  Mode of data update (Full, Delta, etc.)
*   i_read_only =               " srsc_s_if_simple-readonly
  TABLES
*   e_t_data =                  " gho_s_alloc_p_extract  extract structure for Data Source
    i_t_select =                " srsc_s_if_simple-t_select
    i_t_fields =                " srsc_s_if_simple-t_fields
  EXCEPTIONS
    ERROR_PASSED_TO_MESS_HANDLER = 1  "
    NO_MORE_DATA = 2            "
    .  "  EA_GHO_EXTRACT_PLANNED

ABAP code example for Function Module EA_GHO_EXTRACT_PLANNED

The ABAP code below is a full code listing to execute function module EA_GHO_EXTRACT_PLANNED including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_e_t_data  
 
 TYPE STANDARD TABLE OF GHO_S_ALLOC_P_EXTRACT,"TABLES PARAM
wa_e_t_data
 
 LIKE LINE OF it_e_t_data
,
it_i_t_select  
 
 TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_SELECT,"TABLES PARAM
wa_i_t_select
 
 LIKE LINE OF it_i_t_select
,
it_i_t_fields  
 
 TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_FIELDS,"TABLES PARAM
wa_i_t_fields
 
 LIKE LINE OF it_i_t_fields
.



DATA(ld_i_requnr) = some text here


DATA(ld_i_dsource) = some text here


DATA(ld_i_maxsize) = some text here


DATA(ld_i_initflag) = some text here


DATA(ld_i_updmode) = some text here


DATA(ld_i_read_only) = some text here
 

"populate fields of struture and append to itab
append wa_e_t_data to it_e_t_data.
 

"populate fields of struture and append to itab
append wa_i_t_select to it_i_t_select.
 

"populate fields of struture and append to itab
append wa_i_t_fields to it_i_t_fields.
.

CALL FUNCTION 'EA_GHO_EXTRACT_PLANNED'
  EXPORTING
    i_requnr =                   ld_i_requnr
*   i_dsource =                  ld_i_dsource
*   i_maxsize =                  ld_i_maxsize
*   i_initflag =                 ld_i_initflag
*   i_updmode =                  ld_i_updmode
*   i_read_only =                ld_i_read_only
  TABLES
*   e_t_data =                   it_e_t_data
    i_t_select =                 it_i_t_select
    i_t_fields =                 it_i_t_fields
  EXCEPTIONS
    ERROR_PASSED_TO_MESS_HANDLER =    1
    NO_MORE_DATA =               2
    .  "  EA_GHO_EXTRACT_PLANNED

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_i_requnr
 
 TYPE SRSC_S_IF_SIMPLE-REQUNR ,
it_e_t_data
 
 TYPE STANDARD TABLE OF GHO_S_ALLOC_P_EXTRACT ,
wa_e_t_data
 
 LIKE LINE OF it_e_t_data,
ld_i_dsource
 
 TYPE SRSC_S_IF_SIMPLE-DSOURCE ,
it_i_t_select
 
 TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_SELECT ,
wa_i_t_select
 
 LIKE LINE OF it_i_t_select,
ld_i_maxsize
 
 TYPE SRSC_S_IF_SIMPLE-MAXSIZE ,
it_i_t_fields
 
 TYPE STANDARD TABLE OF SRSC_S_IF_SIMPLE-T_FIELDS ,
wa_i_t_fields
 
 LIKE LINE OF it_i_t_fields,
ld_i_initflag
 
 TYPE SRSC_S_IF_SIMPLE-INITFLAG ,
ld_i_updmode
 
 TYPE SRSC_S_IF_SIMPLE-READONLY ,
ld_i_read_only
 
 TYPE SRSC_S_IF_SIMPLE-READONLY .



ld_i_requnr = some text here 

"populate fields of struture and append to itab
append wa_e_t_data to it_e_t_data.

ld_i_dsource = some text here 

"populate fields of struture and append to itab
append wa_i_t_select to it_i_t_select.

ld_i_maxsize = some text here 

"populate fields of struture and append to itab
append wa_i_t_fields to it_i_t_fields.

ld_i_initflag = some text here

ld_i_updmode = some text here

ld_i_read_only = some text here