Product Information
Reasons To Upgrade From SAP ERP 5.0 To SAP ERP 6.0
Why Stuck to SAP ERP 5.0?
SAP Enterprise Resource Planning Central Component which is called ‘SAP ECC’ is an on-premise enterprise resource planning (ERP) software. SAP ERP 5.0 was released in 2004 and SAP ERP 6.0 was released in 2005. Between 2005 and 2019 SAP has routinely released multiple enhancement packages to keep up with changing customer requirements. SAP ECC 5.0 is part of SAP ERP 2004 which runs on SAP NetWeaver 2004. SAP ECC 6.0 is a part of SAP ERP 6.0 (2005) which runs on SAP NetWeaver 7.0 (2004s).
Globally, almost 80 percent of all the SAP customers are running at least one SAP ERP 6.0 system which means that four out of five customers have moved completely or part of their installation to 6.0 according to Van Rossam. There are many new features in SAP ERP 6.0. It will support Web Dynpro for ABAP. It has a new ABAP Editor.
Do You Really Need to Overpay?
In SAP ERP 5.0 you are almost without support or expensive customer-oriented support which might cost huge. Whereas in SAP ERP 6.0 you will be quite close to nothing i.e. no legal fixes etc. There you will pay as per the incident requirement.
Think About the Increased Security
In most of the cases, it is better to go for the upgraded version. Nothing is different in this case also. SAP ERP 6.0 will provide you more security. SAP ERP 5.0 provides one stack whereas in SAP ERP 6.0 we can install four stacks.
The strong dislike against SAP ERP 5.0 will upgrade to SAP ERP 6.0 and the “skater on thin ice” will stay on SAP ERP 5.0, with the knowledge that a critical failure could turn into an avalanche.
Do You Really Want To Stay With Old Functionalities?
In SAP ERP 5.0 you can’t add new functionalities whenever you need them.
SAP provides several ways of capturing an order within the system.
In SAP ERP 6.0 you will get many new functionalities like :
1.Pickup list – Batch where-used list display in transaction MB56.
2.Usability enhancements for transaction MIGO for the posting of goods movements. The transaction for goods movements MIGO has some new functions like Transfer postings and stock transfers.
3.New report: display list of invoice documents (MIR5). Requirement prioritization in materials management.
4.Mass maintenance of outline agreements.
5.Goods receipt: new movement types in inventory management.
About APPSeCONNECT (Integration Platform as a Service):
Now, you can easily integrate your SAP ERP with Ecommerce store or CRM System to automate the business process!
To say I am puzzled by this blog is a mild understatement.
If you were on a lower release then ECC 6.0 and wanted to upgrade, then S/4HANA would seem to be the logical choice. You have to migrate to S/4HANA eventually anyway, so why go through the pain of TWO upgrade projects, especially as the S/4HANA change is pretty much an ERP system replacement as opposed to an upgrade thus ten times more difficult.
Am I missing something obvious here?
Hi Paul Hardy
If i was supposed to purchase a new sap erp system, then it was feasible to go for SAP S/4 HANA. If i have an existing business in SAP ERP 5 and i want to upgrade and use new features, then as a user i would not like to change my existing business architecture altogether and instead i would upgrade to SAP ERP 6.0 to get some additional features.
Best Reagrds,
Anmol
As I understand it n 2004, a new release of SAP was released under the name "mySAP 2004" which is now ECC 5.0. The next year "mySAP ERP 2005 was released which is now ECC 6.0"
The mySAP2004 or ECC 5.0, whatever you want to call it, went out of mainstream support in March 2010. That is almost ten years ago now, which is not to say a lot organisations still might be on it.
Going off on a tangent for second, you note an advantage of ECC 6.0 is that it supports ABAP Web Dynpro, which indeed it does. However SAP does not advocate using Web Dynpro for new developments, and has not for a long time. UI5 is the way forward.
Getting back on track, it is true that moving to S/4HANA is, in effect, an ERP replacement. I can understand why people do not want to do that but sadly SAP has left them no choice.
Tying this all together an organisation who is on ECC 5.0 and therefore has not upgraded for ten years is not the sort of organisation who likes frequent changes. Given this moving to ECC 6.0 which runs out in 2025 might not be the best option for such an organisation.
Cheersy Cheers
Paul
Dear Paul,
That's absolutely correct point.
But from technical perspective, there number of limitations from applications, DB & OS side.
As far as I know, we need to do two step conversion for this environment.
Cheers!
Regards
Wajid