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

DATA: IT_P01A1_DBBA TYPE STANDARD TABLE OF P01A1_DBBA,
      WA_P01A1_DBBA TYPE P01A1_DBBA,
      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: <P01A1_DBBA> TYPE P01A1_DBBA.

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

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM P01A1_DBBA
*  INTO TABLE @DATA(IT_P01A1_DBBA2).
*--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_P01A1_DBBA INDEX 1 INTO DATA(WA_P01A1_DBBA2).


*Demonstrate how to loop at an internal table and update values using a FIELD-SYMBOL
LOOP AT IT_P01A1_DBBA ASSIGNING <P01A1_DBBA>.
*To update a field value using a field symbol simply change the value via the field symbol pointer
<P01A1_DBBA>-MANDT = 1.
<P01A1_DBBA>-GUID = 1.
<P01A1_DBBA>-BEGDA = 1.
<P01A1_DBBA>-ENDDA = 1.
<P01A1_DBBA>-TTSC = 1.
ENDLOOP.

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

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline,   WA_P01A1_DBBA-KZ_BESCHVOR, sy-vline,
WA_P01A1_DBBA-KZ_GESAMTDAUER, sy-vline,
WA_P01A1_DBBA-GRUND_1, sy-vline,
WA_P01A1_DBBA-GRUND_2, sy-vline,
WA_P01A1_DBBA-GRUND_3, sy-vline,
WA_P01A1_DBBA-GRUND_4, sy-vline.
ENDLOOP. *Add any further fields from structure WA_P01A1_DBBA 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_P01A1_DBBA 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_P01A1_DBBA INTO WA_P01A1_DBBA. *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_P01A1_DBBA_STR,
MANDT TYPE STRING,
GUID TYPE STRING,
BEGDA TYPE STRING,
ENDDA TYPE STRING,
TTSC TYPE STRING,
KZ_BESCHVOR TYPE STRING,
KZ_GESAMTDAUER TYPE STRING,
GRUND_1 TYPE STRING,
GRUND_2 TYPE STRING,
GRUND_3 TYPE STRING,
GRUND_4 TYPE STRING,
KZ_VERBUND TYPE STRING,END OF T_EKKO_STR. DATA: WA_P01A1_DBBA_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_P01A1_DBBA_STR-MANDT sy-vline
WA_P01A1_DBBA_STR-GUID sy-vline
WA_P01A1_DBBA_STR-BEGDA sy-vline
WA_P01A1_DBBA_STR-ENDDA sy-vline
WA_P01A1_DBBA_STR-TTSC sy-vline
WA_P01A1_DBBA_STR-KZ_BESCHVOR sy-vline
WA_P01A1_DBBA_STR-KZ_GESAMTDAUER sy-vline
WA_P01A1_DBBA_STR-GRUND_1 sy-vline
WA_P01A1_DBBA_STR-GRUND_2 sy-vline
WA_P01A1_DBBA_STR-GRUND_3 sy-vline
WA_P01A1_DBBA_STR-GRUND_4 sy-vline
WA_P01A1_DBBA_STR-KZ_VERBUND sy-vline INTO ld_text SEPARATED BY SPACE. *Add any further fields from structure WA_EKKO_STR you want to CONCATENATE... ENDLOOP. ENDFORM.