Unit 1: Essential Changes in User Experience: Week 3: UX and Main Impacts On Functional Side - Logistics

Week 3: UX and Main Impacts on Functional Side – Logistics
Unit 1: Essential Changes in User Experience

Essential Changes in User Experience
Why SAP Fiori is part of your system conversion to SAP S/4HANA
People
Business
SAP Fiori
Technology
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Understanding SAP Fiori Design
role-based adaptive simple coherent delightful

Understanding the evolution of the SAP Fiori user experience
SAP CoPilot
SAP Fiori for iOS
2013 2014 2015 2016 2017

Understanding the SAP S/4HANA user experience
Single entry point via the SAP

SAP CoPilot*
Fiori launchpad *optional
Domain-specific information
and actions
Coherent visual look across

Enter details and SAP Fiori and classic apps
explore in depth

SAP Fiori apps for SAP S/4HANA compared with classic apps
1 SAP GUI transaction may be Related features of

decomposed into several SAP Fiori apps n x SAP GUI transactions
may be recomposed into
1 SAP Fiori app
Plus new innovations

may be introduced

Quick wins in SAP S/4HANA user experience – SAP Fiori lighthouse scenarios
SAP Fiori apps that offer a

delightful user experience (UX)
SAP Fiori apps that support

tasks and processes that were
not supported before
SAP Fiori apps that simplify

work and increase the efficiency
of tasks and processes

Understanding classic apps and the SAP Fiori visual theme
SAP GUI with Fiori Visual Theme Web Dynpro ABAP with Fiori Visual Theme

Moving to a Mobile First experience
Contacts
Calendar Tasks
Camera Barcode Push Printing
Barcode
Push
Camera
Offline
Voice Recording
3rd Party
Plug-Ins
GPS
Settings Lifecycle
Security Management
Web Browser SAP Fiori Client SAP Fiori mobile app

Mobile Web / Hybrid / Native
Extending SAP Fiori apps from SAP S/4HANA core to edge
SAP Fiori
SAP Cloud Platform Integration
Customer-
SAP Custom Specific
Cloud Apps and 3rd Party
Agile Data Applications
Marts
SAP API Business Hub

Business Services UX Services Mobile Services ML Services IoT Services
Modern Data
SAP S/4HANA Warehouse SAP Cloud Platform
SAP HANA

Extending SAP Fiori apps within the SAP S/4HANA core
SAP S/4HANA In-App Extensions

Extensibility Concept
Custom
Side-by-Side Extensibility Based on User Interface
SAP Cloud Platform
Custom
SAP S/4HANA SAP Analytics / Reports UI
Extensions
Cloud S/4HANA Custom
In-App
Forms
In-app Extensibility with Key User Tools Custom Application
Fields
Custom
SAP S/4HANA SAP Business Objects Database
Cloud S/4HANA
Custom
Business Logic
Custom Code Development and SAP S/4HANA
Extensions Custom
CDS Views
SAP Extensibility Lifecycle
S/4HANA Extensibility Cockpit
Inventory Management
Extending classic apps within SAP S/4HANA

Adapting the SAP Fiori launchpad to your business role
Human
Finance Resources CRM Procurement
Roles End-to-end process

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2018 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.
The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP 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 platforms, 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, and they
should not be relied upon in making purchasing decisions.
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. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Unit 2: Simplification List and Essential Changes
in MRP
Simplification List and Essential Changes in MRP
Functional activities
Preparation phase Realization phase
Application-
System Maintenance Pre- Custom code Software Update
specific follow-up
requirements planner checks preparation Manager (SUM)
activities
Unicode conversion Database migration
Cross-application & application-specific preparation Software update Functional
activities Data conversion Activities
CVI conversion/ post-processing
Functional Activities Consistency checks of transactional
data before FI migration
CVI synchronization
Migration of FI Customizing and data
Solving pre-check errors Material number field extension
Check pre-check warnings Module-specific follow-up activities
Consistency checks of transactional Test the solution
data & totals
Preparation of financial data Bring your Functional team!
Material number field extension It is not only a technical migration
Simplification List – Overview
Simplification List
SAP Business Suite SAP S/4HANA
Area Streamlined Accelerated Optimized Enhanced
Master Sales and
CRM Simplification Item Procure to Plan to Order to Request to
Data Distribution
Simplification Item Pay Product Cash Service
Simplification Item
Procure-
MM / SRM Logistics
ment Area 5 Solutions + 3 Solutions + 3 Solutions + 4 Solutions +
Simplification Item Core Core
Finance HCM Simplification Item Human Finance
Simplification Item Resources
Area
Basic Topics Cross-Topics + +
Simplification Item 2 Solutions 2 Solutions
Basic Information Description Edition / Release Category

Impact Description Recommendation Custom Code
Related Services Customer Effort Service Offering
Simplification List – Documentation
SAP S/4HANA Help Simplification Item Catalog

Industry to core
Examples:
Industry Add-On 1
Industry Add-On 2
Industry Add-On 3
LoB Add-On A
LoB Add-On Z
Automotive
ONE physical shipment
Retail
Industry 01 Industry 02 LoB A Mill Products
ERP
Oil & Gas
SAP S/4HANA
Consumer Products

Industry to core
Examples:
Automotive
ONE physical shipment
Retail
Industry 01 Industry 02 LoB A Mill Products
Oil & Gas

SAP S/4HANA
Consumer Products

MRP in SAP S/4HANA – Overview
Main impacts in
SAP S/4HANA MRP:
▪ Storage location
▪ MRP area
▪ Simplified sourcing
▪ Production version

Simplification List and Essential Changes in MRP Refer to SAP Note 2268045
MRP in SAP S/4HANA – Storage location MRP
SAP S/4HANA MRP only plans on plant and

MRP area level:
▪ Planning on storage location level is no longer
supported
▪ The MRP area logic is more advanced than the logic
for planning on storage location level
▪ All MRP types and lot-sizing procedures are possible
on MRP area level

MRP in SAP S/4HANA – MRP area
In SAP ERP you have to activate the MRP areas in

Customizing for MRP (transaction OM01).
For S/4HANA systems, MRP area is active by

default and cannot be deactivated.
Basically, there are three types of MRP area in

SAP S/4HANA:
▪ Plant MRP area
▪ MRP areas for storage locations
▪ MRP areas for vendor

MRP in SAP S/4HANA – Simplified sourcing
The basic idea of this simplification is a reduced If sourcing determines several valid sources of
set of possible sources of supply. supply, it will prefer:
▪ Production versions over delivery schedules
SAP S/4HANA supports the following types
▪ Delivery schedules over purchasing contracts
of sources of supply:
▪ Purchasing contracts over purchasing info records
▪ Sourcing for purchasing
▪ Sourcing for manufacturing
SAP S/4HANA

MRP in SAP S/4HANA – Production version
SAP ERP 6.0 SAP S/4HANA

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Essential Changes in Output Management
and Material Field Length
Essential Changes in Output Management and Material Field Length
SAP S/4HANA Output Management– Overview
The SAP S/4HANA Output Management:

▪ Coexists with other frameworks
▪ Is Optional in SAP S/4HANA on-premise
For SAP S/4HANA on-premise, the old output

management (NAST) is still available

SAP S/4HANA Output Management – Key benefits
▪ Extensibility (broad usage of CDS views)

▪ BRFplus (flexible and powerful output parameter determination)
▪ PDF-based print forms with fragments (separation of layout and content)
▪ SAP Fiori (full integration with SAP Fiori apps)
▪ State-of-the-art email support (flexible configuration, multiple recipients, email templates)
▪ Unified solution across the product (SD, MM, FIN, …)

SAP S/4HANA Output Management – Considerations for your business application
The recommendation is to establish a coexistence of old and

new output management. This means:
Define the objects that will use SAP S/4HANA Output

Management
▪ For existing customers who are using the old output management
▪ For new customers
System settings:
▪ Enabled objects → Set the system following SAP Note 2228611
▪ Non-enabled objects → Set the old output management solution

Material field length extension – Overview
SAP Leonardo
Interfaces with SAP products
BW extractors
Interfaces with legacy systems
▪ The appropriate related SAP development

entities have been adapted accordingly
▪ Therefore any custom code with reference to
the domain MATNR is affected by this change Domain, structures, table types,
and transparent tables
▪ By default, extended material number
functionality is NOT switched on Internal interfaces
Custom code

Material field length extension – Technical implementation
The complete data flow in the system has

been analyzed:
▪ Usage of material numbers in other fields,
e.g. characteristics, are also extended
▪ These kinds of analyses also need to be done
in customer or partner coding
Refer to SAP Note 2267140

Material field length extension – Internal interfaces
The same principle has been applied to

parameters of all interfaces that are usually
called only within one system:
▪ The material number has simply been extended
to 40 characters by NOT changing the referenced
data element or domain
▪ Local function modules, class methods, BADIs
etc.

Material field length extension – Storage on the database
No changes in how material number is stored

in the database field compared to SAP
Business Suite
▪ With standard Customizing, pure numeric
material numbers are still restricted to 18
characters
▪ Data conversion will be needed for
concatenated content

Material field length extension – External released interfaces
External interfaces used for integration have to

be compatible with old versions of the
interface:
▪ Examples: BAPI, RFC, and IDoc
▪ The already existing field keeps its original length
▪ For transmitting the 40 character material number,
a new field has been added at the end of the
structure (or as new parameter)

Material field length extension – Activation in Customizing
To make the material field length extension as

non-disruptive as possible for SAP S/4HANA
customers:
▪ The extended material number functionality must be
switched on explicitly
▪ Only after this decision is it possible to use more
than 18 characters for the material number
▪ Behavior of internal and external interfaces changes

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Essential Changes in Logistics Tables and
SD Pricing
Essential Changes in Logistics Tables and SD Pricing
Inventory management – Data model changes
Key Messages:
▪ No aggregates: On-the-fly aggregation of 21 tables eliminated + stock aggregate columns in 8 tables eliminated
inventories
▪ Self-contained: Full transactional access
and most important analytical queries
avoiding JOINs
▪ Compatibility views for full compatibility
with legacy code (customer, industries)
Mixed tables:
MARC Plant Data for Material
MARD Storage Location Data for Material
MCHB Batch Stocks
MKOL Special Stocks from Vendor
MSLB Special Stocks from Vendor
MSKA Sales Order Stock
MSPR Project Stock
MSKU Special Stocks with Customer
Inventory management – Goods movements w/o exclusive locking

SAP S/4HANA supports increased data throughput for high
volume goods movement transactions
Exclusive Lock vs Late Lock

▪ SAP S/4HANA supports Late Lock functionality
▪ Deactivation of the statistical moving average price necessary
▪ Report SAPRCKM_NO_EXCLUSIVELY_LOCKING is used to
deactivate the statistical moving average price
Exclusive locking is still required

▪ if material master data is created or changed by a goods movement
▪ for material with moving average price
Temporary inconsistencies due to rounding differences may occur.

Inventory management – Benefits of new data model
Key Benefits:
▪ Simplified inventory management data model (fewer tables >> simplified solution)
▪ High-volume backflush enablement with parallel posting possibilities
▪ Actual stock quantity data will be calculated on-the-fly >> fewer aggregates
▪ Simple and fast reporting capability because most information is in one place: MATDOC >> fewer joins and
less data gathering required
MATERIAL VALUES SAP S/4HANA MATERIAL QUANTITIES

Inventory management – Obsolete transactions
Refer SAP Note 2210569

The following transaction codes are no longer available in SAP S/4HANA:
▪ MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31,
MBNL, MBRL, MBSF, MBSL, MBST, MBSU, and MBBM
These have been replaced by:

▪ The single-screen generalized transaction MIGO or
▪ The BAPIs BAPI_GOODSMVT_CREATE and
BAPI_GOODSMVT_CANCEL
Alternatively, the SAP Fiori Stock Overview app can

be used.
Transaction MMBE_OLD has been replaced by

transaction MMBE.

Data model changes in SD Pricing

Sales and Distribution (SD) Pricing data model has
been redesigned, but the changes have no impact
on the business processes
Pricing condition table KONV has been replaced

with a new table PRCD_ELEMENTS, and a few
fields from KONV are no longer available
▪ However, KONV is still used for data declaration
purposes and to define the structure of the pricing result
▪ During system conversion, automatic data migration
from KONV to PRCD_ELEMENTS takes place
The concatenated variable key field VAKEY was

removed from all condition header tables
▪ Several data elements have been introduced or
extended
Data model changes in SD Pricing – Benefits

Key Benefits:
▪ Pricing result can now be directly accessed for analytical purposes
▪ Enhanced field lengths for several fields allow more flexibility in pricing and condition technique
▪ The number of possible customer condition tables for pricing has been roughly doubled
▪ The number of possible accesses in an access sequence has been enhanced from 99 to 999
▪ The removal of redundant fields from condition header tables reduces the memory footprint of condition
records
SAP S/4HANA

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Essential Changes in Foreign Trade
Essential Changes in Foreign Trade
SAP ERP Foreign Trade is being replaced in SAP S/4HANA
Foreign trade functionality not been carried

forward natively in SAP S/4HANA
The foreign trade functionality of SAP ERP

included:
▪ Intrastat
▪ Preference handling
▪ Documentary payment (e.g. letter of credit)
▪ Export compliance
Options to enable needed functionality in an

SAP S/4HANA environment:
1. SAP S/4HANA for international trade
2. SAP Global Trade Services

SAP S/4HANA for international trade and SAP GTS
SAP S/4HANA
▪ One of the selected options for delivering ▪ Fully available in a side-by-side scenario
foreign-trade functionality ▪ Functions available with pre-built integration
▪ Different scope and different delivery cycles in ▪ Independent scope and delivery cycles
cloud and on-premise editions
▪ New SAP Fiori apps for an improved user
experience

SAP S/4HANA for international trade on-premise – Overview and roadmap
SAP S/4HANA for international trade on-premise includes:

▪ Intrastat for 26 countries
▪ Classification and reclassification of commodity codes
▪ Integration to SAP GTS
Innovations:
▪ Export legal control – Manage export licenses
▪ ECCN classification
▪ Embargo
Future direction:
▪ Export management
▪ Partner screening
▪ Preference management
▪ Import management
SAP S/4HANA for international trade – Simplification items of FT fields in Material Master
The fields for Letter of Credit / Legal Control / Export Control / Preference Management
not supported through Material Master component LO-MD-MM.
▪ CAP product list no. (MARC-MOWNR)
▪ CAP prod. group (MARC-MOGRU)
▪ Preference status (MARC-PREFE)
▪ Vendor decl. status (MARC-PRENE)
▪ Exemption certificate (MARC-PRENC)
▪ Exemption cert. no. 9 (MARC-PRENO)
▪ Iss.date of ex.cert. (MARC-PREND)
▪ Military goods (MARC-ITARK)
Refer to SAP Notes 2267225 and 2204534

SAP S/4HANA for international trade – Simplification items of FT in O2C & P2P
Check whether third-party foreign trade systems are in use for

foreign trade processes.
Transactions not available in SAP S/4HANA

(examples – for complete list check simplification list)
▪ VX99 FT/Customs: General overview
▪ EN99 General Foreign Trade Processing
To migrate financial documents in Foreign Trade to Trade

Finance, you carry out the migration steps available as
Customizing activities.
Analysis of all foreign trade processes that are currently in use.

Key recommendations for adopting SAP S/4HANA for international trade
▪ Report /SAPSLL/XPRA_1610_MARC_STAWN is
executed automatically. Migration is executed on
cross-client level.
▪ Pre-check report can be executed to check
inconsistent data. Note – only consistent data can
be taken over to SAP S/4HANA.
Migrate from: Migrate to:

▪ T604 ▪ /SAPSLL/TDNOS
▪ T604T ▪ /SAPSLL/TDNOST
▪ /SAPSLL/TUNOS
▪ /SAPSLL/DNOSCT
▪ /SAPSLL/DNOSCTT
▪ /SAPSLL/NOSCA
▪ /SAPSLL/CLSNR
▪ /SAPSLL/CLSNRT
▪ MARC ▪ /SAPSLL/MARITC
Key recommendations for adopting SAP S/4HANA for international trade
Software component SD-FT: Pre-Transition Checks messages:

1. The functionality – Legal Control service – is active/used.
This functionality is not available in SAP S/4HANA. See Note
2213485.
2. The functionality – Letter of Credit – is active/used.
2213485.
3. The functionality – Preference Management – is active/used.
2213485.
4. Warning Message: Functionality will be delivered in future
feature pack or release.
5. Error Message: Upgrade to SAP S/4HANA is not possible.
Reason: SAP GTS installed in current business suite system,
but it is not possible to use it as such with SAP S/4HANA.

Summary
Two options to enable Foreign Trade functionality

when transitioning to an SAP S/4HANA
environment:
1. SAP S/4HANA for international trade (on-premise or
cloud edition)
▪ Functionalities are gradually being rolled out
▪ Includes functionality for intrastat
▪ Innovations include export control and embargo
▪ Future directions include additional topics
2. SAP Global Trade Services (on-premise)
▪ Will continue to deliver ongoing innovation
▪ SAP’s most comprehensive global trade
management solution

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Essential Changes in Settlement
Management
Essential Changes in Settlement Management
Technology limitations of the former solution: sales and purchase rebates
BUSINESS VOLUME
Constant updating of aggregates, statistics, and other forms of redundant
data structures; no external data sources possible
Inflexible business volume determinations
BUSINESS PROCESSES
Complex and inflexible
Limited but complex subsequent settlement scenarios with only fix technology hinders
account assignments
subsequent innovative
settlement scenarios
Inflexible and limited processes and business growth
INTEGRATION AND FUNCTIONS

Limitations in pricing, no manual statement, no APIs, no ‘exclusive’
functions and other missing functions
Legacy functions for key processes

Settlement process – Completely new and replacing rebates management
CUSTOMIZATION
Split Criteria on Header and Item Level | Condition and Scale Base
Business Volume Table | Transfer Rules for Document Creation
Settlement Calendar Detail Statement

Settlement Information
SETTLEMENT PROGRAM
CONDITION SETTLEMENT
Business Volume Determination | Calculation via Pricing
CONTRACT DOCUMENTS
Settlement Document Creation
Business Volume Document Collection

Selection Criteria | Output | FI/CO
Condition Records Messaging
DATA SOURCE
Sales Orders | Purchase Orders | Deliveries | Invoices | Goods Movements

Settlement Management Documents | External Systems | POS Data

Condition contract settlement – Architecture and key capabilities
CONDITION CONTRACT SETTLEMENT

SAP HANA
FLEXIBLE AND ADJUSTABLE PROCESSES
Rich in pricing functions | Flexible contract entry | Accessible via launchpad MULTICORE/
Flexible business process definition in Customizing | Definable business volume selection criteria PARALLELIZATION
No adjustments of procure-to-pay and order-to-cash processes necessary
Standalone solution | GLD (moving average price) adjustments and posting of accruals supported
IN-MEMORY ACID
OPEN ARCHITECTURE COLUMNAR
Flexible business volume sources | Document and item split | No aggregates, statistics, or indices
Detailed settlement statement available | Calculation on SAP HANA
ADVANCED
IN-MEMORY INTEGRATION
BUSINESS
BUSINESS VOLUME AND FUNCTIONS
PROCESSES

Condition contract settlement – Set up business configuration
Configuration of condition contract settlement comprises

three main steps:
▪ Configure condition contract conditions:
– Define pricing conditions relevant for settlement calculation.
▪ Configure condition contract maintenance:

– Define and configure parameters for condition contract types.
▪ Configure condition contract settlement process:

– Define and configure parameters for condition contract
settlement process.
Refer SAP Note 2481672

SAP Fiori launchpad

Maintain condition contracts – Key features
▪ Flexible definition of
business volume base and
selection criteria
▪ Intuitive data entry of
settlement information
▪ Possibility to define accrual
conditions independently
from settlement conditions
▪ Calendar-based settlement
with multiple settlement
types
▪ Simulation of settlement run
▪ Detailed settlement overview

Condition contract settlement – Useful apps







Condition contract settlement – 5 functional benefits
Condition Contract Settlement (CCS) by Settlement Management
1 Already available in SAP Business Suite (EHP 7)  be ready for SAP S/4HANA!
2 No additional license fees and fully integrated to logistic and financial processes
3 Condition contracts used for standard maintenance of condition records
4 Delivered within SAP S/4HANA with preconfigured Customizing
5 MORE capabilities to map various subsequent settlement scenarios

Condition contract settlement – 5 key takeaways
Condition Contract Settlement (CCS) by Settlement Management
–1 THE solution for subsequent settlement scenarios in SAP S/4HANA and SAP S/4HANA Cloud
–2 Designed for high performance
–3 Model new and innovative subsequent settlement scenarios
–4 Flexible and state-of-the-art
–5 Architected to benefit from SAP HANA

Move towards SAP S/4HANA using rebates with a system conversion – Useful information
Refer to the following SAP Notes for your System Conversion using rebates:
▪ SD Rebate: simplifications in S/4HANA – SAP Note 2200691
– Table VBOX Deleted
– Business Functions always on
▪ Deprecation of SD Rebate Processing – SAP Note 2226380 and 2267377
– Transactions no longer available
– Usage of existing agreements
▪ Subsequent Settlement Vendor Rebate Agreements – SAP Note 2267415
– Transactions no longer available
– Usage of existing agreements
▪ Optimization of SD Rebate Processing for TPM Customers - SAP Note 2267344
– Exception for CRM TPM business scenarios
– Redundant index data removal
SAP service for accelerated implementation of condition contract-based settlement
Business Needs Service No.:

▪ Support all types of settlement processes (order-to-cash cycle/procure-to-pay 50132913
scenarios)
Duration:
▪ Model new and innovative settlement scenarios 10 Days
▪ Future-proof processes
Delivery Approach and Scope
▪ Program to migrate MM/SD agreements to condition contracts
▪ Concept workshop: data requirements and solution
▪ Pre-configured Customizing
▪ Knowledge transfer session
Value and Benefits
▪ Support all document types in ERP
▪ No restriction or limitations to current business processes
▪ Improved user experience and data quality
Thank you.
open@sap.com
Follow all of SAP

warranty.

Unit 1: Essential Changes in User Experience: Week 3: UX and Main Impacts On Functional Side - Logistics

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 1: Essential Changes in User Experience: Week 3: UX and Main Impacts On Functional Side - Logistics

Uploaded by

Copyright:

Available Formats

Week 3: UX and Main Impacts on Functional Side – Logistics

Unit 1: Essential Changes in User Experience

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

role-based adaptive simple coherent delightful

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

SAP Fiori for iOS

2013 2014 2015 2016 2017

Single entry point via the SAP

Coherent visual look across

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

1 SAP GUI transaction may be Related features of

Plus new innovations

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

SAP Fiori apps that offer a

SAP Fiori apps that support

SAP Fiori apps that simplify

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Web Browser SAP Fiori Client SAP Fiori mobile app

SAP API Business Hub

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

SAP S/4HANA In-App Extensions

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Roles End-to-end process

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

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

Preparation phase Realization phase

Basic Information Description Edition / Release Category

SAP S/4HANA Help Simplification Item Catalog

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Industry 01 Industry 02 LoB A Mill Products

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Industry 01 Industry 02 LoB A Mill Products

Oil & Gas

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

SAP S/4HANA MRP only plans on plant and

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

In SAP ERP you have to activate the MRP areas in

For S/4HANA systems, MRP area is active by

Basically, there are three types of MRP area in

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

SAP ERP 6.0 SAP S/4HANA

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

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

The SAP S/4HANA Output Management:

For SAP S/4HANA on-premise, the old output

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

▪ Extensibility (broad usage of CDS views)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

The recommendation is to establish a coexistence of old and

Define the objects that will use SAP S/4HANA Output

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Interfaces with legacy systems

▪ The appropriate related SAP development

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

The complete data flow in the system has

Refer to SAP Note 2267140

The same principle has been applied to

Refer to SAP Note 2267140

No changes in how material number is stored

Refer to SAP Note 2267140