rainsr2018 ‘SAP e-book Unt SAP Soluton Manager 2 fr SAP S4/HANA, Tino 6 SAP Uno hoplance erry Corea It youare interested in accessing the preconfigurec solutions available inthe brary, there are three basic steps to get started, as follows: 1. Create your cloud provider account. As described previously, the cloud provider wil provide the hardware infrastructure and charge you for the amount of resources you 2, Create your SAP Cloud Appliance Library account by registering at hitp:/cal sap.com When creating the account, provide your clouc provider information. After choosing. Accept in the Terms and Conditions prompt onthe ste, you can browse the lst of avallzble solutions. {3 Greate your own instance from ane ofthe solutions. This takes 15 to 60 minutes, in most cases. An instance is a running system copied from a solution and is created in the clout provider infrastructure you have selectes, After the instance is created, you can access i with full authorizations and can ereate additonal users as needed. Secure access to the ‘operating system is also possiole using free applications such a the WinSCP too). The figure, SAP Cloud Appliance Library Usage Scenario, shows a simple view ofthe process. Taponwan ewan a - “| > a ) ‘oud Provera) Finro GaP Co Asparce sary Usage Seeran tome SOOO a"rainsr2018 ‘SAP e-book ‘The Transition to SAP Solution Manager 72 Ityouare already actively using SAP Solution Manager 7. and plan to upgrade to the new release, you should be well prepared for the transition needs to prevent issues during the Upgrade wien only the technical ungrade should be executed, Ths section explains documents, tools, and services SAP provides to help prepare forthe transition tothe actual Upgrade to SAP Solution Manager 72 well in advance. The solution documentation scenario has been completely rebuiltin SAP Solution Manager 7.2. For this reason, preparation of customers with exsting and vital solution documentation sa entical step if they need to use ‘their existing solution decumertation inthe new environment after the upgrace to SAP Solution Manager 72. We call the process o selecting your relevant solution documentation content to use in the ew solution decumentation environment content activation, This pracess is mandatory for all customers who need to use their solution documentation content in SAP Solution Manager 72 Tote D> Met sattn cocuentatonenvorrent (he SOLAR wansactos hoa wietbe sala eae mace n SH Solon age 7a eucanat charg nyc + Select activation content + Design to-be landscape layout + Upgrade to SAP Solution Manager 7.2 + Execute content activation + Activate related applications Fagres8 Phasesof eon von [As shown inthe figure, Phases of the Content Activation Procedure, the content activation process consists ofthe following three phases: 1 Prepare 2. Ungrede 3, Activate tome OOOO a"rainsr2018 ‘SAP e-book Unt SAP Soluton Manager 2 fr SAP S4/HANA, = These phases need to be executed in the correct order. SAP's recommendation sto execute the prepare phase before the upgrade phase. wile you are still running your SAP Solution Manager 7. system. The preparation activities can be executed without affecting your product've enviroament, and wll ensure a smooth transition to SAP Solution Manager 7.2, Then, after the upgrade, the actvate phase needs tobe performed, after which you can use the new solution documentation environment with your activated content. Post activation ‘activites ean be carried oul to fully leverage the potential of the new solution dacumentation, ‘The upgrade to SAP Solution Manager 72 is a standard SAP software upgrade using the so'tware logistics (SL, toolset. During the upgrade, a stack spit willbe performed. and the relevant softwere components wil be updated. A database migration to SAP HANA can also be initiated. Tne figure, Upgrade from SAP Solution Manager 7.1 to 7.2, shows the change of ‘component versions during such an upgrade. Relevant for all customers: Manage 720s nt conan a new SAP CRM teense. awe ony move to 9 re enhancement paoege the past ote 7.2 we ‘The tocus ofthe readiness check I to provide a holistic view of functional lirvtations issues that might pravent an installation. and application change requiternents. tomenaeeee OSOO a"rainsr2018 ‘SAP e-book Unt SAP Soluon Manager 21 SAP S4/HANA. The checks are mainly based on restriction nates, the SAP S/4HANA simplification list custom code requirements, and data volume management opportunities. Inadaltion, basic system requirements for the new target release are part of the check, as are system landscape requirements enriched with important version interoperability remarks. These remarks can identify potential version dependency issues with SAP NetWeaver hub systems in your system landscape. The outcome ofthe readiness check isa service result document covering software prerequisites, infrastructure requirements, SAP S/4HANA functional checks, custom code- rolated activities, and application data migration requirements. Specificaly, the SAP S/ HANA readiness check repart covers the following areas: + Holistic technical analysis of our existing SAP ERP system Fulfilment and gaps of all technical system requirements, such as software levels single-stack system, and Unicode List of activated industry solutions, enterprise extensions, and business functions and their impact List of installed compatible andincompatible add-ons (Overview of version dependency issues anc required minimum release levels of connected SAP NetWeaver hud systems. Estimated SAP S/4HANA system size and recommendations to reduce the size before the conversion + Functional analysis List of obsolete SAP standard transactions and tables: includes intensive checks on ‘functionality used today but that will be replacea in SAP S/4HANA (for example, SAP Cash Management) Data model changes and their functional impact Analyses of business-crtical transactions in use today that will be replaced or removed in SAP S/4HANA (for example, 191 transaction family MSXX ‘or goods movements, replaced by transaction family 20) Recommendations for configuration adjustments + Checks and analysis for Custom Code Management ‘Analysis and number of modifications to SAP standard code ‘Analysis and number of custom code objects impacted by the system conversion, the ‘implication of functional changes, end functional changes in SAP S/2HANA, Effort estimation calculation for required and recommended modification and custorn code agjustment ‘The figure, Overview of Readiness Check For SAP S/4HANA, outlines the focus areas analyzed by the readiness check for SAP S/4HANA. The results are divided into required and recommended project tasks. tome OR a"rainsr2018 ‘SAP e-book Lesson: xpining SAP Slaton Manager 72 na SAP S/AHANA Functional System Landscape Changes Requirements, Requirements eMirauy —* Unkode* SAPNateaer Soulots —* Sralestack Fubsytone > + Emepme | SABHANA 7527 Bre i) + Frions| + Stan cexmecners tary fsa + Fant Cogetoe changes Recommended Recommended Addons! Customcede Data Volume Information Fajustments Management SAPHANR fagusimenis "as Sing Fire Ovarvan Reaoas Cronk or SAP SANA ‘SAP S/4HANA Implementation Roadmap As stated, the SAP Activate methodology realaces ASAP as SAP's implementation methodology for SAP S/4HANA ancll other SAP solutions. There are generic or general variants ofthe methodology that are not sortware solution specific, and there are solution specific variants (for example, the SAP S/AHANA roa Requirements oT Rured SAP FAN epatrer + Vie satonents hee + Roughefor eheaton ssmap). ‘The methodology content is organized into a three level hierarchy as follows: + Phases + Delverabies + Tasks Each node inthe hierarchy has a deseription that provides SAP's advice and guidance, Each nade also links to documentation accelerators tnat may be generic (such as an open issues template) or solution specific (such as an administration guide for SAP S/4HANA.on- premise) The SAP S/4HANA specific nethodology is called a roadmap and is available inthe following ‘wo ways! + Online read-only information in the roadmap viewer (hitps://zo support san.com/ roadmanviewer/, as shown inthe figure, Readman Overview) + Project within SAP Solution Manager 72 where it can be changed to reflect the specifies of yur project The SAP Activate phases and their main activities are as follows: Conyers Aligharesored = EY a"rainsr2018 ‘SAP e-book Unt SAP Soluon Manager 21 SAP S4/HANA. Discover: Define and agree the scope ofthe project + Prepare: The project is formally initiated, SAP Best Practices are activated and project planningis started Explore: Verity solution scenarios meet business needs and document deta scope and ps + Realize: Customer specific requirements are configured and implemented, The solutions tested to check that it matches the agreed design Deploy: You wll train end users, undertake data migration and provide support during the golive + Run: Monitor and optimize the solution Winere to find an study a rosemap? * The SAP SANA plementation aanap shed be consumed ne ‘Rencmap Vever running n SAP Cu ‘The contents ona updos Te escapee shows a ay Sescrptions in svete way Yo on “Took Oscipton ter on peas oF werk eam + Alruretnk e doses ae Ey (or wary, hime iratin —| Supporting malta mp, ad 6.) FanreaS Reoarap Oven Custom Code Management for SAP S/4HANA Many customers have developed custom code over the years in their existing SAP solutions, usually because they needed particular capabiltes and business features. Witha transition to SAP S/SHANA, you need io analyze custom code in detail due tothe simplification and data structure recesign in ne SAP digital core itsell. Implemented custom code is technically integrated into the SAP code, and therefore an adoption and remeciation process's ‘mandatory. SAP Solution Manager 72 delivers Custom Code Management, which helps you tomitigate potential problems efficiently, before you start the transition to SAP S/4HANA. The Custom Code Management approach supported by diferent capabilities includes 2 clear way forward as follows: + Transparency ard simplification Custom Code Management helps to achieve transparency for all your custom code objects, (including moditicat ons). Evaluation and impact Ithelps to evaluate the impact of changes on custom code. With this information about SAP changes, you can evaluate, review, and eritigate adjustment requirements at an early stage, + Planning and control tome OS a"rainsr2018 ‘SAP e-book Lesson: xpining SAP Slaton Manager 72 na SAP S/AHANA ‘This approach helps to reduce the effort of change adoption and ensure smooth ‘completion of identified adjustments, For example. Custom Code Impact Analysis helps {guide stakeholders through the adjustment process while encouraging adherence to best practices. + Re-engineering and refactoring ‘This approach helps to evaluate whether your current business process is available within SAP standard. Adjustment support Itoers code adjust ment based on the analysis ofthe identtied adjusted objects. Ityou transition your system landscape to SAP S/AHANA, you also have a great opportunity to optimize your custom code and the arocessos around it. agin by decommissioning unused custom code (based on the input from your business department ang on usage measurements). Follow this by selting up a governance model with tne goals to avoid naw custom code, review existing mocification, and improve or optimize the quality, performance, and security of your custorn code. The last, mandatory stea is te prepare your custom code so that it can be adopted into the SAP S/4HANA system, ‘SAP supports achioving your Custom Code Management aims by helping you avoid. improve, and minimize custom code elements and ingvidual enhancementsin the SAP standard solutions run by your company. Following lean principles, you accomplish these aims by running through the following activities: transparency and measurement, oatimization, and control, SAP provides numeraus tailored tools and best practieas for effective, holistic custom code management trom requirement to retirement. Using the Custom Cade Management tools. you can analyze the usage and quality of specific custom code objects and mosifications in your systems and thus achieve transparency for your customer developments, Based on the results of the analysis, you can identity the customer developments that are actually used and have better controlover them by using the functions provided in SAP Solution Manager 22. ‘The objective of Custom Code Managements to improve custom code's quality and technical Implementation while reducing its quantity and impact. SAP Solution Manager helos you achieve sustainable cost reductions forthe operation and maintenance of your SAP systern landscape. By leveraging ts innovations te contral gaps and minimizing existing ‘modifications, SAP Solution Manager ensures the value of IT and an increase in business value Today's IT system landscapes are seldom comprised of homogeneous solutions. Beyond established software modules, gaps inthe landscape are closed ad hoc. or standard business processes are enhanced inne with requirernents. Your custom developments are an important element your system landscape: such develoaments become necessary when ‘your standard software cannot map certain business processes as desired and there is no specialized, ideally certified, solution on the market ‘Accomplex amalgamation of standard software, enhancements, and custom code quickly develops, driven by the need to respond to changing business requirements ina timely manner. As @ result, program code is implemented quickly, anc there is less focus on sustainabilty and transparency of implemented objects. Important factors such as the complete documentation of changes, the impact of changes on core business processes, anc ‘maintainablity ae rot taken into account until planned or unplanned events modify the ‘overall system landscape, leaving a multitude of unanswered questions about custom enhancements. Planned, recurring events—such as rminor and major software updates or the introduction of new standard “unctions or innovat ons, like SAP S/2HANA—can lead to tomenaeeee OOS a"rainsr2018 ‘SAP e-book Unt SAP Souton Manager 21 SAP S4/HANA, Increased testing requirements and significantly higher implementation costs for your custom developments. Unplanned events, such as the need to implement new legal requirements, the use of new technology, or the need to adapt interfaces for external reasons, also frequently present unexpected challenges for custom enhancements, SAP proactively supports targeted handling of tnese aspects. ‘The green city model sa visualization of custors enhancements and custom code within your system landscape. The metrics it evaluates correspond to the abstract representation of 2 city with buildings o various heights, colors, and locations with the city, Every city reflects an inivdual system within your system landscape (see the figure, Green City Mo¢el). Governance Model Guidance for Decision-making and Execution Quality Technical Criticality on nceanco 41: Non msn eta! 5 Msion ete ‘Technical Severity Figure Green Oy Weel In light ofthe known characteristics of custom enhancements and custom code—number, ua. type of implementation, and so on—SAP has cefined three plus two primary criteria that can be measured and evaluated. These are: quantity, classification of technical implementation in relation to the SAP standard, technical eitcality, qualty. and usage. The ‘model also considers management and software iecycle elements, The ety model gves a ‘irst impression ofthe custom code situation in your landscape and helps you identity the areas on which you shoul focus For the transition to SAP S/4HANA, SAP enables you to analyze the optimization potential, prepare for the optirization project, and determine the impacto running business processes, including custom code and madifications To see the results in clear and Coherent manner, SAP provides you with an approach thal you can easly apply. Conran Al ighsresoredrainsr2018 ‘SAP e-book Lesson: xpining SAP Slaton Manager 72 na SAP S/AHANA e 8 ° Si —_— “ta Foon Used jects pacts tet (Opec Obici area SAP SHANA hoproach vo aston Gaze Manaeenert On your way to SAP S/4HANA, we recommend that you execute the following phases, ilustrate inthe figure, Green City Model 1 Phase 1: Capture the custom code footprint Use CCLM in SAP Solution Manager 7.2 fora stable and solid starting point asa single source of truth fer your custom cade, Custom code Ifecycle management (CLM) ‘documents your customs code and its dimensions based on the green cty model 2, Phase 2: Reduce the scone Reduce the scope to the objects that are usec by leveraging usage and procedure logging (UPL) and SQL monitoring (SQL). 3, Phase 2: Focus on the impacted objects For these objects, SAP offers end-to-end Change Impact Analysis, which includes the fallowing: Impact of classical upgrade or enhancement package implementation + Impact of SAP HANA, including performance optimization by transitioning toan SAP HANA database «Impact of SAP S/AHANA based on the simplification and optimization ofthe digital ‘core provided wth anew SAP product, To atdress allo these impacs you can use SAP's comprehensive toals that support analysis, and effort reduction and that provide impact worklsts for your review. These tools include the Custom Development Management Cockpit, Custom Coce apps, the Code Inspector, the ABAP test cockpit (ATC), and the Custos Code Migration Worklist. Focus on those objects that are critical or the business and those with the most optimization potential Data Volume Management for SAP S/4HANA Transition and Operations {as system landscape environments become ever more complex and data volumes continue (on an upward trend, it's now more important than ever tobe able to produce a landscape- based view of the data within the environment. It's necessary not only to be able to identity ‘the source of data but also to Getermine strategies for managing ancicontrolingit. An efficent data management strategy plays an important part in trying to maintain good system performance and keep the total cost ofa system in check. This particularly relevant for applications that generate large amounts of data, such as retalland consumer products. In this section, we will start by providing you with an overview of Data Volume Management tome OSS a"rainsr2018 ‘SAP e-book Unt SAP Soluon Manager 21 SAP S4/HANA. (DVM) before jumping into DVM for SAP S/4HANA and the DVM Workcenter apaications for SAP S/SHANA project, The end ofthis section covers data aging and the SAP Fiori applications for DVM. DVM and the DVM Workcenter play an important part in an SAP S/4HANA pre- and post conversion scenarios, Existing DVM Workcenter applications in SAP Solution Manager assist in identifying data reduction measures, which, in turn, speed up the corversion process and reduce SAP HANA's memory cost. The new DVM SAP Fiori agps and data aging measures provide options to keep the data growth in check during the operation phase. The methedology provided under the DVM framework consists of best practices, tools, and SAP services along all stages of the DVM Ifecycle, trom intial identification of the challenges all the way through to continuous improvement. also supports the deployment and. ‘operation of a DVM strategy. The methodology covers concepts for data discovery (alerting, monttoring) and data profiling (analyzing). data management and data archiving (managing the information ifecycle), and efficiont data storage ulization (database management, data aghyg) ln accordance with legal requirements and corporate policies. The DVM Workcenterin SAP Solution Manager provides detailed insight into the sourco of data volume moverients in single- and multisystem landscape environments, Ths tool is based on SAP NetWeaver and an integrated SAP Business Warchouse (SAP BW). which provides a holistic, landscane- based overview of system data, SAP's analytical and reporting infrastructure provides a rch array of functions and features that allows you to perform the following tasks: + Achieve syster landscape data consumption transparency at aiflerent levels, + Reveal potential for creating or optimizing a OVM strategy Leverage best practices documents to drive your DVM strategy Simulate ctferent data volume scenarios (for examole, moderate versus aggressive archiving) + Provide monitoring and reporting capabillies fr technical KPIs across a systern landscape ‘SAP Solution Manager for SAP S/4HANA and the Cloud It youwant to use SAP S/4HANA, you can run it on-premise or inthe cloud, The following, aifferent cloud eations are available: + SAP S/4HANA. cloud marketing ection offers processes for the marketing ine of business, SAP S/4HANA, cloud project services ecition, supports customers in the professional services industry. + SAP S/4HANA, cloud enterprise ection, covers the main SAP ERP scenarios, such as procurement, production, sales, and finance. After reading the previous chapters, you should understanc how SAP Solution Manager supports you in managing SAP S/4HANA, on-premise edition li you use SAP S/AHANA, Claud edion, SAP Solution Manager's also valuable for cloud solutions. Cloud solutions are typically not used standalone, but ae part of hybrid landscapes. This means thal you use cloud services and on-premise applications in parallel. You wil need an integration to share some data between your existing systems anc the cloud, and even if you have SAP S/4HANA, tomenaeeee a"rainsr2018 ‘SAP e-book Lesson: xpining SAP Slaton Manager 72 na SAP S/AHANA on-premise edition, you might enc! up with a hybrid solution. For example, your SAP S/AHANA, system may be integrated with other cloud services. tae SAP Ariba or SAP SuccessFactors, wet DD Metceta sar soutien Manages to supperyounmansging yur etre Ehfoneretrencnergihe ci How does SAP Solution Manager support cloud solutions? The answer to this question depends on which type of cloud you are referring to. There are two types of clout: private and public. n private clouds, systems are owned by the customer. Each customer has its own private network segment in the cloud. In a public cloud. clout services are owned by the clout provider. The services are accessible over an open network. Depencing en which type of cloud ‘you have chosen, SAP Solution Manager will address your solution differently. We will now discuss private cloud services. For private cloud services, the cloud provider assigns a personal network segment to each customer. This means that users accessing the cloud service in this network segment cannot access other private cloud services proved for anather company in other network segments. Your dedicated network segment will be integrated with your on-premise network via a virtual private network (VPN), and you will ave full access to the system. This VPN also connects your SAP Solution Manager to the system inthe private cloud. The cloud provider will deploy an SAP Solution Manager agent on your dedicated system in the private cloud. Your SAP Solution Manage in your own network will receive all required information from this agent. It can execute all of its functions for the system in the private cloud—thooretcally. In practice. however. you outsource some of the system management tasks tothe cloud provider, For SAP products, SAP Managed Clous Delivery runs SAP S/ AHANA, on premise ecition in the private SAP HANA Enterprise Cloud for you. Therefore, you tse your SAP Solution Manager only or those parts that are your responsibility—mainly business process and apalication management topics. You can even outsource parts of application management by purchasing corresponding services. The cloud provider takes care ofthe entice IT infrastructure and system management and ensures that the agreed-inon service levels are tuliled For this, SAP Managed Cloud Delivery uses its own SAP Solution Manager connected to the hosted private cloud solutions. However, this SAP Solution Manager instance is strongly protected so that you and other customers cannot access. Inthe public cloud, SAP Solution Manager has no drect access tothe system providing the cloud services. This ensures that no tenant can access the data of another tenant inthe open network, Communication withthe system providing public cloud services is only possible via public interfaces that are invoked via a dedicated URL and user/password combination, Hence. SAP Solution Manager covers only scenarios in which corresponding services have been set up This works, because the cloud operations model dtfers trom tractional on-premise ‘operations models. Inthe public cloud. the cloud provider delivars SAP S/4HANA as software a.a service (S288). The cloud provider shares responsioilty for application manegement with the customer. System management and IT infrastructure management are completely the responsibilty of the provider. Asa customer, you sigh a service level agreement with the cloud provider. You only need to know ifthe provider fll the agreed-upon service level, not interested specific details about how the cloud provider does so. The only responsibility you have as a SaaS consumer isto manage your business processes thal run on SAP S/4HANA in the public cloud. Anotner public cloud model scaled platform as a service (PaaS), tome OO a"rainsr2018 ‘SAP e-book Unt SAP Soluton Manager 2 fr SAP S4/HANA, The cloud provider offers a software platform on which customers can develop and run their ‘own applications, Here. the cloud prover is responsible for the platform itself and the Underlying systems, databases, and infrastructure, The availabilty and performance of the service are measured as key performance indicators (KPIs). As @ customer, you have to take care of beth application management and business pracess management yourselt forthe sottware running on the platform. SAP Cloud Platforms the main SAP PaaS offering, In ‘addition to developing entire new applications on this platform, you can also use i to develop lenhancements for your SAP S/4HANA system, For example, youcan build additional SAP For Uls or applications that consume existing SAP S/AHANA assets and enhance ther ‘functionality. The maintenance provess also difers significantly between clouc: and on: premise operations. In your own landscape. you can decide yourself when to apply the latest patches or implement enhanced functionality; you donot have ths freedom in the public cloud. The cloud provider deploys the patches biweekly and new functions quarterly. In the private cloud, at least some alignment between you and your cloud pravicer's possible. For integration scenarios between on-premise and cloud, tis important that you coordinate ‘he diferent maintenance plans. In SAP Solution Manager. you perform this synchronization va the T calendar (see the following figures). eure | ‘wniyiomcome oon ely Fret Bldon your) Una CAL Papa Eo a) Use as AP Soon gee Benue seh sour ttngerr2 “” yorsonarnndmanapeseymas "SS ee eee, | aieeeaemneene Beor (Tews > any eat amen sso a Cpe ES Faw vanaga Stvare Waiter ee) ll Ts Frama ra coe [reve palo see Feros Varo Stlare Nantosania Hyer ansaranen 2) tome OSSrainsr2018 ‘SAP e-book Lesson: xpining SAP Slaton Manager 72 na SAP S/AHANA The purpose ofthe IT calendars to support IT-relevant activites and make them easier to ‘manage. In the calendar, you can schedule all key IT events ‘or development, maintenance, business, and generic tasks. In this way the IT calendar gives you a landscape-wide overview ofall connected systems as wel as scheduled key events, CCustorners in some industries have to comply with strong regulations regarding the ‘documentation of anges. They nave tolbe abl to trace all changes to actual software components and changes to the configuralion. This apalis also for changes in cloud maintenance. Change Request Menagement in SAP Solution Manager takes care of documenting these changes, anc you can use it for documenting changes in the cloud as wel To do so, create a change recuest without links to physical transport management; the physical transport of the change will be handlec not by you but by the cloud provider. For SaaS, the software itself has already been tested by development, and you have only restricted configuration possibilities. Theretore, a two-ter lancscape is sufcient for most cases, You can test maintenance changes on a quality assurance system before the new version is deployed in the productive cloue. Only f you perform cevelopments in the cloud yourself (according to the PaaS approach) might a three-tier landscape with development, {quality assurance, and production system be necessary ‘SAP Solution Manager in Premium Engagements for SAP S/4HANA ‘SAP has constructed four unique premium engagement offerings. which can be tailored toa customer's scope and requirements. These offerings assist inte systern conversion to move every SAP customer successtully to SAP S/SHANA. These packages vary in size and coverage. The four offerings areas follows: SAP ActiveEmedded for planning and safeguarding of SAP S/AHANA This package is for customers who want to plan the conversion project properly together with SAP. Project execution is supported and safeguarded by SAP, but executed by the customer or the implementation partner. + SAP Active msedded for technical implementation of SAP S/2HANA, In adaition to planning and safeguarding, SAP runs the technical conversion of SAP ERP to SAP S/4HANA according to SAP Best Practices. Functional implementation is performed by the customer or the implementation partner. + SAP ActiveEmoedded for tunct’onalimalementation of SAP S/4HANA, Inadaition to running technical implementation. SAP configures a subset of simplified standard business processes (sun as, financial business processes from SAP S/44ANA) The implementation of additional functionality is performed by the customer or the implementation partner. + SAP MaxAttention for innovation with SAP S/SHANA, ‘This package's for SAP MaxAltention customers who would Ike to collaborate with SAP ang innovate beyonc the conversion to SAP S/AHANA in order to transform their ‘companies—for example, taking advantage of consume first, smart services, Internet of Things, boardroom ofthe future, and realatforming your business possibilities witn SAP S/ HANA. Functional gaps can be adcressed by coinnovation. In adcition to running ‘technical and funct’onal implementation, SA? also supports the edaptation of custom ‘code to SAP S/AHANA, The figure, Overview of SAP Premium Engagement Packages, ilustrates the different premium engagement offerings on the scale o SAP volvement and engagement duration. The SAP engagement duration 's based on the selected scope ofthe ind vidual service offerings. SAP S/4HANA implementation engagements consist of sets of outcome based, tome a"rainsr2018 ‘SAP e-book Unt SAP Soluton Manager 2 fr SAP S4/HANA, predefined services bundled as packages that help ensure fast and efficient SAP S/4HANA implementations, Each engagement will also have e close connection to the mission control center for seamless, immediate access to required expertise. ‘SAP S/& HANA Promium Engagement packages Involvement of SAP. 2 ee eee Tins 20ers SAP Prion Eraarent Pane liu) LESSON SUMMARY You should now be able to: + Describe what SAP Solution Manager 72 can do for SAP S/HANA tome OR wns90s2018 SAP e-book Th a4 Lesson 1 Defining Technical Prerequisites for S4/HANA Implementation Projects Lesson 2 Using the Solution 2s Single Source of Truth UNIT OBJECTIVES + Explain the role of SAP Solution Manager as a central source of system landscape information + Administrte your solution + Document a solution + Manage authorizations in SAP Solution Manager tome OOOO wnrainsr2018 ‘SAP e-book Defining Technical Prerequisites for S4/HANA Implementation Projects LESSON OVERVIEW LESSON OBJECTIVES ‘ter completing this lesson, Explain the role of SAP Solution Manager as a central source of system landscape information Central Administration of Managed Systems ‘SAP Solution Manage isthe center ofthe customer's solution landscape, It is 2 valuable source of technical information about the enti landscape, and provides transparency. Allinformation on msnaged systems with which you work inthe implementation project and in other application Iitecycle management (ALM) pracesses, such as during systern ‘monitoring, is stored centrally in SAP Solution Manager. This is als true tor otner system related information, such as servers and databases, ofr third-party (non-SAP) systems, Not all systems that you work with are installec and con‘igured at tne beginning of the implementation project. The system's landscape management database (LMOB) isp with system information. You need to agree ana time schedule for IT to make the required physical systems available before the start of each project stage (for example, before development and testing) The SAP Solution Manager LMDB is the central landscape information repository. A system landscape description isthe basis or almost all SAP Solution Manager applications, such as Monitoring and Alerting, & landscape descristion is required to calculate updates and Upgrades with the maintenance planner in SAP Support Portal ‘SAP Solution Manager collects and stores detailed information about the technical system landscape. This information is built from two parts: the software descriptions from the SAP sottware catalog (SAP software catalog data (CR) content) and the information that is sent ‘automatically by technical systems via the system landscape directory (SLD). lated a"rainsr2018 ‘SAP e-book Lesson: etn Techn Perego S4/HANA inplementation jets eiroSh bala low detawon SLD SAP Solalon Mager IND, and Clon Pro The figure, Data Flow Between SLD, SAP Solution Manager LMDB, and Customer Profile, depicts the data flow between the SLD, SAP Solution Manager LMDB, and Customer Profile as follows + First existing SLD and LMD8 topologies stay vali - this is important because there are ‘other client applications ef SLD in the landscape than SAP Solution Manager + Second, this is our detault recommendation ~one central SLD system reports to one product ve (uploading) SP Solution Manager system: the SAP Solution Manager system ‘with role test doesn’t upload to the Customer Profile ‘Anon-SAP product inthe system landscapes either developed by a customer (customer product) or by a company other than SAP (third-party procucl). Non-SAP products often do ot have an entry in the SAP so‘tware catalog and are therefore not part of the SAP CR content. They can be deployed in SAP runtimes, Ike SAP NetWeaver AS for ABAP or SAP. NetWeaver AS for Java or in non-SAP runtimes, Ike IBM WebSphere. Products that were not developed by SAP but are described in the SAP Sottware Catalog (partner products) are not classified as non-SAP praduects, inthis context. 'Non-SAP product descriptions are createdin the SLD and are synchron zed te the LMDB ‘automatically. ‘System Information Systems managed by SAP Solution Manager can be configured so that they report their data tothe SLD continuously (automatic registration and update) Modern installations write the installed product instances tothe system. The chain SLD. MDB is used to automatically trans‘er this data to the Solution Manager system landscape. It the product data s missing, frst maintain the data forthe techricalsystem in the LMOB. After saving the data, check the product system data in the Solution Manager system landscape. For an SAP Netileaver AS for ABAP system type, identify the product instances as relevant, If the product system does not exist, itis created automatically. For the other system types. the product instance is transferred automatically only if the product system exists In this case, Create the product system frst or assign the technical system to an existing product system, then save the assigned product instance again in the LMDB. ‘SAP Sclution Manager collects the system landscape data trom the SLD in aperiodic job, and stores it in the LMDB (transaction code 123) ofthe Solution Manager system. tomenaeeee OOS wnrainsr2018 technical system isa runtime system on top of a computer system (host). Itisa set of so‘tware elements that are installed. configured and administered as a unit. technical system offers services at service access points. The software that forms the technical system cane installed on a single host (standalone system) or distributed over several hosts (Cistrbuted system or cluster system). Individual product instances of product versions are installec on technicalsystems, A technical system often consists of sub-systems (technical instances or technical nodes) Technical systems are the central element of the solution landscape in terms of software component deployment and operational activities, such as monitoring and alerting. They are ‘ypicelly created by installation and register themselves inthe SLD, which forwards the Information te SAP Solution Manager. Tachnical systems ae identilied by their system ID hostname, and other attributes lke the installation number. A technical system is ofa certain type, for example, SAP NetWeaver AS for ABAP, SAP NetWeaver AS for Java, or TREX system. Logical components and logical component groups are an important part of your systeen landscape. A logical component can be an. ts, With this information an system role funetion, allows to determine t system, for example the ‘maintenance or development system, Logical component groups are uniquely defined for each solution. Ikis not possible to assign a logical component group to several solutions, The unique identifier for a logical componer srcup is the logical component group name. The narneis unique for the whole system. This name cannat be changed after the creation of a logical component group, > ee 2? Asarute of thumb, alogical component group comprises all systems of solution that have the same productive system and system type (for examale, ABAP o' Java). Hence, for eacn ABAP based and each nor-ABAP based procuctive system, you create a separate logical component group. For example, a solution could contain the logical component groups HR, SAP ERP, CRM, Bl, Pl, BOBU, and PORTAL. There isan important exception to the rule: companies with, for example, multiple SAP ERP procuctve systems per site (country plant) must use cnly one SAP ERP logical component group. Technically logical component ‘groups are created within solutions, > we PP Alogical components the branch view ona logical component group (that's the suibset of systems which belong to the production, maintenance or development tracks of your solution, fr example). Similar to SAP Solution Manager 71. logical components a vector of technical systems and system roles that usually orrespond toa transport track ol your landscape.rainsr2018 ‘SAP e-book Lesson etn Techn Perequstes o S4/HANA plementation jets ‘Logical Component Group * esorbes a group of systems which beng together * consis topes components win descr te ncdual woos ofa ystem tence Example: ‘Theron snows a cunarae ncape ee RSIASISEN GEERT] lmielnntarce rand scoop prosucve tm, whee Senaprent che unaor epg non eae a snack andes eo ‘onponnt rospouls compe ony ne topes consent [Advantages of Logical Component Groups comparedto SAP Solution Manager a ‘Synchronization of solution documentation and change request management + Easior handing duet the removal ofthe product assignment [tee 2tesicnpemcem OSOS~SCSY Landscape topology Logical Component Group layout [ERP (Logical Component Group) “Sim RSIS [Bil ese Sears ctopcal Corcoran uptore Tres Lanascape Landscape topology — Logical Component Group layout "ERP [Logical Componont Group) Cnpeprethayaan Mnsicen Pee ise ‘Som tome SSO wnrainsr2018 LESSON SUMMARY You should now be able to: + Explain the rle of SAP Solution Manager as a central source of system landscape information a"rainsr2018 Using the Solution as Single Source of Truth LESSON OVERVIEW LESSON OBJECTIVES Aer completing this lesson, you willbe able to ‘Administrate your solution Document a solution Manage authorizations in SAP Solution Manager Solution Administration The solution administration provides an overview of existing solutions. You can display and ‘maintain solutions. Furthermore, you can create and define new solutions. ‘solution contains the complete business descriotion, comprising the complete syst landscape all Business processes, and branches for the versioring of Solution Documentation. Only one solution should be used for the whole business. but itis possible to tse several solutions, for example in large companies with several separated areas. Note: solution's the sum of a company’s systems, applications, and processes. It acts as a contziner for versions of Solution Documentation, one of whichis the production version. From a process perspective, 2 solution covers al the company’s business processes, system perspective, a solution covers all praductive systems that ar rough interfaces, {As solutions form independent areas with very iited access to functionality outside of themselves there is typically only one productive solution per company, Even for an international multisite company, one solution is generally suficient ‘Multiple productive solutions typically cover the use case of a service provider running ‘multiple productive solutions for citferent clients, a"rainsr2018 ‘SAP e-book Unt 2: reese or SAP SA/HANA Inpleenaton Projets “he solution te sum of companys fyatone.spnlesore ana prostesos I rear cortaner for vars of son reducer version + Recommendation Solution ‘ovetest ie ele sae cssape nds dovumeriaton ao age nd ‘terannaced consones -Anoe2pton of Ps recommendation ean bea seco powder who raraaee Several ndependert cuss Inthat = ‘seraate etter Fee S5 Sakon Bases You can share a solution between business units, connected companies, and project teams. It Is also shared across geographies and locations It serves as single source of truth ands the container of the entire solution documentation. \Whon you want to benefit from the Process Managernent capabiltios in SAP Solution Manager 72, you need to understan the following fundamental concepts: + Solution documentation content “The term solution documentation content denotes all artifacts, documents, diagrams, test ‘cases, and so on, which you created to describe one or multiple aspects of your software solution. SAP Solution Manager 72 allows you to structure anc organize the solution {documentation n as many process levels as required by your organization. Italso allows you to manage these elements along tae complete Itecycle, + Branches to separate different versions of solution documentation content Branches are the linepin of the SAP Solution Manager content lifecycle concept. They control the visibly and changeablity of solution documentation content. By default, when yu create a solution, there willbe a production and a maintenance branch. While the procuction branch only contains productive documentation the maintenance branch ‘offers a version of solution documentation centent ina staging area to further maintain customer solution documentation without any interference with productive content. + Thesystem landscape that you use to execute processes Solution documentation content provides most value to customers, itis fully synchronous with the technicalrealty of tne actual systems. SAP Solution Manager 721s the only tool in the IT industry that firmly inks documentation and system reality along the ‘complete Ifecyce. To do so, youneec:to document your system landscape precisely. SAP Solution Manager introduces logical component groups to facilitate this process. Logical component groups allow you to document all aastraction levels required forthe ind vidual user types, Sites to represent localized system landscapes Experience shows that many customers cannot define business processes that are valid in all geographies or locations because you need to take variations specific to @ country or region into account. This is why SAP Sclution Manager 72 introduces the site concept. tome OSS a"rainsr2018 ‘SAP e-book Lesson: Using te Soon a Single Sours of Huth Sites allow you to document local exceptions of global stanciards. They also enable you to ‘tag solution documentation content as relevant fora specific location and offer access to the corresponding systems. Solution Feres6 Irportan Salen Toms ‘The folowing activities and tabs are part ofthe Solution Administration: + Displaying and maintaining soltion ‘Yu can select an existing solution via dropdown ist for displaying and maintainingit. + Creating a new solution You can create and define 2 new solution via the Create Solution entry in the Global Functions menu, + Import and export of content ‘Abranch in Solution Documentation contains specific business content. For example, it ‘contains scenarios, processes, and library elements. You can import and export content ia solution administration, + Service activities ‘You can perform various activities to Update Search Indox, Calculate Derived Attributes, and Update Remote Element Text Buffer + Library Generation Cockpit You can open the Library Generation Cockpit with the Library Generation Cockpit entryin the Global Functions menu. + Document Type Administration The Document Type Administration is the central place to administer document types that are used forthe solution or within branches of the pracess documentation. Solution Settings tome OOOO a"rainsr2018 ‘SAP e-book Unt 2: reese or SAP SA/HANA Inpleenaton Projets “The Solution Sottngs section on the right ofthe sercen shows whether the site handling is ‘enabled or cisabled, With the Eft lik. you can open a dialog in which you can change this selting. Furthermore, the content languages forthe Solution Documentation content are displayed. With the Edit lin, you can open a dialog in which you can adc andl remove further content languages, System Landscape Tab ‘The System Landscape tab cisplays the main administrative information about the system landscape in a graphical representation It shows the elements that are assigned to the solution including logical component groups, logical components, branches, sites, and system roles. tome OOOOrainsr2018 ‘SAP e-book Lesson: Using te Soon a Single Sours of Huth Branches Tab ‘The Branches tab cisplays all information about branches. Fare Sekton harineaton Boneree (Change Control Landscapes Tab ‘The Change Control Landscapes tab d splays the change control landscapes that area subset ofthe whole system landscape. Those change control landscapes are used forthe setting of Change Request Management. You can create a new change control landscape va the context menu in the table of change control landscapes. Choose New and enter aname and a technical name for the new change control landscape. From thelist of all logical components sroups that belong to the system landscape, select the logical components groups thal you want to assign to the change controllandscape. \With the radio buttons All and In Scope, you can toggle the view ofthe logical components groups. With the option Al, you can cisplay all logical components groups that exist in the system landscape. You can mark the logical component that you want to use forthe selected tome OOS a"