SAP 4.7 Upgrade

[Former Member]

Hi,

My client is <b>upgrading from SAP 4.6C to 4.7.</b> Oracle 9i and AIX 5.4 are used as database and o/s.

Would appreciate, if any step by step instructions and also any issues encountered during upgrade is appreciated.

Thanks in advance !!

Raj

[Former Member · Accepted solution]

Functionally Enterprise is more or less identical to 4.6c in fact the release is 4.7 indicating the changes are slight. It's the technology that underlies (BASIS layer) that is radically different. Essentially a full J2EE runtime environment and Web Dynpro open up some really exciting possibilities for transactional web services and integration with portals for rolling out custom functionality on a global scale, ESS and custom apps for light users.

Also, XML messages can be exchanged for interfaces with other systems, legacy data import/export, raising PO's etc.

From the business side, it's just like 4.6c.

However, after the upgrade, you need to thoroughly test all the roles against the test scripts. We had to amend nearly every role so they still worked as they did under 4.6c.

Not sure if it was just the way we set the roles up, but this was the biggest change we found.

Use this link:

https://websmp201.sap-ag.de/~sapidb/011000358700001453302003E/menue2.htm for more information/to compare versions....

[Former Member]

1. Built a project team

2. Order upgrade media

3. Order GoingLive Functional Upgrade Check

4. Work through the upgrade guide (https://websmp202.sap-ag.de/instguides) and the related notes (e.g. 534334, 575280, 587896, etc.)

5. Make a copy of the PRD system to an Upgrade-Test-System (UPG)

6. Make a first test upgrade on UPG

7. Make tests and get experiences on UPG

8. Upgrade your DEV then QAS

9. Apply the necessary changes

10. Upgrade your PRD

[Former Member]

I am interested more specific on merging Authorisation of New and Old. Also how to test changed profiles? Detailed info. would be appreciated.

Thanks,

Sam

[Former Member]

Sam

The testing was completed by the Support Teams against the roles created for the business users.

We had test scripts for each transaction so knew the expected outcome. When we didn't get the expected outcome we were provided with SU53s for the failed transactions... kept the Basis team very busy for a few weeks, but we had a ramp up approach to production and wehad about 3 months of testing both dev and QA before applying the upgrade to production.

These scripts are used at every patch upgrade in QA - we did both positive (expected results) and negative testing (to make sure there were no security holes).

We test the baseline config in Dev to make sure we can still create sales order and purchase orders (etc), then in QA we make sure we can test the creation of sales orders using the Income Generator Role, and create PO documents with the Purchase Officer role (etc)....

Due to the specific nature of our Business (Public Sector) these scripts will not be of any use to anyone else!

Feel free to ask if you need any further information...

[Former Member]

Dear Barry

we are in the proceess of upgrading our 4.7 system to ERP 6..how are we going to address the authorization testing/changes in an upgrade..whats is the recomended methodoloy for this apporch , my objective is to keep the same level of authrorizations for the users which exist in 4.7 to new system ..

if you can guide me to some source where i can refer will be highly appreicated

Buddhike