‎2009 Apr 29 9:51 AM
Hello ,
May I know what are all the changes to be done to the programs when upgrading from 4.6c to ecc6?
Thanks
‎2009 Apr 29 10:00 AM
hi,
there is a big list of dos and dont.....
some errors are:
Syntax Error:
REPORT/PROGRAM statement missing, or program type is INCLUDE.
Unicode Error
Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not
Unicode-enabled; use the class cl_gui_frontend_services
Syntax error
TEXT E00 is not defined in text pool of ZSTEXTEM in the
original language E
Error message in ABAP Objects if the following syntax is used:
NEW-PAGE PRINT ON NO DIALOG.
Correct syntax:
DATA pripar TYPE pri_params,
arcpar TYPE arc_params.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
IMPORTING out_parameters = pripar
out_archive_parameters = arcpar
...
NEW-PAGE PRINT ON NO DIALOG
PARAMETERS pripar
ARCHIVE PARAMETERS arcpar.
The list continues................ do a google or search for documentations
ags.
‎2009 Apr 29 9:54 AM
hi,
Unicode check using transaction UCCHECK.
syntax check
code inspector check.
text element conversion.
replacement of old FM.
The basic steps are :
To upgrade the ABAP development:
Compile all programs and resolve syntax errors associated with the ABAP development.
Test the new environment and make modifications as needed.
Modify the program as per Unicode compliance (if required)
Edited by: AD on Apr 29, 2009 10:57 AM
‎2009 Apr 29 10:00 AM
>
> Unicode check using transaction UCCHECK.
> Edited by: AD on Apr 29, 2009 10:57 AM
This is not needed when upgrading to ecc 6. Its only needed when changing to a unicode system. An ecc 6 system is not necessarily a unicode system.
‎2009 Apr 29 10:04 AM
‎2009 Apr 29 10:07 AM
AD wrote:
Unicode check using transaction UCCHECK.
Edited by: AD on Apr 29, 2009 10:57 AM
This is not needed when upgrading to ecc 6. Its only needed when changing to a unicode system. An ecc 6 system is not necessarily a unicode system.
That true that we can have one-code pages script and a non-unicode system, but it makes no sense. SAP is pushing everyone to unicode for
good reason, it cuts down substantially on the amount of kernel
support they will have to do in the future as well as simplier
logistics and installation in getting patches and upgrades to
the client.
So unicode check is very essential....
Along with this there are many Function modules which are obselete. They also need to be replaced.
ags.
‎2009 Apr 29 9:55 AM
‎2009 Apr 29 10:02 AM
‎2009 Apr 29 9:59 AM
1.Initially make your programs Unicode Enabled (in Attributes)
2.By using UCCHECK txn,check for the syntax error of the program and change accordingly.
3.Have to replace obsolete functions/syntax according to ECC 6.0
4.Have to change syntax which supports ECC rather than 4.6C
‎2009 Apr 29 10:00 AM
hi,
there is a big list of dos and dont.....
some errors are:
Syntax Error:
REPORT/PROGRAM statement missing, or program type is INCLUDE.
Unicode Error
Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not
Unicode-enabled; use the class cl_gui_frontend_services
Syntax error
TEXT E00 is not defined in text pool of ZSTEXTEM in the
original language E
Error message in ABAP Objects if the following syntax is used:
NEW-PAGE PRINT ON NO DIALOG.
Correct syntax:
DATA pripar TYPE pri_params,
arcpar TYPE arc_params.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
IMPORTING out_parameters = pripar
out_archive_parameters = arcpar
...
NEW-PAGE PRINT ON NO DIALOG
PARAMETERS pripar
ARCHIVE PARAMETERS arcpar.
The list continues................ do a google or search for documentations
ags.
‎2009 Apr 29 10:00 AM