Upgrade to CRM7.0

CRM 7.0 upgrade at Australia Post

Motivation

We are preparing to
deploy a new project and added functionality on the existing CRM2007
platform. So what better time to peform the CRM7.0 upgrade and realise
the cool user driven web application improvements made to the existing
enterprise software application.

The CRM 7.0 upgrade will take the CRM2007 server to
CRM7.01. This means you get the CRM Application upgraded to Business suite
Foundation 7.0 and the underlying NetWeaver7.0 upgraded to Enhancement Pack 1

1. CRM2007 Dual Stack
2. AIX 5.3 TL7
3. Oracle 10.2.0.4
4. [Support package level before upgrade | http://i30.tinypic.com/2e5ttfs.jpg]
5. [Support package level after upgrade | http://i30.tinypic.com/2gydtfd.jpg]

The upgrade for both ABAP and Java is synchronized by running the
upgrade programs SAPup and SAPJup. The Java server upgrade is started after the
Configuration roadmap step of the ABAP server upgrade is completed. Ensure the J2EE Engine is up and running, do not stop the J2EE
engine manually and let SAPup/SAPJup take control.

Upgrade preparation

1. [CRM ABAP upgrade master (note 1292070) | https://service.sap.com/sap/support/notes/1292070]
2. [CRM JAVA upgrade master (note 1156186) | https://service.sap.com/sap/support/notes/1156186]
3. [Back up table EDIFCT (note 865142) | https://service.sap.com/sap/support/notes/865142]
4. Various Oracle notes (558197, 830576, 983548, 669902, 819655, 836517)
5. [Shared Pool Special (note 556764) | https://service.sap.com/sap/support/notes/556764]

1. 51036905 – CRM Java Components
2. 51036855 – CRM Upgrade Export
3. 51036853 – CRM Language
4. 51036854 – CRM Components
5. 51036767 – CRM Kernel 701
6. 51033402 – CRM Add ons
7. 51036860 – CRM Upgrade export
8. 51036861 – NW701 Language
9. 51036889 – Upgrade Master
10. 51036862 – New Java Components

When you start, the ABAP installer will ask you for a username, password and role. If you proceed as the administrator, you will be presented with the ABAP SDTGui configuration roadmap.

• [Initialization | http://i25.tinypic.com/28cnk2f.jpg]
• [Extraction | http://i30.tinypic.com/311s3t3.jpg]
• [Configuration | http://i32.tinypic.com/2igm7vc.jpg]
• [Checks | http://i31.tinypic.com/2iafq07.jpg] (Start your JAVA upgrade at this point)
• [Pre processing | http://i28.tinypic.com/1116uy8.jpg]
• [Downtime | http://i27.tinypic.com/23mu4h2.jpg]
• [Post Processing | http://i31.tinypic.com/ojijup.jpg]
• [Finalization | http://i31.tinypic.com/2mdp9he.jpg] 

When you start, the JAVA installer will ask you for a user name, password and role. If you proceed as the administrator, the Java SDTGui will start, and it will look a little different to the ABAP SDTGui.

1. [Start the upgrade | http://i27.tinypic.com/59sl5u.jpg] 
2. [Prepare | http://i32.tinypic.com/2q8dnjs.jpg]
3. [Initialization | http://i31.tinypic.com/30iamnr.jpg]
4. [Extraction | http://i29.tinypic.com/e16kyh.jpg]
5. [Configuration | http://i25.tinypic.com/2yuaijt.jpg]
6. [Check | http://i29.tinypic.com/263ui35.jpg]
7. [Finalization | http://i27.tinypic.com/2cxda36.jpg]

1. SGEN, SICF, SMQR, SMQS
2. Finalise alloutsatanding SPAU conflicts
3. Delete old tablespace PSAPSR3700 using BRSPACE
4. Import EDIFCT table
5. Backup and switch on Archive redo logs
6. Activate VMC for IPC

Timing

With proper preparation, our upgrade was performed in less than 1 day with total downtime of less than 1 hour. Depending on how many notes and changes you have applied, the longest part of the upgrade will be the SPAU conflict resolution process.