Organize the Software Engineering teams in such a way that each can go at its own speed as required by marketing. Technology Prespective: Align the technology with Business Goals. Etc, this persepective has Business goals and objectives as drivers. Integration: Maximize Product Integration to keep customers buying SAP Products e.g have the popularity of ERP induce customers to by SAP CRM, or SAP HCM, SCM, etc for better TCO. For example, release 2 required products in 1 quarter and 3 in the next might show a steady profits growth to the investment community. Business Needs: Organize the different Releases in such a way that Revenue and profit goals are met and kept predictable. Internet/Standards: Rapid Adoption of new standards e.g SOA Innovation: Keep the different Development Teams independent from each other so that Innovation in one team can move forward without having to wait for other teams.

Technology perspectives you may have another logic. I do understand Boris's logic but I think there's another vision of what's going on with all the SAP versions and components progress! If you look at it from a Business and Industry Solution Catch Weight ManagementĬan you tell me by seeing this in which EHP my sap system is running now ? SAP Enterprise Extension Financial Services

SAP Enterprise Extension Defense Forces & Public Security SAP Enterprise Extension PLM, SCM, Financials Code line 7.20 (listed in brackets in figure 5) was only used for products based on the SAP NetWeaver Application Server Java, like Composition Environment (CE). Figure 5 for example does only focus on the ABAP stack of SAP NetWeaver Process Integration (PI), although PI used to be a dual-stack, running a Java stack with java software components as well. This blog intends to make you aware of the fact that product versions and software component versions have their own numbering – it still simplifies the picture. Software Update Manager (SUM): introducing the tool for software maintenance

Learn about the Software Update Manager (SUM) that replaces the Enhancement Package Installer (EhpI):.

Understanding Landscape Descriptions – Part II: Products and Product Instances in Detail

Learn details about product instances and Funtionally Equivalent Instances.

Not completely up to date, but worth reading: SAP product naming confusion.

Overview on SAP Business Suite releases: Confused with different SAP Business Suite Releases ? Read it !!.

Read SAP Note 1566412 for a mapping between technical usages and software component versions for SAP ERP.

ℹ Part 2 of this blog is now available: SAP versioning, part 2 (why EHP7 contains SAP APPL 6.17).

Sap erp 6 0