topic Re: Better replacement for Obsolete statement in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487853#M1652962 <HTML><HEAD></HEAD><BODY><P>you can use - </P><P></P><P>struc1 = struc2.</P></BODY></HTML> Mon, 19 Dec 2011 10:44:49 GMT Former Member 2011-12-19T10:44:49Z Better replacement for Obsolete statement https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487852#M1652961 <HTML><HEAD></HEAD><BODY><P>Hi ,</P><P></P><P>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 ?</P></BODY></HTML> Mon, 19 Dec 2011 10:30:49 GMT https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487852#M1652961 Former Member 2011-12-19T10:30:49Z Re: Better replacement for Obsolete statement https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487853#M1652962 <HTML><HEAD></HEAD><BODY><P>you can use - </P><P></P><P>struc1 = struc2.</P></BODY></HTML> Mon, 19 Dec 2011 10:44:49 GMT https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487853#M1652962 Former Member 2011-12-19T10:44:49Z Re: Better replacement for Obsolete statement https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487854#M1652963 <HTML><HEAD></HEAD><BODY><P>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 .</P></BODY></HTML> Mon, 19 Dec 2011 11:37:34 GMT https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487854#M1652963 Former Member 2011-12-19T11:37:34Z Re: Better replacement for Obsolete statement https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487855#M1652964 <HTML><HEAD></HEAD><BODY><PRE><CODE><P></P><P>Move-Corresponding is an obsolete statement now</P><P></P></CODE></PRE><P></P><P>Who said ????</P><P></P><PRE><CODE><P></P><P>at many places in order to correct the Unicode error we need to use the Move statement</P><P></P></CODE></PRE><P></P><P>What type of error ?</P></BODY></HTML> Mon, 19 Dec 2011 11:42:40 GMT https://community.sap.com/t5/application-development-and-automation-discussions/better-replacement-for-obsolete-statement/m-p/8487855#M1652964 kesavadas_thekkillath 2011-12-19T11:42:40Z