SAP S/4HANA Sales

Agenda

 Introduction to SAP S/4HANA 2022 Sales

 Advantages of SAP S/4HANA

 Major Table changes in SAP S/4HANA Sales

 S/4HANA - On premises Vs Cloud

 Activate Methodology

 Introduction to Fiori Apps

Introduction to SAP S/4HANA
 SAP Business Suite for SAP HANA
 S – Simplified/ Suite, 4 – 4th generation
 A new product and a next generation of business applications
 Fully built on the in-memory platform SAP HANA
 Provides an instant insight by using a single source of truth, real-time
processes, dynamic planning and analysis
 Modern and Simplified User Experience optimized for all devices using SAP
Fiori
 Reduces the data footprint of your company by removing the aggregates
 Choice of Deployments (On Premise, Cloud, Hybrid)
Challenges in Traditional DBs
 Designed to perform well on computers with limited RAM
 Data Storage in HDDs
 Complex Data Model
 Redundancy of Data/ Need of Aggregations
 High Data Footprint
 Row based Data Storage
 Slower Transaction Processing
 Slower Reporting
Advantages of SAP HANA DB
 Designed for In memory computing
 Data is stored in RAM
 Simplified Data Model
 Row + Column based storage
 Removed Redundancy (Removal of Aggregates & Indices)
 Less Data Footprint
 1800* times faster processing

“SAP HANA permits OLTP and OLAP workloads on the common platform by storing
data in high-speed memory, organizing it in columns. This delivers faster query
processing that aggregates data for efficiently”
Advantages of SAP HANA DB
Aggregates eliminated
 Advantages of SAP S/4HANA

SAP ® S/4HANA
SAP Fiori ® user experience (UX)
People Role-based user experience for all devices Internet of Things

Application and extensions for S/4HANA

instant insight-drive application
for all lines of business and industries
Devices Business network
SAP HANA® platform
In-memory platform for all data

Cloud edition On-premise edition

Big Data Social network
Major Table Changes – Sales

 Status Tables VBUK, VBUP are not updated any more

 Status fields have been moved to the corresponding header and item tables -
VBAK and VBAP for sales documents

 Elimination of redundancies – Document Index Tables VAKPA , VAPMA, VLKPA,

VLPMA, VRKPA, VRPMA (Target Architecture)
Major Table Changes – Sales (Pricing)

 Business documents within the SAP Business Suite such as the sales order or
the purchase order used to store the pricing result in the database table
KONV

 The content of KONV is transferred to PRCD_ELEMENTS when moving to SAP

S/4HANA

 The maximum number of possible accesses in an access sequence (DTEL

KOLNR) has been increased from 99 to 999

 Check box is added in V/08 to post statistical condition types to accounting

Material Master Data - changes

Material Master : Material Number Field Length Extension

 SAP S/4HANA, on-premise edition can support a material number with 40

characters
 The appropriate related SAP development entities (domains, structures, table
types, and transparent tables, external and internal interfaces, user
interfaces, and so on) have been adapted accordingly
 Where required, automated logic is in place and executed automatically in
case a customer converts his current SAP Business Suite system into SAP
S/4HANA, on-premise edition
Activation of Extended Material Number

Material Master : Material Number Field Length Extension

 SAP S/4HANA, on-premise edition can support a material
number with 40 characters
 Activation of the Extended Material Number
Functionality
IMG - Cross-Application Components - General Application
Functions - Field length Extension - Activate extended
fields
Note : If the extended material number functionality is
activated in a system, it cannot be easily deactivated as
values may exist in different fields that are only allowed
with extended material number
 SAP S/4HANA - On-Premise Vs Cloud

SAP S/4HANA On Premise SAP S/4HANA On Cloud

Upgrade controlled by customer by using Opt Automatic enrollment for upgrades

in or Opt out
Slim down version of the on-premise solution
Full capabilities of business functions
Faster Deployment than On-Premise
In comparison to S/4HANA cloud,
deployment time is slightly longer Less Scalable than On-Premise, a template-based
solution, focusing on a limited number of key processes,
Full rage of functionalities and highly with only a reduced set of customization options.
scalable
SAP S/4HANA Implementation scenarios

SAP ECC System On-Premise

Non-SAP System Cloud

On-Premise
SAP ECC System
Cloud

SAP ECC System (Region A)

On-Premise
SAP ECC System (Region B)
SAP ECC System (Region C) Cloud
SAP S/4HANA – Implementation Accelerators
Business Value
Best Practices
•Faster implementation on
premise
•Rapid adoption of innovation
S/4HANA
throughout the product
Implementation Guided Configuration
lifecycle
On Premise / On Cloud •Extensible framework for
partners
•Faster TIME TO VALUE
Methodology •Reduced Total Cost of
Ownership

Best Practices Tools Methodology

For a Guided Configuration

Pre-Built
S/4HANA Self-Service Configuration
One agile
For Migration Integration Expert Configuration
Implementation
Model Content Content Solution Builder
methodology
Company Solution Manager
on-premise
Activate Methodology
Activate Methodology
Activate Methodology
Introduction to Fiori Apps
Advantages of Fiori Apps

Users have the best possible experience when interacting with Business Suite

Users can access business critical applications on any device –

Mobile/Tabs/Laptops

Integration with existing IT system landscape

Can be expanded to incorporate specific needs of the business

Types of Fiori Apps

Transactional

Analytical

Factsheets
Introduction to Fiori Apps
Why Focus on UI

Gain Productivity

Increase User Adoption

Decrease User Errors

Save Training Costs

Fiori Apps Characteristics

Role Based

Responsive

Simple

Coherent
 Introduction
SAP to Fiori
Fiori for SAP S/4HANA Apps
TODAY SAP Fiori UX
Functional–based applicants Role-based applications

From : One Transaction for multiple roles To: Decomposed apps for each role
Exposing all data & functions to al users Exposing only relevant data and functions

From : Multiple entry points for the user and inconsistent user To: One entry point for the user and UX
experience ( e.g. ERP vs CRM) Following common design directions
SAP Fiori Launchpad
Fiori Apps Library

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#