ABAP Select data from SAP table OA2C_CLIENT_EXT 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 OA2C_CLIENT_EXT 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 OA2C_CLIENT_EXT 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 OA2C_CLIENT_EXT 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 OA2C_CLIENT_EXT. See here for more generic Select statement tips.

DATA: IT_OA2C_CLIENT_EXT TYPE STANDARD TABLE OF OA2C_CLIENT_EXT,
      WA_OA2C_CLIENT_EXT TYPE OA2C_CLIENT_EXT,
      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: <OA2C_CLIENT_EXT> TYPE OA2C_CLIENT_EXT.

*Process all fields in table header/work area as string values, full declaration of the OA2C_CLIENT_EXT 
*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_OA2C_CLIENT_EXT.

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM OA2C_CLIENT_EXT
*  INTO TABLE @DATA(IT_OA2C_CLIENT_EXT2).
*--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_OA2C_CLIENT_EXT INDEX 1 INTO DATA(WA_OA2C_CLIENT_EXT2).


*Demonstrate how to loop at an internal table and update values using a FIELD-SYMBOL
LOOP AT IT_OA2C_CLIENT_EXT ASSIGNING <OA2C_CLIENT_EXT>.
*To update a field value using a field symbol simply change the value via the field symbol pointer
<OA2C_CLIENT_EXT>-MANDT = 1.
<OA2C_CLIENT_EXT>-CLIENT_UUID = 1.
<OA2C_CLIENT_EXT>-GRANTTYPE = 1.
<OA2C_CLIENT_EXT>-PW_SEGMENT_COUNT = 1.
<OA2C_CLIENT_EXT>-USERNAME = 1.
ENDLOOP.

LOOP AT IT_OA2C_CLIENT_EXT INTO WA_OA2C_CLIENT_EXT.
*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_OA2C_CLIENT_EXT 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_OA2C_CLIENT_EXT 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_OA2C_CLIENT_EXT INTO WA_OA2C_CLIENT_EXT.


*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_OA2C_CLIENT_EXT_STR,
MANDT TYPE STRING,
CLIENT_UUID TYPE STRING,
GRANTTYPE TYPE STRING,
PW_SEGMENT_COUNT TYPE STRING,
USERNAME TYPE STRING,END OF T_EKKO_STR. DATA: WA_OA2C_CLIENT_EXT_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_OA2C_CLIENT_EXT_STR-MANDT sy-vline
WA_OA2C_CLIENT_EXT_STR-CLIENT_UUID sy-vline
WA_OA2C_CLIENT_EXT_STR-GRANTTYPE sy-vline
WA_OA2C_CLIENT_EXT_STR-PW_SEGMENT_COUNT sy-vline
WA_OA2C_CLIENT_EXT_STR-USERNAME sy-vline INTO ld_text SEPARATED BY SPACE. *Add any further fields from structure WA_EKKO_STR you want to CONCATENATE... ENDLOOP. ENDFORM.