CONCEPT PAGE FOR SAP IDEA PLACE

Either using the search option or selecting the product from a list would give you a timeline of the product/platforms from a historical and even future perspective.


The timeline shown below would be the start of the timeline for ERP.

Similar timelines would exist for other products (CRM, BW/BI, XI/PI, Business Objectes and so on) and would be either found through the search option or through the product list.

SAP product and platform timeline
Instructions:
  • Slide the scrollbar underneath the years bar to the right or left to navigate through the timeline.
  • Click on a product or platform to get more information, click outside of the information box to return to the timeline.
  • Information on the platform on which the product resides will also be displayed in the information box of the product.

1970
  • SAP R/1
    The R stands for real-time data processing. The 1 stands for the fact that the product was residing on a mainframe (no separate layer for database, application or presentation) so only one layer.
    This product resides on the following platform: Mainframe
    SAP R/1
    January 1, 1970
  • Mainframe
    SAP (Systems, Applications and Products) was founded in 1972 and the first product served the purpose to do financial accounting and was called “R/1”. The “R” stands for real-time data processing. The “1” stands for the fact that the product was residing on a mainframe (no separate layer for database, application or presentation) so only one layer.
    The following list of products feature products which are build on this platform:
    SAP R/1
    Mainframe
    January 1, 1970
1979
  • SAP R/2
    At the end of the 1970s R/2 was released. 1 was changed into 2 because now it used two layers, (a database+application and a presentation layer). Mainframe (database+application) and a terminal (presentation layer) to connect to the mainframe.
    This product resides on the following platform: Mainframe + terminal
    SAP R/2
    January 1, 1979
  • Mainframe + terminal
    At the end of the 1970s “R/2” was released. “1” was changed into “2” because now it used two layers, (a database+application and a presentation layer). Mainframe (database+application) and a terminal (presentation layer) to connect to the mainframe.
    The following list of products feature products which are build on this platform:
    SAP R/2
    Mainframe + terminal
    January 1, 1979
1992
  • SAP R/3
    In 1992 R/3 was released. 2 was changed into 3 because now it used three layers (a database, an application and a presentation layer). With this version multiple operation systems and multiple platforms were supported. Now you could have an Oracle database on a Windows server and SAPgui on a desktop to connect to your SAP system.
    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3
    January 1, 1992
  • Client + server architecture (3 layer)
    In 1992 “R/3” was released. “2” was changed into “3” because now it used three layers (a database, an application and a presentation layer) which is also reffered to as client + server architecture.

    With this architecture multiple operation systems and multiple platforms were supported.

    Now you could have an Oracle database on a Windows server and SAPgui on a desktop to connect to your SAP system.

    The following list of products feature products which are build on this platform:
    SAP R/3
    SAP R/3 4.6B
    SAP R/3 3.1I
    SAP R/3 4.0B
    SAP R/3 4.6C
    SAP R/3 4.5B
    Client + server architecture (3 layer)
    January 1, 1992
1998
  • SAP R/3 4.0B
    After the release of R/3 SAP began to put release information behind the product names to continue the product line. It still made sense, R/3 3.1I and R/3 4.0B and so on up till R/3 46C and R/3 46D (here and there you can still find R/3 SAP systems at customer side).

    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3 4.0B
    May 22, 1998
  • SAP R/3 3.1I
    After the release of R/3 SAP began to put release information behind the product names to continue the product line. It still made sense, R/3 3.1I and R/3 4.0B and so on up till R/3 46C and R/3 46D (here and there you can still find R/3 SAP systems at customer side).

    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3 3.1I
    June 15, 1998
1999
  • SAP R/3 4.5B
    After the release of R/3 SAP began to put release information behind the product names to continue the product line. It still made sense, R/3 3.1I and R/3 4.0B and so on up till R/3 46C and R/3 46D (here and there you can still find R/3 SAP systems at customer side).
    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3 4.5B
    May 17, 1999
2000
  • SAP R/3 4.6B
    After the release of R/3 SAP began to put release information behind the product names to continue the product line. It still made sense, R/3 3.1I and R/3 4.0B and so on up till R/3 46C and R/3 46D (here and there you can still find R/3 SAP systems at customer side).

    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3 4.6B
    January 31, 2000
  • SAP R/3 4.6C
    After the release of R/3 SAP began to put release information behind the product names to continue the product line. It still made sense, R/3 3.1I and R/3 4.0B and so on up till R/3 46C and R/3 46D (here and there you can still find R/3 SAP systems at customer side).

    This product resides on the following platform: Client + server architecture (3 layer)
    SAP R/3 4.6C
    May 29, 2000
2001
  • SAP WebAs 6.10
    SAP build a platform, the first being WebAS to be included in product naming or referenced when talking/writing about the product.

    SAP Web Application Server 6.10 was the first release and supports native web technologies like HTTP, HTTPS, SMTP, XML, SOAP. The Business Server Page (BSP) programming model is available for developing web.

    One of the major changes was the replacement of ITS by ICM.
    SAP WebAs 6.10
    July 23, 2001
2002
  • SAP WebAs 6.20
    SAP build a platform, the first being WebAS to be included in product naming or referenced when talking/writing about the product.

    The first version of the SAP J2EE engine was released with SAP Web AS 6.20 as shown in Figure 3. This means that the engine is fully compliant with the 1.2 J2EE standards, making it a J2EE-certified application server.

    It became possible to use JSP pages and run customer build Java web applications.
    The following list of products feature products which are build on this platform:
    SAP R/3 ENTERPRISE 47X110
    SAP R/3 ENTERPRISE 47X200
    SAP WebAs 6.20
    February 4, 2002
  • SAP R/3 ENTERPRISE 47X110
    Once R/3 Enterprise 4.x came out things became even more confusing (we are still miles away from what we have today).

    Now the above wasn’t enough really, the Enterprise part was added to the product name because now they had split up some components.

    You can read the following information on the facts of the split up, to what purpose and so on:
    R3 Enterprise.

    So now you have your R/3 (real-time 3 layer SAP system) Enterprise (components split and possibility to use extensions) 4.x (version of your R/3) on WebAS (base platform) 6.20 (version of your platform).

    This product resides on the following platform: SAP WebAs 6.20
    SAP R/3 ENTERPRISE 47X110
    July 15, 2002
2003
  • SAP WebAs 6.30
    SAP build a platform, the first being WebAS to be included in product naming or referenced when talking/writing about the product.

    Web AS 6.30 only contains changes to Java functionality—the ABAP is at the 6.20 level. 6.30 is also a ramp-up only release that was never released to mass shipment.
    SAP WebAs 6.30
    June 10, 2003
  • SAP R/3 ENTERPRISE 47X200
    Once R/3 Enterprise 4.x came out things became even more confusing (we are still miles away from what we have today).

    Now the above wasn’t enough really, the Enterprise part was added to the product name because now they had split up some components.

    You can read the following information on the facts of the split up, to what purpose and so on:
    R3 Enterprise.

    So now you have your R/3 (real-time 3 layer SAP system) Enterprise (components split and possibility to use extensions) 4.x (version of your R/3) on WebAS (base platform) 6.20 (version of your platform).

    This product resides on the following platform: SAP WebAs 6.20
    SAP R/3 ENTERPRISE 47X200
    September 22, 2003
2004
  • SAP WebAs 6.40
    SAP build a platform, the first being WebAS to be included in product naming or referenced when talking/writing about the product.

    SAP Web AS 6.40 is the mass ship release and is where the ABAP side of the house catches up with Java development in terms of adding new features. There are no overall architecture changes since SAP Web AS 6.30. The main feature introduced with 6.30/6.40 is Web Dynpro, a runtime and development environment for creating easily adaptable web-based user interfaces.

    WebAs 6.40 is not mentioned in the product availability matrix as it became part of a new platform, SAP Netweaver 2004.
    SAP WebAs 6.40
    January 1, 2004
  • SAP Netweaver 2004
    SAP Netweaver 2004 is a platform SAP launched in 2004. It has WebAs 6.40 included and both names are mixed in sources and references. Another variant which was commonly used is BASIS 6.40.

    SAP Netweaver 2004 really opened the doors for Java as it offered not only the capability to procedure java based applications but also the tools to manage them (Development Infrastructure and so on).
    The following list of products feature products which are build on this platform:
    mySAP ERP 2004
    SAP ERP 2004
    SAP ERP 5.0
    SAP ECC 5.0
    SAP Netweaver 2004
    March 31, 2004
  • mySAP ERP 2004
    mySAP ERP 2004 also called SAP ERP 2004 , SAP ERP 5.0 or SAP ERP ECC 5.0 is the succesor of R/3 Enterprise and is build on the new SAP Netweaver platform.

    It offered new functionality such as eCATT test repository and integration with SAP Portal and applications such as self services and so on.
    This product resides on the following platform: SAP Netweaver 2004
    mySAP ERP 2004
    June 21, 2004
  • SAP ERP 2004
    SAP ERP 2004 also called SAP ERP 5.0 or SAP ERP ECC 5.0 is the succesor of R/3 Enterprise and is build on the new SAP Netweaver platform.

    It offered new functionality such as eCATT test repository and integration with SAP Portal and applications such as self services and so on.
    This product resides on the following platform: SAP Netweaver 2004
    SAP ERP 2004
    June 21, 2004
  • SAP ERP 5.0
    SAP ERP 5.0 also called SAP ECC 5.0, SAP ERP 2004 or mySAP ERP 2004 is the succesor of R/3 Enterprise and is build on the new SAP Netweaver platform.

    It offered new functionality such as eCATT test repository and integration with SAP Portal and applications such as self services and so on.
    This product resides on the following platform: SAP Netweaver 2004
    SAP ERP 5.0
    June 21, 2004
  • SAP ECC 5.0
    SAP ECC 5.0 also called SAP ERP 5.0, SAP ERP 2004 or mySAP ERP 2004 is the succesor of R/3 Enterprise and is build on the new SAP Netweaver platform.

    It offered new functionality such as eCATT test repository and integration with SAP Portal and applications such as self services and so on.
    This product resides on the following platform: SAP Netweaver 2004
    SAP ECC 5.0
    June 21, 2004
2005
  • SAP ERP 6.0
    SAP ERP 6.0 also referenced as SAP ECC 6.0, mySAP ERP 2005 or SAP ERP 2005 features over 300 enhancements (improved functionality) compared to its predecessor SAP ERP 5.0 (~ECC 5.0, mySAP ERP 2004, SAP ERP 2004).

    With SAP ERP 6.0 a new concept is launched called Enhancement Packages. Instead of going for frequent upgrades (to go from product version X to product version X+1) SAP has a new vision on how they should handle adding new functionality.

    Instead of releasing ERP 7.0 as next product they will release Enhancement Packages (EHP) which provide new functionality but do not touch the core components of the SAP product (thus less impact and easier to apply).
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ERP 6.0
    October 24, 2005
  • SAP WebAs 7.00
    SAP WebAs 7.00 is the succesor of SAP WebAs 6.40 and the name WebAs is sometimes referenced or used instead of SAP Netweaver (2004s).

    The main change is that SAP now based the products based on SAP Netweaver upon scenarios. For example a Portal scenario would consist out of certain usage types. Those usage types determine the SAP components that are installed.

    Another major change was SOA (Service Oriented Architecture).

    Although SAP Netweaver has a seperate productline with products such BI, PI and Portal, the platform is still used by other products such as ECC (or ERP) but there it is only truly the basic components of the SAP Netweaver platform which are included in those products.
    SAP WebAs 7.00
    October 24, 2005
  • SAP Netweaver 2004s
    SAP Netweaver2004s is the succesor of SAP Netweaver2004 and is also referenced as SAP Netweaver 7.0 and SAP WebAs 7.0.

    The main change is that SAP now based the products based on SAP Netweaver upon scenarios. For example a Portal scenario would consist out of certain usage types. Those usage types determine the SAP components that are installed.

    Another major change was SOA (Service Oriented Architecture).

    Although SAP Netweaver has a seperate productline with products such BI, PI and Portal, the platform is still used by other products such as ECC (or ERP) but there it is only truly the basic components of the SAP Netweaver platform which are included in those products.
    The following list of products feature products which are build on this platform:
    SAP ERP 6.0
    SAP ERP 2005
    SAP ECC 6.0
    mySAP ERP 2005
    EHP1 for SAP ERP 6.0
    SAP ERP enhancement packages 2005.1
    EHP3 for SAP ERP 6.0
    SAP ERP enhancement packages 2005.2
    EHP2 for SAP ERP 6.0
    SAP ERP enhancement packages 2005.3
    SAP Netweaver 2004s
    October 24, 2005
  • SAP ERP 2005
    SAP ERP 2005 also referenced as SAP ECC 6.0, mySAP ERP 2005 or SAP ERP 6.0features over 300 enhancements (improved functionality) compared to its predecessor SAP ERP 5.0 (~ECC 5.0, mySAP ERP 2004, SAP ERP 2004).

    With SAP ERP 6.0 a new concept is launched called Enhancement Packages. Instead of going for frequent upgrades (to go from product version X to product version X+1) SAP has a new vision on how they should handle adding new functionality.

    Instead of releasing ERP 7.0 as next product they will release Enhancement Packages (EHP) which provide new functionality but do not touch the core components of the SAP product (thus less impact and easier to apply).
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ERP 2005
    October 24, 2005
  • SAP ECC 6.0
    SAP ECC 6.0 also referenced as SAP ECC 6.0, mySAP ERP 2005, SAP ERP 2005 or SAP ERP 6.0features over 300 enhancements (improved functionality) compared to its predecessor SAP ERP 5.0 (~ECC 5.0, mySAP ERP 2004, SAP ERP 2004).

    With SAP ERP 6.0 a new concept is launched called Enhancement Packages. Instead of going for frequent upgrades (to go from product version X to product version X+1) SAP has a new vision on how they should handle adding new functionality.

    Instead of releasing ERP 7.0 as next product they will release Enhancement Packages (EHP) which provide new functionality but do not touch the core components of the SAP product (thus less impact and easier to apply).
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ECC 6.0
    October 24, 2005
  • mySAP ERP 2005
    SAP ERP 6.0 also referenced as SAP ECC 6.0, mySAP ERP 2005 or SAP ERP 2005 features over 300 enhancements (improved functionality) compared to its predecessor SAP ERP 5.0 (~ECC 5.0, mySAP ERP 2004, SAP ERP 2004).

    With SAP ERP 6.0 a new concept is launched called Enhancement Packages. Instead of going for frequent upgrades (to go from product version X to product version X+1) SAP has a new vision on how they should handle adding new functionality.

    Instead of releasing ERP 7.0 as next product they will release Enhancement Packages (EHP) which provide new functionality but do not touch the core components of the SAP product (thus less impact and easier to apply).
    This product resides on the following platform: SAP Netweaver 2004s
    mySAP ERP 2005
    October 24, 2005
2006
  • EHP1 for SAP ERP 6.0
    EHP1 for SAP ERP 6.0 also referenced as SAP ERP enhancement packages 2005.1 is the succesor of SAP ERP 6.0 (mySAP ERP 2005, SAP ERP 2005, ECC 6.0) and features enhancement packages (EHP) version 1 (EHP1).

    Components which have EHP1 functionality installed will have component version 601.


    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: SAP Netweaver 2004s
    EHP1 for SAP ERP 6.0
    December 21, 2006
  • SAP ERP enhancement packages 2005.1
    SAP ERP enhancement packages 2005.1 also referenced as EHP1 for SAP ERP 6.0 is the succesor of SAP ERP 6.0 (mySAP ERP 2005, SAP ERP 2005, ECC 6.0) and features enhancement packages (EHP) version 1 (EHP1).

    Components which have EHP1 functionality installed will have component version 601.

    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ERP enhancement packages 2005.1
    December 21, 2006
2007
  • EHP3 for SAP ERP 6.0
    EHP3 for SAP ERP 6.0 also referenced as SAP ERP enhancement packages 2005.3 is the succesor of SAP ERP 6.0 EHP3 and features enhancement packages (EHP) version 3 (EHP3).

    Components which have EHP3 functionality installed will have component version 603.


    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: SAP Netweaver 2004s
    EHP3 for SAP ERP 6.0
    July 12, 2007
  • SAP ERP enhancement packages 2005.3
    SAP ERP enhancement packages 2005.3 also referenced as EHP3 for SAP ERP 6.0 is the succesor of SAP ERP 6.0 EHP3 and features enhancement packages (EHP) version 3 (EHP3).

    Components which have EHP3 functionality installed will have component version 603.


    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ERP enhancement packages 2005.3
    July 12, 2007
  • SAP ERP enhancement packages 2005.2
    SAP ERP enhancement packages 2005.2 is also referenced as EHP2 for SAP ERP 6.0 and is the succesor of SAP ERP 6.0 (mySAP ERP 2005, SAP ERP 2005, ECC 6.0) and features enhancement packages (EHP) version 2 (EHP2).

    Components which have EHP2 functionality installed will have component version 602.

    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: SAP Netweaver 2004s
    SAP ERP enhancement packages 2005.2
    July 27, 2007
  • EHP2 for SAP ERP 6.0
    EHP2 for SAP ERP 6.0 also referencesd as SAP ERP enhancement packages 2005.2 is the succesor of SAP ERP 6.0 (mySAP ERP 2005, SAP ERP 2005, ECC 6.0) and features enhancement packages (EHP) version 2 (EHP2).
    This product resides on the following platform: SAP Netweaver 2004s
    EHP2 for SAP ERP 6.0
    July 27, 2007
2008
  • EHP1 for SAP Netweaver 7.0
    EHP1 for SAP Netweaver 7.0 was released in 2008 and the naming and vision derived from the new release strategy of SAP (using enhancement packages) and not touching core components frequently.

    New functionality (enhancements) where made on all area's of the SAP Netweaver Platform.

    After implementing EHP1 for your SAP Netweaver 7.0 platform, the product which resides on the platform will have kernel version 701 (where 1 is derived from EHP1).

    Components which are part of the SAP Netweaver EHP1 platform have component version 701.

    The following list of products feature products which are build on this platform:
    EHP4 for SAP ERP 6.0 / NW7.01
    EHP4 for SAP ERP 6.0
    EHP1 for SAP Netweaver 7.0
    October 13, 2008
  • EHP4 for SAP ERP 6.0 / NW7.01
    EHP4 for SAP ERP 6.0 / NW7.01 features enhancement packages (EHP) version 4 (EHP4) for SAP ERP 6.0 and EHP1 for Netweaver 7.0.

    Although the term Netweaver was first used as the name of the platform it is also a seperate product line (Netweaver products such as BI, PI, Enterprise Portal and so on).

    The product name ERP / NW states that a combination of an ERP product along with a Netweaver product forms the SAP system which is used by the customer.

    Components which have ERP EHP4 functionality installed will have component version 604.

    Components which belong to NW EHP1 functionality will have component version 701.

    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: EHP1 for SAP Netweaver 7.0
    EHP4 for SAP ERP 6.0 / NW7.01
    November 21, 2008
  • EHP4 for SAP ERP 6.0
    EHP4 for SAP ERP 6.0 is the succesor of SAP ERP 6.0 EHP3 and features enhancement packages (EHP) version 4 (EHP4).

    Components which have EHP4 functionality installed will have component version 604.

    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: EHP1 for SAP Netweaver 7.0
    EHP4 for SAP ERP 6.0
    November 21, 2008
2010
  • EHP2 for SAP Netweaver 7.0
    EHP2 for SAP Netweaver 7.0 was released in 2010 and the naming and vision derived from the new release strategy of SAP (using enhancement packages) and not touching core components frequently.

    New functionality (enhancements) where made on all area's of the SAP Netweaver Platform.

    After implementing this platform release the kernel version of your SAP product residing on the platform will be 702 (where the 2 is reflecting the EHP2 version).

    Components which are part of the SAP Netweaver EHP2 platform have component version 702.

    The following list of products feature products which are build on this platform:
    EHP5 for SAP ERP 6.0
    EHP2 for SAP Netweaver 7.0
    April 19, 2010
  • EHP5 for SAP ERP 6.0
    EHP5 for SAP ERP 6.0 is the succesor of SAP ERP 6.0 EHP4 and features enhancement packages (EHP) version 5 (EHP5).

    Components which have EHP5 functionality installed will have component version 605.

    There are multiple available business functions and the customer can choose to install and activate the new functionality which they require.
    This product resides on the following platform: EHP2 for SAP Netweaver 7.0
    EHP5 for SAP ERP 6.0
    July 12, 2010
1970
1979
1992
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2010