Difference between ECC 6.0 vs 4.

7EE
Difference between ECC 6.0 vs 4.7EE

ECC means Enterprise Central component.

SAP R/3 4.7 is based on the 3-tier architecture.
With ECC SAP evolved into using the Internet technology and is called as service oriented architecture (SOA). There are lots of
functionalities available in ECC 5.0 and ECC 6.0 compared to R/3 in integrating with other systems.

All the differences in release notes of SAP ECC can be found here:
http://help.sap.com/saphelp_erp2004/helpdata/en/9e/f8da406dd4b533e10000000a155106/frameset.htm
https://websmp204.sap-ag.de/bfp
http://solutionbrowser.erp.sap.fmpmedia.com/Search.aspx

Here is a brief review:

Some of the differences in SD Module are:

1. Enhancement of SD documents with new modification management, budgeting, and billing functionalities, including support
for alternative billing structures. This function helps customers meet specific legal requirements relating to change
management, budget allocation, and invoicing
2. Document Flow: In ECC 6.0, the flow of sales documents is seen much better and improved as compared to 4.7.
3. Sales Order Look and Feel: There are more tabs in ECC 6.0 for Item Level Details.
4. ECC 6.0 is built on Net Weaver Technology (SOA - service oriented architecture), hence more reliable and improved as
compared to previous one.
5. Valuated Delivery Note: enables to print a delivery note on which the values of the expected invoices are shown.
Difference between ECC 6.0 vs 4.7EE

Some of the differences FI Module side:

  
1.      ECC 6.0 enables Business area posting - Segment reporting made easy.
2.      Profit center accounting is through new GL.
3.      Document splitting: Split of entry to post assets and liabilities to respective profit centers. (Balance sheet items)
4.      Enables commitment of FM, improved CRM feature & Mobile sales feature
5. Added SAP NetWeaver Mobile, a component of SAP NetWeaver that allows you to Mobilize business processes
6. The authentication and SSO has been reorganized to align the configuration and administration tasks in enabling an
authentication or SSO mechanism to the user interface used for authenticated access.

Some of the differences MM Module side:

  
1.      Redesign of Funds Management Warehouse Concept
2.      Enhanced Order Optimization
3. Functional Enhancements for Transaction MIGO
4. Warranty Claim Processing (Enhanced)
5. Interactive Forms for Creating and Changing Products: products can be created and changed by using the following
interactive forms:
– Request form New Product
– Request form Change Request for Product
Difference between ECC 6.0 vs 4.7EE

Some of the differences ABAP Module side:

1. For installing ECC 6.0 you require a solution manager key. With out solution manager key you cannot install ECC6.0.
ECC 6.0 is called net weaver component with ABAP+JAVA stack
For installing 4.6 you don't require solution manager key. I t only having ABAP stack.
2. ECC6.0 supports UNCODE & 4.6C supports NONUNICODE.
3. ECC is more towards OOPS concepts, ECC is very developer friendly
4. It has new debugger.
5. New Enhancement Framework is introduced in ECC.
6. It is more efficient to use Adobe forms in ECC.
7. ECC has new options in BADIs where you can create your own badis and implement it.
8. You have new concept called Implicit and explicit source code plugins in ECC.
9. Has WebDynpro component accessible from SE80 transaction Itself.
10. In terms of ABAP some function modules are obsolete in 4.7. e.g. WS_UPLOAD, WS_DOWNLOAD etc. You can find the list of
obsolete FMs in the table RODIR. These need to be replaced in the ECC System.
11. Also ECC is very strict in case of EPC Errors. You need to check the EPC and remove the call function interface errors where
it says SLIN observes catching of a runtime error. These might work with no issues in 4.7 but will short dump in ECC.
Difference between ECC 6.0 vs 4.7EE

Upgrade Project

The upgrade strategy usually consists of several stages that progressively expand functionality, increase business value, and
prepare the organization for the transition to SOA while minimizing risk.
This process typically consists of three distinct phases:
- the technical upgrade: This initial phase involves a purely technological upgrade whose major goal is the implementation
of the new software release as the foundation for all subsequent improvements. The impact of this phase on your
business and business processes is very limited.

- functional enhancements: this phase focuses on increasing business value by implementing the most valuable functions
of the new software and laying the foundation for future business innovation and improved process automation. During
this phase, SAP software modifications and custom developments are replaced with (new) standard SAP software
functions. This phase can be used to activate new business functions provided by SAP enhancement packages.

- strategic enhancements: Phase three involves implementing new and optimized business processes that fully exploit
new SAP ERP functions and enable SOA.