COM_EEW_GEN_BW_VIEW_STD SAP Function module

COM_EEW_GEN_BW_VIEW_STD 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 COM_EEW_GEN_BW_VIEW_STD into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM COM_EEW_GEN_BW_VIEW_STD - COM EEW GEN BW VIEW STD

CALL FUNCTION 'COM_EEW_GEN_BW_VIEW_STD' "
  EXPORTING
*   iv_application =            " char30
    iv_object_name =            " char32
    it_object_new =             " comt_gox_def_header
    it_object_old =             " comt_gox_def_header
    iv_devclass =               " devclass
*   iv_request_wb =             " trkorr
  IMPORTING
    et_bapireturn =             " bapirettab
    et_transport =              " comt_gox_trans_object
    .  "  COM_EEW_GEN_BW_VIEW_STD

ABAP code example for Function Module COM_EEW_GEN_BW_VIEW_STD

The ABAP code below is a full code listing to execute function module COM_EEW_GEN_BW_VIEW_STD 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:
ld_et_bapireturn  
 
 TYPE BAPIRETTAB
,
ld_et_transport  
 
 TYPE COMT_GOX_TRANS_OBJECT
.


DATA(ld_iv_application) = 'Check type of data required'.

DATA(ld_iv_object_name) = 'Check type of data required'.

DATA(ld_it_object_new) = 'Check type of data required'.

DATA(ld_it_object_old) = 'Check type of data required'.

DATA(ld_iv_devclass) = 'Check type of data required'.

DATA(ld_iv_request_wb) = 'Check type of data required'.
.

CALL FUNCTION 'COM_EEW_GEN_BW_VIEW_STD'
  EXPORTING
*   iv_application =             ld_iv_application
    iv_object_name =             ld_iv_object_name
    it_object_new =              ld_it_object_new
    it_object_old =              ld_it_object_old
    iv_devclass =                ld_iv_devclass
*   iv_request_wb =              ld_iv_request_wb
  IMPORTING
    et_bapireturn =              ld_et_bapireturn
    et_transport =               ld_et_transport
    .  "  COM_EEW_GEN_BW_VIEW_STD

IF SY-SUBRC EQ 0.
  "All OK
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_et_bapireturn
 
 TYPE BAPIRETTAB ,
ld_iv_application
 
 TYPE CHAR30 ,
ld_et_transport
 
 TYPE COMT_GOX_TRANS_OBJECT ,
ld_iv_object_name
 
 TYPE CHAR32 ,
ld_it_object_new
 
 TYPE COMT_GOX_DEF_HEADER ,
ld_it_object_old
 
 TYPE COMT_GOX_DEF_HEADER ,
ld_iv_devclass
 
 TYPE DEVCLASS ,
ld_iv_request_wb
 
 TYPE TRKORR .


ld_iv_application = 'Check type of data required'.
ld_iv_object_name = 'Check type of data required'.
ld_it_object_new = 'Check type of data required'.
ld_it_object_old = 'Check type of data required'.
ld_iv_devclass = 'Check type of data required'.
ld_iv_request_wb = 'Check type of data required'.