AND SAP INTEGRATED IT PORTFOLIO MANAGEMENT. Dispersed SAP systems present a business challenge

Transcription

1 INTEGRATED IT PORTFOLIO MANAGEMENT AND SAP The importance of complete IT transparency in SAP consolidation projects TABLE OF CONTENTS 1 Dispersed SAP systems present a business challenge 2 Documenting SAP landscapes for SAP 3 CTI Landscape Analyzer 3 Accelerated information delivery 4 Delivery of non-sap information 4 Implementation example: International automotive supplier 5 The approach 6 The Alfabet survey 7 The results 8 Transparency at the push of a button Dispersed SAP systems present a business challenge Emerging from the economic downturn, many companies are again investing to foster business growth and are embarking on major IT projects. In many cases, the goal is to finally take advantage of the synergies between the vast number of systems resulting from mergers and acquisitions. To this end, decentralized SAP landscapes, which are often distributed across various national and international subsidiaries, need to be consolidated or an integrated master data management must be established. In attempting to do so, many large organizations are finding themselves faced with a similar challenge. These organizations come very quickly to the realization that they lack the required transparency to successfully execute their consolidation projects. On one hand, individual SAP modules may be running on different release levels or different master data numbers may exist (oftentimes 20 or more). On the other hand, various business units, each with its own perspective, are initiating similar even overlapping projects. This includes, for example, the technical consolidation of SAP systems, parallel roll outs, system upgrades and enhancement packages, functional or technical master data management, as well as system and client migrations. In pursuing this project-based approach, companies risk redundant and costly efforts that subsequently need to be revised or altered. Hence, before starting major IT projects, it is essential to first answer the following questions: Which clients are already on the latest release? Which of the SAP systems exchange which data for example, material numbers? Which interfaces will change when a new module is integrated? Using conventional methods, creating the necessary degree of transparency would require a great amount of effort. But mission-critical programs cannot wait on the lengthy process of gathering information in many workshops and interviews with the business process owners, application owners and other stakeholders. On top of that, the data is usually outdated by the time of approval. WHITE PAPER

2 Yet, gaining transparency over existing structures and having a consolidated view of the SAP landscape including its interrelations with the rest of the IT portfolio needs to be neither costly nor complex. Typically, the data is already available in the different systems business process modeling tools, CMDBs and the SAP Solution Manager they all have the information needed to make decisions on simplifying the SAP landscape. Once this is understood, then, the challenge is in bringing the information together in one uniform view and being able to understand the relationships between the various architecture elements. Alfabet from Software AG helps companies meet this challenge by providing a repository in which to consolidate information in a consistent, transparent, comprehensive and integrated manner. Documenting SAP landscapes Alfabet ensures that IT powers business success by sustainably planning and managing integrated IT portfolios. It combines a deep understanding of the business and its strategy with the insight, planning and execution required to evolve the IT landscape. Alfabet provides for transparency, planning and management of the enterprise architecture and IT portfolio. This includes road mapping, risk and compliance management, and IT financial management. SAP users can use Alfabet for effective planning and management of the SAP landscape and coordinating changes here with changes in other areas of the IT landscape. To this purpose, Alfabet is integrated with the SAP Solution Manager. This white paper explains how the data within the SAP Solution Manager can be augmented with information that is already available in Alfabet and how Alfabet then provides a current, detailed description of the SAP landscape at any point in time. Alfabet describes the individual components of distributed SAP systems as applications and displays the way they exchange data as information flows. In addition, data, such as material data, is represented as business objects. Using these descriptions, Alfabet is able to show how information is being used. SAP System (SID) Application Client 1 (SID Client ID) Client 2 (SID Client ID) Client 3 (SID Client ID) Application Variant Client Presentation Integration Application Data Business Enabling OS SAP_APPL600 SAP_HR600 SAP_BASIS600 SAP_ABA600 Win 2003 Oracle 10g Application Platform Local Components Host frvs209a frvs209a Deployment Deployment Server (Application) Server (Data) Device Figure 1: This is an overview of planning elements, which are provided about the SAP application landscape by the SAP Solution Manager, and how these elements can be mapped to the Alfabet meta model. The SAP Solution Manager data on which to focus depends heavily on the questions being asked. When analyzing, for example, large roll outs or roll ins, a functional view together with business processes would be relevant. When focusing on a system view, which is typically required for common System Landscape Optimization (SLO) tasks, then systems, clients, accounting codes, and platforms should be analyzed to understand the relevant basic operations required for the consolidation (client split, client merge, etc.). 2

3 Documenting and evaluating information about interfaces to other systems will also be of particular interest in the context of such analyses. Even though the relevant systems and clients are typically known within the organization, information about interfaces is often outdated and incomplete. SAP SYSTEM A (SID) RFC Connections SAP SYSTEM B (SID) Client 800 (SID-Client ID) ALE Connections Client 900 (SID-Client ID) Data Figure 2: Here s an overview of the SAP interface categories which can be provided. for SAP CTI Landscape Analyzer CTI CONSULTING AG, an expert in IT management and SAP for more than 20 years, offers a service that leverages Alfabet. The CTI Landscape Analyzer for SAP begins with a workshop during which the customer s documentation and modeling needs are identified. The needs are then synchronized with best practices for modeling SAP landscapes in Alfabet and with modeling processes that have already been implemented. Afterwards, an extractor in the form of an ABAP report is installed in the relevant SAP Solution Manager instances. The relevant planning and management data is then extracted, prepared, and imported into Alfabet via the Alfabet Data Integration Framework (ADIF) a standard interface for importing, exporting, and modifying data. During data processing, the imported data is matched with existing models to avoid redundancies. In Alfabet, the data can then be further processed with the known analysis tools. To ensure the documentation of the landscape information is always up-to-date, the import described above may be repeated at any time with minimum effort. Thus, business-critical programs have access to continuously updated information about the SAP application landscape. This leads to an improved usability of the information for better planning. A key benefit of up-to-date information is the elimination of planning and implementation errors, avoiding unnecessary costs. The level of detail is defined within the extraction process, and the mapping and reporting within Alfabet may then be adjusted accordingly. With this procedure, the required information becomes available very quickly. Manual processes for capturing data to assess the SAP landscape are no longer required. Accelerated information delivery Conventional Process for SAP CTI Landscape Analyzer Selection of relevant Systems Research Responsibilities for 145 Systems Create Survey Distribute Surveys Collect Surveys Conducting Interviews Evaluation for 145 Systems Create Landscape Presentation Office Products Over 100 Days Install Report Execute Report Initial Time Advantage Configuration of Data Landscape Presentation in EAM Application 10 Days Iterative Time Advantage Execute Report Iterative Time Advantage Overnight Figure 3: This compares a common data capturing process with the approach of accessing the requested information via the SAP Solution Manager interface to Alfabet. 3

4 In addition to documentation that is continuously updated, further advantages over the conventional data capturing processes are: Faster availability of information Faster update of information Better information quality More consistent information, and more up-to-date information Delivery of non-sap information Planning elements of non-sap systems, which are connected to SAP, may easily be included in the overview using the interface described above. The various views, custom views, and reports in Alfabet are then used to display this information. In this context, information flow diagrams, in particular, structure the information about such planning elements in a clear fashion. Figure 4: The interfaces as well as the exchanged business objects or IDoc message types may be displayed. Implementation example: International automotive supplier The value of obtaining information from the SAP Solution Manager via the interface to Alfabet becomes apparent in this example of a large, global automotive supplier. The major programs of this automotive supplier are looking at migration from SAP systems and SAP consolidation. Given that all these programs and related projects reference and change areas of the SAP landscape that are partially overlapping, creating transparency of the application landscape was considered crucial for success. However, the underlying data was outdated and specific information, such as which of the SAP and non-sap systems carry material numbers, was missing. This was a problem, as in addition, one of the programs was aimed at establishing a standardized, alphanumeric material number with 13 digits. The goal was to transfer this material number in a consistent way, i.e., across all systems, without needing to convert it. Thus, the following questions were raised by the business: Which applications, systems and interfaces use material data / material numbers? Which applications, systems and interfaces cannot process the required alphanumeric, 13-digit material number? 4

5 The approach Activities Week A Analyze basic requirements from MDM program side B Design survey questionaire and conduct survey C Import information from SAP Solution Manager (SAP Systems, ALE Connection with used IDOC Message Types) D Integration of data from MDM Survey into the Alfabet Data Model E Result analysis and set up of reporting F Presentation of analysis results to the steering board Figure 5: This schedule illustrates the selected approach. The required information was provided within a short period of time. Within six weeks, comprehensive information depicting a complex SAP landscape was extracted from the SAP Solution Manager: 146 SAP systems (development, test and productive systems) 55 productive systems were imported 76 productive clients were imported Approx. 13,000 RFC connections between systems and clients RFC connections were imported (for productive systems and clients alone) 65 IDoc message types Approx. 20,000 ALE connections 540 ALE connections were imported (aggregated via Sender, Recipient, and IDoc message types) Work Package 1: CONDUCT SURVEY Work Package 2: IMPORT DATA FROM SAP SOLUTION MANAGER Scope: Scope: Non-SAP SAP SAP SAP Non-SAP Non-SAP Figure 6: This is an overview of the project work packages that were realized to obtain the required information. 5

6 The Alfabet survey In addition to using the interface between the SAP Solution Manager and Alfabet, the collected information for the project was augmented using a Alfabet-facilitated survey targeted at individuals in the enterprise who are responsible for SAP. This survey also gathered information about non-sap systems and their interfaces. Care was taken to ensure that the survey design was user-friendly. In the context of the program it was, on one hand, important to identify any limitations regarding the processing of the alphanumeric, 13-digit material number. On the other hand, the survey also needed to capture the exact number of digits that could be processed by the relevant applications. Furthermore, any conversions carried out by the applications and interfaces were to be captured. With this information, any need for action was to be identified to plan a timely alignment of applications and interfaces, and to address and plan further analyses. Figure 7: The Alfabet Survey The following data was captured in addition to the information provided by the SAP Solution Manager: Approx. 100 applications (mainly non-sap) that use the material number (including the information regarding the processed length of the alphanumeric or numeric number) 18 applications that convert the material number Approx. 280 interfaces that transfer the material number 10 additional applications and more than 50 interfaces that are currently not able to process the alphanumeric, 13-digit material number 6

7 The results 1. SYSTEM LIST 2. INFORMATION FLOWS 3. TECHNICAL PLATFORM Figure 8: These are typical application portfolio perspectives in Alfabet used to support the SAP programs. The information flow diagram clearly illustrates the current complexity of the application landscape. The company is now able to retrieve individual aspects of the application landscape based on the information captured in the Alfabet repository and the reports available (e.g., display all applications that process a material number and at the same time convert this number). The following image shows the different areas to which the applications have been mapped. Both information sources (SAP Solution Manager information and survey information) have been successfully merged and consolidated in a consistent and comprehensive overview. Figure 9: An Application Landscape Diagram in Alfabet 7

8 About CTI CONSULTING CTI unites long-standing, quality IT expertise with industry-specific and methodical know-how, as well as with a sound scientific foundation, and as consulting partner, CTI shares this knowledge gladly with its clients. CTI CONSULTING has been consulting since 1991 in various industrial sectors, for large as well as midsize companies at the national and international levels, in the areas of IT management consulting and SAP consulting. CTI CONSULTING accompanies clients throughout the entire IT valued-added chain. In addition to IT architecture consulting, the organization and management of IT projects, process digitization and document management on the basis of SAP NetWeaver belong to the CTI CONSULTING portfolio. The additional limitations (e.g., the limitations regarding the material number) is nicely illustrated using an interface matrix. In this matrix, the interfaces that do not support the alphanumeric, 13-digit number are color-coded. This creates a clear overview of whether there is a need for action. Sender Application Figure 10: An interface matrix Data Format Receiver Application The results were useful for both the business and for the progress of the project. Any need for action could be easily identified and further analyses to identify implementation efforts could be initiated. Value was obtained in particular from the newly gained transparency over: The SAP landscape and its systems, clients, and platforms The material numbers that can currently be processed The applications processing the material numbers The interfaces processing the material numbers The interfaces that are not able to process the alphanumeric, 13-digit number All RFC and ALE interfaces The transparency over the entire portfolio enables better alignment of all concurrent projects. Transparency at the push of a button Integrated IT portfolio management for complex SAP landscapes helps avoid planning errors. Costs and risks of consolidation projects can be lowered significantly. Information can be provided within a few weeks The collected information serves as the basis for sustainable planning The information quality is much higher compared to data gathered manually ABOUT SOFTWARE AG Software AG offers the world s first Digital Business Platform. Recognized as a leader by the industry s top analyst firms, Software AG helps you combine existing systems on premises and in the cloud into a single platform to optimize your business and delight your customers. With Software AG, you can rapidly build and deploy digital business applications to exploit real-time market opportunities. Get maximum value from big data, make better decisions with streaming analytics, achieve more with the Internet of Things, and respond faster to shifting regulations and threats with intelligent governance, risk and compliance. The world s top brands trust Software AG to help them rapidly innovate, differentiate and win in the digital world. Learn more at Software AG. All rights reserved. Software AG and all Software AG products are either trademarks or registered trademarks of Software AG. Other product and company names mentioned herein may be the trademarks of their respective owners. SAG_Integrated_IT_Portfolio_Management_8PG_WP_Feb16