4. TS410_1610_S4HANA_Certification.pdf

(1)

Integrated Business Processes in

SAP S/4HANA

.

PARTICIPANT HANDBOOK

INSTRUCTOR-LED TRAINING . Course Version: 10

Course Duration: 10 Day(s) Material Number: 50138662

(2)

(3)

SAP Copyrights and Trademarks

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://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

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 in this 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 information 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.

(4)

Typographic Conventions

American English is the standard used in this handbook.

The following typographic conventions are also used.

This information is displayed in the instructor’s presentation

Demonstration

Procedure

Warning or Caution

Hint

Related or Additional Information

Facilitated Discussion

User interface control Example text

(5)

467 Unit 12: SAP Enterprise Asset Management (EAM) 469 Lesson: Processing Business Steps in SAP EAM 470 Lesson: Describing Master Data Used in SAP EAM 471 Exercise 73: Display a Functional Location Structure 477 Exercise 74: Create an Equipment Master Record 481 Exercise 75: Display an Asset Master Record 487 Lesson: Creating Notifications

489 Exercise 76: Create a Notification 493 Lesson: Processing Maintenance Orders 495 Exercise 77: Create a Maintenance Order 499 Exercise 78: Plan a Maintenance Order 505 Exercise 79: Release a Maintenance Order 509 Lesson: Executing Maintenance Orders

511 Exercise 80: Confirm Time for Maintenance Order and Goods Issue Posting

515 Exercise 81: Technically Complete a Maintenance Order 519 Lesson: Processing Period-End Closing Activities

(11)

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

(12)

(13)

UNIT 1

SAP S/4HANA Enterprise

Management: Overview

Lesson 1

Outlining the Motivation for SAP S/4HANA 2

Lesson 2

Explaining the SAP S/4HANA Simplification List 19

UNIT OBJECTIVES

● Outline the motivation for SAP S/4HANA ● Explain the usage of the Simplification List

(14)

Unit 1

Lesson 1

Outlining the Motivation for SAP S/4HANA

LESSON OBJECTIVES

After completing this lesson, you will be able to:

● Outline the motivation for SAP S/4HANA

SAP S/4HANA Overview

Figure 1: The Business Landscape is 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 us is not getting simpler, it’s 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)

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

(15)

creating a digital network of virtually everything. And 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.

Figure 2: Advances in Technology

In the last few years, there have been significant advances in technology that application developers can take advantage of in order to build smarter and more powerful applications. Examples include the following:

● Multi-core processors enabling parallelism of tasks

This means more throughput of data and faster processing to give us real-time responses.

● Big memory

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 was a bottleneck as the hungry CPUs demanded more data and the journey from memory to CPU was not optimal. 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

Lesson: Outlining the Motivation for SAP S/4HANA

(16)

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 to everyone to the latest solutions, reducing the costs and simplifying everything.

Figure 3: Time to Rebuild the Business Suite for the Digital World

Since the beginning of enterprise computing, SAP have 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 of a 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 a 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 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, a little 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 – A new wave of advances in hardware architecture brings massive computing power Unit 1: SAP S/4HANA Enterprise Management: Overview

(17)

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.

Figure 4: Core ERP Processes Unchanged

The main ERP processes are, for example, procure to pay, plan to produce, order to cash or request to service are unchanged. What is changing? The way that we access these processes has changed dramatically. In the past , these processes were executed on desktop or laptop. Today, it is important that these solutions can be used on a mobile device using data stored in Cloud solution.

Additionally, new Services and new technologies require new solutions.

Figure 5: Some Facts about SAP S/4HANA

SAP S/4HANA comprises a new code base, and new SAP Fiori UX, and new guided configurations. It is our new generation of the suite.

(18)

These simplified applications are seamlessly integrated to offer one solution for every business problem.

All of these applications offer a modern web-based SAP Fiori User Experience, ready for real cloud consumption.

All 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, in one system reintegrated

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 less process steps: Processing receivables app in SAP GUI vs. SAP Simple Finance: Number of screen changes 8 --> 2 (4x)

Figure 6: SAP HANA – The Great Simplifier

We should recognize the key enabler of SAP S/4HANA from the software side. It is called SAP HANA, and it is 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 identify to optimal design of a database that could exploit the full 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 (BI) reports and applications on top. This meant BI was an early beneficiary of the power of SAP HANA.

Next, SAP began developing SAP HANA-based accelerators, which were deployed as side-car

(19)

were performing 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 Oncolyzer.

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. Ensure 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 vendors’ database. 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.

Figure 7: SAP S/4HANA Suite — Introducing the Next Generation Core and Lines of Business Solutions for the Digital Economy

The next generation core and lines of business solutions includes solutiosn for SAP S/4HANA Finance for SAP S/4HANA HR, SAP S/4HANA Supply Chain & Asset Management, SAP S/ 4HANA Sales, Services, and Marketing, and for SAP S/4HANA Sourcing and Procurement. Thereby solutions from ARIBA, CONCUR successfactors, fieldclass and hybris will be 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.

(20)

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 editions (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 helps businesses around the globe sell more goods, services, and digital content

through every touchpoint, channel, and device Evolution to SAP S/4HANA Enterprise Management

Figure 8: Evolution to SAP S/4HANA Enterprise Management

The evolution starts on SAP R/3 Rel. 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.

(21)

SAP S/4HANA Enterprise Management

Figure 9: SAP S/4HANA Enterprise Management

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 Ariba Portfolio. This is the Ariba Business Network for supplier collaboration and 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) solutions.

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 a combination of both, to provide flexible options to customers.

(22)

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.

SAP S/4HANA Logistics – Key Innovations

Figure 10: SAP S/4HANA Logistics – Key Innovations

Within SAP S/4HANA the following key innovations have been developed:

● In Material Requirements Planning, 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 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

(23)

Key Aspects of SAP S/4HANA

Figure 11: Key Aspects of SAP S/4HANA

Here we highlight the most important aspects of SAP S/4HANA and describe why it is 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.

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, 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.

Bringing OLTP and OLAP Together

(24)

Figure 12: Bringing OLTP and 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).

Online Transaction Processing (OLTP) has been separated from Online Analytical Processing (OLAP). This is due to the database design of OLTP and OLAP. Database models have been either built for OLTP optimization or OLAP optimization, but not both.

However, this has also bought with it complexity, redundancy, and latency. It has 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 data is available in real time at every level of detail.

Data Footprint

Figure 13: Data Footprint

A simplified solution architecture will benefit your IT organization immediately.

(25)

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 to a 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, UIs, which were the interfaces of function modules have died and the batch is now dying in these days.

Data Footprint 2

Figure 14: Data Footprint 2

A reduction from 593 GB to 8,4 GB provides much more than simply storage capacity reduction:

(26)

● 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.

Simplified Applications

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 (FI) document and the Controlling (CO) document. These

documents provide the required views of the finance data from a legal perspective (FI) 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.

(27)

Previous Complexity

Figure 16: Previous Complexity

Another example of application simplification relates to material requirements planning (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.

(28)

Current Simplicity

Figure 17: Current Simplicity

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 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. If a 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.

(29)

Ready-to-Go Integration with Existing Cloud Solutions

Figure 18: Ready-to-Go Integration with Existing Cloud Solutions

SAP S/4HANA can be natively integrated with the existing SAP Cloud solutions, such as Ariba, SAP Concur, SAP Hybris, SAP SuccessFactors, SAP Cloud Analytics, and SAP Cloud for Customer (C4C).

Let us consider an example to help illustrate what this might look like.

A customer 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 like to be able to ask vendors detailed questions about the items. By integrating SAP S/4HANA with Ariba Network, this is possible. SAP provides best practices and tools to rapidly integrate SAP S/4HANA with all SAP Cloud solutions, including SAP Business Networks.

(30)

SAP S/4HANA: Deployment Options

Figure 19: SAP S/4HANA: 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 Unit 1: SAP S/4HANA Enterprise Management: Overview

(31)

Unit 1

Lesson 2

Explaining the SAP S/4HANA Simplification

List

LESSON OBJECTIVES

● Explain the usage of the Simplification List

Content of Simplification List

Figure 20: The Simplification List

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. It is a collection of single simplification items 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)

(32)

Figure 21: Simplification List As a Basis

To accomplish the transition to SAP S/4HANA, the study of the simplification list is a good starting point and guideline. SAP also provides additional 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 FI 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 Management is not available with SAP S/4HANA 1511. 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 agreement. They must then be closed by a final settlement. New agreements can only be

(33)

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 IFRS15, even if an upgrade to SAP S/4HANA is not completed.

Computer-Aided Selling (SD-CAS) is not available within SAP S/4HANA, because it is not the target architecture. It is recommended to use SAP CRM on-premise (side-by-side with SAP S/4HANA) or SAP Cloud for Customer.

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

● Explain the usage of the Simplification List

Lesson: Explaining the SAP S/4HANA Simplification List

(34)

(35)

UNIT 2

New User Experience: SAP Fiori

UX

Lesson 1

Understanding the New User Experience 24 Exercise 1: Adjust the SAP Fiori Launchpad in SAP S/4HANA 39

UNIT OBJECTIVES

● Understand the new user experience

(36)

Unit 2

Lesson 1

Understanding the New User Experience

LESSON OBJECTIVES

● Understand the new user experience

Traditional User Interface

Figure 23: Traditional User Interface

It does not matter how good an application is if the user experience is poor. In the past, user interfaces all suffered from the same problem: They were too complicated. 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:

● A quality assurance worker in the delivery department needs to release a blocked item in

the order.

● A finance person needs to adjust tax assignments. ● A salesperson needs to adjust discounts.

(37)

● A project 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

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 smartphones 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 UI 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, it is important to have a clear understanding of the goals and target groups of each UI technology, in order 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 UI and UX.

Lesson: Understanding the New User Experience

(38)

UI versus UX

Figure 25: UI versus UX

The terms UI and UX represent two different ways of thinking. From a software perspective, UI 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

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,

(39)

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. SAP GUI is still available with the on-premise edition, and can be used alongside SAP Fiori, but we recommend using SAP Fiori to take full advantage of the features of SAP S/4HANA.

User Types

Figure 27: User 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:

● Occasional users

An occasional user makes use of the system occasionally, and therefore needs simple and easy-to-use applications. In many cases single-step transactions are executed.

● Experts

(40)

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 very often uses multiple systems and different UIs.

● Developers

A Developer (or programmer) has detailed process and system know-how, and deals with the adaptation and extension of the existing applications. They look after several

applications with different UIs.

Deployment Types

Figure 28: Deployment Types

The deployment type defines the license model and operational environment. In the On Premise type, the customer buys software and hardware, and operates the combination 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, different 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.

(41)

Next Generation of UI

Figure 29: Next Generation of UI

A key theme of SAP S/4HANA is simplification, and this certainly applies to the user

experience. We use the term user experience , rather than user interface, because we need to

consider the overall experience of the user, rather than just the look of the screen. For example, if you went to a restaurant that was strong on food presentation, but where the service was poor, you would say that the overall experience was not good, and you would not be keen to repeat it.

It is important to provide not only a great-looking UI, 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 user experience, 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.

(42)

Target: Unified UX Direction for all SAP Software

Figure 30: Target: Unified UX Direction for all SAP Software

The long-term goal of the SAP UX strategy is to offer SAP Fiori (as the unified UI) to all business and all analytic applications on SAP HANA.

Types of Fiori Applications

Figure 31: Types of SAP Fiori Application Details

SAP Fiori applications can be classified into different types. Examples include the following:

● Transactional

These follow an optimal design for fast transaction processing, such as purchase receipt entry.

(43)

● 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.

Figure 32: Types of SAP Fiori Application

Here are the three most common types of SAP Fiori App:

● Transactional apps use ABAP to provide the classic approach for functions of a business

system. They are available for S/4HANA and Business Suite on any DB.

● Analytical apps use the analytical capabilities of SAP HANA to provide insights in business

data. They are available for S/4HANA and Business Suite on HANA.

● Fact Sheet apps use the enterprise search capabilities of SAP HANA to provide search

results. They are available for S/4HANA and Business Suite on HANA.

(44)

SAP Fiori Architecture

Figure 33: SAP Fiori Architecture

For the technical audience who would like to know about what goes on under the hood with a SAP Fiori application, the following is a quick view of the underlying SAP Fiori architecture. One of the key technical principles is to de-couple the interface logic from the back-end application logic. This means that, technically, SAP Fiori can be used by any back-end application, as it uses industry-standard methods of connecting the applications to the interface. In this case, the back end is an ABAP-based application (SAP S/4HANA).

Front-end components identify the calling device (phone, tablet, and so on), so that you know which native template to use to present the application optimally to the device. The front end also identifies the type of foundation for the application, for example, whether the call comes from Launchpad, an SAP Fiori application, or Personas. (We will discuss Personas later.) For applications that access the back end via OData services, the SAP Gateway server is used. Otherwise, HTTPS is used directly with the back end.

The Gateway component can be installed on the AS ABAP back-end server, but for production purposes we do not recommend this. The Gateway should be deployed on its own ABAP server. Otherwise, performance conflicts could arise. The database for the front-end server can be SAP HANA, SAP ASE, or SAP MaxDB. The back-end server database is always SAP HANA.

The data can be exposed to the ABAP S/4HANA application directly from SAP HANA tables, but it is more likely to be exposed through CDS views. CDS views provide a business-ready view of the data, ready for consumption, and is a new approach to reusable data entities. The CDS views sit on top of the database tables.

(45)

Note:

For more detailed information on SAP Fiori technology, follow the training courses with the code SAPX__ (SAPUI5) and GW100 (SAP Gateway).

SAP Fiori Application Examples

Figure 34: SAP Fiori Application Example: Monitor Material Coverage

A SAP Fiori application called Monitor Material Coverage supports the user in both getting an overview of stock availability (or material coverage) and directly navigating to the current material’s stock or requirements situation.

(46)

Figure 35: SAP Fiori Application Example: Sales Order Fulfillment Issues

An SAP Fiori application called Sales Order Fulfillment Issues supports the user in both seeing an overview of the issues in sales orders and navigating directly to the documents, to solve the issues.

Search

Figure 36: Search

SAP HANA Search is available via Launchpad at any time. You can avail of the following functions:

(47)

● Search the result list across all business objects ● Specify result list per document type

● Navigate to related objects, showing an object page of the document

● Navigate to related transactional applications to start maintaining the business object

With SAP S/4HANA, a global search across all applications, business documents and master data is provided. By providing a search term on the top of the screen, the system starts a google-like search across various entities.

The search result list is structured along categories like business documents (for example, purchase orders) or master data (for example, suppliers). The search term is highlighted in yellow. Depending on type of search result, either the related object page is started, or the transactional SAP Fiori application. To facilitate providing correct search results, a preview of data related to the search result is provided.

SAP Fiori Launchpad

Figure 37: SAP Fiori Launchpad

The SAP Fiori Launchpad is a role-based, personalized UI client that enables users to access SAP Fiori applications side by side with established UIs. The Launchpad is based on SAPUI5, and can be used on multiple devices to leverage the responsive design paradigm. It can be deployed on multiple platforms: SAP NetWeaver Application Server (ABAP Stack), SAP Enterprise Portal, and SAP HANA Cloud Platform. The SAP Fiori Launchpad comes with predefined content to streamline implementation processes.

The SAP Fiori Launchpad is aligned with the two main UI clients: SAP Enterprise Portal (available) and SAP NetWeaver Business Client (planned). Alignment with the SAP Enterprise Portal is achieved by running the SAP Fiori Launchpad UX within the SAP Enterprise Portal (also known as the SAP Fiori framework page), while also leveraging established portal infrastructure and best practices.

Note:

Alignment of SAP NetWeaver Business Client for Desktop (NWBC) with SAP Fiori Launchpad design is planned for future releases.

(48)

The SAP Fiori Launchpad can be visually adapted and customized using the UI Theme Designer. It is designed according to the simple and intuitive SAP Fiori user experience, while supporting established UI technologies (such as Web Dynpro ABAP and SAP GUI for HTML).

Role Concept

Figure 38: Role Concept

The assigned user roles control which applications are available. The applications are available for a user depending on the roles that have been assigned to that user.

SAP S/4HANA Sales Business Roles with SAP Best Practices - Examples

Figure 39: SAP S/4HANA Sales Business Roles with SAP Best Practices - Examples

SAP has created some tailored user roles within the SAP Best Practices for SAP S/4HANA. These roles include the relevant applications to fulfil the main tasks of the respective role, for example: maintain master data, and create documents within a certain process. Examples of SAP S/4HANA sales business roles with SAP best practice include the following:

● Internal Sales Representative ● Billing clerk

(49)

● Pricing Specialist ● Shipping Specialist ● Sales Manager

(50)

(51)

Unit 2

Exercise 1

Adjust the SAP Fiori Launchpad in SAP S/

4HANA

Business Example

You are new to use SAP S/4HANA and the new UX. You need to know what kind of

applications (SAP Fiori Apps) are available and how you can add them to your Launchpad. To do this, you must be able to find the application in the catalog and add the application to the Launchpad. First you want to see whether an application is available, therefore you check the SAP Fiori Apps Library. Once you know that the application is available, you would like to include the application in your Launchpad

Find the Manage G/L Account Master Data Tile in the Catalog

1. You want to know whether the Manage G/L Account Master Data application is available and included in your catalog assigned. Therefore, you use the SAP Fiori Apps Library to

identify the catalog where the application is available. What is the name of the Assigned Business Catalog?

2. Check whether that application is included in your Training for TS410 (ZTRAINING_TS410) catalog as well. In the Gateway system (T4N), open the catalog that you are assigned.

Check the original business catalog identified and the corresponding Tile. With a Where used function, you can see whether the tile is assigned to your catalog.

Add the tile Manage G/L Account Master Data to your Launchpad

1. From the Easy Access Menu in the Gateway System, open the SAP Fiori Launchpad and

include the Manage G/L Account Master Data applications in the SAP Fiori Launchpad.

(52)

Unit 2

Solution 1

Adjust the SAP Fiori Launchpad in SAP S/

4HANA

Business Example

You are new to use SAP S/4HANA and the new UX. You need to know what kind of

applications (SAP Fiori Apps) are available and how you can add them to your Launchpad. To do this, you must be able to find the application in the catalog and add the application to the Launchpad. First you want to see whether an application is available, therefore you check the SAP Fiori Apps Library. Once you know that the application is available, you would like to include the application in your Launchpad

Find the Manage G/L Account Master Data Tile in the Catalog

1. You want to know whether the Manage G/L Account Master Data application is available and included in your catalog assigned. Therefore, you use the SAP Fiori Apps Library to

identify the catalog where the application is available.

a) Open an internet browser and go to the Web page https:// fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#

b) In Categories , choose Apps .

c) To search for the Manage G/L Account Master Data application, in the Search by App Name field, enter Manage G/L Account Master Data.

d) Choose the second entry.

e) Click the Implementation information.

What is the name of the Assigned Business Catalog?

The name of the catalog is: SAP_TC_FIN_ACC_COMMON

2. Check whether that application is included in your Training for TS410 (ZTRAINING_TS410) catalog as well. In the Gateway system (T4N), open the catalog that you are assigned.

Check the original business catalog identified and the corresponding Tile. With a Where used function, you can see whether the tile is assigned to your catalog.

a) In the SAP Easy Access Menu of the Gateway System, open the Training for TS410 catalog and double-click the entry Training for TS410 .

b) To search for the catalog identified in Step 1, in the Search for Catalog field, enter the name of the catalog, SAP_TC_FIN_ACC_COMMON.

c) When you find the catalog, look for the tiles included and see whether the Manage G/L account Master Data tile is available. Click the first icon tiles on the header and search

(53)

for the tile Manage G/L account Master Data . When you have found the tile, go back to the catalog search.

d) To check if this tile is included in the ZTRAINING_TS410 training catalog, in the Search for Catalog field, enter ZTRAINING_TS410. Click the first icon tiles on the header and

search for the Manage G/L account Master Data tile.

e) Leave the maintenance of the catalog.

Add the tile Manage G/L Account Master Data to your Launchpad

1. From the Easy Access Menu in the Gateway System, open the SAP Fiori Launchpad and

include the Manage G/L Account Master Data applications in the SAP Fiori Launchpad.

a) Open the SAP Fiori Launchpad.

b) Go to Group for TS410 and include the Manage G/L Account Master Data application.

c) In the Launchpad, scroll down to Group TS410 and choose the Personalize Homepage icon.

d) To add a new tile, scroll down to the end of group TS410 and choose the + entry.

e) In the All catalogs field, select the Training for TS410 catalog.

f) Search for the Manage G/L Account Master Data tile Manage G/L account Master Data and click Add tile to group TS410 .

g) Go Back and exit Action mode .

The new tile should be available now in the Group as the last tile.

(54)

● Understand the new user experience Unit 2: New User Experience: SAP Fiori UX

(55)

UNIT 3

SAP S/4HANA Basics

Lesson 1

Explain the Organizational Structures 44 Exercise 2: Display the Organizational Structures 45

Lesson 2

Understanding the Concept of Master Data 49 Exercise 3: Display a Material Master Record 51 Exercise 4: Display a Customer Master Record 55

UNIT OBJECTIVES

● Explain the organizational structures ● Understand the concept of master data

(56)

Unit 3

Lesson 1

Explain the Organizational Structures

LESSON OBJECTIVES

● Explain the organizational structures

(57)

Unit 3

Exercise 2

Display the Organizational Structures

Business Example

You want to gain an overview about the enterprise structures in Sales and Distribution, Logistics, and Finance. Therefore, you need to log on to the back-end system and check configuration.

Note that, in this exercise, when the values include ##, replace ## with the number your instructor assigned to you.

1. Log on to the back-end system with your user, navigate to the Definition of Enterprise

Structure.

2. What is the address of company code 1010?

Address:_________________________________

3. What is the valuation level?

Valuation Level:_________________________________

4. What is the key for Plant 1 DE?

Plant:_________________________________

5. What is the first key for the Sales Organization Dom. Sales Org DE?

Sales organization: _________________________________

6. Which plants are assigned to company code 1010?

Plants: _________________________________

7. Which sales organization is assigned to company code 1010?

Sales Organization: _________________________________

(58)

Unit 3

Solution 2

Display the Organizational Structures

Business Example

You want to gain an overview about the enterprise structures in Sales and Distribution, Logistics, and Finance. Therefore, you need to log on to the back-end system and check configuration.

Note that, in this exercise, when the values include ##, replace ## with the number your instructor assigned to you.

1. Log on to the back-end system with your user, navigate to the Definition of Enterprise

Structure.

a) Log on to the back-end system with your user.

b) On the SAP Easy Access Menu, choose Tools → Customizing → IMG → Execute Project . Alternatively, use transaction code SPRO.

c) On the Customizing Execute Project initial screen, choose the SAP Reference IMG icon (F5).

d) Open the entry Enterprise structure → Definition .

You see the Definition of the enterprise Structures in various areas.

2. What is the address of company code 1010?

Address:_________________________________

a) In the Financial accounting menu area, choose Edit, Copy, Delete, Check Company Code .

b) Choose Edit Company Code Data .

c) Double-click 1010 and choose the Address icon.

The address is Dietmar Hopp Allee 16, 69190 Walldorf.

d) Go back to Display IMG. 3. What is the valuation level?

Valuation Level:_________________________________

a) In the Logistics General menu area, choose Define valuation level . The Valuation area is plant.

b) Go back to Display IMG. 4. What is the key for Plant 1 DE?

Plant:_________________________________

(59)

b) Choose Define Plant.

The key for Plant 1 DE is 1010.

c) Go back to Display IMG.

5. What is the first key for the Sales Organization Dom. Sales Org DE?

Sales organization: _________________________________

a) In the Sales and Distribution menu area, choose Define, copy, delete, Sales Organization .

b) Choose Define Sales Organization .

The first key for Sales Organization Dom. Sales Org DE is 1010.

6. Which plants are assigned to company code 1010?

Plants: _________________________________

a) In the Assignments menu area, choose Logistics General. .

b) Choose Assign plant to company code .

The plants 1010 and 1020 are assigned to company code 1010.

7. Which sales organization is assigned to company code 1010?

Sales Organization: _________________________________

a) In the Assignments menu area, choose Sales and Distribution .

b) Choose Assign Sales Organization to company code . The Sales Organization 1010 is assigned to company code 1010.

Lesson: Explain the Organizational Structures

(60)

● Explain the organizational structures Unit 3: SAP S/4HANA Basics

4. TS410_1610_S4HANA_Certification.pdf

Integrated Business Processes in

SAP S/4HANA

.

PARTICIPANT HANDBOOK

SAP Copyrights and Trademarks

Typographic Conventions

Contents

Course Overview

UNIT 1

SAP S/4HANA Enterprise

Management: Overview

Lesson 1

Lesson 2

Unit 1

Lesson 1

Outlining the Motivation for SAP S/4HANA

SAP S/4HANA Overview

Unit 1

Lesson 2

Explaining the SAP S/4HANA Simplification

List

Content of Simplification List

UNIT 2

New User Experience: SAP Fiori

UX

Lesson 1

Unit 2

Lesson 1

Understanding the New User Experience

Traditional User Interface

Concepts and Influence Factors

UI versus UX

Focus on Function

User Types

Deployment Types

Next Generation of UI

Target: Unified UX Direction for all SAP Software

Types of Fiori Applications

SAP Fiori Architecture

SAP Fiori Application Examples

Search

SAP Fiori Launchpad

Role Concept

SAP S/4HANA Sales Business Roles with SAP Best Practices - Examples

Unit 2

Exercise 1

Adjust the SAP Fiori Launchpad in SAP S/

4HANA

Unit 2

Solution 1

Adjust the SAP Fiori Launchpad in SAP S/

4HANA

UNIT 3

SAP S/4HANA Basics

Lesson 1

Lesson 2

Unit 3

Lesson 1

Explain the Organizational Structures

Unit 3

Exercise 2

Display the Organizational Structures

Unit 3

Solution 2

Display the Organizational Structures