So they "Decoupled " the Apps from the A.S, Added ICM for HTTP(s) at kernel level to support Internet standards, and added J2EE Engine to support Non-SAP to SAP Integration. SAP needed to focus on Integration and Internet Standards for EC/eBusiness. Fastforward to the Ecomerce era after Y2K. ) which are ABAP apps but couldn't run on the AS of R/3 without tweeks. When SAP came up with New Dimensions products (BW, CRM, APO. However, since SAP had one Product R/3, so the AS and the ABAP Apps were "Tightly Coupled". The role of the AS is to isolate the ABAP Apps from OS/Net, RDBMS dependencies and ensure Portability of those apps. Initially in R/3, the Application Server (AS) was a Kernel (a bunch of Virtual Machines )Executing Apps written in ABAP and some ABAP components (SAP_BASIS and SAP_ABA) to manage ABAP to Kernel integration. To understand the evolution one has to understand how SAP Systems and Apps work. This leads sometimes to irreconcilable results that's why we see glitches in the release logic sometimes.
#Sap erp 6 0 software#
Thus Componentize the Software devlopment while keeping the Components Integration possible. 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.
#Sap erp 6 0 update#
Software Update Manager (SUM): introducing the tool for software maintenance
0 kommentar(er)
