ABAP Select data from SAP table ARO_S_OBJECT_CHANGES 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 ARO_S_OBJECT_CHANGES 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 ARO_S_OBJECT_CHANGES. 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 ARO_S_OBJECT_CHANGES 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_ARO_S_OBJECT_CHANGES TYPE STANDARD TABLE OF ARO_S_OBJECT_CHANGES,
      WA_ARO_S_OBJECT_CHANGES TYPE ARO_S_OBJECT_CHANGES,
      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: <ARO_S_OBJECT_CHANGES> TYPE ARO_S_OBJECT_CHANGES.

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

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM ARO_S_OBJECT_CHANGES
*  INTO TABLE @DATA(IT_ARO_S_OBJECT_CHANGES2).
*--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_ARO_S_OBJECT_CHANGES INDEX 1 INTO DATA(WA_ARO_S_OBJECT_CHANGES2).


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

*To update a field value using a field symbol simply change the value via the field symbol pointer
<ARO_S_OBJECT_CHANGES>-OBJECTID = 1.
<ARO_S_OBJECT_CHANGES>-TCODE = 1.
<ARO_S_OBJECT_CHANGES>-PLANNED_CHANGE_NUMBER = 1.
<ARO_S_OBJECT_CHANGES>-UTIME = 1.
<ARO_S_OBJECT_CHANGES>-UDATE = 1.

ENDLOOP.

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

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline,   WA_ARO_S_OBJECT_CHANGES-USERNAME, sy-vline,
  WA_ARO_S_OBJECT_CHANGES-CDOC_PLANNED_OR_REAL, sy-vline,
  WA_ARO_S_OBJECT_CHANGES-CDOC_UPD_OBJECT, sy-vline,
  WA_ARO_S_OBJECT_CHANGES-CDOC_NO_CHANGE_POINTERS, sy-vline,
ENDLOOP.
   
*Add any further fields from structure WA_ARO_S_OBJECT_CHANGES 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_ARO_S_OBJECT_CHANGES 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_ARO_S_OBJECT_CHANGES INTO WA_ARO_S_OBJECT_CHANGES.


*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.

*Conversion exit ALPHA, internal->external for field PLANNED_CHANGE_NUMBER
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
  EXPORTING
    input =                      WA_ARO_S_OBJECT_CHANGES-PLANNED_CHANGE_NUMBER
  IMPORTING
    output =                     ld_input.
WRITE:/ 'Org Value:', WA_ARO_S_OBJECT_CHANGES-PLANNED_CHANGE_NUMBER.
WRITE:/ 'New Value:', ld_input.
ENDFORM. 

*&---------------------------------------------------------------------*
*& Form process_as_string_field_values
*&---------------------------------------------------------------------*
FORM process_as_string_field_values CHANGING p_EKKO LIKE wa_EKKO.

TYPES: BEGIN OF T_ARO_S_OBJECT_CHANGES_STR, 
OBJECTID TYPE STRING,
TCODE TYPE STRING,
PLANNED_CHANGE_NUMBER TYPE STRING,
UTIME TYPE STRING,
UDATE TYPE STRING,
USERNAME TYPE STRING,
CDOC_PLANNED_OR_REAL TYPE STRING,
CDOC_UPD_OBJECT TYPE STRING,
CDOC_NO_CHANGE_POINTERS TYPE STRING,END OF T_EKKO_STR.
DATA: WA_ARO_S_OBJECT_CHANGES_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_ARO_S_OBJECT_CHANGES_STR-OBJECTID sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-TCODE sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-PLANNED_CHANGE_NUMBER sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-UTIME sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-UDATE sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-USERNAME sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-CDOC_PLANNED_OR_REAL sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-CDOC_UPD_OBJECT sy-vline 
WA_ARO_S_OBJECT_CHANGES_STR-CDOC_NO_CHANGE_POINTERS sy-vline      INTO ld_text SEPARATED BY SPACE.

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