Add-Info-on-Upgrading-to-SAP-ECC-6-0-SR2-ABAP

23.06.2008 Page 1 of 16

Note 961410 - Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP

Note Language: English Version: 39 Validity: Valid from 27.02.2008

Summary

SymptomErrors in the upgrade procedure or in the upgrade guide; preparations forthe upgrade

More TermsUpdate, migration, upgrade, release, maintenance level, R3up, PREPARE SAPERP Central Component 6.0 SR2

Cause and Prerequisites*

Solution

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

What information can I expect from this note?This note describes problems that may occur during the system upgrade andprovides information on how to solve them. This usually takes the form ofreferences 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?This depends on the functions that you are using. You will need one orseveral of the following notes:

Short text..................................................Note number_______________________________________________________________________Add. info. for upgrades to SAP NetWeaver 7.0 ABAP: MaxDB.........817463Add. info.: Upgrade to SAP NW 7.0 AS ABAP i5/OS..................961146IBM DB2 for UNIX/Windows: Add. info for upgrade to SAP NW 7.0....819876IBM DB2 for z/OS: Add. info. for upgrade to SAP NW AS 7.0........815202Add. info. on upgrading to SAP NW 7.0 MSSQL......................825146Add. info.: Upgrade to SAP NW 7.0 AS ABAP Oracle ................819655_______________________________________________________________________Repairs for upgrade to SAP NW 7.0 AS ABAP........................813658Corrections for SAPup release 7.00...............................821032_______________________________________________________________________OCS: Known problems with Support Packages in SAP NW 7.0 AS ABAP..822379_______________________________________________________________________

ContentsI/ ...... SAPup Keyword

23.06.2008 Page 2 of 16


II/ ..... Important General InformationIII/ .... Corrections to the GuideIV/ ..... Errors on the CD-ROMV/ ...... Preparing the UpgradeVI/...... Problems During the PREPARE and Upgrade PhasesVII/ .... Problems After the UpgradeVIII/ ... Chronological Summary

I/ SAPup keyword

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

II/ Important General Information

-----------------------< D025323 MAY/24/02 >--------------------Corrections and Repairs for the UpgradeBefore the upgrade, it is vital that you check whether the following isavailable for your specific upgrade:

o A new version of SAPup. For more information, see note 821032.

o Repairs to the ABAP upgrade programs. For more information, seenote 813658.

It is ESSENTIAL that you apply these two notes.

-----------------------< D034302 DEZ/03/03 >--------------------Windows only: Execute program R3dllins.exeThe 6.40 kernel is compiled with the new version of MS compiler andrequires additional libraries for operation. To prevent problems during andafter the upgrade, you must execute program R3dllins.exe on your centralhost, all application hosts, and on the remote shadow host, if you areplanning to use one.You can find the program on the Upgrade Master CD in the NT\I386\NTPATCHfolder. It must be executed before you start PREPARE and directly from theNTPATCH folder (it can be shared). Copying and executing the program willnot work!

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

o 525677: Problems when starting the shadow instance

o 430318: Remote shadow instance on a different operating system

------------------------< D042621 FEB/02/05 >-------------------------

23.06.2008 Page 3 of 16


LSWM now part of SAP_BASISAs of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW andyour source release is based on SAP Web AS 6.10 or lower, do not implementLSMW after the upgrade.For more information, see Note 673066.

-------------------<changed D023138 OCT/18/07 >-------------------------------------------<changed D022030 AUG/24/07 >-------------------------------------------<changed D001330 FEB/13/07 >------------------------------------------< D023138/D003551 JAN/23/07 >------------------------Applying Support Package StacksBefore applying a Support Package Stack, check which BW Support Package isincluded in the stack!To avoid problems during the upgrade, do not include BW Support Package 11(SAPKW70011), 12 or 13 as the highest Support Package in the upgrade.Instead, use either BW Support Package 10 (SAPKW70010) or BW SupportPackage 14 (SAPKW70014) or higher.Fore more information, see Note 1013807.

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

o You have upgraded your SAP NetWeaver '04 ABAP only system to SAPNetWeaver 2004s ABAP

o You have upgraded your SAP NetWeaver '04 ABAP only system to SAPNetWeaver 2004s ABAP, and now want to install a Java Add-In. Thesplit must done before the Java Add-In installation.

The split is required for the use of the enqueue replication server. If yourun an MSCS configuration without enqueue replication server, which is thetraditional MSCS configuration (where the clustered central instance runsthe message server and enqueue work process), you will loose the enqueuelock table during a failover. The enqueue replication server configurationprevents this loss.If you want to migrate an ABAP+Java system that is already upgraded to SAPNetWeaver 2004s to the new configuration with enqueue replication serveryou must perform a homogeneous system copy.

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

III/ Corrections to the Guides

------------------------< D028310 08/FEB/08 >------------------------Dual Stack Upgrade: Downtime-Minimized OnlyIn the upgrade guide, the chapters on upgrade strategy and synchronizedupgrade of a dual stack SAP system do not mention the fact that asynchronized upgrade only works with upgrade strategy "downtime-minimized".

------------------------< D034302 12/NOV/07 >-------------------------Windows only: Upgrading the Application Servers

23.06.2008 Page 4 of 16


The procedure to upgrade the application servers on Windows has changed:

1. On the application server execute R3dllins.exe program from theUpgrade Master DVD. It is located in the directory UMN_WINDOWS_<PROC>\DBINDEP\NTPATCH for non-unicode and UMU_WINDOWS_<PROC>\DBINDEP\NTPATCH for unicode systems.

2. Restart the application server.

---------------------<changed D022030 OCT/12/07 >---------------------------------------------< D022030 SEP/07/07 >-------------------------New Entry Page to SAP NetWeaver Library DocumentationThe Help Portal page for SAP NetWeaver 7.0 has changed. The paths to SAPNetWeaver Library documentation in the installation and upgrade guidesstill refer to the old structure. If you need to follow a path as describedin the guides, you can use the entry to the old SAP NetWeaver Librarystructure from the following link:http://help.sap.com/nw70 -> Knowledge Center for SAP NetWeaver 7.0 (2004S)-> Access to SAP NetWeaver Library [EN] [DE]

------------------------< D035220 APR/23/07 >--------------------------Migrate data from table TVARV to TVARVCAs of SAP Basis 6.10, the client-specific table TVARVC is used instead ofcross-client table TVARV. If you want to migrate entries from table TVARVto the new table, you can use report RSTVARVCLIENTDEPENDENT.For more information, see Note 557314.

------------------------< D037666 28/FEB/07 >------------------------Applying Support Packages on the Source ReleaseIf you have to apply Support Packages on your source release shortly beforethe upgrade, check whether the equivalent Support Package is available forthe target release.Consider if you can bind the Support Package to the upgrade instead ofapplying it to the source release.

------------------------< D003551 04/JAN/07 >------------------------Modification Adjustment Planning: Unicode RequestAs of SAPup version 7.00/2, build 24.070, you can import the modificationadjustment transport request which you created in the Unicode system intothe non-Unicode system.

------------------------< D019369 15/DEC/06 >------------------------Migration of Workload Statistics Collector DataFor SAP NetWeaver 2004s, the workload statistics collector has changedincompatibly to older releases. Workload statistics data from the sourcerelease can no longer be viewed on the target release.To preserve your workload statistics data, you must copy the data beforethe upgrade into a different database tables, convert it, and copy it backafter the upgrade.For more information on the copy the data, see Note 1005238.For more information on the conversion and copy the data back, see Note1006116.

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

23.06.2008 Page 5 of 16


IV/ Errors on the CD-ROM

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

V/ Preparing the Upgrade

------------------------< D044675 17/JAN/08 >--------------------------Upgrade from Source Release 4.6C: Including a minimum SP levelIf your source release system includes SAP_HR 46C Support Package level D1,data loss may occur during the upgrade. To prevent any data loss, includeat 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 D2before the upgrade.

--------------------< changed D001330 07/JAN/08 >----------------------------------------------< D001330 26/NOV/07 >--------------------------Source Release 4.6C and below only: Phase TABIM_UPGIf your source release is based on SAP Basis 4.6C or lower, the upgrade maystop in phase TABIM_UPG. Log files SAPI700TG2.<SID> orSAPI700TK2.<SID> showthe following error message:2EETW109 table "BSKEYWORD" does not exist in nametab.To prevent this error, proceed as follows:

3. After PREPARE,before you start the upgrade, go to subdirectory"cofiles" of the upgrade directory.

4. Create / update files with the name A700TG2.SAP and A700TK2.SAP.

5. Open the files and enter exactly the following:

I 2EETW109 table "BSKEYWORD" does not exist in nametab

6. Save the file.

To fix this error in phase TABIM_UPG, use the same procedure.

----------------------<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 to14<no.> and 15<no.>. Make sure that the ports are not used by otherapplications. If so, choose some other number.For more information, see Note 1069225.

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

23.06.2008 Page 6 of 16


-------------------< D003327 05/FEB/07 >-------------------------------Back up customer-specific entries in table EDIFCTIf you have maintained customer-specific entries in table EDIFCT, they mayget 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 ReleaseBefore you include Support Package SAPKH60007 in the upgrade, you mustapply at least the following SPAM/SAINT versions on your source release:

o Source Rel. SAP R/3 4.x: SPAM/SAINT version 0045

o Source Rel. SAP R/3 Enterprise, SAP ECC. 5.0: SPAM/SAINT version0022

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

------------------------< D019369 15/DEC/06 >------------------------Migration of Workload Statistics Collector DataBefore the upgrade, copy the workload statistics collector data asdescribed in section "III/...Corrections to the Guide".

-----------------------< D028310 28/AUG/06 >--------------------------Update SAP Kernel on Source ReleaseIf you want to convert logical cluster tables incrementally usingtransaction ICNV during the upgrade, you must make sure that the level ofthe 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 upgradeIf your source release is SAP R/3 4.6C or below and table COEP containsmany data, the conversion of this table during the upgrade can lead toaprolonged downtime.For more information about reducing downtime, see Note 937389.

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

-----------------------< D038006 02/NOV/05 >--------------------------Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat4.0 IA64If you are using the above combination on your source release and have setenvironment 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 variableLD_ASSUME_KERNEL 2.4.21 and deactivate component icman by setting thefollowing instance profile entry:rdisp/start_icman=falseRestart the system.After the upgrade, delete the instance profile entry again.

23.06.2008 Page 7 of 16


----------------------<changed D022030 20/JUN/06 >---------------------------------------------< I0276299 21/SEP/05 >-------------------------Checking Application LogBefore the upgrade, check your application log according to Note 196113.This avoids short dumps in the XPRAS_UPG phase, where you receive runtimeerror 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 linefeedbackCheck that the last text line in all profiles ends with a line feedback.Tocheck this, open a profile file with a text editor, go down with the cursorand ensure that the last line is empty. Otherwise there could be problemsin the KX_SWITCH phase as some tools will not be able to handle theprofiles properly.

------------------------< D031149 13/JUL/05 >-------------------------Source Rel. ECC DIMP 5.0: MPN Conversion ExitIn release ECC DIMP 5.0 - up to and including CRT02 - the MPN conversionexit is delivered as "active" by default. The conversion exit is set toactive, if the checkbox "Active conversion exit" in the followingcustomizing transaction is flagged: Logistics - General -->Interchangeability of Parts --> Set Up Conversion Exit for MaterialNumbers.If the MPN conversion exit should not be used in the system, it is veryimportant that it is deactivated before the upgrade (in Source release ECCDIMP 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 SystemsPhase 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 andLinux IA64.

------------------------< D030022 14/OCT/04 >-------------------------Source Rel. 3.1I: Loss of Address DataIf you are using component "Plant Maintenance" (PM-WOC-MN) and convert theaddresses with report RSXADR05 before the upgrade from Source Release3.1I, make sure to read note 360929.Otherwise you may lose address data during the upgrade.

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

------------------------< D024329 14/OCT/04 >-------------------------Component PS-ST-WBS: Preliminary Inclusion of Field KIMSKIf you do not want the upgrade to overwrite field KIMSK, you can includethefield in the table of modifiable fields before the upgrade.For more information, see note 185315.

----------------------< D033898 06/OCT/04 >---------------------------

23.06.2008 Page 8 of 16


Source Release 4.6C and below: SMODILOG EntriesIn Releases 4.6C and below, when you created customer-specific parametereffectivities, the system did not make SMODILOG entries. In order not tolose 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 containersIf your system was installed with SAP R/3 Enterprise Ext. Set 1.10 (basedon SAP Web AS 6.20) and you are using a database that uses differentcontainers for saving data (Oracle, Informix and DB2 UDB for UNIX andWindows), refer to note 674070 before the upgrade.Otherwise, the exchange containers (tablespaces/dbspaces) cannot be emptiedduring the upgrade and cannot be deleted after the upgrade.

------------------------< D038245 19/APR/04 >------------------------Unicode Systems: Downward Compatible Kernel 6.40If you are using the normal kernel for Release 6.20 with your Unicodesystem, PREPARE issues the error message:Could not open the ICU common library.Before you start PREPARE, install the Downward Compatible Kernel forRelease 6.40. Until this kernel is available, proceed as described in Note716378.

------------------------< D032986 22/SEP/05 >------------------------Upgrading with reintegrated add-ons (retrofit)For SAP ERP Core Component 6.0 (ECC 5.0), more add-ons were reintegratedinto the main ECC system or the Extension Sets.The following Notes contain additional information on processing theseadd-ons before, during and after the upgrade.

o Note 838002 Add-ons (non-IS) integrated in SAP ECC 600

o Note 838003 Industry Add-ons integrated in SAP ECC 600

--------------------------< D032986 27/JAN/04 >-----------------------Upgrading with PI/PI-AFor information on how to upgrade your system with PI/PI-A plug-ins, seeNote 700779.

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

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

-----------------------< D025323 FEB/20/02 >--------------------------Source Releases on UNIX 32-bit or AIX 64-bitIn some cases, you may have to upgrade the operating system to 64-bitbefore the actual upgrade.When you upgrade from AIX 4.3 64-bit, you must perform some additionalactions before upgrading.For more information, see Notes 496963 and 499708.

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

23.06.2008 Page 9 of 16


VI/ Problems During the PREPARE and Upgrade Phases

This section addresses known problems that cannot be avoided usingpreventive measures. These problems will only occur under very specificcircumstances.

Problems During the PREPARE Phases

-----------------------< D028310 JUL/26/04 >----------------------Source Release 3.1I and 4.0B: Error in PhaseTR_CMDIMPORT_FDTASKS If there are nametab entries with a non-unique UUID, you get an errormessage in phase TR_CMDIMPORT_FDTASKS. Proceed as described in note705485

-----------------------< D038245 APR/11/02 >--------------------Termination in the TOOLIMPD3 phaseThe TOOLIMPD3 phase terminates in the PREPARE module import. The followingmessage appears in the log file:ABAP runtime error CALL_FUNCTION_NO_RECEIVERReceiving data for unknown CPIC link XXXXXX.Repeat the phase and continue with the upgrade.

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

Problems During the Upgrade Phases

-----------------------< D023536 JAN/14/08 >--------------------------Phase: ACT_700Description: Error when SAP_BASIS Support Package 14 is includedIf you have included SAP_BASIS Support Package 14 into the upgrade, theupgrade stops and you can find the following error text in the log file:4 EDT014XActivate dependent table "SI_WD_ALLOWED_OBJECT_STR"4EEDT002 Table "SI_WD_ALLOWED_OBJECT_STR" does not exist4 EDT015 Dependent table "SI_WD_ALLOWED_OBJECT_STR" was not activatedTo continue, repeat the phase.

--------------------------< D028310 27/FEB/08 >-----------------------Phase: STOP_SHDI_LASTDescription: Remote Shadow Instance on UNIX onlyIf you run the shadow instance remotely and you stop it in phaseSTOP_SHDI_LAST, sometimes sapstartsrv keeps running on the dialog instance.Stop sapstartsrv with the following command:sapcontrol -nr <SHDSID> -prot NI_HTTP -function StopService

--------------------------< D034302 16/AUG/05 >-----------------------Phase: KX_SWITCH (Windows only)Description: Upgrade stops with an error message which asks you to checkfile NTPARVAL.LOG. In this file, messages like the following are displayed:

23.06.2008 Page 10 of 16


fopen(...): Invalid argumentCheck that the last text line in all profiles ends with a line feedback. Tocheck the profile, open a profile file with a text editor, go down with thecursor, and ensure that the last line is empty. If it is not, add an emptyline at the end of the file and save it.

---------------------<changed D003551 OCT/04/05 >-----------------------------------------------< D021867 AUG/10/04 >-----------------------Phase: JOB_RDDNTPURDescription: In the longpost-log file, you may get the error message:3PETG447 Table and runtime object "TA22EQU_WAO" exist without DDICreference.or3PETG447 Table and runtime object "TVERTREE" exist without DDIC referenceYou can ignore this message.

--------------------------< I002675 OCT/07/05 >-----------------------Phase: SHADOW_IMPORT_INCNote: 884809Description: The Upgrade fails in phase SHADOW_IMPORT_INC. Check if the logfiles display error messages as stated in the above note. If so, proceed asdescribed in the note.

----------------------< D003551 07/NOV/05 >----------------------------Phase JOB_RSTLANUPGNote: 626272Description: Termination; the log file for job RSTLAN_UPGRADE contains thefollowing error message:"..Job terminated after system exception ERROR_MESSAGE."

--------------------------< D025323 MAY/23/02 >----------------------Phase: CHK_POSTUPNote: 197886Description: If you have imported Notes 178631, 116095 or 69455 into yoursystem before the upgrade, error messages for objects without DDICreference appear in the log LONGPOST.LOG. Proceed as described in the Note.

----------------------< D038245 FEB/28/06 >--------------------------Phase: MODPROFP_UPGDescription: When you are performing a double-stack upgrade (ABAP and Javasystem at the same time), in phase MODPROFP_UPG the ABAP system is startedtogether with the Java system part for the first time. The phasemay fail ifthe 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.

--------------------------< D023536 NOV/28/07 >----------------------Phase: XPRAS_UPGDescription:If you applied Basis Support Package SAPKB62058 or higher or you appliedSAPKB64017 or higher, the phase XPRAS_UPG will abort with syntax errorswhen executing the after import methodSCPR_SCP2_AFTER_IMPORT. To avoid this error, proceed as follows:

o When using strategy resource-minimized:

Just before starting the downtime with phase EU_IMPORT1, run the

23.06.2008 Page 11 of 16


function module DD_NAMETAB_DELETE (transaction SE37) in test mode,enter SCPR_FLDV_TAB as tabname and choose execute.

Continue with the upgrade. In case you need to reset the upgrade,activate the table type SCPR_FLDV_TAB in transaction SE11.

o When using strategy downtime-minimized:

Just before starting the downtime with phase MODPROF_TRANS, executethe following command on the database:

delete from "DDNTT~" where tabname = 'SCPR_FLDV_TAB'

On database IBM DB2 for i5/OS, use the following command:

delete from "DDNTT^" where tabname = 'SCPR_FLDV_TAB'

If phase XPRAS_UPG already aborted with syntax errors inprogram "%_CSCPR " and the following error message is displayed:"The type name "SCPR_FLDV_TAB" is ambiguous, ..."run the function module DD_NAMETAB_DELETE (transaction SE37) in test mode,enter SCPR_FLDV_TAB as tabname and choose execute.Repeat the phase XPRAS_UPG.

--------------------------< I006704 DEC/12/05 >----------------------Phase: XPRAS_UPGDescription: If your codepage does not equal 1100, you may get a codepageconversion error. In this case, replace the current kernel with the latestversion and repeat the phase.

--------------------------< D039929 OCT/19/05 >----------------------Phase: XPRAS_UPGDescription: If your codepage does not equal 1100, you may receive thefollowing error message:Runtime Error: CONNE_IMPORT_CONVERSION_ERRORException: CX_SY_CONVERSION_CODEPAGEThis error can only be prevented by including SAP_BASIS Support Package 05in the upgrade, which includes correction transport Y7AK014268.

-----------------------< D023890 MAY/23/06 >---------------------------Phase: RUN_RSDB02CK_ENDDescription: The phase stops and log file RSDB02CK.ELG displays thefollowing error message:2EETG000 Primary index "MEMGMT_DEPLOYMNT-0" does not exist in the databaseCheck that the primary index of table MEMGMT_DEPLOYMNT exists. If not,create the index manually. If you still get the message thatMEMGMT_DEPLOYMNT00 is an unknown object in the dictionary, drop it on thedatabase level.Repeat the phase.

----------------------------------------------------------------------Phase: CHK_POSTUPNote: 996953Description: Log file LONGPOST.LOG asks you to migrate a CMOD projectalthough no project exists.

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

23.06.2008 Page 12 of 16


VII/ Problems After the Upgrade

This section addresses known problems that cannot be avoided usingpreventive measures. These problems will only occur under specificcircumstances.

-----------------------< D000587 25/FEB/08----------------------------Error when Converting Print ParametersAfter the upgrade, in some clients the printing parameters have either goneor been replaced by other parameters. For more information, see Note1142364.The problem is solved with SAP Basis Support Package 16.

----------------------< D023536 17/DEC/07 >---------------------------DB02: Unknown Objects in SAP DictionaryIf you have included SAP Basis Support Package 10 in the upgrade,transaction DB02 reports tables which do not exist in the SAP Dictionary.For more information, see SAP Note 1122725.

----------------------< D020815 03/JUL/07 >---------------------------Missing BAdI ImplementationsIf you include SAP Basis SP11 in the upgrade, in Customizing, someimplementations for switching on or off are missing for a BAdI activity.This problems is solved with SAP Basis SP 13.For more information, see Note 1065960.

----------------------< D021078 03/JUL/07 >---------------------------Transaction DB02: Tables not known to DDICIf you have included SAP Basis SP 12 in the upgrade, transaction DB02 maylist 30 tables as "Unknown objects in ABAP Dictionary". The table names allstart with "DB6".For more information, see SAP Note 1068628.

-----------------------< D033258 DEC/12/05 >-------------------------Addition to the Release NotesThe depreciation posting run and the periodic posting run for APC valuesmust be converted to document number ranges that use an internal documentnumber assignment.For more information, see Note 890976.

--------------------<enhanced D038245/JUNE/05 >---------------------------------------------< D003551 02/MAY/05---------------------------Check Primary Index of Table MEMGMT_DEPLOYMNTAfter the upgrade, check that the primary index of table MEMGMT_DEPLOYMNTexists. If not, create the index manually.If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown objectin the dictionary, drop it on the database level.

-----------------------< D000434 28/JAN/04 >-------------------------Source Release 6.20: Missing DB View STWB_INFOIf your source release is based on SAP_BASIS 6.20 SP 48 or lower,transaction DB02 might show DB view STWB_INFO missing after the upgrade.This view is not needed in the system and requires no further actions.

23.06.2008 Page 13 of 16


------------------------< D020815 AUG/23/02 >-------------------SPAU: Names of interface methods are truncatedSome methods (ABAP objects) that were modified and overwritten by theupgrade can be displayed in transaction SPAU with their names shortened to30 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 inSPAU. It is easily possible to overlook these!For more information about the correction, see Note 547773.

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

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

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

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

VIII/ Chronological Summary

Date.....Topic..Short description-----------------------------------------------------------------------FEB/27/08...VI..Phase: STOP_SHDI_LAST - Remote Shadow InstanceFEB/25/08..VII..Error when Converting Print ParametersFEB/08/08..III..Dual Stack Upgrade: Downtime-Minimized OnlyJAN/17/08....V..Source Release SAP R/3 4.6C: Including a min. SP levelJAN/14/08...VI..Phase ACT_700: Error with SAP_BASIS SP 14DEC/17/07..VII..DB02: Unknown Objects in SAP DictionaryNOV/28/07...VI..Phase XPRAS_UPG: Syntax errorNOV/26/07....V..Source Release 4.6C and below only: Phase TABIM_UPGNOV/12/07..III..Windows only: Upgrading the Application ServersSEP/07/07..III..New Entry Page to SAP NetWeaver Library DocumentationJUL/03/07....V..Parameter for the Central Syslog rslg/collect*JUL/03/07.VIII..Missing BAdI ImplementationsJUL/03/07.VIII..Transaction DB02: Tables not known to DDICMAY/09/07....V..Preparations for FI-CAAPR/23/07..III..Migrate data from table TVARV to TVARVCMAR/15/07...II..MSCS ConfigurationFEB/28/07...VI..Applying Support Packages on the Source ReleaseFEB/28/07...VI..Phase CHK_POSTUP - CMOD/SMOD migrationFEB/05/07....V..Back up customer-specific entries in table EDIFCTJAN/23/07...II..SAP NW BI: Do not include BW SP 11JAN/04/06..III..Modification Adjustment Planning: Unicode RequestDEC/18/06....V..New SPAM/SAINT Version on Source ReleaseDEC/15/06..III..Migration of Workload Statistics Collector Data

23.06.2008 Page 14 of 16


AUG/28/06....V..Update SAP Kernel on Source ReleaseMAY/23/06...VI..Phase RUN_RSDB02CK_END: Index MEMGMT_DEPLOYMNTAPR/24/06....V..Prepare table COEP for the upgradeFEB/28/06...VI..Phase MODPROFP_UPG fails - check J2EE EngineDEC/12/05....V..SD Texts: Check Text Customizing on Source ReleaseDEC/12/05..VII..Addition to the Release NotesDEC/12/05...VI..Phase XPRAS_UPG: Codepage Conversion ErrorNOV/07/05...VI..Phase: JOB_RSTLANUPGNOV/02/05....V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64OCT/19/05...VI..Phase: XPRAS_UPG - CONNE_IMPORT_CONVERSION_ERROROCT/07/05...VI..Phase: SHADOW_IMPORT_INCSEP/22/05....V..Upgrading with reintegrated add-ons (retrofit)21/SEP/05....V..Checking Application LogAUG/16/05...VI..Windows only: KX_SWITCH - Check file NTPARVAL.LOG.AUG/16/05....V..Windows only: Last profile text line - line feedbackJUL/13/05....V..Source Rel. ECC DIMP 5.0: MPN Conversion ExitMAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNTFEB/02/05...II..LSWM now part of SAP_BASISJAN/28/05..VII..Source Release 6.20: Missing DB View STWB_INFO14/OCT/04....V..Component PS-ST-WBS: Prel. Inclusion of Field KIMSK14/OCT/04....V..Source Rel. 4.0B: Project-Related Incoming Orders14/OCT/04....V..Source Rel. 3.1I: Loss of Address Data06/OCT/04....V..Source Release 4.6C and below: SMODILOG EntriesSEP/09/04....V..Source Release Extension Set 1.10: Exchange containersAUG/10/04...VI..Phase JOB_RDDNTPUR: TA22EQU_WAO without referenceJUL/26/04...VI..Start-Rel. 3.1I / 4.0B: Phase TR_CMDIMPORT_FDTASKSAPR/19/04....V..Unicode Systems: Downward Compatible Kernel 6.40JAN/27/04....V..Upgrading with PI/PI-ADEZ/03/03...II..Windows only: Execute program R3dllins.exeSEP/17/03....I..SAPup keywordAPR/24/03....V..Upgrade on AIX: saposcolDEC/10/02....V..Upgrading with AIX 5.1AUG/23/02..VII..SPAU: Names of interface methods are truncatedJUL/23/02 ...I..Windows: Windows XP is not supportedJUL/19/02...II..Problems with the shadow instanceMAY/24/02...II..Corrections and repairs for the upgradeMAY/23/02...VI..Phase CHK_POSTUP - objects without DDIC referenceAPR/11/02...VI..Termination in the TOOLIMPD3 phaseFEB/20/02....V..Source releases on UNIX 32-bit or AIX 64-bitOCT/19/00..VII..Linux: Importing the new saposcol versionFEB/16/00..VII..saposcol version 32-bit or 64-bit on Reliant UNIXFEB/16/00..VII..saposcol version 32-bit or 64-bit on Solaris----------------------------------------------------------------------

Header Data

Release Status: Released for CustomerReleased on: 27.02.2008 11:12:01Priority: Correction with high priorityCategory: Upgrade information

Main Component BC-UPG-RDM README: Upgrade Supplements

23.06.2008 Page 15 of 16


Valid Releases

Software Component Release FromRelease

To Release and Following

SAP_APPL 600 600 600

SAP_BASIS 70 700 700

Related Notes

Number Short Text

1170069 Text lines are returned twice when reading text files > 2 GB

1122725 DB02: Unknown objects in SAP Dictionary after Upgrade

1069225 NO HW ID RECEIVED BY MSSG SERVER

1068662 ME51N: Default values disappear after you upgrade

1068628 DB02: 30 tables starting with 'DB6' not known in DDIC

1065960 Missing BAdI implementations in IMG

1013807 Problems after upgrade to NW2004s - Adding table entries

1011190 MSCS:Splitting the Central Instance After Upgrade to 7.0/7.1

1006116 Migration of workload statistics data to NW2004s (2)

1005238 Migration of workload statistics data to NW2004s

996953 SPAU entry exists for nonexistent CMOD project

946659 ICNV for cluster tables and extension of TIMESTAMP

938706 ME21N: Default values disappear after upgrade

937389 COEP line item display incorrect after upgrade

900607 Checklist: SD texts when upgrading to 4.70 and higher

890976 Converting closing report to internal doc number assgnmnt

884809 SQL Error 11 - General network error

865142 Customer-specific entries in EDIFCT are deleted

858271 Upgrading to EH&S in ERP 2005/ERP 6.0

854523 MPN conversion exit is delivered as 'active' by default

838003 Industry add-ons integrated into SAP ECC 6.0

838002 Add-ons (non-IS) that are integrated into SAP ECC 600

834815 Upgrade to SAP ECC 6.00 with FM

825146 Add. info. on upgrading to SAP NW04s (SR1, SR2. SR3) MSSQL

822379 Known problems with Support Packages in SAP NW 2004s AS ABAP

822296 Additional info: Upgrade to SAP NW 2004s AS ABAP (iSeries)

821032 Corrections for SAPup release 7.00

819876 DB6: Additional info about upgrade (based) on SAP NW AS 7.0

819655 Add. info.: Upgrade to SAP NW 2004s ABAP ORACLE

817463 Addtnl info for upgrades to SAP NetWeaver 2004s ABAP: MaxDB

815202 DB2-z/OS: Additions upgrade to SAP NW AS 7.0

813658 Repairs for upgrades to products based on SAP NW 2004s AS

741280 OS60: Updating parameter effectivities

716378 Missing libraries during Unicode upgrade

23.06.2008 Page 16 of 16


Number Short Text

705485 Error in TR_CMDIMPORT_FDTASKS and TR_CMDIMPORT_PREPARE

700779 Upgrading SAP ECC 500/600 with PI/PI-A/SLL_PI

674070 Tables in the substitution container after an upgrade

673066 LSMW: Upgrade to SAP Enterprise 4.7 (or Basis 6.20)

626272 Termination in the JOB_RSTLANUPG phase

557314 As of Release 610: TVARV replaced with TVARVC

547773 SPAU: interface method names are truncated

526694 saposcol based on AIX perfstat library

525677 Problems when starting the shadow instance

502532 Composite SAP Note: Migrating to AIX 5L for 64-bit software

499708 Additional information on upgrading to Basis 620 with AIX

496963 32-bit source release in upgrades to 620

430318 Shadow instance on other operating system

369542 CJA1: Upgrade of Release 4.0 preliminary solution to >= 4.5

360929 Loss of address data on execution of RSXADR05

197886 Upgrade: messages in CHK_POSTUP: BDL*, STSL*, BAM*, SQLR*

196113 SAPSQL_ARRAY_INSERT_DUPREC, BALHDR

185315 SFAC:Advance inclusion of KIMSK into field select.

162980 saposcol for 64-bit Solaris

148926 saposcol version 32 or 64 bit on ReliantUNIX

19227 Open newest saposcol

Documents

Add-Info-on-Upgrading-to-SAP-ECC-6-0-SR2-ABAP