topic Re: Move Corresponding and move statement in Application Development and Automation Discussions

Move Corresponding and move statement

koushikking — Thu, 14 Apr 2016 09:13:24 GMT

Hi Experts,

As per i have analysed, move corresponding is working faster than move statement but in sap forum it is mentioned move statement is faster, so please any one help on this performance wise, as am using move corresponding inside the loop of 600000 records.

Re: Move Corresponding and move statement

Former Member — Thu, 14 Apr 2016 09:17:51 GMT

What's your question in detail? If MOVE is faster or MOVE-CORRESPONDING?

Re: Move Corresponding and move statement

koushikking — Thu, 14 Apr 2016 09:28:15 GMT

Move corresponding is faster

Re: Move Corresponding and move statement

Former Member — Thu, 14 Apr 2016 09:39:59 GMT

In your case, I guess. In general MOVE should be faster because it does not need to find the corresponding fields.

Re: Move Corresponding and move statement

Former Member — Thu, 14 Apr 2016 09:42:49 GMT

Hi Koushik,

MOVE: means from move one field to other , and the field names may be different

MOVE-CORRESPONDING means both the field names in both sides are to be same.then only we use this.

MOve-Corresponding is more convinient than moving fileds individually. but this command takes more CPU time this result in poor performance.

Regards,

E.Ananthachari.

Re: Move Corresponding and move statement

pranay570708 — Thu, 14 Apr 2016 10:13:16 GMT

Don't use Move-corresponding inside the loop, move each fields separately.

As above mentioned move-corresponding checks field name between two structures to move contents to respective fields. This hampers performance. Using Move will directly transfers the value without bothering about field names.

Re: Move Corresponding and move statement

prad_k — Thu, 14 Apr 2016 10:24:57 GMT

As per i have analysed ??

Could you please tell us how you analysed the statements move and move-corresponding ?

Refer below links

https://help.sap.com/abapdocu_70/en/ABAPMOVE-CORRESPONDING.htm

Re: Move Corresponding and move statement

PeterJonker — Thu, 14 Apr 2016 11:03:42 GMT

But what if you have 20 fields. Then that would be 20 times a move statement. Wouldn't move corresponding be faster (only one statement to do by abap).

I don't know the answer, just a question that pops up reading this discussion.

By the way I almost always use move-corresponding and never had any performance issues . If I have a perfomance issue it is because of other statements. Maybe I am just lucky ?

Re: Move Corresponding and move statement

Former Member — Thu, 14 Apr 2016 11:24:03 GMT

Well, I can imagine that 20 single moves are not as good as one move corresponding, because I guess the kernal can execute the single statement quicker than the 20 statements (depending on the huge of the structure). But if there is one move statement against one move corresponding statement, the first should win the race in general.

But to improve the performance the first question should be: Can I avoid the moving (copying)?

Re: Move Corresponding and move statement

pranay570708 — Thu, 14 Apr 2016 11:35:21 GMT

when you need to move maximum fields from one structure to another, then you can go for Move-Corresponding. But only for couple of fields, Move is preferable.

Re: Move Corresponding and move statement

Former Member — Thu, 14 Apr 2016 11:56:41 GMT

Move corresponding may be faster but this is risky. This can be used if you are sure that every field name and corresponding data type is correct. Move for me is the safest way.

Re: Move Corresponding and move statement

raphael_almeida — Thu, 14 Apr 2016 12:06:05 GMT

But folks... The MOVE is considered obsolete (on SAP_ABA 7.4), instead it should use the equal sign. Of course the user who opened the issue not said component version SAP_ABA he is using, yet I think much better to use the = sign of what to do the MOVE command.

About MOVE-CORRESPONDING (still talking about 7.4), we have other ways of doing, and not think it's bad performance.

Re: Move Corresponding and move statement

koushikking — Fri, 15 Apr 2016 12:55:41 GMT

Hi Pradeep,

i have used move-corresponding inside the loop and work area contains 16 fields and structure of both work area is same.... it takes less time compare to individual 16 move statements.

Re: Move Corresponding and move statement

Former Member — Fri, 15 Apr 2016 13:01:40 GMT

Why do you use 16 individual moves, if the structure is the same and you can do it with one move? So, if you want a real comparison between MOVE (or 😃 and MOVE-CORRESPONDING use in both cases one statement.

Re: Move Corresponding and move statement

Former Member — Fri, 15 Apr 2016 14:30:20 GMT

Both are pretty efficient memory operations, so I wouldn't worry about performance. If that's your only concern, you're a mighty good troop of ABAPers.

However, from a maintenance perspective I prefer move-corresponding. You can add a field to the structure or table and it is automatically transported in memory (if you design your code well).

Wolfgang

Re: Move Corresponding and move statement

jay_kumar8 — Fri, 15 Apr 2016 15:03:45 GMT

Hi,

Move corresponding is better when you had more fields inside the loop.

Regards

Raj

Re: Move Corresponding and move statement

Former Member — Fri, 15 Apr 2016 15:57:16 GMT

I'm a little surprised that this is still being asked. Many years ago, we were taught not to use MOVE-CORRESPONDING because it was less efficient for the kernel to analyze and perform. In the intervening time, hardware became much quicker but programming costs increased, so MOVE-CORRESPONDING became much more widely accepted. I don't know if newer releases handle this statement more efficiently or not.

Rob

Re: Move Corresponding and move statement

SuhaSaha — Fri, 15 Apr 2016 16:17:00 GMT


Pranay Patel wrote:

when you need to move maximum fields from one structure to another, then you can go for Move-Corresponding. But only for couple of fields, Move is preferable.

Where exactly do you get this information from? Can you please enlighten us with the source?

Re: Move Corresponding and move statement

matt — Sat, 16 Apr 2016 05:33:24 GMT

The internals may well be more efficient with all kinds of optimisation. For example, perhaps the interpreter is smart enough to buffer the mapping so it's done only once between two object structures, and the actual moves are done in a single operation, then move-corresponding now may be faster than a bunch of moves.

If the OP has run his tests several times and got the same result that move-correspdoning is faster than move alone, then that's what he's got.

Certainly not something I'd worry about.

Re: Move Corresponding and move statement

matt — Sat, 16 Apr 2016 05:34:39 GMT

It is safer, but there's a trade-off perhaps of readability. However, in 7.4 onwards you can have the best of both worlds using CORRESPONDING operator with MAPPING.