Upgrade from 46C to ERP 2005

Can you help me with some questions?
We are going to upgrade from 46C to 6.0 and we have questions.
1. How much do we expect the database to grow when we
   change the format?.
2. What are the minimum requirements of the workstations
   with the new version?
3. How the change of EBCDIC to ASCII can affect of Disck
   load?.
4. What percentage grow the data, when this is changed to
   ASCII?
5. How the changed to ASCII affect the server.?
6. Is necessary grow in memory and CPU?
7. Is possible install several application server Intel
   with the AS/400 Data base, once the changed to ASCII?
8. Is affected the performance of the system is we
   installing hard disk of 30GB with hard disk of 70GB?
9. What is the impact if we made the upgrade with Unicode
   or No Unicode?

Hi,
Detailed info can be found at
https://service.sap.com//upgrade
and
https://service.sap.com/instguides
Eddy
PS.
Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.
Spread the wor(l)d!

Similar Messages

Error in Prepare Upgrade from 46C to ERP 2005 - R3trans too old

I have seen a few threads on this issue, but I am still slightly puzzled.
The error message in Prepare ( initialisation - 02 ) is that the R3trans is too old, it needs to be at least 07/05/2007.
The version of R3trans in the put directory is a 46D one ( 6.05 ) and the date is previous to that mentioned, however the most recent version of the 46D that I can download is the 22/04/2007 and you will get the same error.
Ther error seems odd in that it would normally complain about the version rather than a date and it is happy about tp etc.
I could download a more recent version of R3trans, but that would be a 6.40 or 7.0 !
I have the FIX_ERP2005SR2.UPG in /usr/sap/put.
Has anybody tripped over this issue ? Cheers

The 46D R3trans was a bit of a red herring, however I do have a problem.
The 7.00 kernel goes into \usr\sap\put\exe etc and it is a 7.00 R3trans ( 6.14 ). When the initialisation phase is run ( 2 ), it complains that the R3trans is too old and it quotes 07/05/2007.
If I download the newest version of R3trans it fails with a connect problem. For some reason it goes off to /usr/sap/SID/SYS/exe/run to reference the dboraslib.dll, while the earlier version of the 7.0 R3trans references it within /usr/sap/put.
It could be something like Oracle Client environmental settings !
Anybody had this issue ?
Cheers
The R3trans was R3trans_119-20000961.SAR
ETW000 D:\usr\sap\put\exe\R3trans.exe version 6.14 (release 700 - 10.07.07 - 13:48:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 08.08.2007 - 17:45:45
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: D:\usr\sap\put\exe\R3trans.exe -d -w D:\usr\sap\put\log\DBCONNCHK.LOG
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Wed Aug 08 17:45:45 2007                               0 0.000000
4 ETW000 [dev trc     ,00000] db_con_init called                                     0 0.000000
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                              0 0.000000
4 ETW000 [dev trc     ,00000] Loading DB library 'dboraslib.dll' ...                 0 0.000000
4 ETW000 [dev trc     ,00000] load shared library (dboraslib.dll), hdl 0          5202 0.005202
4 ETW000 [dev trc     ,00000]      using "D:\usr\sap\DV2\sys\exe\run\dboraslib.dll"
4 ETW000                                                                              20 0.005222
4 ETW000 [dev trc     ,00000] Library 'dboraslib.dll' loaded                         8 0.005230
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library dboraslib.dll
4 ETW000                                                                              14 0.005244
4 ETW000 [dbcon.c     ,00000] *** ERROR => Version mismatch between kernel (700.08) and DBSL shared library (46D.00)
4 ETW000                                                                              32 0.005276
2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

CU & UC from 46c to ERP 2005

Hi,
I am in Planning phase for CU & UC from 46c to ERP 2005 need to know few things
- Hardware requirement for Unicode preparation system - CPU/ Memory and Storage - I am planning to use Copy of Prod for Unicode prep system : My prod DB is 1TB.. Which SAP verion is recommanded for Unicode Prep- 4.7 on 620 or directely ERP2004 / 640 or ERP 2005700
- Storage requirement for Export dump for 1TB database ??
- Approximate Timing to export / import -- I know it depends on CPU's/ memory etc os source/ target ... in general ??
- SAP suggest 10-30% increase in Memory - any comments ?
- SAP suggest 40-50% increase CPU usage - any comments ?
One last question :
i am planning to use parallel landscape for this for non-prod but Prod I am planning to use same hardware as it is today. any comments on this idea ?
Awating response from experts... thanks in advance....
Jignesh

Hello Jignesh,
>> I am planning to use Copy of Prod for Unicode prep system : My prod DB is 1TB.. Which SAP verion is recommanded for Unicode Prep- 4.7 on 620 or directely ERP2004 / 640 or ERP 2005700
As you told you have 4.6c ... why are you want to make a copy of the prod system? You can make all preparations for that in the "Live"-system and upgrade directly to ERP 2005 (take a look at sapnote #928729). After that you can make the unicode conversion... i have done a CU&UC for 4.6c to ERP 2005 ... the steps are:
1) Make preparations in 4.6c
2) Upgrade your 4.6c to ERP 2005
3) Make the unicode conversion
4) Make After-Steps
>> Storage requirement for Export dump for 1TB database ??
I have exported a 2.4 TB database.. the export data was round about 550 GB
>> Approximate Timing to export / import -- I know it depends on CPU's/ memory etc os source/ target ... in general ??
There is no general.. in my experience it depends on the biggest tables (if you export parallel) and the cpu for the convertion. I have used distribution monitor and table splitting to get good export times. Only to say some values.. i needed round about 13 hours for exporting and importing the 2.4 TB database with the distribution monitor (package & table splitting)
>> SAP suggest 10-30% increase in Memory - any comments ?
>> SAP suggest 40-50% increase CPU usage - any comments ?
I have seen that the memory is really a big topic.. but the CPU was not as expected... but this also depends on the amount of parallel users. In my experience memory +40% and cpu +25%.
Regards
Stefan

Upgrade from 46c to ECC6.0 : Java or Java-AddIn ?

Hello
Can you explain me what is the difference between Java and Java-AddIn as proposed in evaluation phsae of an upgrade from 46c to ECC6.0?
Thank You.

Hi Alain,
But if we implement a JavaAddin solution today, do you think it will be possible to create a Java instance later to create a Portal solution ?
If you implement a java addin today then you can use later for portal solution.
Regards,
Anil

Error in upgrade from 46c to ecc 6.0

hi experts,
we are facing an error at the time of upgrade from 46c to ecc 6.0 in the phase JOB_RSUPGAIMEXE.
did anyone face this error anytime during upgrade on windows plotform?
Please let us know your comments..
regards
raghu

Hello,
Can you please look in the /put/log directory and copy the error from the appropriate log file. You should find a log file with a name similar the to upgrade phase that is causing the error.
Thanks
N.P.C

Open dataset for input don't work after upgrade from 46C to 47

We did an upgrade from 46C to 47, after that all the Z programs that have the sentence "open dataset for input" alwas send a sy-subrc = 8, the curios things is that the sentece "open dataset for output" works ok.
Please I need help to solve this?
En example of code.
PARAMETERS: P_ARCHF(60) OBLIGATORY DEFAULT
'C:\20050900.txt' LOWER CASE.
OPEN DATASET P_ARCHF FOR INPUT IN TEXT MODE.
IF SY-SUBRC <> 0. MESSAGE i001 WITH ARCHIVO. stop. endif.

Well, it's telling you that the datset doesn't exist. From the help in 4.7:
OPEN DATASET
Addition 1a
... FOR INPUT
Effect
OPEN ... FOR INPUT opens the file in read mode.
If the file does not exist, OPEN ... FOR INPUT fails with Return Code SY-SUBRC = 8.
Note
If OPEN DATASET is not executed in a Unicode program and if the user has write authorization for the file, the file is opened in read and write mode. Otherwise, it is only opened in read mode.
Rob

Upgrade from 46C to ECC 6

Hello:
We are planning to begin technical upgrade in SAP, from 46C to ECC 6.0.
I have the next landscape:
-Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
-New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
We want to install SAP ECC 6.0 in NS and get the data from CS.
Which is the best and easy way to do this? SAP manuals are quite generic. I have two ideas but I would like your comments:
1st way
1. Homogeneous copy of CS
2. I install ECC 6.0 in NS with the option to import data generated in 1. (is this possible??)
3. Finish installation and aditional configurations. I begin to test.
2nd way
1. Homogeneous copy of CS
2. I install 4.6C in NS with the option to import data generated in step 1. (Not sure if 4.6C will accept Solaris 10 and Oracle 10.2).
3. I suppose I don't need to reconfigure after installation and import.
4. I do necessary tests. At this point I would have 46C on the new versions of Solaris and Oracle.
5. I begin the SAP upgrade to ECC 6.0 in NS
6. .... The remaining processes indicated by SAP
Thanks for your attention.

> -Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
> -New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
The database software is usually installed during the run of sapinst/R3setup, not before. You may run into problems if you pre-install Oracle (environment, necessary database options not set etc.)
The easiest way would be do to a system copy.
I would then
- install the latest Oracle instantclient
- install the latest kernel 46D_EX2 kernel
Markus

Short dump in MIGO and VL02N when upgrading from 46C to ECC 6.0

Hello,
We are doing an upgrade from R/3 46C to ECC 6.0 and we face a shortdump in trx MIGO (upon saving the document).
DBIF_RSQL_INVALID_REQUEST
a BKPF_INSERT in program SAPLF005
The same shortdump happens when doing a Goods Issue on the SD side.
Looking at the program, this is not modyfied so I guess it is a standard SAP error.
OSS however, up to know did not respond to my message and there does not seem to be a SAP Note on this issue!
Anyone had this problem before. How did they solve it.
Thanks for any reply,
Aart

Posted in another forum

Upgrade from 46c to ECC 6.0 new components support package

dear experts,
we have upgraded our test system from 46C to ECC 6.0
before upgrade in 46C we have support packages components
SAP_BASIS 46C
SAP_ABAP 46C
SAP_APPL 46C
SAP_HR
PI 2003_1_46C
SAP_NOTES 46C
ST-A/PI 01B_R3_46C
ST-PI 2005_1_46C
after upgrade to ECC 6.0 we found
SAP_ABA 700 0006
SAP_BASIS 700 0006
ST-PI 2005_1_700 0001
PI_BASIS 2005_1_700 0006
SAP_BW 700 0006
SAP_AP 700 0003
SAP_HR 600 0003
SAP_APPL 600 0003
EA-IPPE 400 0003
EA-HR 600 0003
EA-GLTRADE 600 0003
EA-PS 600 0003
EA-RETAIL 600 0003
EA-FINSERV 600 0003
EA-DFPS 600 0003
EA-APPL 600 0003
FINBASIS 600 0003
ECC-DIMP 600 0003
ERECRUIT 600 0003
FI-CA 600 0003
FI-CAX 600 0003
INSURANCE 600 0003
IS-CWM 600 0003
IS-H 600 0003
IS-M 600 0003
IS-OIL 600 0003
IS-PS-CA 600 0003
IS-UT 600 0003
LSOFE 600 0003
SEM-BW 600 0003
we are planning to apply SPS 06. Is it mandatory we have to apply
all the support packages in SPS 06.
we are confused as we dont use IS-OIL,EA-,ERECUIT,INSURANCE,FI-
please suggest which support packages we have apply relating to the
functionality we have in 46C
regards
Raghu

Hi,
you have to apply the same type of packages as before.
All other are included in ECC, but if you don't use the special services and applications (for example IS Oil or stuff like this), there is no need to apply all these packages.
SAP_ABA 700 0006
SAP_BASIS 700 0006
ST-PI 2005_1_700 0001
PI_BASIS 2005_1_700 0006
SAP_AP 700 0003
SAP_HR 600 0003
SAP_APPL 600 0003
should be enough
Regards
Timm

Upgrading from 46C to ECC 7.0

Guys,
My company is going to upgrade R/3 46C to ECC 7.0 later this year. From the development (ABAP programs, any ABAP objects) standpoint, any suggestions on preparation, or what can be done in our current 46C environment to ensure a smooth transition from 46C to ECC (unicode, obsolete ABAP syntax, etc)? Also any idea and recommendation on planning the upgrade, as well as things to watch out for are welcome.
Thanks,
Yan.

First ECC 7.0 does not exist, so you will be upgrading to ECC 6.0. And yes, you can start by doing a start for any calls to WS_UPLOAD and WS_DOWNLOAD. You will need to change these calls to call the GUI_UPLOAD or GUI_DOWLOAD function modules.
Other syntax issues will need to be handled after the upgrade, like using the ECODING extension on all OPEN DATASET statements.
Regards,
Rich Heilman

Upgrade from 46C to ECC600 terminates in phase SHADOW_IMPORT_INC

The upgrade of our develoment/test system terminates in phase
SHADOW_IMPORT_INC. We got the message 27 errors detected and 3
activities have been aborted.
Below you'll find the entries as they are in log file SHDALLIMP.ELG.
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKA70007.DV0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function:   db_report_interface_ext
2EETW000 fcode:      TOUCH_REPORT
2EETW000 tabname:    SOURCE
2EETW000 len:        40
2EETW000 key:        CL_AC_BADI_MNT_BRF============CP
2EETW000 retcode:    1
2EETW125 SQL error "208" during "" access: "[208] Invalid object name 'D010SINF~'.
1 ETP111 exit code           : "12"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKAAA700.DV0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKB70007.DV0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function:   db_report_interface_ext
2EETW000 fcode:      TOUCH_REPORT
2EETW000 tabname:    SOURCE
2EETW000 len:        40
2EETW000 key:        CLUR_NW5_FACTORY==============CP
2EETW000 retcode:    1
2EETW125 SQL error "208" during "" access: "[208] Invalid object name 'D010SINF~'.
1 ETP111 exit code           : "12"
In this log file (shadow) table D010SINF~ is mentioned.
I have looked in SQL Enterprise Manager and can't find this table.
We are upgrading from release 46C to ECC6.0
We are running on Windows 2003 Server with SQL Server 2000 SP4 patch 2040
Anybody any clue how to solve this?.
Thanks in advance.
Kind regards,
Dave Arends

Hi Michael,
I did use the latest r3trans (patch 86), tp.exe (patch 86) and dbmssslib (patch81). But in the meantime there were new patches of r3trans and dbmssslib. Both version 87. Now it is working.
Thanks.
Kind regards,
Dave Arends

Upgrade from SQL 2000 to 2005

In our test environment, we are on 2005 SP01 PL34, and are
upgrading SQL Enterprise Edition from the 2000 to the 2005 SP2 edition.
The SQL upgrade advisor has given some error messages
in relation to SAP tables, as per below. Should we be concerned about
these, or will they have any effect on upgrading from SAP B1 2005 to
2007 versions?
Remove references to undocumented system tables
Many system tables that were undocumented in prior releases have changed or no longer exist; therefore, using these tables may cause errors after upgrading to SQL server 2005.
Affected tables
Object Name : TmSP_GetDbSizeByDrives
Object Type : P
System Table : spt_value
Object Name : TmSP_CheckDiskSpace
The above messages point to SAP stored procedures.

I believe all those SP are temporary SP for you previous upgrade. Therefore. it should be no problem to upgrade your test database first. You have to back up the pre upgrade database anyway, you should be safe.
Thanks,
Gordon

Problem with FIELD SYMBOL upgrading from 46c to ECC6.0

Hi people... i'm having big trouble making an upgrade from 4.6c to ECC6.0 with this portion of code of Z's programm.
In the line
ASSIGN (w_field) TO <fs_field>.
i don't see any assigment, so <fs_field> remains empty, when enters into firts IF conditions it is TRUE, then go into second IF condition, it is FALSE, and finally assing
<fs_field> = '/'.
, at this point i have a DUMP telling me MOVE_TO_LIT_NOTALLOWED_NODATA
I'm try any way of definition, assigment, but always i have a DUMP.
Someone can give a hand with this issue!
Thanks in advance!!!
This is the full code from the FORM with the problem.
*       FORM GRABA                                        *
* --> VALUE(P_TABLE)                                  *
FORM graba USING value(p_table) TYPE c.
DATA:
    w_field(60),
    w_dd03l TYPE dd03l.
FIELD-SYMBOLS <fs_field>.
CLEAR w_flag.
CASE p_table.
    WHEN 'BGR00'.
      d_bgr00-group = w_batin.
      d_bgr00-mandt = sy-mandt.
      d_bgr00-usnam = sy-uname.
      d_bgr00-xkeep = 'X'.
      d_bgr00-nodata = '/'.
      d_bgr00-stype = 0.
      TRANSFER d_bgr00 TO w_fname.
    WHEN 'BBKPF'.
      LOOP AT gt_dd03l INTO w_dd03l WHERE tabname EQ p_table.
        CONCATENATE
            'd_'
            w_dd03l-tabname
            w_dd03l-fieldname
          INTO w_field.
        ASSIGN (w_field) TO <fs_field>.
        IF <fs_field> IS INITIAL OR <fs_field> EQ '/'.
          IF w_dd03l-fieldname EQ 'TBNAM'.
            <fs_field> = p_table.
          ELSE.
            <fs_field> = '/'.
          ENDIF.
        ELSE.
          w_flag = 'X'.
        ENDIF.
      ENDLOOP.
      TRANSFER d_bbkpf TO w_fname.
    WHEN 'BBSEG'.
      LOOP AT gt_dd03l INTO w_dd03l WHERE tabname EQ p_table.
        CONCATENATE
            'd_'
            w_dd03l-tabname
            w_dd03l-fieldname
          INTO w_field.
        ASSIGN (w_field) TO <fs_field>.
        IF <fs_field> IS INITIAL OR <fs_field> EQ '/'.
          IF w_dd03l-fieldname EQ 'TBNAM'.
            <fs_field> = p_table.
          ELSE.
            <fs_field> = '/'.
          ENDIF.
        ELSE.
          w_flag = 'X'.
        ENDIF.
      ENDLOOP.
      TRANSFER d_bbseg TO w_fname.
ENDCASE.
ENDFORM.
Edited by: Matt on Dec 15, 2008 5:03 PM - Made subject more informative

Gentlemen:
The problem around this statement:
ASSIGN (w_field) TO <fs_field>
is explained as follows:
1. In ABAP language, there are two ways for assigning a new value to a field-symbol.
- Sentence: ASSIGN (values) TO <my_field_symbol>.
In this case, the <my_field_symbol> receives from (w_field) the data type and value content of this variable. So, we keep that a FSymbol is assigned and, at the same time, receives an initial value.
- Sentence: <my_field_symbol> = '/' or <my_field_symbol> = my_var.
In this way, we only pass the content of the variable next to = sign. But before this, the field-symbol must had been assigned (using ASSIGN statement), in another case, the compiler raises an exception.
Following the example of Federico... I think he tried to assign a field like this (please, supose the program imports the structure of a database table with a standard function, into a internal table which is looped by the work area w_field ):
- If w_field contains 'BKPF-WERKS', so sentence ASSIGN will affect the field symbol, passing to this the data type and current content of table field BKPF-WERKS.
- If w_field contains 'BKPF-.INCLUDE': *the column .INCLUDE obviously is not associated with a data type... so our statement ASSIGN... TO... never pass any data type or value to our field-symbol. So that, this field is never initialized properly, and when inmmediately you try to execute something like this: <my_field_symbol> = '/', the game (program) is over.. XD
I hope this post was helpful for anyone...
Best Regards!!
RRG
ABAPer(u) - EVOLution

Upgrade from 46C to ECC 6.0

Hi All,
We are upgrading from 4.6C to ECC 6.0.I have downloaded all the SOFTWARE from Service market place except ORACLE 10.2 which I am not able to locate it.
Do I need to order ORALCE UPGRADE CDS from SAP? or is there any way to find out on the service market place...
Would appreciate If any of you can throw some light in this regard...
Thanks in Advance,
Johnny.

Of course the DVDs are available for download.
I do not know your OS, but you can follow this path:
http://service.sap.com/installations
Entry by Application Group ( you should also have it available in "My Company's Application Components" )
From here there are several ways. For example:
SAP NetWeaver
SAP NETWEAVER
SAP NETWEAVER 2004S
Installation and Upgrade
Your OS
ORACLE
You get a list including oracle 10g

Recommandations for upgrading from 46C to ECC 6.0

Hello
Our SAP system landscape is actually in 46c and is only composed of 3 servers with almost 40 users declared (25 actives) on production system. Modules FI/CO HR MM are actually implemented.
We plan to upgrade the system to ECC 6.0 between March and August of 2009. The evaluation of the upgrade should begin as soon as possible. Do you think it can be possible to realise the upgrade alone, without the help and expertise of a SAP consultant? Do you think the delay for preparing the upgrade is suffisant?
Thank you.

As suggested earlier, refer to Master and technological guides for reference.
also for information, the upgrade can fall under any below scenarios.
1. Strategic Business Improvement
Focus on functionality extension and improvement
Enablement of new and optimized business processes and scenarios based on new ERP core functionality
2. Functional/Retrofit Upgrade
New functionality to be implemented as part of the upgrade, modification clearing
Focus on reduction of system complexity
3. Technical Upgrade
Focus on pure technology upgrade
Retain functionality used
Review Usage of custom developments
As per the requirement. knowledge and experience the decision can be made.

Upgrade from 46C to ERP 2005

Similar Messages

Maybe you are looking for