Upgrade XI 3.0 SR1 to XI 7.0

Hi want to upgrade XI 3.0 to XI 7.0.
What are the steps?
Please give links of Documents,Weblogs,common problems faced and resolutions etc.
Thanks

Asad,
XI 7.0 which I think will be called as PI7.0 will more or less same as XI3.0 except a few changes. Some of them can be found in:
PI 7.0 Information
XI 7.0 installation
SAP XI 7.0 version
Re: SAP XI 7.0 version
---Mohan

Similar Messages

Error in PREP_INIT/VERSCHK_INI phase during upgrade to NW70 EHP1 SR1

Hi All,
We have a NW system with the following components to NW 70 EHP1 SR1:
SAP_ABA     700     0013     SAPKA70013     Cross-Application Component
SAP_BASIS     700     0013     SAPKB70013     SAP Basis Component
PI_BASIS     2005_1_700     0013     SAPKIPYJ7D     PI_BASIS 2005_1_700
ST-PI     2005_1_700     0000          -     SAP Solution Tools Plug-In
SAP_BW     700     0015     SAPKW70015     SAP NetWeaver BI 7.0
BI_CONT     703     0000          -     Business Intelligence Content
We are in the process of upgrade to SAP EHP1 FOR SAP NETWEAVER 7.0 SR1 and we got the below error during the upgrade:
Checks after phase PREP_INIT/VERSCHK_INI were negative!
Last error code set: Start Release configuration 'SAP_ABA=700,SAP_BASIS=700,SAP_BW=700' is not supported Compare the release of your SAP system with the requirements listed in the documentation.
Choose action
     Repeat phase VERSCHK_INI to continue at the point it stopped
     Cancel the current phase VERSCHK_INI and go back to wizard
     Exit this program
We verified the DVDs (media list) we are uing for the upgarde and it is correct.
Any ideas on how this can be resolved?
Regards
ND

Have you read this note: https://service.sap.com/sap/support/notes/1568031
Looks like you have to include the latest corrections for EHPI installer.
Thanks
Srikanth Mandalapu
Cert Basis/Netweaver

SR1 to SP14 Upgrade - Portal Platform Warning

Hello all,
I am upgrading the recently installed SR1 to SP12. I successfully applied the Patch for WEBAS J2EE server. Now I'm trying to apply Portal Platform patches. During the "Deploy EAR Files" phase (6 of 12), it gave a warning Message box saying "The deloplyment may require manual postprocessing. See output of logfile C:\ProgramFiles\sapinst_instdir\callSdmViaSapinst.log' and in the status Bar it said 'Finished but with Warning'.
When I checked the log file i didnt fine any error or warning. It seems to me fine. Wonder what this message means.
(During the WAS Upgrade i upgraded the Central Instance and I dont have any other dialog instances).
But After I clicked Ok on the message box, the installation continued Normally and it seems to be going fine.
Can anyone help me out in this ?
Thanks.

Eric,
Thank you so much for answering me. It really helps.
One more question before i end this thread. I am new to portals and we are installing Portal on the Test box. To demonstrate the upper authorities how it might help for the company. I have so far installed SR1 and now upgrading to SP14. I have not installed TREX so far but will be installing in future. We are installing everything onto one box. I have installed Oracle database, WEBAS, Portal and KMC on the same drive(D:). The drive capacity is 34GB and i have so far used 11.5 GB and left with like 22.5GB. So my question is if I install TREX on another Drive (E:), will 22.5GB space on D: sufficient for doing the development which includes ESS, MSS import and bit of development?

Upgrading 4.7 SR1 to ERP ECC6.0

Hi All,
We are planning for upgrading SAP 4.7 SR1 to ECC6.0. At present the suuport pack level in 4.7 is
SAP_BASIS     620     0017     SAPKB62017     SAP Basis Component
SAP_ABA     620     0017     SAPKA62017     Cross-Application Component
SAP_APPL     470     0006     SAPKH47006     Logistics and Accounting
SAP_HR     470     0010     SAPKE47010     Human Resources
Can any one please update upto which stack level is required for upgrading to ECC6.0.
Regards,
Venu

Hi Venu
I recommend you the Upgrade Master Guide, and the Upgrade Gudies for SAP ERP 6.0/ SAP ECC. You find them in the Service Marktetplace at service.sap.com/erp-inst
regards,
Andreas R

Upgrade - SAP XI 3.0 to PI 7.0

Hello,
Can you please let me know the defined steps in upgrading XI 3.0 to PI 7.0? I checked the blogs on this. But couldn't get the right infomation on this. Can any pass on this information?
Thanks.
Srinivas.

Hi,
The Upgrade depends upon what Service Pack you will be implying with PI 7.0
Service packs in 2004 and 2004s;
in 2004 - in 2004s
SP12 & < - SP04
SP13 + 14 - SP05
SP15 - SP06
SP16 - SP07
SP17 - SP08
SP18 - SP09
Now as per the information I got in the forum from one of the XI expert Raj, currently PI is with latest SP 13.
Check this thread. Should help u out..
Upgrade XI 3.0 SR1 to XI 7.0
Thanks
Swarup

Upgradation from XI 3.0 to PI 7.0

Hi All,
If anybody have upgradation document from XI 3.0 to 7.0 Please share it with me..what are the major differences between XI 3.0 and PI 7.0?
Thanks in advance,
Hemu

Hi Hemanth,
Check out these two threads on Upgradation docs:
XI 3.0 to PI 7.0 upgrade
Upgrade XI 3.0 SR1 to XI 7.0
Regards,
Subhasha Ranjan

Upgrade SAP XI 3.0 to SAP XI 7.0

Is there a list of checks that should be perform after the upgrade since is mainly a kernel upgrade (ABAP/JAVA).

Hi Joao,
Its PI 7.0, not XI 7.0. Check this thread. Should help u out..
Upgrade XI 3.0 SR1 to XI 7.0
cheers,
Prashanth

Unable to extend tablespace while EhP4 upgrade

Hi Gurus,
We are doing EhP4 upgrade from EhP ready SR1. Our database version is DB6 9.7.2. We are using EhPI version 37.
In the chack phase the installer suggests to increase some tablspace size. But the tablespaces are in "Auto Storage Mode". We are unable to extend or add a container to it.
Any suggestions or workarounds for this issue?
Advance thanks.
Kind Regards,
Indrakumar

Thanks for all the replies.
SAP replied with the following workaround and it worked for us.
i)Save all files <upgdir>/bin/DBF.SPC and their content (for example by copying each of these files to DBF.SPC.SAV)
ii) Empty all files <upgdir>/bin/DBF*.SPC; that is do not delete/remove these files but delete all content, so that these files are completely empty!
iii) Make sure that you are having sufficient space in the file systems.
iv) Restart the upgrade/SPACECHK. with empty files there are no space requirements and thus the SPACECHK should finish successfully.
Kind Regards,
Indrakumar

Support Pack level for upgrade

Hi All,
We are upgrading from R/3 4.7 to ECC 6.0, can anybody provide me Support Pack level for SAP_ABA, SAP_BASIS etc. before starting upgrade.
I have gone through lot of OSS notes but not getting exact SP level.
Regards,
Sachin

I depends on
- what upgrade package you use (SR1, SR2, SR3)
- the SP level of the source system
The upgrade guide tells you the minimum SP level needed to do the upgrade.
If you use the new CD/DVD set, the system will be upgraded to SP 12 (BASIS, ABA, SAP_APPL).
If you backup your wage tables before the upgrade (as described in the installation guide) you can also go to the highes SP level for SAP_HR.
Markus

Urgent - XML Form Builder - lnode

Hi,
Strange behaviour, i created a new XML Form Project and have defined a schema with some nodes (day, month, year, lead, body, link under root node), for data schema.
I build the Edit form and run it, everything works fine until push save button, when i do this, i get an error message saying that "..star-tag link different from end-tag root...".
I made some changes until i find that by simple removing the node link from data schema, everythings works fine, if put it again, gives the same error message.
Is there any limitation of using a node link, under root node of data schema? Any one tried?
EP6 SP11.
Thanks and Regards,
John

Hi Darin,
Changing the node name link to another think, was my first thought, but there are 2 issues:
- What's the reason why a node named link doesn't work?(Looks like a "bug")
- I have upgraded the portal from SR1 SP09 to SP11, and in SP09 i have already created some items with XML Form with this structure, and because of the upgrade, i have already to change all the XML Forms, because listShow and listEdit doesn't work anymore, and now, for some strange reason i can't see my old news, because doesn't accept de node named link and i can't rename the node named link, because this means that i have to re-save all old news items.
Other think is, all XML Forms, incluind the standards ones, HTML editor are not working, clicking on any option available(Bold, Italic, ...), gives a message saying "[Object required]".
If you get another thought on this, please tell me.
Thanks and Regards,
John

Error "could not find code page for receiving system"

Hello Everyone,
We are trying to load data and receive the message:
Could not find code page for receiving system
We have searched notes and this forum and can't find anything. We also checked WE20 and could not find anything wrong.
Can someone please elaborate specifically what this error is and where to fix it?
Thanks so much.
Colleen

I just upgraded to NW 2004 SR1, and when loading data from a non-unicoded R/3 system to our BW unicoded system I experienced the exact problem. Here is the resolution that is stated in note #613389 (it's not very clear in the note).
- Language EN must be specified in sm59
- Under Special Options -> RFC Bit Options
Make sure that Use Found Communication Code Page has a check mark.
Once this was done, the data loads started completing successfully.

Need help correcting message error number

Hello, i need help correcting message number for running archiving test runs.
05.08.2011 08:31:42 Message number 999999 reached. Log is full                                BL           252          E
05.08.2011 08:31:42 Job cancelled after system exception ERROR_MESSAGE                        00           564          A
Any help wopuld be appreciated.
Regards.

Summary
Symptom
One or several database tables of the application log contain too many entries.
The following database tables belong to the application log:
- BALHDR (all releases)
- BALHDRP(< 4.6C)
- BALM   (< 4.6C)
- BALMP (< 4.6C)
- BALC   (< 4.6C)
- BALDAT (>= 4.6C)
- BAL_INDX (all releases)
Other terms
RSSLG200,
RSSLGK90,
SLG2,
application log,
log
delete,
performance
Reason and Prerequisites
The application log is a tool to collect, save and display logs.
Many different applications collect messages in the application log which contain information or messages for the end user. The application automatically log serves as a temporary storage for messages. The logs are written on the database but they are not automatically deleted.
There is no general procedure for switching the application log on or off. Some applications provide this option or they offer the option of reducing the number of entries created. (See Notes 91519, 183960, 141244).
The expiration date of application logs
A log usually has an expiration date, which is set by the application, that calls the 'Application log' tool. If the application log does not set an expiration date, the 'Application log' tool sets the expiration date as 12/31/2098 or 12/31/9999,depending on the release, which allows the logs to stay in the system for as long as possible. The end user cannot set the expiration date. The expiration date does not mean that logs which have reached that date will automatically be deleted. It is used to control the deletion of logs when you call the Deletion report. The DEL_BEFORE flag in the BALHDR table determines whether or not the log can be deleted even before the expiration date is reached.
DEL_BEFORE= SPACE means that the log can be deleted before the expiration date is reached. (Default value)
DEL_BEFORE='X' means that the log can only be deleted after the expiration date.
Solution
Deleting the logs of the application log.
Releases >= 4.6A:
=====================================================================
In Releases >= 4.6A, use Transaction SLG2.
On the selection screen you can restrict the amount of logs to be deleted:
The 'Object' and 'Subobject' fields specify the application area in which the logs were written (see F4 Help).
The 'External Identification' field specifies the number which was          provided for this log by the application.
o If you also want to delete logs which have not reached the expiration date you must set the option "Also logs which can be deleted before the expiration date".
Select 'Help with application' in Transaction SLG2 for further explanation of the procedure for deleting.
SLG2 is a report transaction. The corresponding report is SBAL_DELETE. At regular intervals, this can be scheduled as a background job.
Releases < 4.6A:
=====================================================================
For Releases < 4.6A, note the following instructions:
In general, the deletion of application logs can be carried out in two steps:
1. Report RSSLG200: Deletion of all logs which expired:
Use report RSSLG200 to delete all logs whose expiration date is reached or exceeded. (This report is not yet available in the standard in Release 3.0F. In this case, the report can be installed in advance; see corrections attached to this note).
As of Release 3.1H, Report RSSLG210 is also available. This report allows the definition of a job that runs regularly and deletes such logs.
2. Report RSSLGK90: Deleting all logs for which a deletion is allowed before expiration:
Sometimes, step 1 does not delete enough logs. The reason for this might be that the expiration date of the logs is too far in the future or that no expiration date has been defined at all (in this case, depending
on the release, the assumed expiration date is 12/31/2098 or 12/31/9999)
Use report RSSLGK90 for these logs.
When you execute this report, you can restrict the logs to be deleted in a selection screen:
The fields 'Object' and 'Subobject' specify the application area which wrote the logs (see F4 help).
The field 'External number' indicates the number which was assigned by the application for this log.
Field 'Log class' indicates the importance of the log.
NOTE: By default, this field contains the value '4', this means only logs with additional information. If you want to delete all logs, enter the value '1' in this field. All logs with log class '1' or higher will then be deleted.
The fields 'To date' and 'Until time' refer to the creation date of a log.
If you enter 12/31/1998 and 23:59:59, you get all logs created in and before 1998
NOTES:
Client-dependency:
Note that the application log tables are client-dependent. Therefore, you must delete data in each client.
Which applications create entires in the application log:
To determine which applications create the logs, look in Table BALHDR to see which objects the logs were created for ( Transaction SE16, Table BALHDR, Field OBJECT). You can find the text description for the object in Table BALOBJT. The application is usually derived from the name and text of the object. The log is displayed in Transaction SL61. The display is restricted to certain objects, among other things.
Database error:
If very many data exists on the DB, Report RSSLGK90 might cause problems. In this case, implement Note 138715.
In very rare cases a dump is created even after Note 138715 was implemented:
    ABAP/4 runtime error DBIF_RSQL_SQL_ERROR
    SQL error 1555 occurred accessing table "BALHDR "
    Database error text...: "ORA-01555: snapshot too old
If you cannot correct the error by means of database utilities, Note 368700 provides a way to bypass this error.
Report RSSLG200 can also run into problems. In this case, use the correction for Report RSSLG200 attached to this Note.
Expiration date in Report RSSLGK90:
There are logs on the database which may only be deleted explicitly after the expiration date (flag DEL_BEFORE = 'X' in table BALHDR). These logs are not deleted in advance by report RSSLGK90. Since, however, this flag is used very rarely, you can ignore this data.
Restriction of the quantity of log data by the application:
To avoid large quantities of logs from different applications, also refer to the following notes:
- 91519
- 183960
- 141244
Archiving logs:
As of Release 6.20, it has been possible to archive logs.
The logs are archived via archiving object BC_SBAL.
The archiving programs are started via Transaction SARA (archive administration).
Via Support Packages, the archiving of application logs has been made available for Releases 4.6C (SAPKB46C27), 4.6D (SAPKB46D17), and 6.10 (SAPKB61011) as well.
Header Data
Release Status: Released for Customer
Released on: 04.08.2005 13:55:45
Master Language: German
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-BAL Basis Application Log
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 30 30F 31I
SAP_APPL 40 40A 40B
SAP_APPL 45 45A 45B
SAP_BASIS 46 46A 46D X
SAP_BASIS 60 610 640 X
Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Last
Modifcation
158903 30F 30F SAP_APPL 16.05.2000 07:13:08
162069 31H 45B SAP_APPL 16.05.2000 07:16:07
Related Notes
1009281 - LAW: Runtime error CONNE_IMPORT_WRONG_COMP_TYPE
856006 - Mass processing saves unnecessary logs
737696 - Add. info on upgrade to SAP R/3 Enterprise 4.70 Ext. 2 SR1
706478 - Preventing Basis tables from increasing considerably
637683 - Add info about upgrade to SAP R/3 Enterprise Core 4.70 Ext 2
587896 - Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1
540019 - Report RJBTPRLO does not work correctly
400687 - Delete application log: DBIF_RSQL_INVALID_CURSOR
390062 - Additional information about upgrading to 4.6C SR2
370601 - Composite SAP note: APO 3.0 and 3.1 performance
365602 - M/AM: Sales agent determination log - perf.
327285 - Additions to upgrade to 4.6C SR1
183960 - ALE: Deactivating application logs for data transfers
141244 - Deactivating the application log during data transfer
138715 - RSSLGK90: Too many lock entries in the database
118314 - Installing the interface to a separate EH&S
91519 - Deleting logs of the application log
Print Selected Notes (PDF)
Attributes
Attribute Value
Transaction codes BALC
Transaction codes BALM
Transaction codes CLEAR
Transaction codes HIER
Transaction codes SARA
Transaction codes

Could anybody advise the general procedure for SAP system migration?

I may have chance to be involved into a SAP system migration. Generlly speaking, there are several SAP instances will be migrated into 1 box.The existing instances are 4.6C, and the target instance is ECC6.
Could anybody provide me some reference material for SAP system migration? or Is there any tools or software can facilitate the migration?
Thank you so much!
null

We are currently running and upgrade from 46C to ECC6 and I have found the following very usefull:
<a href="https://websmp108.sap-ag.de/upgrade-erp">Upgrade Guides</a>
SAP Notes:
Note 825146 - Add. info. on upgrading to SAP NW04s (SR1, SR2) MSSQL
Note 913971 - Add. info. on upgrading to SAP ERP Central Component 6.0 SR
Note 813658 - Repairs for upgrades to products based on SAP NW 2004s AS
Hope this helps!!
Phil
Message was edited by:
Phil Wade

Difference between Netweaver 7 SR2 and Netweaver 7 SR3

Guys,
Can anyone tell me the difference between Netweaver 7 SR2 and Netweaver 7 SR3, I have a question out with SAP regarding the supportability of SCM 5.1 on Windows 2008.
The response I got back was that SCM 5.1 is based on Netweaver 7 SR2, but it was my understanding that the SR designation was for the level of support packs and kernel upon vanilla installation. Have I missed something fundamental, because my SCM installation is patched to the highest level and therefore surpasses the patch and kernel levels provided by Netweaver 7 SR3.
TIA
Chris

Hello Chris,
The main difference between these releases is the initial SP level that comes with each media kit:
NetWeaver 7.0 SR3: 14
NetWeaver 7.0 SR2: 9
NetWeaver 7.0 SR1: 6
For more details, you can check note:
#789220 Support Package level for NetWeaver Installations/Upgrades
Other differences relate to the (new) installer with some bugs corrections and a few additional features and restrictions:
- the Unicode restriction in SR3: "Only Unicode support for new installations" - "Every newly installed SAP system is a Unicode system. However, non-Unicode is still supported for copied and upgraded systems." So a new install based on SR3 must be UNICODE. On the other way, if you upgrade your, say, SR1 system to SR3, you can still run it NON-UNICODE.
- SR3 supports only 64bit new installs on the Central Instance. However, if you need to add dialog instances (application servers), they can be 32bit ones (albeit 64bit is always recommended). When upgrading your system from SR1 to SR3 (for example), you can skip this restriction. That is, you can keep your CI in 32bit, although this is highly not recommended.
A common workaround for these restrictions (if you want to keep your system NON-UNICODE and/or if you want to keep it 32bit) is to:
1) Install a SAP NetWeaver 7.0 SR2 (SAP ERP 2005 SR2, SAP CRM 5.0 SR2, SAP SCM 5.0 SR2, SAP SRM 5.0 SR2) system.
2) Patch this system to SAP NetWeaver 7.0 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3).
There are more features / restrictions on the installation guides for SR3 in section: "1.1 New Features"
Also, there is many more minor differences like, for example, that you can only install a SAP system in a Windows 2008 from NetWeaver 7.0 SR3 and up - see note #1054740.
I hope this information helps.
Best regards,
Tomas Black

Upgrade from SCM 5.1 to SCM 7.0 SR1 (with NW 7.0 EHP1 SR1)

Hi folks,
we are trying to upgrade our SCM5.1 to SCM 7.0 SR1. There seems to be a problem in the phase, where SAPup is trying to detect the needed CDs / DVDs. SAPup recognizes that "FRP" is used within the system. There appears a dialog to enter the mount points for the DVDs required for the upgrade.
It says <<Enter at least the mount point for the DVD titled "FRP Software DVD">>. All other needed media is accepted, but not the DVD with the FRP-Software.
SAP Note "1300960" explains, that as of SAP Business Suite 2008 onward, no media without a MID.XML file will be accepted for upgrades (e.g. media containing Add-Ons).
I have opended a message to SAP Support, but there is no solution / workaround until now. I cannot skip the phase and therefore it is not possible to launch / continue the entire upgrade.
SAPup Version is "7.10/7, build 31.010 for UNICODE"
Has anyone faced the same problem with no-MID.XML based media?
Thank you for any advice!
Kind regards,
Marcel Jentsch

Hi,
We just upgraded from SCM 5.0 to 7.0 sp9.
You need not deactivate the DP planning areas before upgrade.
We did not face any issues because of this.
Regards,
Ashok

Upgrade XI 3.0 SR1 to XI 7.0

Similar Messages

Maybe you are looking for