Skip to Content

What’s in the Name

A product nomenclature is very important aspect. It not only gives unique identity to the product but also helps a customer to understand the product evolution with different versions.

Recently I have gone through the complete business suite of SAP. While looking into different products, I found that product names are not consistent and changes year after year. The release document was required to be handy to know what the given product was named earlier and how it is known today. It is not possible for someone who is out of SAP for some time to understand what current trend is.

It makes consultant’s life difficult as the information is not available at one central place. One has to search through different SAP portals (, etc) to assure the products information. E.g. SAP SRM 2007 & SAP SRM 7.0 are many a times interpreted as same product versions by consultants. This is due to the fact that most of products were renamed to 7.0 version after NetWeaver 7.0 release. Another example for this is of SAP Solution Manager 4.0, which was renamed to SAP Solution Manager 7.0. Commonly known Web Application Server (WAS) is now known as Application Server. 


Product Versions Evolution for SAP SRM –




SAP SRM 2007



Old Name – SAP Supplier Relationship Management 6.0

New Name – SAP Supplier Relationship Management 2007


Old Name – mySAP Supplier Relationship Management 2005

New Name – SAP Supplier Relationship Management 2005


Old Name – mySAP ERP 2005

New Name – ERP 6.0


Old Name – SAP NetWeaver 2004s

New Name – SAP NetWeaver 7.0


Old Name – SAP NetWeaver Composition Environment 1.0

New Name – SAP NetWeaver Composition Environment 7.1

You must be Logged on to comment or reply to a post.
    • Thanks Robin for the information. In PAM, I found release strategy as most useful. Expected was a table, which shows the previous names of the products and the current name along with rest of the details that PAM provides. But for previous names of the same product, one has to look into release brochure.  And most painful is the changes in the same product names and versions.
      Also, during my search, I found that there were links in Marketplace redirecting to SDN. And when SDN page opens, system says link not found. In such scenario, helped me a lot.

      Sapna Modi

  • Hi Sapna

    yes. it was the same  confusion for me more than 3 years back but you expressed a concern on naming conventions of SAP SRM.

    The SAP SRM naming conventions has many versions due to branding in the Global procurement market.

    SRM has another name internally as Enterprise Buyer Portal.

    I believe SAP SRM would have started with B2P(BBP- Business to Business procurement in 1999. SAP SRM is 10 year old.
    SRM history says as follow as
    1999-B2B PROCUREMENT 1.0
    2000-B2B PROCUREMENT 2.0/Enterprise Buyer 1.0
    2001-Enterprise Buyer 2.0
    2001-Enterprise Buyer 3.0/ SRM 1.0
    2002-Enterprise Buyer 3.5/ SRM 2.0
    2003-Enterprise Buyer 4.0/ SRM 3.0
    2004-Enterprise Buyer 5.0/ SRM 4.0
    2005-Enterprise Buyer 5.0/ SRM 5.0
    ..keep going on.
    I believe is SAP putting  lot of efforts to meet the customer expectations and trying to improve customer satification and more competetive in the market / introduced latest cuting technology in the existing SRM product and introduced lot of srm components with respect to businesses.

    keep the SRM flag always high in the Procurement and Sourcing Arena.

    • Thanks Muthu for this detailed info on SRM. My article is only aimed to highlight some concerns on changes in the same product name & versions.

      Sapna Modi

  • Hi Sapna,
    Normally, every nomencalture has some valid logic once it published at that time, soon it becomes outdated due to some other logics or reason.
    It's very difficult to justify the same logic for nomenclature all the time, so either live with it or change wrt to time choice is with Owners of  the product itself.