SAPTechno

Note 1341975 - Add. info. on upgrading to SAP ERP 6.0 including EHP5 ABAP

Header
Version / Date 8 / 2012-10-05
Priority Correction with high priority
Category Upgrade information
Primary Component BC-UPG-RDM README: Upgrade Supplements
Secondary Components

Summary
Symptom

Errors in the upgrade procedure or in the upgrade guide; preparations for the upgrade; additional information to the upgrade guide

Other terms

Update, migration, upgrade, release upgrade, SAPup, SAP ERP Central Component 6.0,

Reason and Prerequisites

*

Solution


CAUTION:
This note is updated regularly!
Therefore, you should read it again immediately before starting the upgrade.

What information can I expect from this note?

This note describes problems that may occur during the system upgrade and provides information on how to solve them. This usually takes the form of references to other notes.
The main purpose of this note is to prevent data loss, upgrade shutdowns, and long runtimes.
It deals with database-independent problems only.

Which additional notes do I require in preparation for the upgrade?

You need to refer to the relevant database-specific note below:

Database .................................................. Note number
_______________________________________________________________________
SAP MaxDB .......................................................817463
IBM DB2 for i (NetWeaver-specific)..............................1168235
IBM DB2 for i (Business Suite-specific).........................1179413
IBM DB2 for Linux, UNIX and Windows .............................819876
IBM DB2 for z/OS.................................................815202
MS SQL Server....................................................825146
Oracle...........................................................819655

You also need to refer to the following important SAP Notes:

Short text ................................................ Note number
_______________________________________________________________________
Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP2......1299009
OCS: Known problems with Support Packages in SAP NW 7.0 AS ABAP..822379
Migration tool for Travel Management for CEE countries..........1475582



Contents

I/ ...... SAPup Keyword
II/ ..... Important General Information
III/ .... Corrections to the Guide
IV/ ..... Errors on the CD-ROM
V/ ...... Preparing the Upgrade
VI/...... Problems During the PREPARE and Upgrade Phases
VII/ .... Problems After the Upgrade
VIII/ ... Chronological Summary

I/ SAPup keyword


----------------------------------------------------------------------
The SAPup keyword is: 13549812
This must be entered in phase KEY_CHK.
----------------------------------------------------------------------




II/ Important General Information


-----------------------< D050445 OCT/04/12 >--------------------
Windows only: Windows Runtime must be installed
To prevent problems during and after the upgrade, you must execute program vcredist_ <Platform>.msi on all application hosts and on the remote shadow host (if you are planning to use one), as the upgrade tool will install it only on the central installation host.
You can find the program on the Upgrade Master CD in the folder <UpgradeMaster>\DATA_UNITS\UM_SAPCAR_WINDOWS_<Platform>.

-----------------------< D035496 DEC/14/10 >-----------------------
LOAD_SWITCHSTATES_LOST shortdump
If the procedure stops in phase MAIN_SHDRUN/ACT_UPG with a LOAD_SWITCHSTATES_LOST shortdump, then stop the shadow instance and start the shadow instance again.
This error can occur if you selected several technical usages and SAP Kernel 720 with patch level 70 is used for the shadow instance.

-----------------------< D025323 NOV/21/08 >--------------------------
Corrections and Repairs for the Upgrade
Before the upgrade, it is vital that you check whether the following is available for your specific upgrade:

  • A new version of SAPup.
  • Repairs to the ABAP upgrade programs.

For more information, see Note 1299009.
It is ESSENTIAL that you apply this Note.

-----------------------< D028310 JUL/19/02 >--------------------------
Problems with the Shadow Instance.
The following Notes contain information about problems with the shadow instance:

  • 525677: Problems when starting the shadow instance
  • 430318: Remote shadow instance on a different operating system


------------------------< D042621 FEB/02/05 >-------------------------
LSWM now part of SAP_BASIS
As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW and your source release is based on SAP Web AS 6.10 or lower, do not implement LSMW after the upgrade.
For more information, see Note 673066.

-----------------------< D020904 MAR/15/07 >---------------------------
MSCS: Upgrade of the ABAP system only, or Upgrade of the ABAP system
with subsequent Java Add-In installation:
In an MSCS configuration, you must split the ABAP central instance into the ABAP central instance (ASCS) and central instance, as described in SAP Note 1011190, if one of the following cases apply:

  • You have upgraded your SAP NetWeaver '04-based ABAP system to SAP NetWeaver 7.0-based ABAP system
  • You have upgraded your SAP NetWeaver '04-based ABAP system to SAP NetWeaver 7.0-based ABAP system, and now want to install a Java Add-In. The split must done before the Java Add-In installation.

The split is required for the use of the enqueue replication server. If you run an MSCS configuration without enqueue replication server, which is the traditional MSCS configuration (where the clustered central instance  runs the message server and enqueue work process), you will loose the enqueue lock table during a failover. The enqueue replication server configuration prevents this loss.
If you want to migrate an ABAP+Java system that is already upgraded to SAP NetWeaver 7.0 to the new configuration with enqueue replication server, you must perform a homogeneous system copy.

---------------------------------------------------------------------


III/ Corrections to the Guide


------------------------< I014707 23/MAY/12 >------------------------
Advanced GUI Options: Role Management and Alert Function
The section "Advanced GUI Options: Role Management and Alert Function" can be ignored as the options described there are not offered by SAPup.

---------------------------------------------------------------------


IV/ Errors on the CD-ROM




---------------------------------------------------------------------

V/ Preparing the Upgrade


------------------------< D047992 23/APR/09 >------------------------
Check if Matchcodes Exist in Your System
Before starting the upgrade, check if old help views or matchcodes existin your SAP system. If so, this can lead to an upgrade failure with a subsequent system restore.
Use report TWTOOL01 as described in SAP Note 1330256 to check if matchcodes exist in your system.
If you are running a combined upgrade and Unicode conversion, it is mandatory that you delete or migrate matchcode objects to Search Helps before you start SAPup.
For more information about Search Helps that have replaced the matchcodes, see the online documentation for the ABAP Dictionary.

------------------------< D035496 31/MAR/09 >------------------------
Selecting the Target SP Stack Level in Maintenance Optimizer
When selecting an enhancement package release and a target SP Stack level for the stack XML generation in Maintenance Optimizer, it is mandatory to select Support Package Stack 02 or higher. If you select a lower SP Stack level, you will get an error message in phase EHP_INCLUSION.

------------------------< D038245 09/DEC/08 >------------------------
Downloading Kernel DVDs for the Upgrade
The software of the kernel is split into two files with the following naming convention:
<product><version>
<product><version>Upgrade
When you download the kernel DVDs for the upgrade, you must download both files from SAP Service Marketplace.

------------------------< D044675 17/JAN/08 >--------------------------
Upgrade from Source Release 4.6C: Including a minimum SP level
If your source release system includes SAP_HR 46C Support Package level D1, data loss may occur during the upgrade. To prevent any data loss, include at least Support Package 26 of the target release into the upgrade, although the upgrade program does not request it.
Alternatively, update your system to SAP_HR 46C Support Package level D2 before the upgrade.

----------------------<changed D001658 10/JUL/07 >---------------------
------------------------< D001330 03/JUL/07 >--------------------------
Parameter for the Central Syslog rslg/collect*
There may be conflicts with parameter values for the central syslog "rslg/collect*" of the default profile.
If the parameters are set with 39<no.> and 40<no.>, you must change them to 14<no.> and 15<no.>. Make sure that the ports are not used by other applications. If so, choose some other number.
For more information, see Note 1069225.

----------------------< D023250 09/MAY/07 >---------------------------
Preparations for FI-CA
If you are using FI-CA integrated with Funds Management, prepare your system as described in SAP Note 834815. This will prevent activation errors during the upgrade.

-------------------< D003327 05/FEB/07 >-------------------------------
Back up customer-specific entries in table EDIFCT
If you have maintained customer-specific entries in table EDIFCT, they may get lost during the upgrade. If you do not want to lose these entries, export them before the upgrade and reimport them after the upgrade.
For more information, see Note 865142.

------------------------< D044675 18/DEC/06 >------------------------
New SPAM/SAINT Version on Source Release
Before you include Support Package SAPKH60007 in the upgrade, you must apply at least the following SPAM/SAINT versions on your source release:

  • Source Rel. SAP R/3 4.x: SPAM/SAINT version 0045
  • Source Rel. SAP R/3 Enterprise, SAP ECC. 5.0: SPAM/SAINT version 0022

If you use an older version, you will receive conflict messages for SAP_APPL SP 07 with ECC-DIMP, object list SAPKGES01G, during PREPARE. In this case, you can repeat the phase after applying the SPAM/SAINT update.

-----------------------< D028310 28/AUG/06 >--------------------------
Update SAP Kernel on Source Release
If you want to convert logical cluster tables incrementally using transaction ICNV during the upgrade, you must make sure that the level of the SAP kernel on the source release is high enough.
For more information, see SAP Note 946659.

-----------------------< D022188 24/APR/06 >--------------------------
Prepare table COEP for the upgrade
If your source release is SAP R/3 4.6C or below and table COEP contains many data, the conversion of this table during the upgrade can lead to aprolonged downtime.
For more information about reducing downtime, see Note 937389.

----------------------< D037027 12/DEC/05 >---------------------------
SD Texts: Check Text Customizing on Source Release
Before the upgrade, check your text Customizing in transaction VOTX as described in Note 900607.


-----------------------< 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.

----------------------<changed D022030 20/JUN/06 >---------------------
------------------------< 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, see Note 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, see Note 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.

-----------------------< D031049 14/OCT/04 >--------------------------
Source Rel. 4.0B: Project-Related Incoming Orders
If you are using the preliminary solution for project-related incoming orders published with Note 118780, you have to modify data elements before the upgrade.
For more information, see Note 369542.

------------------------< 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, see Note 185315.

----------------------< D033898 06/OCT/04 >---------------------------
Source Release 4.6C and lower: 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 in Note 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 to note 674070 before 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 in Note 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 838002 Add-ons (non-IS) integrated in SAP ECC 600
  • Note 838003 Industry 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, see Note 700779.

--------------------------< D025323 24/APR/03 >-----------------------
Upgrade on AIX: saposcol
Refer to Note 526694 before the upgrade.

--------------------------< D019926 DEC/10/02 >-----------------------
Upgrading with AIX 5.1
If you want to upgrade with AIX 5.1, see Note 502532 before starting the upgrade.

-----------------------< 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, see Notes 496963 and 499708.

-----------------------------------------------------------------------



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


------------------------< D035496 31/MAR/09 >------------------------
Error in the EHP_INCLUSION Phase
If you have selected a target SP stack level lower than SP stack 02 for the stack XML generation in Maintenance Optimizer, you will get a similar error message in phase EHP_INCLUSION:
EHP patch level 34 for component SAP_HR is too low, destination level is already at 37.
Solution:

    1. Select SP Stack 02 or higher as the target SPS level for enhancement package 4 and rerun the package calculation in Maintenance Optimizer.
    2. Download the additional packages calculated by the Maintenance Optimizer to your EPS inbox directory.
    3. Repeat the failed phase with the newly generated stack XML file.


--------------------------< 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 during the tool 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



-----------------------< D035496 DEC/14/10 >-----------------------
LOAD_SWITCHSTATES_LOST shortdump
If the procedure stops in phase MAIN_SHDRUN/ACT_UPG with a LOAD_SWITCHSTATES_LOST shortdump, then stop the shadow instance and start the shadow instance again.
This error can occur if you selected several technical usages and SAP Kernel 720 with patch level 70 is used for the shadow instance.

--------------------< D030182 05/AUG/10 > ------------------------------
Phase: JOB_RCIFSTKUREN2
Description: Oracle Only: After this phase, on DB platform Oracle you may encounter an inconsistency with primary DB index of table "CIFSTKUCOUNT".
Solution: Include the corresponding SP mentioned in SAP Note 1483213 into the upgrade.
If this SP is not yet released, and inconsistency with the DB index exists, rename index with execution of funtion module DB_RENAME_INDEX (transaction SE37, only on DB platform Oracle):
Parameters:
TABNAME:       CIFSTKUCOUNT
INDNAME_NEW:   CIFSTKUCOUNT~0
INDNAME_OLD:   CIFSTKUCNT~0
To avoid errors with index information on Oracle systems, apply SAP Not 1483213.


------------------------< I043270 15/JUL/10 >--------------------------
LONGPOST.LOG

    • The message: "A1PESEEF_BADI 103 BAdI implementation FMFG_HELD_PO_NO_UPD must still be migrated" can be ignore since the implementation is obsolete. See SAP Note 1246090.
    • You can ignore the following messages:

                    '3PETG447 Table and runtime object "/SAPAPO/RESDIM" exist without DDIC reference ("Transp. table")'

                    '3PETG447 Table and runtime object "/SAPAPO/RES_HEAD" exist without DDIC reference ("Transp. table")'

                    '3PETG447 Table and runtime object "/SAPAPO/RES_TXT" exist without DDIC reference ("Transp. table")'

                    The tables are deliberately kept on the database when you upgrade (For more information, see Note 827490).

    • Messages with the following pattern can also be ignored:

                    '4PEDH176 Parameter list of append search help "..." differs from appending one'.


------------------------< D021548 05/MAY/10 >--------------------------
Phase: MAIN_NEWBAS/XPRAS_AIMMRG
Description:  Shortdump  OBJECTS_OBJREF_NOT_ASSIGNED_NO
SAP Note: 1465173

------------------------< D026178 15/OCT/09 >--------------------------
Phase CHK_POSTUP
Description: P messages in LONGPOST.LOG file:

  • 4PEDH176 Parameter list of append search help "ASH_FICO_TREX" differs from appending one
  • 4PEDH176 Parameter list of append search help "FICO_APPEND" differs fro appending one
  • 4PEDH176 Parameter list of append search help "FICO_SUBSTRINGS" differs from appending one
  • 4PEDH176 Parameter list of append search help "ASH_GRANT_TREX" differs from appending one
  • 4PEDH176 Parameter list of append search help "GRANTS_APPEND2" differs from appending one

Solution: You can ignore these P messages.

--------------------------< I027631 17/APR/09 >-----------------------
Phase: ACT_UPG
Note: 1321756
Description: During the ACT_UPG phase, you might get the following error message:
1EEDO519X"Table" "USMDZ1FCRS" could not be activated
Proceed as described in Note 1321756.

--------------------------< 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.

---------------------<changed D003551 OCT/04/05 >---------------------
--------------------------< 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.

--------------------------< C5003135 MAY/03/09 >-----------------------
Phase: SHDUNINST_DB
Description: The upgrade fails with the following error message:
'Could not drop database shadow user <shadow DB user>'
The log file <upgrade directory>/abap/log/SHDUNINST.LOG contains the error:
BR0152E Environment variable SAPDATA_HOME is not set
Solution:

    1. Stop the SL Controller and SAPup.
    2. Set the environment variable SAPDATA_HOME to the directory <upgrade directory>/abap/tmp (by default /usr/sap/<SAPSID>/upg/abap/tmp) in a local shell for user <sapsid>adm.
    3. Start the SL Controller from this local shell by executing the startup script from the upgrade directory.
    4. Start the upgrade GUI and use the 'repeat' option for this phase.


--------------------------< I027631 MAY/03/09 >-----------------------
Phase: XPRAS_UPG
Description: You may get the following error message in phase XPRAS_UPG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700XP3.O64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012X Program terminated (job: "RDDEXECL", no.: "20563602")
  Long text:
    Cause
      Program "V#&"
, which was started in the background, was terminated abnormally.
Solution: Download lib_dbsl_<patch level>.sar (patch level must be at least 38) from SAP Service Marketplace and replace the library dboraslib.dll, then repeat the phase.

-------------------------< D023536 14/MAR/08 >------------------------
Phase: XPRAS_UPG (sourse release < 4.6C only)
Description: In certain cases, the shortdump SAPSQL_ARRAY_INSERT_DUPRECmay occur in program "SAPLSBAL_DB_INTERNAL". If you encounter this error, repeat the phase. If the error persists, proceed as described in SAP Note 196113.

--------------------------< 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 Note 197886.

----------------------------------------------------------------------
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 stack is started together with the Java stack 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.



-----------------------< I036707 26/MAR/10 >--------------------------
Missing instance.box.number in the instance.properties
After the upgrade, you might receive an error message when you try to display the system details in the SAP NetWeaver Administrator.
To solve this problem, apply SAP Note 927561.


-----------------------< 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 Note 1142364.
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, see Note 890976.

--------------------<enhanced D038245/JUNE/05 >----------------------
-----------------------< 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, see Note 547773.

----------------------------------------------------------------------
Linux: Importing the new saposcol version
For more information, see Note 19227.

----------------------------------------------------------------------
ReliantUNIX: saposcol version 32-bit or 64-bit
For more information, see Note 148926.

----------------------------------------------------------------------
Solaris: saposcol version 32-bit or 64- bit
For more information, see Note 162980.

----------------------------------------------------------------------




VIII/ Chronological Summary


Date.....Topic..Short description
-----------------------------------------------------------------------
OCT/04/12..II...Windows only: Windows Runtime must be installed
MAY/23/12..III..Advanced GUI Options: Role Management and Alert Function
AUG/05/10...VI..Phase: JOB_RCIFSTKUREN2
JUL/15/10...VI..LONGPOST.LOG
MAY/05/10...VI..Phase: MAIN_NEWBAS/XPRAS_AIMMRG
MAR/26/10..VII..Missing instance.box.number in the instance.properties
OCT/15/09...VI..Phase CHK_POSTUP
MAY/03/09...VI..Phase: XPRAS_UPG
MAY/03/09...VI..Phase: SHDUNINST_DB
APR/23/09....V..Check if Matchcodes Exist in Your System
APR/17/09...VI..Phase: ACT_UPG
MAR/31/09...VI..Error in the EHP_INCLUSION Phase
MAR/31/09....V..Selecting the Target SPS Level in Maintenance Optimizer
DEC/09/08....V..Downloading Kernel DVDs for the Upgrade
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..Source Rel. 4.0B: Project-Related Incoming Orders
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
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
----------------------------------------------------------------------

Affected Releases
Software Component Release From Release To Release And subsequent
SAP_APPL600600600
SAP_BASIS70702702

Related Notes
1475582Migration Tool for Travel Management for CEE countries
1299009Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2