Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Better replacement for Obsolete statement

Former Member

‎2011 Dec 19 10:30 AM

0 Likes
1,595

Hi ,

During upgradation to ECC 6.0 , at many places in order to correct the Unicode error we need to use the Move statement. Since the Move-Corresponding is an obsolete statement now , so we can't use it any more. It is very difficult and highly time consuming to move huge structures and internal tables field by field . Is there any alternative to this ?

Hi ,

During upgradation to ECC 6.0 , at many places in order to correct the Unicode error we need to use the Move statement. Since the Move-Corresponding is an obsolete statement now , so we can't use it any more. It is very difficult and highly time consuming to move huge structures and internal tables field by field . Is there any alternative to this ?

Reply
3 REPLIES 3
Read only

Former Member

‎2011 Dec 19 10:44 AM

0 Likes
1,109

you can use -

struc1 = struc2.

Read only

Former Member
In response to Former Member

‎2011 Dec 19 11:37 AM

0 Likes
1,109

Yes , we can use that way . BUT it will take a lot of time if there are 250 fields of different structures needed to be moved . Thats the problem.There is not a single program where I have to remediate like this . Minimum 20 programs. So I was looking for a way more useful and less time consuming in such a scenario .

Read only

kesavadas_thekkillath
Active Contributor

‎2011 Dec 19 11:42 AM

0 Likes
1,109 
Move-Corresponding is an obsolete statement now

Who said ????

at many places in order to correct the Unicode error we need to use the Move statement

What type of error ?