ABAP Select data from SAP table FS4BPU_S_BP_RELATIONSHIP_DATA 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 FS4BPU_S_BP_RELATIONSHIP_DATA 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 FS4BPU_S_BP_RELATIONSHIP_DATA. 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 FS4BPU_S_BP_RELATIONSHIP_DATA 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_FS4BPU_S_BP_RELATIONSHIP_DATA TYPE STANDARD TABLE OF FS4BPU_S_BP_RELATIONSHIP_DATA,
      WA_FS4BPU_S_BP_RELATIONSHIP_DATA TYPE FS4BPU_S_BP_RELATIONSHIP_DATA,
      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: <FS4BPU_S_BP_RELATIONSHIP_DATA> TYPE FS4BPU_S_BP_RELATIONSHIP_DATA.

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

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

*Select data and declare internal table using in-line method @DATA
*SELECT *
*  FROM FS4BPU_S_BP_RELATIONSHIP_DATA
*  INTO TABLE @DATA(IT_FS4BPU_S_BP_RELATIONSHIP_DATA2).
*--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_FS4BPU_S_BP_RELATIONSHIP_DATA INDEX 1 INTO DATA(WA_FS4BPU_S_BP_RELATIONSHIP_DATA2).


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

*To update a field value using a field symbol simply change the value via the field symbol pointer
<FS4BPU_S_BP_RELATIONSHIP_DATA>-PARTNER1 = 1.
<FS4BPU_S_BP_RELATIONSHIP_DATA>-BPARTNER = 1.
<FS4BPU_S_BP_RELATIONSHIP_DATA>-BPARTNERGUID = 1.
<FS4BPU_S_BP_RELATIONSHIP_DATA>-IDENTIFICATIONCATEGORY = 1.
<FS4BPU_S_BP_RELATIONSHIP_DATA>-IDENTIFICATIONNUMBER = 1.

ENDLOOP.

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

*Write selected data to screen/report before conversion.
  WRITE:/ sy-vline,   WA_FS4BPU_S_BP_RELATIONSHIP_DATA-PARTNER2, sy-vline,
  WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNER, sy-vline,
  WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNERGUID, sy-vline,
  WA_FS4BPU_S_BP_RELATIONSHIP_DATA-IDENTIFICATIONCATEGORY, sy-vline,
  WA_FS4BPU_S_BP_RELATIONSHIP_DATA-IDENTIFICATIONNUMBER, sy-vline,
  WA_FS4BPU_S_BP_RELATIONSHIP_DATA-RELAT_CATEGORY, sy-vline.
ENDLOOP.
   
*Add any further fields from structure WA_FS4BPU_S_BP_RELATIONSHIP_DATA 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_FS4BPU_S_BP_RELATIONSHIP_DATA 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_FS4BPU_S_BP_RELATIONSHIP_DATA INTO WA_FS4BPU_S_BP_RELATIONSHIP_DATA.


*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 BPARTNER
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
  EXPORTING
    input =                      WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNER
  IMPORTING
    output =                     ld_input.
WRITE:/ 'Org Value:', WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNER.
WRITE:/ 'New Value:', ld_input.

*Conversion exit ALPHA, internal->external for field BPARTNER
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
  EXPORTING
    input =                      WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNER
  IMPORTING
    output =                     ld_input.
WRITE:/ 'Org Value:', WA_FS4BPU_S_BP_RELATIONSHIP_DATA-BPARTNER.
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_FS4BPU_S_BP_RELATIONSHIP_DATA_STR, 
PARTNER1 TYPE STRING,
BPARTNER TYPE STRING,
BPARTNERGUID TYPE STRING,
IDENTIFICATIONCATEGORY TYPE STRING,
IDENTIFICATIONNUMBER TYPE STRING,
PARTNER2 TYPE STRING,
BPARTNER TYPE STRING,
BPARTNERGUID TYPE STRING,
IDENTIFICATIONCATEGORY TYPE STRING,
IDENTIFICATIONNUMBER TYPE STRING,
RELAT_CATEGORY TYPE STRING,
DATE_FROM TYPE STRING,
DATE_TO TYPE STRING,END OF T_EKKO_STR.
DATA: WA_FS4BPU_S_BP_RELATIONSHIP_DATA_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_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-PARTNER1 sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-BPARTNER sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-BPARTNERGUID sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-IDENTIFICATIONCATEGORY sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-IDENTIFICATIONNUMBER sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-PARTNER2 sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-BPARTNER sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-BPARTNERGUID sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-IDENTIFICATIONCATEGORY sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-IDENTIFICATIONNUMBER sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-RELAT_CATEGORY sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-DATE_FROM sy-vline 
WA_FS4BPU_S_BP_RELATIONSHIP_DATA_STR-DATE_TO sy-vline      INTO ld_text SEPARATED BY SPACE.

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