ABAP Select data from SAP table NFE_INSIMPLE_JSON_EVT into internal table

Get Example source ABAP code based on a different SAP table
  

Below is a number of ABAP code snippets to demonstrate how to select data from SAP NFE_INSIMPLE_JSON_EVT 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 NFE_INSIMPLE_JSON_EVT. 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 NFE_INSIMPLE_JSON_EVT 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_NFE_INSIMPLE_JSON_EVT TYPE STANDARD TABLE OF NFE_INSIMPLE_JSON_EVT,
      WA_NFE_INSIMPLE_JSON_EVT TYPE NFE_INSIMPLE_JSON_EVT,
      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: <NFE_INSIMPLE_JSON_EVT> TYPE NFE_INSIMPLE_JSON_EVT.

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

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM NFE_INSIMPLE_JSON_EVT
*  INTO TABLE @DATA(IT_NFE_INSIMPLE_JSON_EVT2).
*--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_NFE_INSIMPLE_JSON_EVT INDEX 1 INTO DATA(WA_NFE_INSIMPLE_JSON_EVT2).


*Demonstrate how to loop at an internal table and update values using a FIELD-SYMBOL
LOOP AT IT_NFE_INSIMPLE_JSON_EVT ASSIGNING <NFE_INSIMPLE_JSON_EVT>.
*To update a field value using a field symbol simply change the value via the field symbol pointer
<NFE_INSIMPLE_JSON_EVT>-UUID = 1.
<NFE_INSIMPLE_JSON_EVT>-ACCESSKEY = 1.
<NFE_INSIMPLE_JSON_EVT>-EVENTTYPE = 1.
<NFE_INSIMPLE_JSON_EVT>-EVENTSEQUENCE = 1.
<NFE_INSIMPLE_JSON_EVT>-ISSUEDATE = 1.
ENDLOOP.

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

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline,   WA_NFE_INSIMPLE_JSON_EVT-PROCESSSTATUSCODE, sy-vline,
WA_NFE_INSIMPLE_JSON_EVT-PROCESSSTATUSDESCRIPTION, sy-vline,
WA_NFE_INSIMPLE_JSON_EVT-EVENTSTATUSCODE, sy-vline,
WA_NFE_INSIMPLE_JSON_EVT-EVENTSTATUSDESCRIPTION, sy-vline,
WA_NFE_INSIMPLE_JSON_EVT-EVENTDESCRIPTION, sy-vline,
ENDLOOP. *Add any further fields from structure WA_NFE_INSIMPLE_JSON_EVT 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_NFE_INSIMPLE_JSON_EVT 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_NFE_INSIMPLE_JSON_EVT INTO WA_NFE_INSIMPLE_JSON_EVT. *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_NFE_INSIMPLE_JSON_EVT_STR,
UUID TYPE STRING,
ACCESSKEY TYPE STRING,
EVENTTYPE TYPE STRING,
EVENTSEQUENCE TYPE STRING,
ISSUEDATE TYPE STRING,
PROCESSSTATUSCODE TYPE STRING,
PROCESSSTATUSDESCRIPTION TYPE STRING,
EVENTSTATUSCODE TYPE STRING,
EVENTSTATUSDESCRIPTION TYPE STRING,
EVENTDESCRIPTION TYPE STRING,END OF T_EKKO_STR. DATA: WA_NFE_INSIMPLE_JSON_EVT_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_NFE_INSIMPLE_JSON_EVT_STR-UUID sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-ACCESSKEY sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-EVENTTYPE sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-EVENTSEQUENCE sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-ISSUEDATE sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-PROCESSSTATUSCODE sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-PROCESSSTATUSDESCRIPTION sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-EVENTSTATUSCODE sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-EVENTSTATUSDESCRIPTION sy-vline
WA_NFE_INSIMPLE_JSON_EVT_STR-EVENTDESCRIPTION sy-vline INTO ld_text SEPARATED BY SPACE. *Add any further fields from structure WA_EKKO_STR you want to CONCATENATE... ENDLOOP. ENDFORM.