Queyr about move-corresponding

Hi guys,
is move-corresponding capable of moving all entries of internal table w/o headerline to another internal table?
or is it only capable of moving one entry?
thanks a lot!

Hi,
To move values between the components of structures, use the statement :
MOVE-CORRESPONDING <struct1> TO <struct2>.
This statement moves the contents of the components of structure <struct1> to the components of <struct2> that have identical names. The other fields remain unchanged.
When it is executed, it is broken down into a set of MOVE statements, one for each pair of fields with identical names, as follows:
MOVE STRUCT1-<ci> TO STRUCT2-<ci>.
Any necessary type conversions occur at this level. This process is different to that used when you assign a whole structure using the MOVE statement, where the conversion rules for structures apply.
Example :
DATA: BEGIN OF ADDRESS,
          FIRSTNAME(20) VALUE 'Fred',
          SURNAME(20) VALUE 'Flintstone',
          INITIALS(4) VALUE 'FF',
          STREET(20) VALUE 'Cave Avenue,
          NUMBER TYPE I VALUE '11'.
          POSTCODE TYPE N VALUE '98765'.
         CITY(20) VALUE 'Bedrock',
         END OF ADDRESS.
DATA: BEGIN OF NAME,
           SURNAME(20),
           FIRSTNAME(20),
           INITIALS(4),
           TITLE(10) VALUE 'Mister',
          END OF NAME.
MOVE-CORRESPONDING ADDRESS TO NAME.
Yes all the values are moved to the corresponding fields.
Hope this will help you.
Plz reward if useful.
Thanks,
Dhanashri.

Similar Messages

Move-Corresponding

Hi,
I'm just interested to know what people make of this article:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30c02051-852d-2c10-3c91-ba2bcf404510
Malcolm.

Funny noticing, though, what Matt wrote at the end of [this thread|Re: Move and "=" Difference; (MOVE vs =), on Apr 23.
>
Matt wrote:
> Not really - it's posted about once a month. Next month, you can watch the one about MOVE-CORRESPONDING.
This was more than a month and a half ago, so I guess these threads are appearing less often than they used to..

About the move corresponding

hi,
       can anyone say about the diff... between the move corresponding and move statment..
wat is the diff.. move corresponding and append stmt.. in which situation we need to use this....

Hi
Reward if help.
MOVE-CORRESPONDING wa_tab1 to wa_tab2.************ End
MOVE: wa_tab1-fld1 to wa_tab2-fld1,      wa_tab1-fld2 to wa_tab2-fld2,      wa_tab1-fld3 to wa_tab2-fld3,
Assigning Values with MOVE
To assign the value of a data object source to a variable destination, use the following statement:
MOVE source TO destination.
or the equivalent statement
destination = source.
The content of source remains unchanged, source does not therefore have to be a variable - it can also be a literal, a text symbol, or a constant. You must always specify decimal points with a period (.), regardless of the users personal settings.
Multiple assignments
f4 = f3 = f2 = f1.
are also possible. ABAP processes them from right to left as follows:
MOVE f1 TO f2.
MOVE f2 TO f3.
MOVE f3 TO f4.
In the MOVE statement (or when you assign one value to another with the equal sign), it is not possible to specify the field names dynamically as the contents of other fields. If you need to do this, you must use field symbols .
The source and target fields can be of different data types. The result of the value assignment depends on whether these data types are compatible and whether a type conversion can be performed. If there is no conversion rule between the data types in question, no assignment can be made.
DATA: t(10) TYPE c,
      number TYPE p DECIMALS 2,
      count TYPE i.
t = 1111.
MOVE '5.75' TO number.
count = number.
Following these assignments, the fields t, number and count have the values 1111      , 5.75, and 6 respectively. When you assign the number literal 1111 to T, it is converted into a character field with length 10. When you assign number to count , the decimal number is rounded to an integer (as long as the program attribute Fixed pt. arithmetic has been set).
Assigning Values Between Components of Structures
The rules for value assignments between data objects also apply to structures. With the command
DATA: struct1 TYPE structure,
      struct2 TYPE structure.
struct1 = struct2.
two structures of the same type can be assigned to one another without difficulty. Here, the entire source structure is seen as a unit and copied to the source structure. It is then possible to access the components individually again. If the structures in question are not compatible, see the conversion rules for structures.
In practice, however, you will often only need to assign certain components of a structure to be certain components of another structure. ABAP has a special statement for this purpose:
MOVE-CORRESPONDING sourcestruct TO destinationstruct.
This statement assigns the contents of the components of structure sourcestruct to the components of the destinationstruct structure that have identical names.
When it is executed, it is broken down into a set of MOVEstatements, one for each pair of fields with identical names, as follows:
MOVE sourcestruct-comp1 TO destinationstruct-comp1.
MOVE sourcestruct-comp2 TO destinationstruct-comp2.
Any necessary type conversions are performed individually.
DATA: BEGIN OF address,
        firstname(20) TYPE c VALUE 'Fred',
        surname(20) TYPE c VALUE 'Flintstone',
        initials(4) TYPE c VALUE 'FF',
        street(20) TYPE c VALUE 'Cave Avenue',
        number TYPE i VALUE '11',
        postcode(5) TYPE n VALUE '98765',
        city(20) TYPE c VALUE 'Bedrock',
      END OF address.
DATA: BEGIN OF name,
        surname(20) TYPE c,
        firstname(20) TYPE c,
        initials(4) TYPE c,
        title(10) TYPE c VALUE 'Mister',
      END OF name.
MOVE-CORRESPONDING address TO name.
In this example, the values of name-surname, name-firstname and name-initials are set to 'Flintstone, Fred, and 'FF'. name-title always has the value Mister.
Append Structure->Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
· Insert new fields in TAB,
· Define foreign keys for fields of TAB that already exist,
· Attach search helps to fields of TAB that already exist,
These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.
Pls Reward if help.

Conditional MOVE-CORRESPONDING

Hi, I need to write a piece of code to move records from one internal table to another table. I got to know about the MOVE-CORRESPONDING statement in ABAP. Now my question is: if I use the following, what will the system do:
MOVE-CORRESPONDING ITAB1 TO ITAB2.
Will all the contents of ITAB1 be moved to ITAB2? I want to add a condition to it. Is that possible?
Thanks.

Hi,
Syntax:
MOVE-CORRESPONDING <sourcestruct> TO <destinationstruct>.
This statement assigns the contents of the components of structure <sourcestruct> to the components of the <destinationstruct> structure that have identical names.
If you want to add a condition to, it is better using MOVE statement instead.
Regards,
Ferry Lianto

Move Corresponding Fields

Hi
I would like to move fields from a structure that has the following fields
data Struc1 type table1.
Fields:
BUKRS
WAERS
MENGE....
(similarly another 50 such fields)
into another structure that has following fields,
data Struc2 type table2.
Fields:
ZZ_WAERS
ZZ_MENGE
ZZ_BUKRS
The data elements linked to the fields in both the structures would be the same. Move-Corresponding will not work as the field names do not match... also the order of the fields in both the structures do not match
What is the easiest way to do this task other than moving each field one at a time?
Can I apply any field symbols concept here... please let me know

Hi Grame,
if you want to create a generic solution, you can use RTTI Runtime Type Information to determine the datatype of the components in both structures. Then you could create assignments for equal types in source and target structure.
This could work as long as you do not have more than one component of the same data type (data element) in the structures.
Something like
FIELD-SYMBOLS:
    <data1> TYPE ANY,
    <data2> TYPE ANY.
DATA:
    lo_typedescr1 TYPE REF TO cl_abap_typedescr,
    lo_typedescr2 TYPE REF TO cl_abap_typedescr.
DO.
    ASSIGN COMPONENT sy-index OF STRUCTURE itab1 TO <data1>.
    IF sy-subrc NE 0.
      EXIT.
    ELSE.
      DO.
        ASSIGN COMPONENT sy-index OF STRUCTURE itab2 TO <data2>.
        IF sy-subrc NE 0.
          EXIT.
        ELSE.
          lo_typedescr1 = cl_abap_typedescr=>describe_by_data( <data1> ).
          lo_typedescr2 = cl_abap_typedescr=>describe_by_data( <data2> ).
          IF lo_typedescr1 = lo_typedescr2.
            <data2> = <data1>.
          ENDIF.
        ENDDO.
      ENDIF.
    ENDDO.
I have some doubts about performance if you do this for every table line. It will be better to do it once, keep the results in some kind of internal assignment table and use it in the loop. For this I don't write the code, thats your homework
Regards,.
Clemens

Move n move corresponding

frends please provide me the detail document and scenarios where we use with examples about move and move corresponding statements?

Hi,
Please check this.
Assigning Values with MOVE:
To assign the value of a data object source to a variable destination, use the following statement:
MOVE source TO destination.
or the equivalent statement
destination = source.
The content of source remains unchanged, source does not therefore have to be a variable - it can also be a literal, a text symbol, or a constant. You must always specify decimal points with a period (.), regardless of the users personal settings.
Multiple assignments
f4 = f3 = f2 = f1.
are also possible. ABAP processes them from right to left as follows:
MOVE f1 TO f2.
MOVE f2 TO f3.
MOVE f3 TO f4.
Assigning Values Between Components of Structures (MOVE-CORRESPONDING):
The rules for value assignments between data objects also apply to structures. With the command
DATA: struct1 TYPE structure,
struct2 TYPE structure.
struct1 = struct2.
two structures of the same type can be assigned to one another without difficulty. Here, the entire source structure is seen as a unit and copied to the source structure. It is then possible to access the components individually again. If the structures in question are not compatible, see the conversion rules for structures.
In practice, however, you will often only need to assign certain components of a structure to be certain components of another structure. ABAP has a special statement for this purpose:
MOVE-CORRESPONDING sourcestruct TO destinationstruct.
This statement assigns the contents of the components of structure sourcestruct to the components of the destinationstruct structure that have identical names.
When it is executed, it is broken down into a set of MOVEstatements, one for each pair of fields with identical names, as follows:
MOVE sourcestruct-comp1 TO destinationstruct-comp1.
MOVE sourcestruct-comp2 TO destinationstruct-comp2.
Regards,
Ferry Lianto

Move-corresponding Doubt

Hello Experts,
I am having 10 fields in say structure s_struct1 and another structure is having 12 fields.
If i will use Move-corresponding from S_STRUCT1 TO S_STRUCT2.
insted of Move statetement 10 time for 10 different fields.
Which will take more time and how much more time?
Neno sec, Micro sec, Mili sec, Sec, mins etc.
Keep in Mind 10 move statements and 1 move-corresponding.
Target 10 field value move.
Regards,
Preeti Gupta
Message was edited by:
Preeti Gupta

The MOVE-CORRESPONDING is not performance issue. It has a slight overhead against the specified moves, this should be clear, if you think about it.
The programmed moves specify something, which the MOVE-CORRESPONDING most find out.
Use MOVE-CORRESPONDING, if you structures can change, otherwise you get an error later or you must the program again.
Don't use MOVE-CORRESPONDING if your table is buffered, because the buffer select is so fast, that the MOVE-CORRESPONDING is in the same range.
But never forget, performance is determined by indexes, not by MOVE-CORRESPONDING!
Siegfried

Which is the best way...MOVE CORRESPONDING or MOVE work are to work area

Hi Friends,
I have two internal tables.
IT1 with 20 fields.
IT2 with 17 fields.
Shall I use MOVE-CORRESPONDIN IT1 to IT2.
or I can do like the below.
IT2-FIELD1 = IT1-FIELD1.
IT2-FIELD2 = IT1-FIELD2.
IT2-FIELD3 = IT1-FIELD3.
IT2-FIELD4 = IT1-FIELD4.
IT2-FIELD5 = IT1-FIELD5.
IT2-FIELD6 = IT1-FIELD6u2026.and so on.
This is related with Performance Optimization.
Kindly suggest a solution,
Thanks.
Viji.

The runtime difference between these two is so minimal, it does not matter most of the time!
MOVE-CORRESPONDING allows for shorter and more effective program code, e.g. when a new field is introduced to a program, often it only has to be added to a global structure and becomes effective throughout the code without further changes. Think about FI document postings, SAP itselfs moves data from BKPF and BSEG to BSIS using CORRESPONDING. When you add a ZZ-field to BSEG and BSIS, the content will also show in BSIS without any code modifications!
I love CORRESPONDING, also in SELECT statements.
Thomas
P.S. when structures are the same, just a MOVE is better, obviously

Which is Performance wise better MOVE or MOVE CORRESPONDING ...

Hi SAP-ABAP Experts .
Which is Performance wise better ...
MOVE or MOVE CORRESPONDING .
Regards : Rajneesh

> A
>
> * access path and indexes
Indexes and hence access paths are defined when you design the data model. They are part of the model design.
> * too large numbers of records or executions
consider a datawarehouse environment - you have to deal with huge loads of data. a Million records are considered "small" here. Terms like "small" or "large" are depending on the context you are working in.
If you never heard of Star transformation, Partitioning and Parallel Query you will get lost here!
OLTP is different: you have short transactions, but a huge number of concurrent users.
You would not even consider Bitmap indexes in an OLTP environment - but maybe a design that evenly distributes data blocks over several files for avoiding hot spots on heavily used tables.
> * processing of internal tables => no quadratic coding
>
> these are the main performance issues!
>
> > Performance is defined at design time
> partly yes, but more is determined during runtime, you must check everything at least once. Many things can go wrong and will go wrong.
sorry, it's all about the data model design - sure you have to tune later in the development but you really can't tune successfully on a BAD data model ... you have to redesign.
If the model is good there is a chance the developers chooses the worst access to it , but then you have the potential to tune with success because your model allows for a better access strategy.
The decisions you make in the design phase are detemining the potential for tuning later.
>
> * database does not what you expect
I call this the black box view: The developer is not interested in the underlying database.
Why we have different DB vendors if they would all behave the same way? I.e. compare concurrency
and consistency implementations in various DB's - totally different. You can't simply apply your working knowledge from one database to another DB product. I learned the hard way while implementing on INFORMIX and ORACLE...

About move statement in abap.

move-corresponding is only for structure or also for internal table?
if you know please some details.

Hi,
To move values between the components of structures, use the statement
MOVE-CORRESPONDING <struct1> TO <struct2>.
This statement moves the contents of the components of structure <struct1> to the components of <struct2> that have identical names.
When it is executed, it is broken down into a set of MOVE statements, one for each pair of fields with identical names, as follows:
MOVE STRUCT1-<ci> TO STRUCT2-<c i>.
Regards
Sudheer

Move-corresponding in table type Field-Symbols

Hi,
    I have to use one statement in field-symbol similar to "move-corresponding" in normal internal table.Is it possible to use statement similar to "Move-corresponding in field-symbols".
For Eg:
Field-symbols <FA_IT> type standard table.
data:begin of wa_ekk,
   f1 type i,
   f2 type werks_d,
   f4 type posnr,
   end of wa_ekk,
it_ekk like standard table of wa_ekk.
begin of wa_final,
   f1 type i,
   f2 type werks_d,
   f3 type i,
   f4 type n,
end of wa_final,
it_final like standard table of wa_final.
assign it_ekk to <fs_it>.
Loop at <fs_it>.
*???????-i dont know how to move the value to it_final
*---I know I can use assign component statement
*-to move each field to the target field
but for that we need to know the field name or index position of the structure-
Endloop.
My requirment is now i want to move the content of <fs_it> into it_final internal table.
I know that In normal itab we can use "move-corresponding" to move the value from it_ekk to it_final.
In the same way how to use it in field-symbol concept.
Requirement:Real time Processing of Internal table
1) Content of it_ekk:
f1   f2       f4
12 1000 0023
23 2000 0037
2)After ASSIGN statement:
Content of <fs_it> is:
f1   f2       f4
12 1000 0023
23 2000 0037
3)Now I want to move the content of <fs_it> to it_final
Output of It_final:
F1   F2    F3    F4
12 1000   ---    0023
23 2000   ---    0037
Regards,
Vigneswaran S

Andrey's code is going to work only if you are running it in a non-unicode system.
See code below for a Unicode system using similar effect to "Move-Corresponding" statement.
FIELD-SYMBOLS: <fs_ekk> LIKE wa_ekk,
               <fs_final> LIKE wa_final.
ASSIGN it_ekk TO <fs_it> .
LOOP AT <fs_it> ASSIGNING <fs_ekk>.
ASSIGN <fs_ekk> TO <fs_final> CASTING.
CLEAR <fs_final>-f3.
APPEND <fs_final> TO it_final.
ENDLOOP.
Hope this solves your problem and please don't forget to reward points.
Cheers,
Sougata.

Change "MOVE-CORRESPONDING" statement to MOVE statement in FM

Hello Guys,
I have created a datasource based on FM standard template RSAX_BIW_GET_DATA. In the source code in this template, there is a LOOP statement and below that there is a "MOVE-CORRESPONDING" statement.
LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'PGMID'.
MOVE-CORRESPONDING l_s_select TO l_r_pgmid.
APPEND l_r_pgmid.
ENDLOOP.
My customer does not allow MOVE-CORRESPONDING statement for performance reasons. Hence I need to change it to MOVE statement. But I do not know the structure of l_s_select and I am not well at ABAP. So How do I write MOVE statement here.
Can anybody help on this?
Regards
Utpal

Hi Tibollo,
Thanks for your prompt reply. Your suggestion has solved my problem. One input to this from my side. It will not accept FIELDNM because it is not present in l_r_pgmid. Remind you l_r_pgmid is declard as a range and ranges does not have FIELDNM.
Anyway, that portion I have modified and it worked. Thanks a lot. I am rewarding u points.
Regards
Utpal

Problem with move-corresponding

Hi,
I have these codes below:
TYPES: BEGIN OF t_employee1,
        carrid LIKE spfli-carrid,
        connid LIKE spfli-connid,
        countryfr LIKE spfli-countryfr,
      END OF t_employee1.
DATA: i_employee TYPE STANDARD TABLE OF spfli WITH HEADER LINE,
      i_employee1 TYPE STANDARD TABLE OF t_employee1 WITH HEADER LINE.
SELECTION-SCREEN BEGIN OF BLOCK b1.
SELECT-OPTIONS: s_carrid FOR spfli-carrid.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
SELECT * FROM spfli INTO TABLE i_employee
WHERE carrid IN s_carrid.
    MOVE-CORRESPONDING i_employee TO i_employee1.
But when i debug the program, carrid, connid and countryfr of i_employee do not move to i_employee1...
is there somethig wrong with my codes???
Thanks a lot!

Change ur code as shown below:
TYPES: BEGIN OF t_employee1,
carrid LIKE spfli-carrid,
connid LIKE spfli-connid,
countryfr LIKE spfli-countryfr,
END OF t_employee1.
DATA: i_employee TYPE STANDARD TABLE OF spfli WITH HEADER LINE,
i_employee1 TYPE STANDARD TABLE OF t_employee1 WITH HEADER LINE.
SELECTION-SCREEN BEGIN OF BLOCK b1.
SELECT-OPTIONS: s_carrid FOR spfli-carrid.
SELECTION-SCREEN END OF BLOCK b1.
START-OF-SELECTION.
SELECT * FROM spfli INTO TABLE i_employee
WHERE carrid IN s_carrid.
if sy-subrc = 0.
loop at i_employee.
MOVE-CORRESPONDING i_employee TO i_employee1.
append i_employee1.
endloop.

Statement not accesible : "MOVE-CORRESPONDING ebkn TO *ebkn."

hi guys,
(system upgraded from 4.6 to 6.0 and made unicode compatible)
thr r two problems........
1. "MOVE-CORRESPONDING ebkn TO *ebkn." is not accessible, is it something related to mirror image......... how to resolve this.
2. Refresh it_tab - "Refresh and clear statements are not accesible" .
These are present inside includes..... ( is it somewhere related to use of subroutines prior to the use of refresh or clear statement......)
Those tables are defined prior to the statement Refresh or Clear.......

Hi Mohd,
please paste error message(s) in detail:
source name(s)
source line(1)
full error message including message class, type and number
If you get W messages (warnings), you may ignore them.
Regards,
Clemens

Syntax of move corresponding

hi
Can anyone give me the syntax of move corresponding.
I even want to know wat does this exactly do.
Can I have some sample sof move corresponding.
Its urgent.U'll get points.
Thanking you
Chandrika.

hi,
MOVE-CORRESPONDING
Basic form
MOVE-CORRESPONDING struc1 TO struc2.
Effect
Interprets struc1 and struc2 as structures. If, for example, struc1 and struc2 are tables, it executes the statement for their header lines.
Searches for the sub-fields which occur both in struc1 and struc2 and then generates, for all relevant field pairs which correspond to the sub-fields ni, statements of the form
MOVE struc1-ni TO struc2-ni.
The other fields remain unchanged.
With complex structures, the full names of the corresponding field pairs must be identical.
Example
DATA: BEGIN OF INT_TABLE OCCURS 10,
        WORD(10),
        NUMBER TYPE I,
        INDEX LIKE SY-INDEX,
      END   OF INT_TABLE,
      BEGIN OF RECORD,
        NAME(10) VALUE 'not WORD',
        NUMBER TYPE I,
        INDEX(20),
      END   OF RECORD.
MOVE-CORRESPONDING INT_TABLE TO RECORD.
This MOVE-CORRESPONDING statement is equivalent to both the following statements:
MOVE INT_TABLE-NUMBER TO RECORD-NUMBER.
MOVE INT_TABLE-INDEX TO RECORD-INDEX.
Example
TYPES: BEGIN OF ROW1_3,
         CO1 TYPE I,
         CO2 TYPE I,
         CO3 TYPE I,
       END   OF ROW1_3.
TYPES: BEGIN OF ROW2_4,
         CO2 TYPE I,
         CO3 TYPE I,
         CO4 TYPE I,
       END   OF ROW2_4.
TYPES: BEGIN OF MATRIX1,
         R1 TYPE ROW1_3,
         R2 TYPE ROW1_3,
         R3 TYPE ROW1_3,
       END OF   MATRIX1.
TYPES: BEGIN OF MATRIX2,
         R2 TYPE ROW2_4,
         R3 TYPE ROW2_4,
         R4 TYPE ROW2_4,
       END OF   MATRIX2.
DATA: ROW TYPE ROW1_3,
      M1 TYPE MATRIX1,
      M2 TYPE MATRIX2.
ROW-CO1 = 1. ROW-CO2 = 2. ROW-CO3 = 3.
MOVE: ROW TO M1-R1, ROW TO M1-R2, ROW TO M1-R3.
MOVE-CORRESPONDING M1 TO M2.
The last MOVE-CORRESPONDING statement is equivalent to the statements:
MOVE: M1-R2-CO2 TO M2-R2-CO2,
      M1-R2-CO3 TO M2-R2-CO3,
      M1-R3-CO2 TO M2-R3-CO2,
      M1-R3-CO3 TO M2-R3-CO3.
Note
The same runtime errors may occur as with MOVE.
Note
This statement assigns values based on pairs of fields with identical names. To avoid unwanted assignments, you should consider all fields of the source and target structures. If either is defined with reference to an ABAP Dictionary type (for example, a database table), remember that any subsequent extension to the type could cause coincidental pairs of identically-named fields, which could lead to incorrect program logic.
Regards,
Sourabh

Queyr about move-corresponding

Similar Messages

Maybe you are looking for