TS410 Integrated Business Processes in SAP S/4HANA INSTRUCTOR HANDBOOK INSTRUCTOR-LED TRAINING Course Version: 06 Course Duration: 10 Day(s) Material Number: 50141072SAP Copyrights and Trademarks © 2017 SAP SE or an SAP affiliate company, All rights reserved, No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries, Please see http://globall?,sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices. ‘Some software products marketed by SAP SE and its distribu’ of other software vendors, 1's contain proprietary software components National product specifications may vary. ‘These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined inthis document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE's or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The nformation in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. © Copyright Alrights reserved u ByTypographic Conventions American English is the standard used in this handbook, ‘The following typographic conventions are also used, YOR «Oa Example text Example text {© Copyright. Allrights reserved.Contents xi al 29 30 45 51 82 n 75 al 85 93 94 103 106 Course Overview Unit 1: Unit 2: Unit 3: Unit 4: ‘SAP S/4HANA Enterprise Management: Overview Lesson: Outlining the Motivation for SAP S/4HANA Lesson: Explaining the SAP S/4HANA Simplification List New User Experience: SAP Fiori UX Lesson: Understanding the New User Experience Exercise 1: Adjust the SAP Fiori Launchpad in SAP S/4HANA, SAP S/4HANA Basics Lesson: Explain the Organizational Structures Exercise 2: Display the Organizational Structures Lesson: Understanding the Concept of Master Data Exercise 3: Display a Material Master Record Exercise 4: Display a Customer Master Record Financial Accounting and Management Accounting: Overview Lesson: Explaining Financial Accounting (Fl) Lesson: Explaining Management Accounting (CO) Lesson: Outlining the Integration Between Fland CO. 45 Minutes 40 Minutes 60 Minutes. 20 Minutes 60 Minutes 20 Minutes 60 Minutes: 10 Minutes 10 Minutes 80 Minutes 30 Minutes 20 Minutes (© Copyright. Allnghts reservedm 13 123 128 133 139 143 147 155 157 161 167 173 wr 181 184, 193 197 202 205 215 219 225 229 233 243 244 253 259 265 270 Unit 5: Unit 6: Financial Accounting and Management Accounting: Basics Lesson: Defining General Ledger (G/L) Accounts and Cost Elements 75 Minutes Exercise 5: Create a Primary Cost Account 15 Minutes, Lesson: Defining Cost Centers 45Minutes Exercise 6: Create and Display Cost Centers 20 Minutes Lesson: Posting a G/L Account Document 60 Minutes Exercise 7: Create a Posting from Financial Accounting, 10 Minutes Exercise 8: Display aG/L Account and G/L Account Line Items 15 Minutes Exercise 9: Check an Account in the Financial Statement 10 Minutes Version (Optional) Exercise 10: Display a Financial Statement Minutes Lesson: Working with Business Partners and Invoices 60 Minutes Exercise 11: Create a Business Partner (FI Vendor) 15 Minutes Exercise 12: Enter a Vendor Invoice with Document Splitting Minutes Exercise 13: Post a Manual Outgoing Payment with Check Minutes Printing Exercise 14: Display Vendors Account 10 Minutes Lesson: Working with Asset Accounting 40 Minutes Exercise 15: Create an Asset Master Record 15 Minutes Exercise 16: Post an Integrated Asset Acquisition 10 Minutes: Lesson: Working with Activity Types 30 Minutes Exercise 17: Create a Secondary Cost Account and an Activity 20 Minutes Type Exercise 18: Post an Activity Allocation 20 Minutes Lesson: Working with Internal Orders 45 Minutes Exercise 19: Maintain Master Data of an Internal Order 10 Minutes Exercise 20: Create Transaction-Based Postings to an Internal 15 Minutes Order Exercise 21: Settle Orders at Period-End 10 Minutes Human Capital Management Lesson: Organizational Management in HCM 105 Minutes: Exercise 22: Create an Organizational Unit and a Position in 10 Minutes Organizational Management Lesson: HCM Master Data 45 Minutes Exercise 23: Create an Employee Master Data Record 10 Minutes Lesson: Integrating with Success Factors 40 Minutes ‘© Copyright. Allrights reserved297 299 312 37 323 327 331 335 341 347 351 353 357 361 366 373 377 381 387 391 395 397 403 413 414 422 442 Unit 7: Unit 8: Purchase to Pay Processing in SAP S/4HANA Lesson: Describing the Purchase to Pay Business Process Lesson: Defining the Master Data Used in the Purchase to Pay Process Exercise 24: Create a Material Master Record Lesson: Creating a Vendor Master Record Exercise 25: Create and Extend a Vendor Master Record Lesson: Listing Additional Vendor Specific Master Data Records Exercise 26: Create a Purchasing Info Record Lesson: Creating Purchase Requisitions Exercise 27: Create a Purchase Requisition for a Stock Item and a Consumable Material Lesson: Creating Purchase Orders Exercise 28: Create a Purchase Order with Reference to PReq Exercise 29: Run an Internal Order Report Exercise 30: Evaluate Purchase Orders Lesson: Posting a Goods Receipt for a Purchase Order Exercise 31: Post a Goods Receipt for a Purchase Order Exercise 32: Transfer Posting for Material Lesson: Processing Vendor Invoices Exercise 33: Post the Vendor Invoice Exercise 34: Query the Supplier Account Lesson: Processing the Automatic Payment Run Exercise 35: Create an Automatic Payment Run Exercise 36: View Vendor Accounts Warehouse Management - Stock Transfer Lesson: Explaining WM Structures and Usage Lesson: Outlining the Difference between EWM, WM. and Inventory Management (IM) Lesson: Processing a Stock Transfer Order 40 Minutes 40 Minutes 10 Minutes 30 Minutes 10 Minutes 45 Minutes 10 Minutes 40 Minutes 15 Minutes 75 Minutes, 15 Minutes 10 Minutes 10 Minutes 60 Minutes 10 Minutes 10 Minutes 45 Minutes 10 Minutes 10 Minutes 45 Minutes 15 Minutes 5 Minutes 15 Minutes. 30 Minutes 60 Minutes (© Copyright. Allnghts reserved. oy451 Unit 9: _ Plan to Produce Business Process in SAP S/4HANA. 454 Lesson: Describing the Plan to Produce Process in SAPS/4HANA 15 Minutes 462, Lesson: Defining the Master Data inthe Planto Produce Process 60 Minutes an Exercise 37: Change a Material Master Record SMinutes 475 Exercise 38: Change Bill of Material 5 Minutes 479 Exercise 39: Change a Work Center 5 Minutes 483, Exercise 40: Change the Routing for a Finished Product 5 Minutes: 486 Lesson: Creating a Product Cost Estimate 60 Minutes 493 Exercise 41: Create a Standard Cost Estimate 20 Minutes 497 Exercise 42: Update Material Valuation 20 Minutes 502 Lesson: Planning Product Demand - Integrated Planning 45 Minutes 503 Exercise 43: Manage Planned Independent Requirements 15 Minutes 508 Lesson: Defining the MRP Process 30 Minutes 515 Exercise 44: Change the Material Master Record 15 Minutes 520 Lesson: Processing MRP 45 Minutes 535 Exercise 45: Process an MRP Run 20 Minutes 539 Exercise 46: Monitor Material Coverage 20 Minutes 544 Lesson: Advanced Planning 40 Minutes 567 Exercise 47: Explore PP/DS in SAP S/4HANA 10 Minutes 572 Lesson: Describing the Manufacturing Business Process 15 Minutes 574 Lesson: Creating and Releasing a Production Order 45Minutes 577 Exercise 48: Convert a Planned Order toaProduction Order 20 Minutes 581 Exercise 49: Release a Production Order 20 Minutes 584 Lesson: Performing Material Withdrawal for a Production Order 30 Minutes 587 Exercise 50: Perform Goods Issue for a Production Order 20 Minutes 593 Lesson: Performing an Order Confirmation and a Materials Goods 30 Minutes Receipt 597 Exercise 51: Confirm a Production Order 20 Minutes 599 Exercise 52: Prepare and Post Goods Receint from Production 20 Minutes. into Warehouse 605 Lesson: Performing Period End Closing Activities 60 Minutes 619 Exercise 53: Calculate Variances in a Production Order, 20 Minutes 621 Exercise 54: Settle a Production Order 20 Minutes 623 Exercise 55: Evaluate CO-PA 20 Minutes vil ‘© Copyright. Allrights reserved,631 633 635, 637 641 643, 649) 651 655 663 667 67 675 679 687 693 699 703 709 m 73 7a 725 729 737 743 749 753 756 759 767 ™ 778 Unit 10: Unit 11: Order to Cash Processing in SAP S/4HANA Lesson: Describing the Order to Cash Business Process 15 Minutes Lesson: Describing the Master Data Used in Sales and Distribution 60 Minutes Exercise 56: Check Material Master Record for Sales 20 Minutes Lesson: Creating a Customer Master Record 45 Minutes Exercise 57: Create a Customer Master Data Record 20 Minutes Lesson: Creating a Condition Record 45 Minutes Exercise 58: Create a Condition Record 20 Minutes Lesson: Processing a Sales Order 60 Minutes Exercise 59: Create a Quotation and a Sales Order 20 Minutes Exercise 60: Create a Sales Order with Reference toa Quotation 20 Minutes Exercise 61: Check and Solve Sales Order Fulfilment Issues 20 Minutes Exercise 62: Review the Sales Order 20 Minutes Lesson: Processing a Delivery Document 75 Minutes Exercise 63: Create a Delivery Document 20 Minutes Lesson: Processing a Customer Invoice 60 Minutes Exercise 64: Create a Customer Invoice 20 Minutes Exercise 65: Run a CO-PA Report 20 Minutes Project System Lesson: Describing the Process Steps in Project System. 15 Minutes Lesson: Creating a Project Structure 60 Minutes Exercise 66: Create a Project Structure 20 Minutes Lesson: Planning a Project, 120 Minutes Exercise 67: Plan Resources in a Project 20 Minutes Exercise 68: Plan Dates in a Project 20 Minutes Exercise 69: Plan Costs in a Project 20 Minutes Lesson: Budgeting in a Project 30 Minutes Exercise 70: Create the Budget for a Project 20 Minutes Lesson: Executing a Project 90 Minutes Exercise 71: Release a Project 20 Minutes Exercise 72: Post @ Confirmation of Time for your Project, 20 Minutes Exercise 73: Post Time Confirmation with CATS 20 Minutes Lesson: Processing Period-End Closing Activities, 45 Minutes © Copyright. Alrghts reserved » oy785 Unit12: SAP Enterprise Asset Management (EAM) 787 Lesson: Processing Business Steps in SAP EAM 15 Minutes 789 Lesson: Describing Master Data Used in SAP EAM 90 Minutes 793 Exercise 74: Display a Functional Location Structure 20 Minutes 801 Exercise 75: Create an Equipment Master Record 20 Minutes 807 Exercise 76: Display an Asset Master Record. 20 Minutes 817 Lesson: Creating Notifications 75 Minutes: 821 Exercise 77: Create a Notification 20 Minutes 825 Lesson: Processing Maintenance Orders 90 Minutes 833 Exercise 78: Create a Maintenance Order 20 Minutes 837 Exercise 79: Plan a Maintenance Order 20 Minutes 843, Exercise 80: Release a Maintenance Order 20 Minutes 847 Lesson: Executing Maintenance Orders 90 Minutes 855 Exercise 81: Confirm Time for Maintenance Order andGoods 20 Minutes. Issue Posting 859 Exercise 82: Technically Complete a Maintenance Order 20 Minutes 863 Lesson: Processing Period-End Closing Activities 45Minutes 865 Exercise 83: Perform Period-End Closing Activities 20 Minutes ‘© Copyright. Allrights reservedCourse Overview TARGET AUDIENCE This course is intended for the following audiences: + Application Consultant + Business Process Architect + Business Process Owner/Team Lead/Power User + Enterprise Architect + Program/Project Manager (© Copyright. Allnghts reserved.(© Copyright. Allrights reserved.Lesson 1. Outlining the Motivation for SAP S/4HANA. 2 Lesson 2 Explaining the SAP S/4HANA Simplification List a UNIT OBJECTIVES + Outline the motivation for SAP S/4HANA + Explain the usage of the Simplification List Scone Angered i ayAA Outlining the Motivation for SAP S/4HANA 2 LESSON OBJECTIVES After completing this lesson, you will be able to: + Outline the motivation for SAP S/4HANA, SAP S/4HANA Overview ‘ast ars arta eee 90% 40% “4 citiverseta Gronthinadostion obsess retorts? has been generat 212B- 9B 51% @ Things wb connate robe uses cored processed inthe dud Inthe werd ScienceDaily. ® Internet of Things (loT) 2013 to 2020 ‘ScienceDaily, 22 May 2013 i Trllions of Dollars, IDC, 2013 Techn Adoption Report: Business Networks, Ardent Partners, 2014 “ Statista, 2014 Figure J: The Business Landseape's Increasingly Complex and Networked If you look at the numbers in the figure, The Business Landscape is Increasingly Complex and Networked, it becomes obvious that the world around usis getting more complex, for the following reasons: Exponential growth of digital information — social, mobile, big data + Globalization and spread of business networks Internet of Things (you could also say, the Internet of everything) ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA ‘The response so far has been the development of more complex business processes, more ‘complex organizations, and more complex software solutions. At the end of 2009, 5% of the world’s population owned smartphones. Four years later. that figure jumped to 22%. Currently, 1.7 billion people are on social networks. Over the next three years. that audience will surpass 2.55 billion. By 2020, 5 billion people will enter the middle class ‘and come online, while 50 billion devices will be connected to the Internet of Things. creating a digital network of virtually everything. In addition, cloud computing - a $41 billion business in 2011 - will grow to a $241 billion business in that same time frame. The exponential proliferation of mobile devices, social media, cloud technologies. and the staggering amounts of data that they generate has transformed the way that we live and work. In fact, 61% of companies report that the majority of employees use smart devices for everything from e-mail to project management to content creation. While all of these advancements have improved our lives and provided us with greater opportunities for innovation than ever before, they have also accelerated the rise of an entirely new problem to contend with: unprecedented and crippling complexity. The world may be getting smarter, but it hasn't gotten any easier. a Powerful multi core processors Huge / affordable memory AMRABEDUUY. Optimised cache Cloud Figure ® Advances in T hnclogy In the last few years, there have been significant advances in technology that application developers can take advantage of to build smarter and more powerful applications. Examples include the following: + Mul ‘core processors enabling parallelism of tasks This means more throughput of data and faster processing to give us real-time responses. + Bigmemory This enables us to fit an entire organization's database in memory, which means that we lose the mechanical spinning disk and the latency it brings. Advances in the design of the on-board cache means that data can pass between memory and CPU cores rapidly. In the past, even with large memory, this created a bottleneck as the CPUs demanded more data and the journey from memory to CPU was not optimal. Scope Avatar EESADAUnit2: SAP S/4HANA Enterprise Management: Overview We can now easily slot more servers into our landscape to add more processing power or ‘memory in order to scale to any size, SAP rewrote its business application software to fully exploit the new hardware. SAP worked closely with leading hardware partners, who shared the product blueprints of their new CPU architectures, so that SAP knew how to write the best modern software to extract as much power as possible. Cloud computing technology has matured in the last few years and is now a compelling deployment option for our customers who do not want to take on the complexity and cost of the installation and maintenance of IT landscapes. Virtualizing machines means lower costs associated with running enterprise-wide applications. Public cloud services based on subscription models increase access for everyone to the latest solutions, reducing the costs and simplifying everything, ( EST SISHANA )! ( ere )) WA R/3 S 1979 1992 2004 2015 Figure 3. Time to Rebull the Business Sule forthe Digital ors Since the beginning of enterprise computing, SAP has been rebuilding the business applications whenever major technology shifts have occurred. ‘Some key moments in the application development history of SAP are the following: + 1979 - SAP invents ERP. SAP builds standard business software based on mainframe technology. The name, SAP R/2 supports and integrates major business functions in real time and handles multi-country and multi-currency implementations (R means real time, and, although there was an R/1, this is not regarded as the first major release). + 1992 - With the rise of the personal computer, the introduction of client/server architecture means another rewrite of the applications to exploit the power ofa layered, three-tier architecture approach, in which processing is split across three layers - client, application, and database. It is the end of the mono-chromatic, text-based, messy green screens and the start of 2 new graphical interface to improve the end user experience. This is the birth of SAP R/3. + 2004 Now the Web is firmly established as the common business network and customers demand better integration between their business applications and the Web. SAP develops a 4 ‘© Copyright Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA new integration application platform called SAP NetWeaver in order to enable this. Now all ‘SAP applications run on a common platform, and customers and partners can build and integrate existing applications easily using widely adopted Web standards, such as service- oriented architecture (SOA). Additionally, alittle later, a new switch framework is introduced to allow customers to selectively enable only the new functions developed by SAP in order to avoid disrupting their core processes. The SAP R/3 name is now replaced by SAP ERP. ERP is part of a larger family known as SAP Business Suite, which also contains many other line of business (LOB) applications from SAP, such as SAP CRM. + 2015 Anew wave of advances in hardware architecture brings massive computing power at decreasing costs. Huge memory and multi-core processors arrive to offer massive computing power. The underlying design of existing SAP applications does not fully exploit the power of the new hardware. A rewrite of the complete Business Suite is required. The new business suite is called SAP S/4HANA. New Services Localization New Data aera Technologies 2B QR Codes, RFID, Sensors Core ERP Finance, Human Resources New Tracking ay, &? Green manufacturing, (Coz tracking, GRC standards New Markets Figure 4 Core ER® Processes Unchanged The main ERP processes include procure to pay, plan to produce, order to cash, or request to service are unchanged. The way that we access these processes has changed dramatically. In the past, these processes were executed on a desktop or laptop. Today, itis important that these solutions can be used on a mobile device using data stored in Cloud solution. Additionally, new services and technologies require new solutions. Scope Avatar = ByUnit2: SAP S/4HANA Enterprise Management: Overview Built on SAP HANA, 10x ERP, CRM, SRM,SCM, PLM co-deployed ‘smaller data footprint 7 shiseaahasipia ad 3. No locking, parallelism 7 4. Actual data (25%) and historical (75%) ee 5. Unlimited workload capacity 6. Predict, recommend, simulate 1800x 7. SAP HANA Cloud Platform extensions Eee 8. SAP HANA muit-tenancy 8. All data: social, text, geo, graph processing 4x 410. New SAP Fiori UX for any device (mobile, desktop, tablet) Jess process steps Choice of deployment: on-premise, cloud, hybrid Figure 5: Some Facts about SAP S/4HANA SAP S/4HANA comprises anew code base, a new SAP Fiori user experience (UX), and new guided configurations. Itis our new generation of the suite. ‘These simplified applications are seamlessly integrated to offer one solution for every business problem. Allof these anplications offer a modern web-based SAP Fiori UX, ready for real cloud consumption. Allof this together makes these applications a completely new product: with a new database, data management, technology, and front-end, offering the following: + 10x smaller data footprint + 1800 times faster analytics and reporting + ERP, CRM, SRM,SCM, PLM, reintegrated in one system ‘A major achievement is the ability to reintegrate ERP, CRM, SRM, SCM, PLM co-deployed - to save hardware costs, operational costs and time. This is possible because SAP S/4HANA has a 10x smaller data footprint compared to a best-in-class business suite on traditional database. ‘Another example is seen when comparing the processing receivables app in SAP GUI versus SAP ‘Simple Finance. The number of screen changes from 8 to 2 (4x) 6 ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA SAP HANA posit | SAP S/4 HANA er < Inmomory + Realtime analysis + Realtime business = Simplified deta medel lator” “Realtime roporing « OLAPand OLTP. Now user experonce together * Advanced pressing Shera «Ghote of Speymnet Enterprise Cloud for* Muttonanoy SAP Busmoss Suto on SAP HANA 201 Zoi 7011 2018 \We should recognize the key enabler of SAP S/4HANA from the software side. itis called SAP HANA and itis the platform on which SAP S/4HANA is natively built, In 2005, SAP started researching the possibility of developing a new wave of applications built on ‘an in-memory database, When SAP realized that no traditional database vendor had what they needed on the database side, SAP began developing its own in-memory database. SAP worked with leading chip manufacturers to identity to optimal design of a database that could exploit the {ull power of the new generation of powerful processors. ‘The first release of SAP HANA was in early 2011. It was initially positioned as a standalone data mart solution, where customers could replicate data from any sources in real time to the in- memory database, and build Business Intelligence (Bl) reports and applications on top. This meant Bl was an early beneficiary of the power of SAP HANA. Next, SAP began developing SAP HANA-based accelerators, which were deployed as side-car ‘engines to run alongside traditional SAP ERP functions that were critical to businesses, yet were pertorming slowly. In simple terms, SAP HANA became a secondary helper database and stepped in to help out with the heavy processing. ‘Around the same time, SAP developed new, innovative applications that were completely powered by SAP HANA and needed massive processing power, such as Smart Meter Analytics and Oncalyzer. ‘Around 2012, SAP successfully converted its first major application, SAP BW, to run completely ‘on SAP HANA, This was quickly followed up with the conversion of SAP Business Suite, These existing applications are referred to as powered by SAP HANA, or simply on HANA: for example, Suite on HANA (SoH) and BW on HANA. Be sure not to confuse SoH with SAP S/4HANA, as these are not the same. Conversion means the code has been adjusted to work with SAP HANA and also to take advantage of some basic optimizations. In 2015, SAP started from scratch and rewrote the complete SAP Business Suite natively to run only on SAP HANA. Unlike Suite on HANA, SAP S/4HANA is a brand new code-line, which works only on SAP HANA. Unlike Suite on HANA, the applications do not have to work on any other copra hivata rere > ByUnit2: SAP S/4HANA Enterprise Management: Overview vendors’ databases. This means SAP was not restricted by the limitations of these databases, which meant code always had to be built so it worked with many databases. This often meant developing over-complicated data models. SAP was finally able to code freely with no compromises, in order to exploit 100% of the power of SAP HANA. successfates: oorcer ahretoouss Ce a (Oba ste Oi stv pute Figure 7 SAP S/4HANA Suite — Introducing he Newt Generation Cove and ‘of Business Solitions forthe Digtal ‘The next generation core and lines of business solutions includes solutions for SAP S/4HANA Finance for SAP S/4HANA HR, SAP S/4HANA Supply Chain & Asset Management, SAP S/ HANA Sales, Services, and Marketing, and for SAP S/4HANA Sourcing and Procurement. ‘Thereby solutions from ARIBA, CONCUR successfactors, fieldclass and hybris are used. SAP Ariba is the world’s business commerce network. SAP Ariba combines industry-leading cloud-based applications with the world's largest Internet-based trading community to help companies discover and collaborate with a global network of partners. Using the SAP Ariba Network, businesses of all sizes can connect to their trading partners anywhere, at any time from any application or device to buy, sell, and manage their cash more efficiently and effectively than ever before Concur Travel and Expense Web and mobile solutions for travel and expense management. it includes corporate travel booking, expense report automation, reimbursement, audit, and business intelligence, and corporate card integration. It is offered in multiple ecitions (Small Business, Standard, Concurforce, Professional, Premium). ‘SAP SuccessFactors is the leader in cloud-based Human Capital Management (HCM) software for talent management, core HR, and HR analytics. SAP Fieldglass provides a cloud-based Vendor Management System (VMS) to manage contingent workforce and services procurement programs. ‘SAP Hybris helos businesses around the globe sell more goods, services, andi digital content through every touchpoint, channel, and device ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA Evolution to SAP S/4HANA Enterprise Management 47 ERP 2004. ERPGEhPx ERPGENPS ERPSENP7 ERPOENPS SAPSA/HANA AryOB = ArYDB—SAPHANA SAPHANA Enterprice Management as ONE Figure & Evolution to SAP S/&41ANA Enterprise Management ‘The evolution starts on SAP R/3 Release 4.7, which was able to run on any database and uses SAP NetWeaver as a basement. ERP2004 was followed by SAP ERP6.0. SAP ERP6.0 EhP7 was the first solution, which runs on SAP HANA, the starting point of SAP Finance, SAP Finance on the other hand was the first step in the SAP S/4HANA Enterprise Management Solution. All of these solutions are executed on an SAP HANA database. SAP S/4HANA Enterprise Management = Po. AT eee Figure &. SAP S/4HANA Enterprise Management Scope hivaa rere EESADAUnit2: SAP S/4HANA Enterprise Management: Overview SAP S/4HANA Enterprise Management component is enhanced by LOB Solutions. In the area of ‘Sourcing and Procurement, SAP S/4HANA Enterprise Management is enhanced by capabilities in the SAP Ariba Portfolio. This is the SAP Ariba Business Network for suoplier collaboration and, SAP Ariba Procurement Content in the area of Requisitions, SAP S/4HANA is not a single product. Customers can start with the basics components and add to them later. SAP S/4HANA Enterprise Management is a great place to start, This is known as, the simplified core, Perhaps it might help to think of SAP S/4HANA Enterprise Management as, the replacement for SAP ERP. Here, we find support for all core business processes, such as order to cash, procure to pay, and so on. For many customers, this is where their SAP S/4HANA adoption begins. Seamlessly integrated with the core, we find SAP S/4HANA Lines of Business (LoB) solut ns. These are options that can be added at any time and provide best-in-class lines of business solutions and connections to SAP Business Networks. In the past, we had multiple add-on applications surrounding a core (for example SAP ERP, SAP CRM, and SAP SRM), but with overlapping models and much redundancy. Now overlaps and redundancy have been completely removed from SAP S/4HANA. SAP S/4HANA is built natively and optimally to run only on the SAP HANA platform, Let's highlight the most important aspects of SAP S/4HANA and what makes it very different from what we had before, We will then drill down on individual topics in later slides. First of all, SAP S/4HANA is built on SAP HANA, so we inherit all the capabilities of this powerful data management and application platform. This includes advanced text mining, predictive analysis, simulations, and powerful real-time decision support. A brand new user experience is delivered to improve the productivity and satisfaction of business users and brings the interface up to a consumer-grade experience on any devices, ‘SAP S/4HANA can be deployed on premise or in the cloud, or 2 combination of both, to provide flexible options to customers. ‘The data model has been massively simplified. This means that we lost unnecessary tables and, of course, the data in those tables, to shrink the footprint dramatically and simplify the application design and extensibility 10 ‘© Copyright. Allrights reserved,Lesson: Outlining the Motivation for SAP S/4HANA 's ~ Key Innovations ooo Material Inventory Material Available To Capacity Requirements Management Valuation Promise & Planning Planning Backorder processing Order Management Procurement & Billing ‘This is the current state of planning and may be changed by SAP at any time. Figure 0: SAP S/4HANA Logistics - Key Innovations Within SAP S/4HANA, the following key innovations have been developed: + In Material Requirements Planning (MRP), fast MRP run and new working model for MRP controllers + In Inventory Management, a simplified data model resulting in increased through-put, and flexible analytics at the most granular level + In Material Valuation, the elimination of locking, and increased throughput for standard price utilizing Material Ledger + In Available To Promise & Backorder processing, a new available to promise (ATP) algorithm, based on SAP HANA embedded in mass component check in production + In Capacity Planning, PP/DS side by side with SAP S/4HANA + In Order Management & Billing, the enabled monitoring of end-to-end order-to-cash process. and take action for any exceptions, information on the exceptions to resolve the issues, + In Procurement, increased efficiency in the Procure-to-Pay processes, new analytical apps and spend KPIs, and Ariba Network Integration for PO OrderUnit2: SAP S/4HANA Enterprise Management: Overview Key Aspects of SAP S/4HANA Native SAP HANA Capabilities Work Patterns Analytics, Decision & Text Mining prediction Si™ulation 'Stpnort , @& 6 Choice of Development Sa” S/IAHANA Footprint Reduction On-premise User Experience Edition. “te ae ® oe Ey Figure Il Key Aspects of SAP S/4HANA Here we highlight the most important aspects of SAP S/4HANA and describe why itis very different from previous solutions, We then drill down on individual areas later. ‘SAP S/4HANA is built on SAP HANA. so it inherits all the capabilities of this powerful in-memory data management and application platform. This includes advanced text mining, predictive analysis, simulations, and powerful real-time decision support, with access to any type of data in real time brand new user experience is delivered to improve the productivity and satisfaction of business users and brings the interface up to a consumer-grade experience, optimized for any device. ‘SAP S/4HANA can be deployed on premise. in the cloud, or a combination of both, to provide flexible consumption options to customers The data model has been massively simplified. This means that we have lost unnecessary tables, and of course the data in those tables, in order to shrink the footprint dramatically and simplify the application design and extensibility 2 ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA Bringing Online Transaction Processing (OLTP) and Online Analytical Processing (OLAP) Together Separated Transaction + Analysis + ‘One atomic copy of data for ‘Acceleration processes Transaction + Analysis, All in Memory Transit Analyse Accelerate + S.copies of data in diferent data modes + Eliminate unnecessary complexity and + Inherent data latency latency + Poor innovation leading to wastage il eee ataret otras + Accelerate through innovation and simplification Figure 12. Bringing OLTP ard OLAP Together For more than 20 years, organizations have been using specialist software, usually with additional hardware, to extract, transform, and load (ETL) data from transaction systems to dedicated reporting systems. Based on the technology available, this has been the optimal way to provide a holistic view of business data with good response times (especially when you add accelerator software or hardware). OLTP has been separated from OLAP. This is due to the database design of OLTP and OLAP. Database models have been either bullt for OLTP optimization or OLAP optimization, but not both However, this has also bought with it complexity, redundancy. and latency. Ithhas been common, for today’s business figures to be available only tomorrow for analysis, once the data has been extracted and loaded to a reporting system, ‘The database that supports SAP S/4HANA (SAP HANA) can handle both OLTP and OLAP processing from a single data model, so there is no need to move transaction data to a separate system. This means that transaction and analytical applications run off the same tables, and dat: is available in real time at every level of detail S cont Awan reserved EESAD AUnit2: SAP S/4HANA Enterprise Management: Overview Data Footprint _ Compression Column Any attribute OLAP + OLTP. store as an index lagethar 2 + 0 7 Traditional DB on SAP HANA Figure 13: Data Footprint A simplified solution architecture benefits your IT organization immediately. The IT landscape, processes, and maintenance routines are all positively impacted by a simplified solution architecture. The numbers shown here are from real-world experience of SAP Benchmarking Services, a division of the SAP services and support organization. ‘The advantages offered by a simplified solution architecture include the following: + Simplified IT landscape Cut memory and storage resources dramatically and improve reliability + 71% reduction in maintenance Maintenance is simplified by greatly reducing ETL and re-indexing batch jobs + Infinite scale Having an engine that allows the processing and analyzing of massive amounts of any data leads toa situation that only our imaginations limits the boundaries to use the system. All data, both inside and outside the company, structured and unstructured, can be processed and analyzed. Therefore, systems need the performance and scale to operate on a complete new level of data quality and quantity; it must be ensured that any redundant data is removed from the system, any data that does not directly contribute and benefit the business process or the quality of the information provided. + Business agility ‘Systems need to be able to support massively increased business agility and need to instantly react on user requests. Processes that hinder system performance and system agility must be avoided. This is the end of batch processing; batch has started with punch cards, punch cards have died, Uls, which were the interfaces of function modules have died and the batch is now dying in these days. “ ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA Data Footprint 2 2015, actual 2o1e 2013 historical cad zon ee te ee Traditional DB on HANA SAP S/4HANA Actual 593 os Figure 1 Data Footpnnt? Areduction from 593 GB to 8.4 GB provides much more than simply storage capacity reduction as follows: + You can run the application on a mobile device + You increase the flow of data through your business applications. + Response times are shorter. + You can see more data on a screen (statistical data directly into a data entry screen) + Backup and updates are faster. + Restores are faster.Unit2: SAP S/4HANA Enterprise Management: Overview plified Applications SAP ERP Stability Flexibility Totals & Indices Financial Accounting) ] [likes 4s Totals & Indices Management Acc. Logistics Pestunns SAP Stability Accounting Er Pesta cd Figure 15: Simplified Applications We have already covered the simplification of applications from the technical side. Now we look at how simplification also applies to the business side, with an example from finance, In traditional SAP ERP finance, financial postings have been supported by two key documents, the Finance (Fl) document and the Controlling (CO) document. These documents provide the required views of the finance data from a legal perspective (Fl) and also an internal management accounting perspective (CO). There is a lot of overlap between these documents. Application code has had to deal with these two types of postings whenever a business event has occurred, that triggered a financial outcome, for example, a material receipt With SAP S/4HANA Finance, we now have only one document. This is called the Universal Journal Entry. A single financial posting is made to one table, which holds all information that is needed by both legal and management accounting. The application code is simplified and any Views of the data that are required are created on the fly by SAP HANA. We do not lose any business meaning, but we lose the underlying complexity of the application. 16 ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA Previous Complexity ioe Bl az @ Coneman re ay en ann ME gO Deeded re eats enn ial |anaze Component ian arin Hee met) Rn Release to Run Long _. Pretosd data ExPenand Es Pome nx > Tomas? E> cue ‘Management [Ragmts (PIRS)_ ‘{Smulaton) pe Lig ¥ a 570 E mm> cea th A ip data or Component Anayee Component Process pin) Nina Ane Rotem Aneta wage ce Z ma uce ah Prouetties (EEF) Set up daa for rventcry—Anayze Inventory ‘antatng hayes Coag ipa falas t oper MEP . E can a Iicrosof Excelesmall phy fi Uewrnraton ee Figure 16: Prevous Comploniy Another example of application simplification relates to MRP. Usually, this key business process is complex, with many steps and, as a result, can run for a long time before results are produced MRP is an iterative process. It involves identifying the components needed to satisfy demand, then checking resource capacity to procure those components, then readjusting the plan, This can take a lot of time, and by the time the processes have completed, the data can already be out of date. For example, you collected the demand data an hour ago and ran MRP to calculate the raw materials, but the demand picture changed while you waited for these results, so information you have is already out of date. ‘Therefore, real-time MRP is impossible, and you are always operating and making decisions on out-of-date results, In a fast-moving business where agility is essential, this is not acceptable.Unit2: SAP S/4HANA Enterprise Management: Overview Current Simplicity Consensus Release to Review Planned demand planning ad ERP Demand - Index Ramts (PIRs) (APO-DP, Management Flexible Planning, Ad-hoc job Microsoft Excel, and so on) Process (optional) Analyze usage probabilties (CBF) E Batch Job Release to E 4 User interaction operative MRP Figure 17: Current Simploty With SAP S/4HANA, MRP is a real-time process. This is achieved because of the raw power available with SAP HANA, and the dramatically simplified data model and application code that runs faster. MRP is no longer a painful batch process, which means you can run it whenever an individual change occurs in the inventory position right down the bill of material (BOM) component level. ‘This means that MRP becomes live. With SAP S/4HANA, you can now plan right down to a lot size of one. Ifa customer order is taken, you can immediately determine the effect on all the dependant subcomponents’ requirements, but only for that single order. This means that the inventory department can i begin working on. the procurement of the missing items immediately, and do not have to wait until the next MRP run to tell them there are missing subcomponents. 1B ‘© Copyright. Allrights reservedLesson: Outlining the Motivation for SAP S/4HANA Ready-to-Go Integration with Exi ing Cloud Solutions successfactors" nnstPCongany Employee Central HR Mast SAP Ariba Network Integration between SAP ‘S/4HANA Public Cloud Edition and SAP Arita Network: SISHANA Public Cloud Edition ‘+ Send Purpose Order to SARjap) [penis and SuccessFactors Ariba Network, relevant for i Employee Central: SAP S/MHANA Core + Employee and Emplayment scenarios Plan to Procure Data and Procure to Pay + Data Privacy (basic) Receive Supplier invoice + Project Staffing from SAP Ariba Network, “+ SAP Fiori Timesheet (basic) relevant for SAP S/4HANA oS Core scenario Procure to Pay SuccessFactors Employee Central Integration between SAP Figure 18: Ready-to-Go Integration with Exstng Claud Sokitons| SAP S/4HANA can be natively integrated with the existing SAP Cloud solutions, such as SAP Ariba, SAP Concur, SAP Hybris, SAP SuccessFactors, SAP Cloud Analytics, and SAP Cloud for ‘Customer (C40). Let us consider an example to help illustrate what this might look like. Acustomer deploys SAP S/4HANA to implement a core procurements process, such as purchase to pay. Employees are now happy that they can place requests for equipment that they need. However, employees would like to be able to read reviews from other purchasers of the same items, just as they do when they are at home using consumer applications, such as Amazon. The ‘employees would also lke to be able to ask vendors detailed questions about the items. By integrating SAP S/4HANA with SAP Ariba Network, this 's possible. SAP provides best practices and tools to rapidly integrate SAP S/4HANA with all SAP Cloud solutions, including SAP Business Networks. Scope Avatar PESAD AUnit2: SAP S/4HANA Enterprise Management: Overview ‘SAP S/4HANA: Deployment Options Cloud Private Cloud Public Srieanne Option Options. Features ana functions Functional scope of Simla to SAP ERP 6 SAP SIHANA 09 premise enterprise Pus con + raj inmovatons Finance and Logisics + ielustnet addtional batoes inthe Core Except Simpson it ems Incuding estonsbity ses aecatenes! promise entero | | , ‘ation Proare' i Mosiicatons Pay Keema ~ eect” | «ee an Detver new nsovatons a leveraging tb pesertalotr- High standardization ||. GoreFoanee ||. ESTEE remo eenneogyandnew TA nCeaiey + Cote atee Sct ot Figure 18: SAP S/AHANA, Deployment Options SAP S/4HANA is both available as on premise edition and as cloud edition. This training focuses on the 1511 SAP S/4HANA, on-premise edition. LESSON SUMMARY You should now be able to: + Outline the motivation for SAP S/4HANA 20 ‘© Copyright. Allrights reservedExplaining the SAP S/4HANA Simplification List 21 LESSON OBJECTIVES After completing this lesson, you will be able to: + Explain the usage of the Simplification List Content of Simplification List Change to ‘Simplification Exetng sim Functionality trapltcaifon tus + Data model changes Area = Removal of aggregates ‘implication Description ‘tem ‘rea Simplification tem Business impact cimliesvon Recommendations ‘Simplification tem ea simplineationitem Consolidation of Existing Functionality Figure20" [he Simplcation Ls With every new release of SAP S/4HANA, the simplification list is updated with release- dependent information. It describes the simplification items valid for SAP S/4HANA. This list must be treated as a complete inventory that is mapped against a productive environment to determine the impact when converting to SAP S/4HANA, Itis a collection of single simplification tems with the focus on what has to be considered through an implementation system conversion project, ‘The following information is provided for each simplification item: + Description + Business impact and recommendations + SAP notes (for related pre-checks or custom code checks) S copaht Aleghsresrved EM SADAUnit2: SAP S/4HANA Enterprise Management: Overview Technical System Assessment B S*? SHANA Transition Pre- Checks 7B Preparation c Figure 21 Simpitication List As a ass To accomplish the transition to SAP S/4HANA, the study of the simplification list is a good starting point and guideline. SAP also provides adcitional tools to support the transition, Pre-checks are shipped as SAP Notes to customers that want to convert to S/4HANA, Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to SAP S/4HANA. The pre-check results list the instances that need addressing before attempting the conversion process. Custom code analysis is used to support the customer in detecting custom code that needs to be adapted so that it can be moved to SAP S/4HANA. SAP offers custom code analysis tools (as part of the SAP NetWeaver 7.50). The customer can verify whether their current custom code will be compliant with SAP S/4HANA data structures and scope, ‘SAP S/4HANA Sales Solution Simplification — The Principle of One The principle of one includes the following: + SAP Global Trade Service (GTS) replaces ERP SD Foreign Trade (SD-FT). + SAP Credit Management replaces ERP Fl Credit Management (FI-AR-CR). + Settlement Management replaces ERP SD Rebates (SD-BIL-RB). + SAP Revenue Accounting replaces ERP SD Revenue Recognition (SD-BIL-RR). + Cloud for Sales and SAP CRM On-Premise are recommended for your field sales team, ERP Sales Support (SD-CAS) is not part of SAP S/4HANA Sales. Currently, SAP offers there are two software services for international trade transactions: Foreign Trade (FT) and Global Trade Service (GTS). FT is part of the normal SD. GTS is an external service that can be installed on an additional instance. The FT functionality is not available with SAP S/4HANA 1511, because SAP GTS is the successor for the business requirement, ‘The FI-AR-CR Credit Managernent is not available with SAP S/4HANA 1811. The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR). In SAP S/4HANA, Settlement Management replaces SD Rebate Processing, which means that existing rebate agreements can only be processed up until the end of the validity date of the 2 ‘© Copyright. Allrights reserved,Lesson: Explaining the SAP S/4HANA Simplitication List ‘agreement. They must then be closed by a final settlement. New agreements can only be created based on condition contracts. The ERP SD Revenue Recognition is not available within SAP S/4HANA. The newly available SAP Revenue Accounting and Reporting functionality should be used instead. This functionality supports the new revenue accounting standard, as lined out in International Financial Reporting Standards (IFRS15) and adapted by local Generally Accepted Accounting Principles (GAAPs). The migration to the new solution is required to comply with IFRSIS, even if an upgrade to SAP S/ HANA is not completed. Computer-Aided Selling (SD-CAS) is not available within SAP S/4HANA because itis not the target architecture. Itis recommended to use SAP CRM on-premise (side-by-side with SAP S/ 4HANA) or SAP Cloud for Customer. * Business Partner Approach * SD Simplified Data Model * Simplifications in SD Analytics ing Document Output Management Figure 22: Further Major Simplifications ‘As shown in the figure, Further Major Simplifications, the following changes are relevant for SAP S/4HANA Sales and Distribution: + Business partner approach + SD simplified data model + Simplifications in SD analytics + Billing document output management lal LESSON SUMMARY ‘You should now be able to: + Explain the usage of the Simplification ListUnit2: SAP S/4HANA Enterprise Management: Overviow 24 ‘© Copyright. Allrights reserved,Learning Assessment 25 1. What are some of the trends driving the need for a re-engineered business suite built for the digital? Choose the correct answers. ‘A Massive increase in device connectivity B Business users are taking on more technical IT tasks € Increase in ownership of mobile devices D Adoption of cloud computing 2. Why was the application code completely re-written for SAP S/4HANA? Choose the correct answers. ‘A The optimized ABAP code that we developed for Suite on HANA would not work with SAP S/4HANA B To take advantage of the simpler data model C SAP S/4HANA is now built with Java D To ensure that the code is optimized for SAP HANA 2. SAP S/4HANA is built to natively integrate with business networks such as Choose the correct answers. A SAP Ariba B Linkedin ¢ Concur D SAP Fieldglass E SAP Hybris S copaht Aves resrved = BOYUnit: Learning Assessment 4, What characterizes the architecture of a simple application? Choose the correct answers. [1] A Use of dedicated aggregation tables [1 8 Works with any database [1 © Reduction in number of tables [1] © No data redundancy 6 ‘© Copyright Allrights reservedLearning Assessment - Answers 27 1. What are some of the trends driving the need for a re-engineered business suite built for the digital? Choose the correct answers. X] A Massive increase in device connectivity B Business users are taking on more technical IT tasks X] © Increase in ownership of mobile devices X] D Adoption of cloud computing 2. Why was the application code completely re-written for SAP S/4HANA? Choose the correct answers. ‘A The optimized ABAP code that we developed for Suite on HANA would not work with SAP S/4HANA X] B To take advantage of the simpler data model C SAP S/4HANA\is now built with Java X] D To ensure that the code is optimized for SAP HANA, 3. SAP S/4HANA is built to natively integrate with business networks such as: Choose the correct answers. X] A SAP Ariba B Linkedin X] © Concur X] D SAP Fieldglass X] E SAP Hybris S copaht Aeghsresrved a BOYUnit: Learning Assessment - Answers 4, What characterizes the architecture of a simple application? Choose the correct answers. [1] A Use of dedicated aggregation tables [1 8 Works with any database Reduction in number of tables D No data redundancy 28 ‘© Copyright Allrights reservedLesson 1. Understanding the New User Experience Exercise 1: Adjust the SAP Fiori Launchpad in SAP S/4HANA &s8 UNIT OBJECTIVES + Understand the new user experience Scone Angnareed = BOYMM Understanding the New User Experience 30 LESSON OBJECTIVES After completing this lesson, you will be able to: + Understand the new user experience Traditional User Interface i owe Pa =e Figure 23. Traditional ser terface Itdoes not matter how good an application is if the user experience (UX) is poor. In the past, user interfaces all suttered from the same problem: they were tao camplicated. The main reason for this is that interfaces were often designed around the business function and not around the person. The result was a cluttered screen that tried to provide many features to many different job roles. For example, consider a sales order screen: how many job roles does this screen support? You might assume one, the sales order entry clerk. However. the reality is that the same screen is used by a large number of people who need to either check information or make adjustments to an existing order. Some examples are as follows: + Aquality assurance worker in the delivery department needs to release a blocked item in the order. + Afinance person needs to adjust tax assignments, + Asalesperson needs to adjust discounts. ‘© Copyright. Allrights reservedLesson: Understanding the New User Experience + Amarketing employee needs to apply promotion codes. + Aproject manager needs to check that costs have been assigned to the correct project phases. Each of these people could find themselves using the same screen, but only a very small part of the screen. The screen ensures that they all work hard to navigate to the specific area they need, ignoring the options they do not need, Lots of clicks are required for very little high-value interaction. Concepts and Influence Factors ie ra nn sa SAP Fiori launchpad SAP Web IDE User types a Pena hac Figure 24: Concepts and Influence Factors The use of IT and electronic devices is no longer reserved for a group of expert users; it has spread throughout society to all social groups. People need high-performing hardware that can support a variety of software products, with different scope and potential. There is added pressure to supply an easy-to-use solution to the end user. ‘The main drivers of this development are smartohones and tablets, with their easy-to-use and flexible user interfaces (UIs). The focus of these UIs is no longer on huge functionality but rather a comfortable user experience (UX), which puts the focus on the consumer. Business software must adapt and transform to turn this trend to its maximum advantage for the roles of an enterprise. In this evolution, the Ul plays an important role. With regard to SAP software products, the challenge is to keep a clear view and to understand the overall SAP strategy in the area of UX. Furthermore, itis important to have a clear understanding of the goals and target groups of each UI technology, to avoid mistakes and frustrated users, In the beginning, it is helpful to clarify the terminology used. A good place to start is with the terms Ul and UX Scope Avatar EM SADAUnit 2: New User Experience: SAP Fiori UX From UI to UX - From Function to Experience Figure 25: Ulversus UX ‘The terms Ul and UX represent two different ways of thinking. From a software perspective, Ul describes the interface between a human being and a device. It aims to maximize the efficiency of the device when used. UX takes on the perspective of the end user, and aims to provide ‘motivation and emotion, not only during use, but also before and after use. UX tries to achieve a sustainable, positive attitude, and to create a motivating experience. Focus on Function Today SAP Fiori UX Function-based applications. Role-based applications From: One transaction for multiple roles, To: Decomposed apps for each role ‘exposing all data & functions to all users exposing only relevant data & functions From: Multiple entry points for the user To: One entry point for the user and UX ‘and inconsistent user experience (ERP vs following common design directions an ) a —— Figure 26. Focus Shift, Contrary to traditional interface design, the design approach with SAP Fiori is that the focus is ‘now on the job role, rather than the function. SAP Fiori applications are always role-based. There are many applications to choose from, and they are organized in easy-to-use catalogs, supplied by SAP S/4HANA. You simply need to assign the roles to the users. 2 ‘© Copyright. Allrights reservedLesson: Understanding the New User Experience Each SAP Fiori application is built around the user, rather than the function. As a result, the screens are very simple and uncluttered. A key goal of any SAP Fiori application is to ensure that, a.user can complete a task with as few clicks as possible. In the past, users could find themselves working with many different interfaces, each one with a ‘completely different look and feel, even when they only had one task to complete. With SAP Fiori, users require little training, because the simple screens are intuitive, with only the essential information and options available. Imagine checking a customer inquiry from SAP CRM using the SAP Portal interface, and then moving to SAP GUI to check the stock availability in ERP. Completely different interfaces are used with their own style and features, with different buttons, menus, and tools. With SAP Fiori, users work with just one design. Not all transactions from ERP are converted to SAP Fiori applications, so SAP GUI must still be used in some cases. The cloud edition uses only SAP Fiori applications, and there are no classic SAP GUI screens. The SAP GUI is still available with the on-premise edition, and can be used alongside SAP Fiori, but we recommend using SAP Fiorito take full advantage of the features of SAP S/4HANA. User Types Different Requirements According to User Type e e@ eS Developer + Fast + Many functions + No specific UI + Simple + Locally installed + Backend- pane GUI oriented + Mutt-step + Overall ea Eraser Decay {ransactions authorization + Multiple + Multiple systems systems Figure 27-Use" Types Depending on the industry and company, various user types can be found. There is a great variety of different user types available, depending on the structure of the specialized area and the IT department, as well as the degree of digitization However, in almost every company there are three basic types as follows: + Occasional users copra Avatar = ByUnit 2: Now User Experience: SAP Fiori UX ‘An occasional user uses the system occasionally, and therefore needs simple and easy-to-use applications. In many cases, single-step transactions are executed, + Experts An expert user (or sometimes key user) is a fully-trained SAP user, who knows the processes and the available applications in detail. An expert user often uses multiple systems and different Uls. + Developers A developer (or programmer) has detailed process and system know-how, and deals with the adaptation and extension of the existing applications. Developers look after several applications with different Uls. Deployment Types On Premise Cloud Hybrid ure 28: Deployment Types The deployment type defines the license model and operational environment. 1e combination In the On Premise type, the customer buys software and hardware and operates th themselves. Therefore, the customer is solely responsible for implementation. the update extensions, and adaptation, as well as replacements and new investments. In the Cloud type, the cloud company provides infrastructure (hardware and software) and business software, and rents this combination to the customer. The cloud company is responsible for the operation, updates, extension, and new investments. At SAP, ditferent operational models are available (for example, public cloud, private cloud, and privately managed cloud) with different software and service provisioning. In the Hybrid type, the customer runs certain parts of their business software on their own servers, and uses additional solutions from a cloud provider. This deployment type requires an intense integration between the On Premise parts and the Cloud types. 34 ‘© Copyright. Allrights reservedLesson: Understanding the New User Experience Next Generation of UI Figure 29: Next Generaton of UI Akey theme of SAP S/4HANA is simplification. and this certainly applies to the user experience (UX). We use the term user experience, rather than user interface (UI), because we need to consider the overall experience of the user, rather than just the look of the screen. For example, if you go to a restaurant that has good food presentation but the service is poor, you would say that the overall experience was not good, and you would not be keen to repeat it. Itis important t provide not only a great-looking Ul, but also features that help the user become more productive, resulting in a good overall experience, This is what SAP Fiori delivers. SAP Fiori is a completely new UX, rather than an upgrade to any existing interface, such as SAP GUI, SAP Portal, or SAP Business Client. It works on any device that allows users to have the same experience, regardless of the device they choose to use. They can set up a basic sales order in the office using their desktop, then visit the customer to complete the configuration and agree pricing using a tablet. SAP Fiori provides the same look, feel, and productivity features on all devices. SAP Fiori applications are designed using a methodology called design thinking, which is a user- centric and solution-based approach to software and user interface design Scop Awan resorved = BOYUnit 2: New User Experience: SAP Fiori UX Target: Unified UX Direction for all SAP Software SAP Flor! Usor Experience: Reem SCN Cy Figure 20, Target: Unified UX Direction fa all SAP Software The long-term goal of the SAP UX strategy is to offer SAP Fiori (as the unitied Ul) to all business and all analytic applications on SAP HANA. ‘Types of SAP Fiori Applications ‘Task-based Access Insights |Access to tasks like change, |_| Visual overview over a create, or approve [complex topic for monitoring processes with guided or tracking purposes navigation Data mining and free analysis through analytics tools like Analysis Path Framework ‘Search and Explore |View essential information about objects and ‘contextual navigation between related objects Figure 3: Types of SAP Fon Aaplication Devas ‘SAP Fiori applications can be classified into different types. Examples include the following: ‘© Copyright. Allrights reservedLesson: Understanding the New User Experience + Transactional ‘These follow an optimal design for fast transaction processing, such as purchase receipt, entry. + Analytical These provide the tools required for analysis, graphs, charts, exploration, data mining, and drill-down, + Factsheet These provide a 360 degree view of all key information related to a business subject, For example, enter an employee name and all information about that employee appears, such as working hours, vacation, pay, performance, manager, and awards. Note: >» This is a good example of the SAP Fiori approach, which is to use a limited number of consistent interfaces to keep things simple, When a developer creates a new SAP Fiori application, they begin by selecting a template that is based on transactional. analytical, or factsheet. so they have a consistent look and feel ces -— i” iz [BRE Few 22: Types or SAP Fon Appcaton ‘The three most common types of SAP Fiori app are as follows: + Transactional apps use ABAP to provide the classic approach for functions of a business, system. They are available for SAP S/4HANA and Business Suite on any database + Analytical apps use the analytical capabilities of SAP HANA to provide insights in business data. They are available for SAP S/4HANA and Business Suite on HANA. + Fact Sheet apps use the enterprise search capabilies of SAP HANA to provide search results, They are available for SAP S/4HANA and Business Suite on HANA. Sopra Avatar ERISA