Upgrade-to ECC60-Unicode-Conversion

SAP Upgrade Plan R/3 4.7e to ECC6.0 and Unicode Conversion

Prepare:-

1. Apply the latest SAP 6.40 Kernels Patches and SPAM update on 4.7 system.2. Apply the OSS transport Y6BK0817143. Execute the report RADNTLANG submit as a background job (will run

overnight). 4. GoTo transaction SPUMG in your 4.7 system and follow as shown in the screen

below

5.

6.

7.

8.

9. Change the Code page from 1100 to 1160. ( If the CODE page is already 1160 you can skip step 10).

10. To do this you need to delete the two lines and add them back. 11. Change the SPUMG settings by going through SPUMG Scanner settings

make changes as shown in the screen below.

12.13. Initialize the work list from SPUMG SCANNER INITIALIZE

WorkList. (This will submit a background job). Wait until it finished the job and refresh the screen.

14. Skip to step 19 if your TABLE LIST shows under the consistency check list in SPUMG Transaction.

15. The screen should look like as shown below.

16.17. Schedule the jobs by selecting the “Schedule Worker Job” Fill the screen as

shown below

18. You can schedule multiple jobs by repeating the above steps.19. Determine host (Central Instance) to run first. SAPDEV0020. Create empty upgrade directory /usr/sap/put21.

a. <SID>adm as ownerb. 10GB minimum freespacec. Must be installed on central instanced. Group SAP_LocalAdmin needs Full Control permissione. MUST be empty before running PREPARE

22. Ensure there is a minimum of 500MB of free space in the database. (review later)23. Run report Z_873466_REPAIR_AFTER_UPGRADE prior to the upgrade

a. For more see note 873466 (Prepare will tell later which tablespaces need space)

b. Before you start prepare execute the command ORATBSXT.BAT from s:\ECC6032bit_upgrade. ( which will increase the necessary tablespaces for prepare and upgrade)

24. Verify that the computer host name capitalization is consistent with how it is in Windows.

a. Check the SAP Profiles, and if a change is made, stop SAP and the services and start them again.

b. Check entries in the HOSTS filei. Ensure that all systems in the landscape are present

ii. Ensure that the host of the machine you are working on is listed in the HOSTS file as well

iii. Do not use aliases such as: 10.10.10.10 mach MACHc. Use SM51 to check the host name. The name in the first and second

column must be identical, and match the name assigned to the computer.d. Use RZ04 and make sure the host name matches in the operating types as

well.\

i. While there, ensure upgrade format for work processes

25. With the database and SAP up, from the CI machine you are upgrading, run PREPARE.BAT from the upgrade master DVD

a. Choose the EXIT option.26. From the upgrade directory run

a. Backup SAPup.exeb. Sapcar –xvf S:\ECC6.0_Upgrade\ERP2005SR2_7-20000914.SAR

27. From the upgrade directory/bin runa. Sapcar –xvf S:\ECC6.0_Upgrade\SAPup7002_15-20001261.SAR

28. Start the upgrade assistant servera. From a command prompt running as <SID>admb. Enter: java –cp <upgrade directory>\UA\ua.jar UaServerc. Enter the one password for both administrator and observer role.

i. Change them in the UA menu: Administrator -> Change Passwords

d. Wait for the prompt: UaServer> Ready29. Start the UA GUI

a. Ensure your computer has JRE 1.4.2 or higherb. Using a web browser on your PC, open: http://<host name>:4239c. On the following screen choose: Start Upgrade Assistant

30. Start the UAa. Enter the requested information and choose Administrator role, then click

login.31. From within the UA click Administrator -> Start Prepare32.

33.

34. Use the > button to enter more CDs35. Use the >> button then OK to continue the upgrade process36. Continue through several screens until the following

37.

38.

39.

40.

41.

42.

43.

44.

45.

46.

47.

48.

49.

50. Connect to the Solution Manager SAP System and run transaction: SMSYa. System -> Other Object

b.

c. Click the Key

d.e. Click Generate Keyf. Return to UA

51.

52.

53.

54.

55.

56.

57.

58.

59.

60.

61.

62.

63.

64.

65.

66.

67.

68.

69.

70.

71.

72.

73.

Make sure you are using common SAP Trans directory. All the patches are unpacked at that location. Below is the patch level’s for the upgrade.

Please select “YES” this will save the variants

Restart all the Failed Checks.

Start Upgrade To start the Upgrade from the upgrade Assistant.

Select the Downtime-minimized option

Select the time to “8” which will finish the step EU_IMPORT in 8 hours. For production, we will increase which will put lot of load on the system.

Select the option “MODPROF_TRANS” option for the Archive log mode off. System will wait for you to switch off the archive log Mode before the downtime starts.

If you get this error go to transaction SM13 and clear all the update logs if there are any.

Back-up the backint file.

After this point you the system will be locked and you cannot import any more transports.

Please select “NO Adjustments” This for SPDD list. After the upgrade a POST Upgrade transport will fix the issue.

If you get the above error login to shadow instance with DDIC user and create a new user to login. execute the function module

Goto transaction SE37 DD_NAMETAB_DELETE Table name as “ E_BAMMAPNG” Repeat above steps for E_BAMUIBT and IOHEADER

For view ZVMSEG

Goto transaction se11 and ZVMSEG

Select option “change”

Change the order as shown below and activate. Ignore any warnings in the activation.

MANDTMBLNRMJAHRZEILEBWARTMATNRWERKSLGORTCHARGSOBKZLIFNRKUNNRSHKZGDMBTRMENGE

Continue the phase

Disable the archive log mode by executing the command alter database noarchivelog; or use the BRTOOLS to do this.

DOWNTIME PHASES STARTS :- Perform System Full offline back-up.

Select the option “revision complete” all the correction steps will be down after the upgrade.

UPGRADEPHASE XPRAS_UPG1PEPU203X--> Messages extracted from log file "SAPR700WF4.DEV" <--

Long text: Cause During the upgrade, a message relevant for postprocessing was written to a log file. This message is not dealt with until the end of the entire upgrade. The upgrade continues. System Response The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by R3up. What to do Note the messages following this message and proceed according to the

instructions.

A2PESEEF_BADI 152 CMOD " " for SMOD "V56LDELI" has yet to be migrated

Long text: Cause Migrate CMOD implementation " " using transaction SPAU System Response What to do To migrate the CMOD implementation to a new BAdI, you must call up transaction SPAU, and then select "Migration Objects" under the tab "Modifications". You will find your SMOD implementation under Migration Objects -> SAP Enhancements. To start the migration, select your CMOD implementation by clicking on it. Tasks for system administration

1PEPU203X--> Messages extracted from log file "SAPR700ZF1.DEV" <--

Long text: see above

A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"

UPGRADEPHASE JOB_RDDNTPUR1PEPU203X--> Messages extracted from log file "RDDNTPUR.DEV" <--

Long text: see above

3PETG447 Table and runtime object "STGLTRAN" exist without DDIC reference ("Transp. table")

Long text: Cause A runtime object was found for a table which is unknown in the ABAP Dictionary. The table contains data, which is why, as a precaution, the runtime object was not deleted. Since there is a runtime object, this means the table was once created in the ABAP Dictionary. The fact that the table can no longer be found

in the ABAP Dictionary could be due to the following reasons: It is a customer-specific table which was created when the correction system was switched off. Depending on the history of your system, there may also be SAP tables which were not deleted completely, or for which only the runtime object was delivered without the related definition in the ABAP Dictionary. System Response What to do RESET N1 Customer-specific tables If it is a customer-specific table, and you still need the data, try to restore the table in the ABAP Dictionary. Note the specified table type when you do this (transparent table, pool table, and so on). The table may still, for example, be contained in the version database. You can access version management through the menu "Utilities" in the in the ABAP Dictionary (transaction SE11). You may also still have a copy of the system that still contains the table definition. You can also display the runtime object and create the table according to the field names, types and lengths specified in the definition. You can display the runtime object in the menu "Extras" of the database utility (transaction SE14). Tables in the SAP namespace Search for notes on these tables in OSS using the key words RDDNTPUR and TG447.

3PETG447 Table and runtime object "STSLEVNTSV" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "STSLTOBJSV" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "STSLTRANSV" exist without DDIC reference ("Transp. table")

Long text: see above

Start the Oracle Stats By executing the script

brconnect -u / -c -o summary -f stats -o SAPR3 -t all -m +I -s P10 -f allsel,collect,method,precision,space,keep -p 8

The above command will take at least 6-8 hours.Run Report COM_PRODUCT_UPGRADEInstall the ST/PI-A patch using SAINT transaction.Run Report TWTOOL01Run report UMG_ADD_PREP_STEPRun UM4_FINISH_PREPERATION programRun SPUMG check as shown in the top session of this document. Only submit the jobs do not change the settings.

Shutdown the SAP system.Start the export as shown below.

Log in again to continue

Adjust the each tablespace size as following sizes

PSAPSR3 242,121,664PSAPSR3700 54,525,952PSAPSR3USR 2,097,152SYSTEM 2,097,152SYSAUX 1,048,576PSAPUNDO 4,194,304PSAPSR370 4,194,304PSAPTEMP 8,388,608

Turn all off

Defaults

Defaults

Informational

Defaults

Use SMSY on Solution manager box to get key:

Click Key Icon

Click Generate Key button

While install continues…

Log into SAP System and run transaction SLICENSE to apply the license key.

From DB02 click RefreshClick second button – DB Checks & Update Histories

Install Data Protector Client

Restore usr/sap/trans folder from backup

Run STMS, go to Overview Systems, Double Click on the system and fake a change

For development only if you are using the same SID:Using se16, view the E070L table in the source system, to find the last transport number used, and add 1000 to it.

Check in se16 on the target system if the number in E070L is at least + 1000 from the source system. If not run the following:

Then on the target system from the command prompt type:Sqlplus /nologConnect / as sysdbaUpdate sapr3.E070L set trkorr = ‘<src transport number + 1000>’;Commit;

Verify on target system with se16 that E070L now displays the new transport number.

Update operational modes in target system

From RZ04 double click the operation modeRemove systems not intended to be in the target system landscape

Go into RZ10 in a new sessionUtilities -> Import Profiles -> of Active Users

Back in the other session with RZ04 still openInstance -> Create Instance

Enter the appropriate information for your target system.

Say No

Highlight your operational mode, and go to:Instance -> Set to Active

Run transaction RZ03Highlight the server and go to:Control -> Switch Operation Mode -> All ServersSay “Yes” to both popups.

End of OP Modes

Run UMG_HISTORY & UMG_POOL_TABLE&RSCPINST from SE38

From SE38 still run RUTTTYPACT_OLD in the background as follows:

Before running SGEN:From the executables directory in usr, run ARCHIVE_OFF.BATRun SGEN and regenerate all objects

Note: May need to increase the tablespace for SGEN to have spaceSqlplus /nologConnect / as sysdbaAlter tablespace PSAPSR3 add datafile ‘e:\oracle\<SID>\sapdata#\sr3_##\SR3.DATA##’ size 4096M autoextend off;

Schedule the Database statistics from DB13.

Adjust the profile parameters as shown below

zcsa/table_buffer_area = 30000000zcsa/presentation_buffer_area = 4400000rsdb/cua/buffersize = 3000rdisp/elem_per_queue = 2000

rsdb/ntab/entrycount = 30000rsdb/ntab/irbdsize = 30000abap/buffersize = 400000rtbb/buffer_length = 30000rsdb/ntab/ftabsize = 40000em/initial_size_MB = 6144PHYS_MEMSIZE = 6144rdisp/wp_no_dia = 6rdisp/wp_no_btc = 5rsdb/obj/large_object_size = 16384rsdb/obj/buffersize = 8192