SAP Basis Tech Supports

———————–< D038006 02/NOV/05 >————————–
Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
If you are using the above combination on your source release and have set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note 797084, proceed as follows:
Before you start the upgrade, you need to delete the environment variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by setting the following instance profile entry: rdisp/start_icman=false
Restart the system.
After the upgrade, delete the instance profile entry again.
———————-———————
————————< I0276299 21/SEP/05 >————————-
Checking Application Log
Before the upgrade, check your application log according to Note 196113. This avoids short dumps in the XPRAS_UPG phase, where you receive runtime error SAPSQL_ARRAY_INSERT_DUPREC for table BALHDR.
For more information, seeNote 196113.
————————–< D034302 16/AUG/05 >———————–
Windows only: Last profile text line must end with line feedback
Check that the last text line in all profiles ends with a line feedback.To check this, open a profile file with a text editor, go down with the cursor and ensure that the last line is empty. Otherwise there could be problems in the KX_SWITCH phase as some tools will not be able to handle the profiles properly.
————————< D031149 13/JUL/05 >————————-
Source Rel. ECC DIMP 5.0: MPN Conversion Exit
In release ECC DIMP 5.0 – up to and including CRT02 – the MPN conversion exit is delivered as “active” by default. The conversion exit is set to active, if the checkbox “Active conversion exit” in the following customizing transaction is flagged: Logistics – General –> Interchangeability of Parts –> Set Up Conversion Exit for Material Numbers.
If the MPN conversion exit should not be used in the system, it is very important that it is deactivated before the upgrade (in Source release ECC DIMP 5.0).
For more information on how to proceed, seeNote 854523.
The problem is solved with CRT03 of release ECC DIMP 5.0.
———————–< D028310 NOV/03/04 >————————-
Phase CONFCHK_IMP on Distributed Systems
Phase CONFCHK_IMP offers you a list of operating systems to select from. This list only contains one entry “Linux” which is valid for both Linux and Linux IA64.
————————< D024329 14/OCT/04 >————————-
Component PS-ST-WBS: Preliminary Inclusion of Field KIMSK
If you do not want the upgrade to overwrite field KIMSK, you can include the field in the table of modifiable fields before the upgrade.
For more information, seeNote 185315.
———————-< D033898 06/OCT/04 >—————————
Source Release 4.6C: SMODILOG Entries
In Releases 4.6C, when you created customer-specific parameter effectivities, the system did not make SMODILOG entries. In order not to lose these customer-specific parameter effectivities during the upgrade, proceed as described inNote 741280.
———————-< D038245 09/SEP/04 >—————————
Source Release Extension Set 1.10: Exchange containers
If your system was installed with SAP R/3 Enterprise Ext. Set 1.10 (based on SAP Web AS 6.20) and you are using a database that uses different containers for saving data (Oracle, Informix and DB2 UDB for UNIX and Windows), refer tonote 674070before the upgrade.
Otherwise, the exchange containers (tablespaces/dbspaces) cannot be emptied during the upgrade and cannot be deleted after the upgrade.
————————< D038245 19/APR/04 >————————
Unicode Systems: Downward Compatible Kernel 6.40
If you are using the normal kernel for Release 6.20 with your Unicode system, PREPARE issues the error message: Could not open the ICU common library.
Before you start PREPARE, install the Downward Compatible Kernel for Release 6.40. Until this kernel is available, proceed as described inNote 716378.
————————< D032986 22/SEP/05 >————————
Upgrading with reintegrated add-ons (retrofit)
For SAP ERP Core Component 6.0 (ECC 6.0), more add-ons were reintegrated into the main ECC system or the Extension Sets.
The following Notes contain additional information on processing these add-ons before, during and after the upgrade.
Note 838002Add-ons (non-IS) integrated in SAP ECC 600Note 838003Industry Add-ons integrated in SAP ECC 600

————————–< D032986 27/JAN/04 >———————–
Upgrading with PI/PI-A
For information on how to upgrade your system with PI/PI-A plug-ins, seeNote 700779.
————————–< D025323 24/APR/03 >———————–
Upgrade on AIX: saposcol
Refer toNote 526694before the upgrade.
————————–< D019926 DEC/10/02 >———————–
Upgrading with AIX 5.1
If you want to upgrade with AIX 5.1, seeNote 502532before starting PREPARE.
———————–< D025323 FEB/20/02 >————————–
Source Releases on UNIX 32-bit or AIX 64-bit
In some cases, you may have to upgrade the operating system to 64-bit before the actual upgrade.
When you upgrade from AIX 4.3 64-bit, you must perform some additional actions before upgrading.
For more information, seeNotes 496963and499708.
———————————————————————–

VI/ Problems During the Preparation and Upgrade Phases

This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.

Problems During the Preparation Phases

————————–< D038245 28/FEB/08 >———————–
Windows only: MSSERV_INTERN port numbers
During PREPARE, the upgrade tool requests a port number for the MSSERV_INTERN port. If your system is running on Windows, you cannot use port numbers within the following range: 6665 – 6669.
———————–< D038245 APR/11/02 >————————–
Termination in the TOOLIMPD3 phase
The TOOLIMPD3 phase terminates in the PREPARE module import. The following message appears in the log file: ABAP runtime error CALL_FUNCTION_NO_RECEIVER
Receiving data for unknown CPIC link XXXXXX.
Repeat the phase and continue with the upgrade.
———————————————————————–

Problems During the Upgrade Phases

————————–< D034302 16/AUG/05 >———————–
Phase: KX_SWITCH (Windows only)
Description: Upgrade stops with an error message which asks you to check file NTPARVAL.LOG. In this file, messages like the following are displayed: fopen(…): Invalid argument
Check that the last text line in all profiles ends with a line feedback. To check the profile, open a profile file with a text editor, go down with the cursor, and ensure that the last line is empty. If it is not, add an empty line at the end of the file and save it.
——————————————
————————–< D021867 AUG/10/04 >———————–
Phase: JOB_RDDNTPUR
Description: In the longpost-log file, you may get the error message: 3PETG447 Table and runtime object “TA22EQU_WAO” exist without DDIC reference.
or 3PETG447 Table and runtime object “TVERTREE” exist without DDIC reference
You can ignore this message.
————————–< I002675 OCT/07/05 >———————–
Phase: SHADOW_IMPORT_INC
Note: 884809
Description: The Upgrade fails in phase SHADOW_IMPORT_INC. Check if the log files display error messages as stated in the above note. If so, proceed as described in the note.
————————–< D025323 MAY/23/02 >———————–
Phase: CHK_POSTUP
Note: 197886
Description: If you have imported Notes 178631, 116095 or 69455 into your system before the upgrade, error messages for objects without DDIC reference appear in the log LONGPOST.LOG. Proceed as described in Note197886.
———————————————————————-
Phase: CHK_POSTUP
Note: 996953
Description: Log file LONGPOST.LOG asks you to migrate a CMOD project although no project exists.
———————-< D038245 FEB/28/06 >————————–
Phase: MODPROFP_UPG
Description: When you are performing a dual stack upgrade, in phase MODPROFP_UPG the ABAP system is started together with the Java system part for the first time. The phase may fail if the SAP J2EE Engine does not start fast enough.
Check manually if the SAP J2EE Engine is running and if so, choose “repeat” to repeat the upgrade phase.
———————————————————————-

VII/ Problems After the Upgrade

This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under specific circumstances.
———————–< D000587 25/FEB/08 >————————–
Error when Converting Print Parameters
After the upgrade, in some clients the printing parameters have either gone or been replaced by other parameters. For more information, see Note1142364.
The problem is solved with SAP Basis Support Package 16.
———————–< D033258 DEC/12/05 >————————-
Addition to the Release Notes
The depreciation posting run and the periodic posting run for APC values must be converted to document number ranges that use an internal document number assignment.
For more information, seeNote 890976.
——————–———————-
———————–< D003551 02/MAY/05 >————————-
Check Primary Index of Table MEMGMT_DEPLOYMNT
After the upgrade, check that the primary index of table MEMGMT_DEPLOYMNT exists. If not, create the index manually.
If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown object in the dictionary, drop it on the database level.
————————< D020815 AUG/23/02 >——————-
SPAU: Names of interface methods are truncated
Some methods (ABAP objects) that were modified and overwritten by the upgrade can be displayed in transaction SPAU with their names shortened to 30 characters.
As a result, the system may also incorrectly sort methods in SPAU under “Deleted objects”.
Caution: Deleted objects are not displayed in the standard selection in SPAU. It is easily possible to overlook these!
For more information about the correction, seeNote 547773.
———————————————————————-
Linux: Importing the new saposcol version
For more information, seeNote 19227.
———————————————————————-
ReliantUNIX: saposcol version 32-bit or 64-bit
For more information, seeNote 148926.
———————————————————————-
Solaris: saposcol version 32-bit or 64- bit
For more information, seeNote 162980.
———————————————————————-

VIII/ Chronological Summary

Date…..Topic..Short description
———————————————————————–
JUL/15/09..III…SAP NetWeaver Library Paths
MAY/07/09…II..Source Release 4.70 Ext. Set 2.00 Only: Use SAPup Version 7.10/4 Patch Level 5
APR/23/09….V..Check if Matchcodes Exist in Your System
MAR/12/09….I..SAPup keyword changed
DEC/09/08….V..Downloading Kernel DVDs for the Upgrade
NOV/21/08..III..Quick Guide
NOV/21/08…II..Corrections and Repairs for the Upgrade
MAR/14/08…VI..Phase XPRAS_UPG – shortdump SAPSQL_ARRAY_INSERT_DUPREC
FEB/28/08…VI..Windows only: MSSERV_INTERN port numbers
FEB/25/08..VII..Error when Converting Print Parameters
JAN/17/08….V..Source Release SAP R/3 4.6C: Including a min. SP level
JUL/03/07….V..Parameter for the Central Syslog rslg/collect*
MAY/09/07….V..Preparations for FI-CA
MAR/15/07…II..MSCS Configuration
FEB/28/07…VI..Phase CHK_POSTUP – CMOD/SMOD migration
FEB/05/07….V..Back up customer-specific entries in table EDIFCT
DEC/18/06….V..New SPAM/SAINT Version on Source Release
AUG/28/06….V..Update SAP Kernel on Source Release
APR/24/06….V..Prepare table COEP for the upgrade
FEB/28/06…VI..Phase MODPROFP_UPG fails – check J2EE Engine
DEC/12/05….V..SD Texts: Check Text Customizing on Source Release
DEC/12/05..VII..Addition to the Release Notes
NOV/02/05….V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/07/05…VI..Phase SHADOW_IMPORT_INC
SEP/22/05….V..Upgrading with reintegrated add-ons (retrofit)
SEP/21/05….V..Checking Application Log
AUG/16/05…VI..Windows only: KX_SWITCH – Check file NTPARVAL.LOG.
AUG/16/05….V..Windows only: Last profile text line – line feedback
JUL/13/05….V..Source Rel. ECC DIMP 5.0: MPN Conversion Exit
MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT
FEB/02/05…II..LSWM now part of SAP_BASIS
OCT/14/04….V..Component PS-ST-WBS: Prel. Inclusion of Field KIMSK
OCT/06/04….V..Source Release 4.6C: SMODILOG Entries
SEP/09/04….V..Source Release Extension Set 1.10: Exchange containers
AUG/10/04…VI..Phase JOB_RDDNTPUR: TA22EQU_WAO without reference
APR/19/04….V..Unicode Systems: Downward Compatible Kernel 6.40
JAN/27/04….V..Upgrading with PI/PI-A
DEC/03/03…II..Windows only: Execute program R3dllins.exe
APR/24/03….V..Upgrade on AIX: saposcol
DEC/10/02….V..Upgrading with AIX 5.1
AUG/23/02..VII..SPAU: Names of interface methods are truncated
JUL/19/02…II..Problems with the shadow instance
MAY/23/02…VI..Phase CHK_POSTUP – objects without DDIC reference
APR/11/02…VI..Termination in the TOOLIMPD3 phase
FEB/20/02….V..Source releases on UNIX 32-bit or AIX 64-bit
OCT/19/00..VII..Linux: Importing the new saposcol version
FEB/16/00..VII..saposcol version 32-bit or 64-bit on Reliant UNIX
FEB/16/00..VII..saposcol version 32-bit or 64-bit on Solaris
———————————————————————-