Recomendados
Mais conteúdo relacionado
Semelhante a Introduction to SAP S/4HANA Sales
Semelhante a Introduction to SAP S/4HANA Sales (20)
Último
Último (20)
Introduction to SAP S/4HANA Sales
- 2. 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
- 3. 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)
- 4. 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
- 5. 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”
- 6. Advantages of SAP HANA DB
- 8. SAP Fiori ® user experience (UX) Role-based user experience for all devices Application and extensions for S/4HANA instant insight-drive application for all lines of business and industries SAP HANA® platform In-memory platform for all data On-premise edition Cloud edition SAP ® S/4HANA Native integration with below solutions Ariba | Concur | Fieldglass | Hybris | SuccessFactors | CPQ Internet of Things Business network Social network People Devices Big Data Advantages of SAP S/4HANA
- 9. 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)
- 10. 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
- 11. 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
- 12. 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
- 13. SAP S/4HANA On Premise SAP S/4HANA On Cloud SAP S/4HANA - On-Premise Vs Cloud Upgrade controlled by customer by using Opt in or Opt out Full capabilities of business functions In comparison to S/4HANA cloud, deployment time is slightly longer Full rage of functionalities and highly scalable Automatic enrollment for upgrades Slim down version of the on-premise solution Faster Deployment than On-Premise Less Scalable than On-Premise, a template- based solution, focusing on a limited number of key processes, with only a reduced set of customization options.
- 14. SAP S/4HANA Implementation scenarios New System Conversion Landscape Transformation SAP ECC System Non-SAP System SAP ECC System SAP ECC System (Region A) SAP ECC System (Region B) SAP ECC System (Region C) On-Premise Cloud On-Premise Cloud On-Premise Cloud
- 15. SAP S/4HANA – Implementation Accelerators S/4HANA Implementation On Premise / On Cloud Best Practices Guided Configuration Methodology Business Value • Faster implementation on premise • Rapid adoption of innovation throughout the product lifecycle • Extensible framework for partners • Faster TIME TO VALUE • Reduced Total Cost of Ownership One agile Implementation methodology Self-Service Configuration Expert Configuration Solution Builder Solution Manager Pre-Built S/4HANA For Model Company on-premise Methodology Tools For a Guided Configuration Best Practices Migration Content Integration Content
- 19. 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
- 20. Why Focus on UI Gain Productivity Increase User Adoption Decrease User Errors Save Training Costs Fiori Apps Characteristics Role Based Responsive Simple Coherent Introduction to Fiori Apps
- 21. SAP Fiori for SAP S/4HANA TODAY Functional–based applicants From : One Transaction for multiple roles Exposing all data & functions to al users From : Multiple entry points for the user and inconsistent user experience ( e.g. ERP vs CRM) SAP Fiori UX To: Decomposed apps for each role Exposing only relevant data and functions To: One entry point for the user and UX Following common design directions Role-based applications Introduction to Fiori Apps
Notas do Editor
- S4H can only be run on Hana database unlike ECC which can be run on Oracle , IBM DB2 etc. Back bone of S4H’s design is with HANA’s in memory capability. In-memory database means that data is read from memory i.e., data always reside in main memory RAM (even though Write happens in hard disk) and hence in-memory database reads data much faster w.r.t traditional databases (fetching the data from hard disk) Hana’s column-based tables provide faster access (as only affected columns need to be read in a query), better compression (due to few distinct values compared to rows), parallel processing (different columns can be easily processed parallelly) There will be no aggregate (total), index and history tables in S4H. Aggregates are created dynamically based on, line-item table instantaneously (on the fly). OLTP and OLAP capability in same system with real time reporting and predictive analysis
- S – Simplified/ Suite, 4 – 4th generation A new product and a next generation of business applications Fully built on 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 Reduces the data footprint of your company by removing the aggregates Choice of Deployments (On Premise, Cloud, Hybrid) Native Integration for Hybrid scenarios from SAP cloud companies like, Ariba , Concur, Field Glass , Hybris & Success factors SAP S/4 Core integrate with other sap products as well like SRM, CRM, HCM and Readymade plug -ins preconfigured in S/4 HANA, it’s like plug in and use like dongle Integration with digital solitons available in the market like IoT, Big Data , AI, ML etc.
- On-Premise we can control release upgrade with help of options Opt in
- Green filed implementation – for instance client running on non sap system , any data base , want to implement s4 hana , in this scenario we will do green field implementation either on On-premise /cloud based client requirement and business operations Brown field /system conversion – For ex. Client using ecc from many year and want use exiting infrastructure , system resource and move on s4 hana , will treat a conversion , will do it on On-premise , SLT- client to consolidate the regional operations into one global SAP system , in this scenario will do SLT on On-Premise/Cloud
- Fiori Apps Characteristics Role Based Responsive Design thinking Coherent – consistent Simple to use Types of Fiori Apps Transactional Apps Analytical Apps Fact Sheets Some of the Apps redesigned by SAP on S/4 Hana platform Some of the apps copy as it is from traditional GUI One entry or Single Sign On So user may not feel inconsistent Fuzzy search