S4SD1 - Sales Functions and Innovations.pdf

SAP Copyrights and Trademarks

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced reproduced or transmitted in any form or for any purpose purpose without the express permission of SAP SE or an SAP affiliate company 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. 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. functionality. All forward-looking statements are s ubject to various risks and u ncertainties 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. All rights reserved.

iii

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

iv

User interface control

Example text

Window title

Example text


Contents

vii

Course Overview

1

Unit 1:

2

SAP S/4HANA Enterprise Management - Materials Management and Operations Overview Lesson: SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

11

Unit 2:

12

User Interface and Role Concept Lesson: User Interface and Role Concept

25

Exercise 1: Get Started with SAP S/4HANA and User-Specific Roles

29 37

Exercise 2: Create a User-Specific UI Unit 3:

38

SAP S/4HANA Sales - Simplifications Lesson: Overview

43

Exercise 3: Identify Simplifications in SAP S/4HANA in the Area of Sales

46

Lesson: Business Partner Approach

51

Exercise 4: Create a New Business Partner

57

Lesson: Data Model Simplifications

61

Exercise 5: Check Data Model Simplifications

65

Lesson: Sales Analytics

69

Exercise 6: Analyze Incoming Sales Orders

73

Lesson: Billing Document Output Management

75 83

Exercise 7: Check Business Rules for Output Determination Unit 4:

84

SAP S/4HANA Best Practice - Sale from Stock Lesson: Sale from Stock

91 99 100

Exercise 8: Execute the Sale from Stock Process Unit 5:

SAP Smart Business for Sales Order Fulfillment Lesson: SAP Smart Business for Sales Order Fulfillment

107

Exercise 9: Add a New SAP Smart Business Evaluation to the SAP Fiori Launchpad


v

vi


Course Overview

TARGET AUDIENCE This course is intended for the following audiences: ●

Application Consultant

●

Business Analyst

●

Business Process Architect

●

Business Process Owner/Team Lead/Power User


vii

viii


UNIT 1

SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

Lesson 1 SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

2

UNIT OBJECTIVES ●

Outline the scope of SAP S /4HANA Enterprise Management (Materials Management and Operations)


1

Unit 1 Lesson 1 SAP S/4HANA Enterprise Management Materials Management and Operations Overview

LESSON OBJECTIVES After completing this lesson, you will be able to: ●

Outline the scope of SAP S/4HANA Enterprise Management (Materials Management and Operations)

Scope of SAP S/4HANA Enterprise Management (Materials Management and Operations)

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

The evolution starts with SAP R/3 4.7 which was able to run on any DB and used SAP NetWeaver as a basis. ERP 2004 was followed by SAP ERP 6.0. SAP ERP 6.0 EhP7 was the first s olution which ran on SAP HANA, the starting point of sFin. sFin on the other hand was the first step in the SAP S/4HANA Enterprise Management solution. All these solutions are executed on the SAP HANA database.

2


Lesson: SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

Figure 2: Scope of SAP S/4HANA Enterprise Management (Materials Management and Operations)

The next generation core and lines of business solutions include the following solutions: ●

SAP S/4HANA Finance

●

SAP S/4HANA HR

●

SAP S/4HANA Supply Chain & Asset Management

●

SAP S/4HANA Sales, Services and Marketing

●

SAP S/4HANA Sourcing & Procurement

Thereby solutions from SAP Ariba, Concur, SAP SuccessFactors, SAP Fieldglass, and SAP Hybris will be used. ●

●

●

●

SAP Ariba is the world's business commerce network. It 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 A riba 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 & Expense Web offers a mobile solution 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, S tandard, Concurforce, Professional, and 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 m anagement system to manage contingent workforce and services procurement programs.


3

Unit 1: SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

●

SAP Hybris helps businesses around the globe sell more goods, services and digital content through every touchpoint, channel, and device.

Figure 3: SAP S/4HANA Enterprise Management (Materials Management and Operations)

SAP S/4HANA Enterprise Management (Materials Management and Operations) is comprised of the functionality covered by SAP ERP ECC 6.0x Logistics. It provides major simplifications in the areas of inventory management, material requirements planning, capacity planning, sales and distribution, and procurement. These simplifications can be found in the Simplification List.

Figure 4: Why Go f or SAP S/4HANA Enterprise Management?

The innovations in SAP S/4HANA Enterprise Management are based on four pillars: increased throughput, reporting and analysis, optimized infrastructure, and user experience. ●

4

Increased throughput



Elimination of data redundancies, reduced data footprint by simplifying the data model, and move from batch processing to real-time processing ●

Reporting and analysis Embedded analytics and analytics based on real-time data

●

Optimized infrastructure Reduced number of systems (less distributed data in several systems)

●

User experience New user experience via the SAP Fiori UI and role-based approach

The core SAP ERP processes remain stable; an order-to-cash process has the same structure as before.

Figure 5: Simplified Data Model - Example: Material Document

In SAP ERP there are two document tables for the material document (header MKPF and item MSEG), which contain business transactions and the following delta information: ●

26 tables containing inventory aggregates for two material master tables (MARC and MARD)

●

11 tables for particular stock types

●

13 tables for historic stock figures

The redesign has led to one new document table merging the header and item levels (avoiding joins); this forms the basis for the on-the-fly-aggregation. In addition, we have semantically corrected the material master data table, which supports table buffering on an application server level. Overall, this has resulted in an ultra-thin data layer that cannot be stripped down any further. Further reduction of the tables and functionality would not lead to more simplification but to data loss. Simplification does not cause reduction; simplification provides the features in a simpler manner. Only primary information is left, all secondary (redundant) information is removed.


5

Unit 1: SAP S/4HANA Enterprise Management - Materials Management and Operations Overview

Figure 6: Intuitive User Experience and Responsive Design

SAP Fiori is a technology that offers a state-of-the-art web UI that is based on HTML5 and SAPUI5 and enables the user to personalize the screen. It technically enables everything that we need to provide the right screens for end users. SAP Fiori design principles make it possible to adjust a screen to any front-end device and to adopt it automatically to future design principles, thus maintaining a s tate-of-the-art screen. SAP Fiori enables developers to design and adopt the screen to the needs of the end user for a particular role, putting the user into the center of the business process. With this principle we ensure that the software is not targeting a neutral individual who enters all information into one screen, but that the software is aware of the business context, the tasks, and the specific situation the user is working in, and thus provides all the relevant information that the user needs to perform their tasks.

Figure 7: Highlights of Key Business Innovations

6



The key business innovations with SAP S/4HANA can be divided into three categories: rearchitecting of functions, new user experience and design, and unifying functionality in the core. ●

Re-architecting of functions An example of re-architecting of functions is material requirements planning, which is now real-time and enhanced by a decision support cockpit. Another example is inventory management, where the number of tables was reduced to eliminate aggregates, and locking was optimized for postings to increase the system throughput. Furthermore, inventory valuation is now only posted once, whereas previously it was posted in both the material ledger and accounting tables. This creates a single source of truth for the user.

●

New user experience and design This means that the UIs run on any device - desktop, tablets, smart phones, and even smart watches. For example, the Sales Order Fulfillment Cockpit for sales representatives has been developed for exception-based issue handling.

●

Unifying functionality in the core This means eliminating functional redundancies which have been built into the SAP Business Suite over the years. An example is the material availability check available-to promise (ATP). The ATP functionality will be brought into the SAP S/4HANA core, by combining advanced global ATP functionality from SCM APO and basic ATP functionality from SAP ERP. With a multi-year roadmap, comprehensive ATP capabilities will be enabled in the core.

LESSON SUMMARY You should now be able to: ●

Outline the scope of SAP S /4HANA Enterprise Management (Materials Management and Operations)


7

UNIT 3

SAP S/4HANA Sales Simplifications

Lesson 1 Overview

38 Exercise 3: Identify Simplifications in SAP S/4HANA in the Area of Sales

43

Lesson 2 Business Partner Approach

46

Exercise 4: Create a New Business Partner

51

Lesson 3 Data Model Simplifications

57

Exercise 5: Check Data Model Simplifications

61

Lesson 4 Sales Analytics

65

Exercise 6: Analyze Incoming Sales Orders

69

Lesson 5 Billing Document Output Management

73

Exercise 7: Check Business Rules for Output Determination

75

UNIT OBJECTIVES ●

Understand the basics of the SAP S/4HANA simplifications for sales

●

Describe the business partner approach

●

Describe the data model simplifications

●

Describe sales analytics in SAP S/4HANA

●

Describe the new Output Management for billing documents


37

Unit 3 Lesson 1 Overview



Basics of SAP S/4HANA Simplifications for Sales

Figure 26: SAP S/4HANA Simplifies Many Lines of Business

In SAP S/4HANA, many functions and topics have been simplified for the various lines of business. The most important document used to get an overview of the simplifications is the Simplification List. This list focuses on the items th at must be considered by customers in an implementation or system conversion project from SAP ERP 6.0 to SAP S/4HANA.

38


Lesson: Overview

Figure 27: The Simplification List

With every new release of SAP S/4HANA, the Simplification List is updated with releaserelevant 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 points that must be considered in an implementation or 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)

Figure 28: Transition to SAP S/4HANA: Simplification List as a Basis

When undergoing a transition to SAP S/4HANA, the Simplification List serves as 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 SAP S/ 4HANA. Customers can use these pre-checks to find out what mandatory steps they must carry out before converting to SAP S/4HANA. The pre-check results list the instances that need to be addressed before attempting the conversion process.


39

Unit 3: SAP S/4HANA Sales - Simplifications

●

Custom code analysis is used to support the customer in detecting custom code which needs to be adapted so that it can be moved to SAP S/4HANA, SAP offers custom code analysis tools (as part of SAP NetWeaver 7.50). The customer can ascertain whether their current custom code will be compliant with SAP S/4HANA data structures and s cope.

Figure 29: SAP S/4HANA Sales Solution Simplification: The Principle of One

One goal of simplifications in SAP S/4HANA Sales is to provide only one application for a certain area, instead of multiple applications. In accordance with this goal, the following simplifications have been realized: ●

Foreign Trade Currently there are two software solutions for international trade transactions: SAP ERP SD Foreign Trade (SD-FT) and SAP Gl obal Trade Service (GTS). SAP GTS is an external service that can be installed on an additional instance. The classical Foreign Trade functionality is not available in SAP S/4HANA; SAP GTS should be used instead.

●

Credit Management FI-AR-CR Credit Management is not available in SAP S/4HANA. The functional equivalent in SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR).

●

Rebate Processing 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 and must then be closed by a final settlement. New agreements can only be created based on condition contracts, which are part of Settlement Management.

●

Revenue Recognition SD Revenue Recognition is not available in 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 outlined in the International Financial Reporting Standards (IFRS15) and adapted by local Generally Accepted Accounting Principles (GAAPs). Migration to the new solution is required to comply with IFRS15 even if an upgrade to SAP S/4HANA is not done.

●

Sales Activities Computer-Aided Selling (SD-CAS) is not available in SAP S/4HANA. We recommend that customers use SAP CRM on premise (side-by-side with SAP S/4HANA) or SAP Hybris Cloud for Customer.

40


Lesson: Overview

Figure 30: Other Major Simplifications Relevant for SAP S/4HANA Sales and Distribution

These simplifications are covered in the respective lessons in this unit.


41


42


Unit 3 Exercise 3 Identify Simplifications in SAP S/4HANA in the Area of Sales

Simplifications in SAP S/4HANA 1. How can you get the latest information about SAP S/4HANA and an overview of the simplifications in this environment?

View Detailed Information about the Business Partner Approach 1. You want to check the details of the business partner approach and therefore have a look at the simplification list.

When a SAP Business Suite customer wants to move to SAP S/4HANA, what must be in place?

View Obsolete Transactions in the Area of Foreign Trade You have learned that the functions of the classic foreign trade in SD are not available in SAP S/4HANA. 1. Provide examples of transaction codes that are no longer available.


43

Unit 3 Solution 3 Identify Simplifications in SAP S/4HANA in the Area of Sales

Simplifications in SAP S/4HANA 1. How can you get the latest information about SAP S/4HANA and an overview of the simplifications in this environment?

To view the latest information about SAP S/4HANA, check the SAP Help Portal, help.sap.com/s4hana. Here, you find a complete overview of this solution and can find many helpful documents. View Detailed Information about the Business Partner Approach 1. You want to check the details of the business partner approach and therefore have a look at the simplification list.

When a SAP Business Suite customer wants to move to SAP S/4HANA, what must be in place?

The SAP Business Suite customers must have Customer/Vendor Integration (CVI) in place. View Obsolete Transactions in the Area of Foreign Trade You have learned that the functions of the classic foreign trade in SD are not available in S AP S/4HANA. 1. Provide examples of transaction codes that are no longer available.

a) Check the simplification list to find the details about the changes in the area of foreign trade.

The obsolete transaction codes are listed in the simplification list.

44


Lesson: Overview

LESSON SUMMARY You should now be able to: ●



45

Unit 3 Lesson 2 Business Partner Approach


Describe the business partner approach

Business Partner Approach

Figure 31: Customers and Vendors are Represented as Business Partners

In SAP ERP, customer master data and vendor master data must be maintained separately. This means that if a certain business partner acts as a customer in some processes and as a vendor in other processes, master data for this business partner has to be maintained twice. The (mandatory) target approach in SAP S/4HANA is the Business Partner (BP) approach. By using this approach, it is possible to centrally manage master data for customers and vendors. In SAP S/4HANA, business partner master data can be maintained with the transaction

BP

or

by using a corresponding app from the SAP Fiori launchpad. There is no specific UI for customer/vendor as there is in SAP ERP. Transactions such as XD01, XD02, XD03 or VD01, VD02 , VD03 / XK01, XK02, XK03 or MK01, MK02, MK03 are not available. Calls to these transactions are redirected to the

46

BP

transaction.



Figure 32: The Business Partner Approach in SAP S/4HANA

When a business partner is created, the Business Partner Category must be selected. Business partners can be categorized as a person, group, or organization. A group r epresents a shared living arrangement, a married couple, or an executive board. An organization represents units such as a company, a department of a company, or an association. The business partner category determines which fields are available for data entry. The link between a business partner and other components is achieved by a role concept. A business partner role corresponds to a business context in which a business partner can appear. Possible roles are, for example, customer (relevant for s ales processes), FI customer, or vendor. This ensures that the relevant master data for the various processes can be recorded correspondingly and that the business partner can be used for the relevant functions (such as sold-to party). From a technical perspective, the Customizing object that is used to control customers and vendors in SAP ERP (the account group) still exists in SAP S/4HANA and is still needed for specific tasks, such as controlling partner functions for sales documents. This is why t he connection of the business partner and customer/vendor objects has to be set up in the Customer/Vendor Integration (CVI).


47


Figure 33: Customer/Vendor Integration: Context and Motivation

The CVI component ensures that the customer and vendor master data tables are updated automatically after a business partner is created or changed. As a prerequisite of an SAP ERP-to-SAP S/4HANA conversion project, all customers and vendors in the system have to be converted to business partners. It is recommended, but not mandatory, that the business partner ID and the customer/vendor ID are the same. IDocs or BAPIs for customer/vendor creation that do not call the CVI function CVI_EI_INBOUND_MAIN cannot be used any more.

Figure 34: Customer/Vendor Integration Conversion Steps

To execute the conversion from customers/vendors to business partners, multiple steps are necessary. First a number of pre-checks have to be implemented. Then the business function CA_BP_SOA has to be activated. Then the CVI Customizing has to be checked and any

48



necessary changes have to be triggered. Number ass ignments according to the conversion guide have to be defined. The synchronization cockpit is then used to synchronize the data (data load). The conversion step is part of the system conversion from the SAP E RP system to SAP S/ 4HANA on premise. No additional CVI action is required. Finally the post processing direction business partner > customer/vendor has to be activated.

Figure 35: Impact on Surrounding Systems

There is no impact on custom code. The custom code call to previous transactions does not need to be adapted, as there is an automatic redirection. Any interface for creating or updating customer or vendor master data has to call the CVI function CVI_EI_INBOUND_MAIN.


49


50


Unit 3 Exercise 4 Create a New Business Partner

Create a business partner master r ecord for a new customer. In this exercise, when the values include ##, replace ## with the number that your instructor has assigned to you. Maintain Business Partner Master Data 1.

2.

3.

Create the new business partner and maintain the general data using the following data: Field

Value

Business Partner Categorization

Organization

Business Partner

T-CUS##

Grouping

Ext.alpha-num.numb. (a-z; CUST/SUPL)

Title

Company

Name

Bikes & More ##

Street/House Number

Prinzenring ##

Postal Code/City

70173 Stuttgart

Country

DE (Germany)

Region

BW (Baden-Wurttemberg)

Language

German

Maintain the company code data for the new business partner using the following information: Field

Value

BP Role

FI Customer

Company Code

1010

Reconciliation Account

12100000

Maintain the sales area data using the following data: Field

Value

BP Role

Customer

Sales Organization

1010


51

S4SD1 - Sales Functions and Innovations.pdf

Recommend Documents