Author: bea4x

  • Lifecycle Management – HP BTO Makes It Happen

    This article shows how Application Lifecycle Management can be implemented for large SAP installations. A description of the respective software components can be found on HP’s BTO website.

    Complex SAP systems landscape
    The subsequent chart illustrates how complex a comprehensive SAP Business Suite can be, with its various systems landscapes that can consist of development, quality assurance and production systems.

    Business processes proceed through various ABAP systems, i.e. SAP CRM, SAP ERP and SAP BW. Consequently, a sales activity will be registered in SAP CRM, while then through SAP ERP, the whole preparation, delivery and financial editing of data will be executed. Finally, corresponding ABC analysis will be run in SAP BW.

    If needed, the user will be offered further front-end functions by means of the role-based SAP Portal – created with SAP NDI (SAP Netweaver J2EE Development Infrastructure).

    In order to save investments, operations and development of such all-encompassing and technically complex systems must be ensured longterm. This calls for specific provisions. The required environment and its components are highlighted in blue in the chart below.

    SOA Lifecycle Management

    SAP Application Lifecycle Management with HP products
    For this reason, a Lifecycle Management Environment has been created for large SAP environments, based on HP’s software products. In the following lines, the roles taken over by the individual products and their integration are described.
    SOA Lifecycle Management

    1. Comprehensive support of all stages in the development cycle
    The actual development cycle is supported by the HP products shown in the chart. In addition, ARIS is used for modelling of the business processes and their visualisation.

    Quality Management (HP Quality Center)
    HP Quality Center, which is integrated into the Lifecycle Management environment by means of HP PPM, ensures proactive testing. Thus, the data relevant for the testing is collected, changed and validated at the adequate moment. At the same time, the respective test objects are managed by HP Quality Center.

    Business Service Management (HP BAC)
    HP BAC is integrated into the development process so that information regarding every single business-service can be obtained at every single stage of the development. On the level of business-service, multidimensional impact analysis can be undertaken in all phases of development and test. Furthermore, any related descriptive, organizational and technical objects can be elicited per Business Service.

    SAP Solution Manager
    Integrating SAP Solution Manager into the Lifecycle Management Environment ensures that the appropriate objects can be transported into the SAP systems landscapes. In so doing, the integrity of ABAP and non-ABAP objects of different SAP systems can be ascertained by means of the combinatorics of HP PPM.

    SOA Management
    By integrating Web Services Monitoring data of HP Systinet, access to the data about a Business-Services running in production is guaranteed at any time.

    2. Driving the development process
    HP PPM is utilised, employing all its functionality, to digitize, integrate and automate the processes. The strengths of HP PPM lie specifically in the execution of tasks for which the integration between process and tool are key: it drives all processes and is capable of communicating with every software used in the development cycle.

    Unfortunately, by changing the name of their Software Suite to HP Project and Portfolio Management Center (HP PPM), HP have removed the reference to the true strength of their product from its name. Therefore, the name situates the product only in reference to one Gartner IT quadrant: Project & Portfolio Management (PPM), while the former name Mercury IT Governance (Mercury ITG) reflected very well how strong the product is.

    • It can be used to effectively reduce, if not eliminate, manual or as well as technical interfaces and communication levels. Duplicate and manual data entry by the user may be removed, so that the risk for failures may be minimised and the efficiency maximised.
    • HP PPM combines organisational process stages with technical ones. By this means, it is possible to automate process stages and to include quality assurance measures directly into the process.
    • HP PPM allows to integrate SAP Solution Manager as a sub-process engine.
    • Thanks to HP PPM, all IT business processes can be formulated, digitalised and optimised in one and the same manner.

    3. Integration of the lifecycle data
    By means of integration across the various data stores of the tools, all used services and their dependencies can be monitored at any time. Comprehensive impact analysis is possible. For any change using HP BAC integration it is possible to determine all effected Business Services from the very beginning.

    Using HP PPM as an integration tool allows to reference and provide the necessary descriptive and organisational objects for every tool or user, while a defined process garantees the consistent integration all the results. This integration of the data of HP PPM into the Lifecycle Management Environment facilitates the complete reuse of the process information across the application lifecycle.

    Does HP promise too much?
    At least in the context of an SAP environment, the promise of HP BTO’s marketing messages holds true in a very realistic manner. HP BTO facilitates the pragmatic setup and successful operation of an Application Lifecycle Management.

  • ERP4IT – the Vision Found its Way into Wikipedia

    Enterprise Resource Planning for Information Technology (ERP for IT, ERP4IT) describes the automation of information technology (IT). Therefore ERP4IT focuses on the automated IT itself and not on the automation of business processes by IT.

    IT organizations define long-term strategies, integrate them into their business models and offer adequate IT services to the business. Integrated systems that support lifecycle-oriented IT management build an ERP4IT.

    Related to established ERP (Enterprise Resource Planing) systems that manage the usage of critical resources, ERP4IT aims on a process-oriented solution. Unlike the classic ERP software (money, productive capital, people, stock or information) takes the information of IT a center stage for the new concept of ERP4IT. Therefore ERP4IT targets on the management of complex data structures within databases and provide them in aggregated pieces for their different stakeholders.

    Because of a great demand but missing standards and applications the call for an ERP4IT solution becomes louder. Accordingly, ERP4IT found its way into Wikipedia: http://en.wikipedia.org/wiki/ERP_for_IT!

  • SAP Template Distribution – a One Way Street?

    Inconsistent customization settings – a typical issue of decentral SAP systems
    Large SAP installations with multiple decentral system landscapes struggle to keep SAP customization settings consistent across the company. Conventional approaches , e.g. SAP Template Customization, to distribute templates lead inevitably to inconsistencies. Maintaining a consistent system requires extraodinary effort.

    Conventional SAP company template roll-out
    In most SAP installations central customization assures the integrity of SAP’s overall company structure. It is built and maintained on a central SAP template customization client. From there it is transported to different decentral customization development systems.

    SAP Company-Template System Landscape

    SAP company templates transported in such a way get activated on the multiple decentral customization clients. Locally enriched by further customization templates get finally transported by the transport management system (called TMS or CTS) into decentral system landscapes.

    It is obvious that with such a procedure decentral customization changes risk to be applied to customization that was configured in the centrally managed company template. The consequence then is an inconsistency between the central and decentral template.

    It is difficult to get this under control with organizational measures since there is no technical support to alert autonomous decentral developers when changing centrally configured items.

    Further updates made to the central SAP company template then just cannot be activated on the decentral systems anymore. After being transported to the decentral system landscapes they potentially overwrite decentral customization. To still adopt changes from the central SAP company template requires extraordinary efforts and inconsistences are more predictable.

    By the way: In contrast to the roll-out of customization the deployment of SAP ABAP development objects is handled without any problems by most large SAP users. Organizational measures are sufficiently assuring the quality of this process.

    SAP Company Template Protection with SAP Solution Manager
    It is not common knowledge that above problem with inconsistencies can be cured with system support from SAP. SAP Solution Manager can be used for this purpose. Correctly configured it can prevent developers from overwriting central template adaptations when they locally modify decentral system landscapes. A very effective automated quality assurance measure. The central customization gets protected on the decentral systems. The overall system configuration remains consistent!

    This quality assurance measure for the roll-out of SAP company templates by SAP Solution Manager can be introduced even after multiple central and decentral modifications and roll-outs. A quality measure highly welcome to any SAP IT managers who know what it means to suffer from template inconsistencies. They normally have a good understanding of what it needs to reactively get rid of them!