This is particularly useful if you require the retrieval of the same data from two different database tables, in which case you can use two SELECT INTO and then an APPEND LINES OF to combine your data. When combining tables of the same structure, instead of looping through one table and appending the records to the other table, use this command that transfers the whole table in one operation. WARNING Be aware that when using the AT statements, the order of the fields in your table or field-group is extremely important, if a field ‘higher up’ (further to the left) changes it will also trigger the AT statement on any field ‘lower down’ (further to the right).ĪPPEND LINES OF. This means performing the operation within the ON CHANGE OF and AT NEW or AT END statements. If you are to perform an action on a field, remember to only perform the action when the value of the field changes and store the result. In loops, only perform operations as necessary. WHERE command instead of a loop and then an IF or a CHECK statement. If you only wish to process certain entries of your internal table, use the LOOP AT. Reads from normal unsorted internal tables have an order N time dependency (where N is the number of records), whereas sorted tables read with the command BINARY-SEARCH have a logarithmic time dependency (Log N), and hashed tables have a constant time dependency regardless of the number of records. Sorted and Hashed tables: Following on from above, if you wish to reference a table several times within a program it is good practice to keep it sorted or to use a hashed table. If you only wish to retrieve a certain record from a table it is much more efficient (especially if the table is sorted) to use a READ WITH KEY or a READ INDEX on the table than looping until the record is found. The only situation where this may not be possible is where subsequent processing depends on the whole table having been processed previously (if the operations are linearly dependent they can still be done within the same loop). Seek to combine operations on an internal table so that they can all be processed in the one loop. Your program should be structured so that your internal tables are processed only once, if possible.
( LINES OF COND ty_table( WHEN var->* NE `` THEN VALUE #( ( var->* ) ) ) ) ).Processing tables only once. Or another possibility like the first one, but without repeating the variable names: TYPES ty_vars TYPE STANDARD TABLE OF REF TO string WITH EMPTY KEY.įOR var IN VALUE ty_vars( ( REF #( lv_var_1 ) ) ( REF #( lv_var_2 ) ) ( REF #( lv_var_3 ) ) ) Or the same principle but less legible with constructor expressions: Data(lt_table) = value ty_table(įOR IN VALUE ty_table( ( lv_var_1 ) ( lv_var_2 ) ( lv_var_3 ) ) ( lv_var_1 ) ( lv_var_2 ) ( lv_var_3 ) ).ĭELETE lt_table WHERE table_line IS INITIAL.
#SAP APPEND LINES OF ITAB TO ITAB CODE#
( LINES OF cond ty_table( WHEN lv_var_3 is not initial THEN VALUE #( ( lv_var_3 ) ) ) ) ).īut you may realize that the code is not legible, other codes are possible like adding all the lines then deleting the initial lines: DATA(lt_table) = VALUE ty_table( ( LINES OF cond ty_table( WHEN lv_var_2 is not initial THEN VALUE #( ( lv_var_2 ) ) ) )
( LINES OF cond ty_table( WHEN lv_var_1 is not initial THEN VALUE #( ( lv_var_1 ) ) ) ) Ty_table type standard table of string with default key. The direct answer to your question is to use LINES OF so that to append an arbitrary number of lines from an intermediate internal table, which can be potentially empty (0 line added) or not (any number of lines, in your case 1 line): types:
0 kommentar(er)
