ABAP Select data from SAP table GBACR_ENVELOPE_MTD into internal table



Get Example source ABAP code based on a different SAP table
  

So we all know S/4Hana is the latest version and the future of SAP but what about the selecting data from hana tables like GBACR_ENVELOPE_MTD is it the same and what the table looks like in an S/4 system. If you havent seen or logged into an S/4Hana system you might be surprised at how similar it looks to the previous ERP/ECC version. Infact when using the gui it is difficult to tell the difference, and selecting data from database tables the same is true. Infact even for tables that have been replaced in hana, SAP have purposfully created versions of the old/original tables for backward compatability. This means your existing ABAP code will still work while you implement changes that take advantage of the new functionality and Hana in-memory tables.

You can see what table GBACR_ENVELOPE_MTD looks like in an S/4 system here and below is a number of ABAP code snippets to demonstrate how to select data from SAP GBACR_ENVELOPE_MTD table and store it within an internal table, including using the newer @DATA inline declaration methods. It also shows you various ways to process this data using ABAP work area, inline declaration or field symbols including executing all the relevant CONVERSION_EXIT routines specific to GBACR_ENVELOPE_MTD. See here for more generic Select statement tips.

DATA: IT_GBACR_ENVELOPE_MTD TYPE STANDARD TABLE OF GBACR_ENVELOPE_MTD,
      WA_GBACR_ENVELOPE_MTD TYPE GBACR_ENVELOPE_MTD,
      GD_STR TYPE STRING.

DATA: lo_typedescr type REF TO cl_abap_typedescr.
DATA: lv_fieldname type fieldname.

FIELD-SYMBOLS: <FIELD> TYPE any.
FIELD-SYMBOLS: <GBACR_ENVELOPE_MTD> TYPE GBACR_ENVELOPE_MTD.

*Process all fields in table header/work area as string values, full declaration of the GBACR_ENVELOPE_MTD 
*table where each field has a char/string type for you to simply copy and paste. This allows 
*you to use processing that is only available to these field types such as the CONCATENATE statement.
  PERFORM process_as_string_field_values CHANGING wa_GBACR_ENVELOPE_MTD.

SELECT *
*restrict ABAP select to first 10 rows
 UP TO 10 ROWS      
  FROM GBACR_ENVELOPE_MTD
  INTO TABLE IT_GBACR_ENVELOPE_MTD.

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM GBACR_ENVELOPE_MTD
*  INTO TABLE @DATA(IT_GBACR_ENVELOPE_MTD2).
*--Further methods of using ABAP code to  select data from SAP database tables

*You can also declare the header/work area using the in-line DATA declaration method
READ TABLE IT_GBACR_ENVELOPE_MTD INDEX 1 INTO DATA(WA_GBACR_ENVELOPE_MTD2).


*Demonstrate how to loop at an internal table and update values using a FIELD-SYMBOL
LOOP AT IT_GBACR_ENVELOPE_MTD ASSIGNING <GBACR_ENVELOPE_MTD>.
*To update a field value using a field symbol simply change the value via the field symbol pointer
<GBACR_ENVELOPE_MTD>-VAT_NUMBER = 1.
<GBACR_ENVELOPE_MTD>-ACCESS_TOKEN = 1.
<GBACR_ENVELOPE_MTD>-FROM_DATE = 1.
<GBACR_ENVELOPE_MTD>-TO_DATE = 1.
ENDLOOP.

LOOP AT IT_GBACR_ENVELOPE_MTD INTO WA_GBACR_ENVELOPE_MTD.
*Write horizonal line to screen report.
  WRITE:/ sy-uline.

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline, ENDLOOP.
   
*Add any further fields from structure WA_GBACR_ENVELOPE_MTD you want to display...

  WRITE:/ sy-uline.
* Aternatively use generic code to Write field values (and NAME) to screen report
  DO.
    ASSIGN COMPONENT sy-index OF STRUCTURE wa_GBACR_ENVELOPE_MTD TO <field>.
    IF sy-subrc <> 0. EXIT. ENDIF.
    WRITE:/ 'Field Value', <field>, sy-vline.
    gd_str = <field> .
    lo_typedescr ?= CL_ABAP_DATADESCR=>DESCRIBE_BY_DATA( <field> ).
    lv_fieldname = lo_typedescr->GET_RELATIVE_NAME( ).
    WRITE:/ 'Field Name', lv_fieldname.
  ENDDO.

  
*Redo loop but convert all fields from internal to out value  
LOOP AT IT_GBACR_ENVELOPE_MTD INTO WA_GBACR_ENVELOPE_MTD.


*Write horizonal line to screen report.
  WRITE:/ sy-uline.

*Sometimes data within SAP is stored within the database table in a different format to 
*what it is displayed to the user. These input/output conversation FM routines are what 
*translates the data between the two formats. This form converts all fields to display/output 
*versions using conversion routines
  PERFORM convert_all_field_values CHANGING wa_EKKO.
	 
ENDLOOP.

  
*&---------------------------------------------------------------------*
*& Form convert_all_field_values
*&---------------------------------------------------------------------*
FORM convert_all_field_values CHANGING p_EKKO LIKE wa_EKKO.
DATA: ld_input(1000) TYPE c, ld_output(1000) TYPE C.
ENDFORM. *&---------------------------------------------------------------------* *& Form process_as_string_field_values *&---------------------------------------------------------------------* FORM process_as_string_field_values CHANGING p_EKKO LIKE wa_EKKO. TYPES: BEGIN OF T_GBACR_ENVELOPE_MTD_STR,
VAT_NUMBER TYPE STRING,
ACCESS_TOKEN TYPE STRING,
FROM_DATE TYPE STRING,
TO_DATE TYPE STRING,END OF T_EKKO_STR. DATA: WA_GBACR_ENVELOPE_MTD_STR type T_EKKO_STR. DATA: ld_text TYPE string. LOOP AT IT_EKKO INTO WA_EKKO. MOVE-CORRESPONDING wa_EKKO TO WA_EKKO_STR. CONCATENATE: sy-vline
WA_GBACR_ENVELOPE_MTD_STR-VAT_NUMBER sy-vline
WA_GBACR_ENVELOPE_MTD_STR-ACCESS_TOKEN sy-vline
WA_GBACR_ENVELOPE_MTD_STR-FROM_DATE sy-vline
WA_GBACR_ENVELOPE_MTD_STR-TO_DATE sy-vline INTO ld_text SEPARATED BY SPACE. *Add any further fields from structure WA_EKKO_STR you want to CONCATENATE... ENDLOOP. ENDFORM.