ABAP Select data from SAP table TREXS_PYTHON_TRACE_CONFIG into internal table

Get Example source ABAP code based on a different SAP table
  Get ABAP code

Below is a number of ABAP code snippets to demonstrate how to select data from SAP TREXS_PYTHON_TRACE_CONFIG 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 TREXS_PYTHON_TRACE_CONFIG. See here for more generic Select statement tips.

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.

There is also a full declaration of the TREXS_PYTHON_TRACE_CONFIG 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.

DATA: IT_TREXS_PYTHON_TRACE_CONFIG TYPE STANDARD TABLE OF TREXS_PYTHON_TRACE_CONFIG,
      WA_TREXS_PYTHON_TRACE_CONFIG TYPE TREXS_PYTHON_TRACE_CONFIG,
      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: <TREXS_PYTHON_TRACE_CONFIG> TYPE TREXS_PYTHON_TRACE_CONFIG.

*Process all fields in table header/work area as string values
  PERFORM process_as_string_field_values CHANGING wa_TREXS_PYTHON_TRACE_CONFIG.

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM TREXS_PYTHON_TRACE_CONFIG
*  INTO TABLE @DATA(IT_TREXS_PYTHON_TRACE_CONFIG2).
*--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_TREXS_PYTHON_TRACE_CONFIG INDEX 1 INTO DATA(WA_TREXS_PYTHON_TRACE_CONFIG2).


*Demonstrate how to loop at an internal table and update values using a FIELD-SYMBOL
LOOP AT IT_TREXS_PYTHON_TRACE_CONFIG ASSIGNING <TREXS_PYTHON_TRACE_CONFIG>.

*To update a field value using a field symbol simply change the value via the field symbol pointer
<TREXS_PYTHON_TRACE_CONFIG>-SERVER_TYPE = 1.
<TREXS_PYTHON_TRACE_CONFIG>-TRACE = 1.
<TREXS_PYTHON_TRACE_CONFIG>-USER = 1.
<TREXS_PYTHON_TRACE_CONFIG>-TRACE_FILE = 1.
<TREXS_PYTHON_TRACE_CONFIG>-SAP_SYSTEM = 1.

ENDLOOP.

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

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline,   WA_TREXS_PYTHON_TRACE_CONFIG-RFC_DESTINATION, sy-vline,
  WA_TREXS_PYTHON_TRACE_CONFIG-TRACE_FUNCTION, sy-vline,
  WA_TREXS_PYTHON_TRACE_CONFIG-RETURN_CODE, sy-vline,
  WA_TREXS_PYTHON_TRACE_CONFIG-RETURN_TEXT, sy-vline,
  WA_TREXS_PYTHON_TRACE_CONFIG-TRACE_HOSTS, sy-vline,
ENDLOOP.
   
*Add any further fields from structure WA_TREXS_PYTHON_TRACE_CONFIG 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_TREXS_PYTHON_TRACE_CONFIG 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_TREXS_PYTHON_TRACE_CONFIG INTO WA_TREXS_PYTHON_TRACE_CONFIG.


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

*Convert 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_TREXS_PYTHON_TRACE_CONFIG_STR, 
SERVER_TYPE TYPE STRING,
TRACE TYPE STRING,
USER TYPE STRING,
TRACE_FILE TYPE STRING,
SAP_SYSTEM TYPE STRING,
RFC_DESTINATION TYPE STRING,
TRACE_FUNCTION TYPE STRING,
RETURN_CODE TYPE STRING,
RETURN_TEXT TYPE STRING,
TRACE_HOSTS TYPE STRING,END OF T_EKKO_STR.
DATA: WA_TREXS_PYTHON_TRACE_CONFIG_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_TREXS_PYTHON_TRACE_CONFIG_STR-SERVER_TYPE sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-TRACE sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-USER sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-TRACE_FILE sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-SAP_SYSTEM sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-RFC_DESTINATION sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-TRACE_FUNCTION sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-RETURN_CODE sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-RETURN_TEXT sy-vline 
WA_TREXS_PYTHON_TRACE_CONFIG_STR-TRACE_HOSTS sy-vline      INTO ld_text SEPARATED BY SPACE.

*Add any further fields from structure WA_EKKO_STR you want to CONCATENATE...
ENDLOOP.
ENDFORM.