Skip to Content

SAP S/4 HANA Simple Logistics- Overview for Consultants New to S4 HANA SLOG/ FINANCE/ FIORI UI-  PART 2.

Weblink for Part-1

https://blogs.sap.com/2017/08/09/sap-s4-hana-simple-logistics-overview-for-consultants-new-to-s4-hana-slog-fiori-ui/

 

************************************************************************************************************************************************************************************************************************************

This is not my own content. I am also new to S/4 HANA SLOG. When i had gone through the S4 HANA Slog info in Google. I got this Reference Guide link it is really more useful. it covers entire details in a S4 HANA Simple Logistics Project. Please refer for Complete Details on “How to Run or Implement S4 HANA Simple Logistics. Hope the blog is useful to new Consultants. This blog is framed for newbies in S4 HANA Simple Logistics and for experts they already know the Concepts.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

************************************************************************************************************************************************************************************************************************************

I hope below Web links are more useful. Please refer for complete Details in SAP S4 HANA Implementation. SAP Provided Complete Information.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

KEY FEATURES OF SAP S/4 HANA FINANCE – 1709 ON-PREMISE PRINCIPALES CARACTERÍSTICAS DE SAP S / 4 HANA FINANCE 1709 ON-PREMISE

Account Determination – FI – MM integration on Fiori App (part-2)

Account Determination FI-GL Integration – FIORI (part-1)

Key Features on S/4 HANA FINANCE

SAP S4HANA Cookbook – What is SAP S4HANA

Implementing SAP S4HANA, on-premise with SAP Activate

SAP S4HANA Cookbook: SAP S4HANA Finance, On-Premise 1605 

https://blogs.sap.com/2016/05/16/s4-hana-and-its-differences-with-ecc/

 

For knowing Functional Module update-  did wonderful job. he shared complete details on module specific info. Great.

SAP PP

#S4HANA 1610 use case series: 9a – Production Planning and Detailed Scheduling – PP/DS (biz view)

#S4HANA 1610 use case series: 9b – Production Planning and Detailed Scheduling – PP/DS (tech view)

https://wiki.scn.sap.com/wiki/display/ERPMan/MRP+on+HANA+FAQ

SAP PLM

#S4HANA 1610 use case series: 8a – Product Lifecycle Management (biz view)

#S4HANA 1610 use case series: 8b – Product Lifecycle Management (tech view)

SAP FI

#S4HANA 1610 use case series: 7a – Finance (biz view)

#S4HANA 1610 use case series: 7b – Finance (tech view)

https://blogs.sap.com/2016/02/22/material-ledger-embedded-in-s4-hana-benefits-and-challenges/

 

SAP QM

#S4HANA 1610 use case series: 6a – Integrated Quality Management (biz view)

#S4HANA 1610 use case series: 6b – Integrated Quality Management (tech view)

SAP WM/EWM

#S4HANA 1610 use case series: 4a – Warehouse Management (biz view)

#S4HANA 1610 use case series: 4b – Warehouse Management (Tech view)

SAP Procurement/Sourcing

#S4HANA 1610 use case series: 3a – Procurement (biz view)

#S4HANA 1610 use case series: 3b – Procurement (tech view)

 

SAP FIORI

#S4HANA 1610 use case series: 5a SAP Fiori 2.0 (biz view)

#S4HANA 1610 use case series: 5b SAP Fiori 2.0 (tech view)

https://blogs.sap.com/2017/03/03/how-to-implement-sap-fiori-procurement-overview-page-for-s4-hana/

 

SAP ATP

#S4HANA 1610 use case series: 1a – advanced Availability to Promise (biz view)

#S4HANA 1610 use case series: 1b – advanced Availability to Promise (tech view)

SAP IM

#S4HANA use case series: 2a – next generation inventory management (biz view)

#S4HANA use case series: 2b – next generation inventory management (tech view)

SAP Logistics

#S4HANA use case series: 1a – next generation logistics (biz view)

#S4HANA use case series: 1b – next generation logistics (tech view)

Learning More about S/4 HANA

Quick update – Learn more about SAP S/4HANA  

SAP S/4HANA Frequently Asked Questions – Part 6 – the cloud edition

SAP S/4HANA Frequently Asked Questions – Part 5

SAP S/4HANA – Frequently Asked Questions – Part 4 – quick update

SAP S/4HANA Frequently Asked Questions – Part 3

SAP S/4HANA Frequently Asked Questions – Part 2 – the value

SAP S/4HANA Frequently Asked Questions – Part 1 – the fundamentals

 

 

SAP S/4HANA can be deployed on-premise, in the cloud or in a hybrid scenario with on-premise and cloud. The implementation approach is different for on-premise and cloud solutions.

Customers new to SAP or customers with an existing SAP landscape may be implementing SAP S/4HANA. Three transition scenarios are described in this section: New Implementation, System Conversion and Landscape Transformation.

SAP Activate methodology phases:

Like our ASAP Methodology in ECC, Here SAP S4 HANA Simple logistics/ Finance uses SAP Activate Methodolgy. Please refer for Complete Details.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

·  Introduction: key concepts, overview of scenarios, different options and overall benefits.

·  Discover: what resources are available before an SAP S/4HANA project starts.

·  Prepare: infrastructure is set up and selected SAP Best Practices are activated.

·  Explore: workshops define the solution and use SAP Best Practice processes.

·  Realize: implementation is undertaken tracking all work in SAP Solution Manager.

·  Deploy: SAP Solution Manager is used in the production cutover.

·  Run: SAP Solution Manager is used to monitor and optimize the solution.

 

The SAP S/4HANA next generation suite is available in these offerings:

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

·         SAP S/4HANA Enterprise Management

·         SAP S/4HANA Enterprise Management Cloud

·         SAP S/4HANA Professional Services Cloud

·         SAP S/4HANA Marketing Cloud

·         SAP S/4HANA Finance Cloud

·         SAP S/4HANA Manufacturing Cloud

All solutions provide hybrid scenarios with integration to SAP Ariba network, SuccessFactors, hybris and SAP Cloud for Customer. More information on hybrid scenarios per line-of-business.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

·  Human Resources: integration to SAP SuccessFactors Employee central.

·  Procurement and business networks: integration to SAP Ariba for purchase orders and invoices.

·  Customer Engagement: integration to SAP Cloud for Customer for opportunities.

·  Finance: integration to SAP Financial Services Network.

The table below shows some of the key differences between on-premise and cloud solutions.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

SAP S/4HANA On-premise SAP S/4HANA Cloud
Licensing model Traditional Licenses Subscription licenses
Infrastructure Customer controls deployment and maintenance SAP provides systems and is responsible for maintaining the infrastructure
Innovation Customer has control of innovation, downtimes and changes Automatic quarterly innovation upgrades
Implementation Individual requirements for business processes and customization Predefined best practice configuration and limited specialization
Scope Full ERP scope and integration with cloud solutions Key ERP scenarios and integration with cloud solutions
Custom code Full traditional ABAP extensibility In-app extensibility with limited ABAP, SAP HANA Cloud Platform as extension

Customers new to SAP or customers with an existing SAP landscape may be implementing SAP S/4HANA. SAP has defined three transition scenarios:

·         New Implementation: for customers migrating from a legacy system and also known as a “greenfield” approach. The legacy system might be an existing SAP solution.

·         System Conversion: for customers who want to convert their current system into an SAP S/4HANA system. They can convert database, SAP NetWeaver and applications in one step.

·         Landscape Transformation: for customers who want to consolidate their landscape or to selectively transform data into an SAP S/4HANA system.

The content about SAP Solution Manager 7.2 in this reference guide covers on-premise new implementation but some of it is also relevant for the other two scenarios. In pure cloud new implementation, SAP Solution Manager 7.2 is not typically used.

This guide focuses on the New Implementation on-premise approach, where you activate the standard SAP Best Practice processes as your starting point. In the System Conversion and Landscape Transformation approaches, the existing SAP solution is the starting point and SAP Best Practices are just used as a reference solution.

SAP Activate consists of three elements:

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

·    SAP Best Practices for SAP S/4HANA: technical content and documentation accelerators that help you get up and running quickly with pre-configured best practice scenarios.

·    Implementation methodology / roadmap: the SAP Activate methodology replaces ASAP as SAP’s implementation methodology for SAP S/4HANA and all other SAP solutions.

·    Tools for guided configuration: tools to activate SAP Best Practices in the SAP S/4HANA on-premise solution and configure and test the SAP S/4HANA cloud solution.

SAP recommends that SAP Activate is used in conjunction with SAP Solution Manager 7.2 for on-premise implementations but Solution Manager 7.2 is not a mandatory requirement for the S/4HANA implementation.

The benefits of using SAP Activate are:

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

·      A faster, less service intensive, initial implementation leading to faster time-to-value.

·      Rapid adoptions of innovations throughout the solution lifecycle.

·      A flexible framework and implementation foundation that can be extended by customers and partners.

SAP Best Practices have been available for SAP solutions for many years.They consist of pre-configured best practice processes and related documentation accelerators such as business process diagrams and test scripts. Some SAP Best Practices are also available as Rapid Deployment Solutions.

With SAP S/4HANA cloud solutions, the predefined SAP Best Practices are part of the standard solution provided by SAP in the cloud. With SAP S/4HANA on-premise solutions, the SAP Best Practices are activated by the customer using the SAP Best Practices Solution Builder tool or delivered as part of the SAP S/4HANA Software Appliance. (We refer to SAP Best Practices Solution Builder as SAP Solution Builder within this guide). The content and tool are shipped with the on-premise software. On-premise customers can use the SAP S/4HANA Software Appliance to speed up the setup of their infrastructure. This has the SAP Best Practices already activated.

SAP Best Practices provide a configured solution that forms a foundation for your project.On-premise customers can select which SAP Best Practices content to use and then make changes or add project specific scope. Cloud customers can refine the configuration within fixed solution boundaries.

·         Scope Items: typically a pre-defined business process, such as sales order processing. They represents a Best Practices implementation choice for you. Each scope item has a set of accelerators delivering detailed documentation that is used during the implementation project. Examples accelerators are process diagrams and test scripts. Scope items require specific building blocks to be implemented.

 

·         Building blocks: a set of configuration for a piece of business content such as credit management. The accelerators include the configuration content to implement the scope item(s), sample organization data, sample master data and project documentation such as configuration guides.

 

·         Package: a selection of scope items that cover the scope of the SAP S/4HANA solutions or other leading industry or line of business segments. Examples accelerators are a customer presentation and software and delivery requirements document.

As stated, the SAP Activate methodology replaces ASAP as SAP’s implementation methodology for SAP S/4HANA and all other SAP solutions. There are generic / general variants of the methodology that are not software solution specific and there are solution specific variants e.g. the SAP S/4HANA roadmap.

The methodology content is organized into a three level hierarchy:

·         Phases

·         Deliverables

·         Tasks

Each node in the hierarchy has a description that provides SAP’s advice and guidance. Each node also links to documentation accelerators that may be generic e.g. an open issues template or solution specific e.g. administration guide for SAP S/4HANA on-premise.

The SAP S/4HANA specific methodology is called a roadmap and is available in two ways:

·         Online read-only information in the roadmap viewer (https://go.support.sap.com/roadmapviewer/ shown below).

·         Project within SAP Solution Manager 7.2 where it can be changed to reflect the specifics of your project.

As already mentioned

The SAP Activate phases and their main activities are:

·         Discover: define and agree the scope of the project.

·         Prepare: the project is formally initiated, SAP Best Practices are activated and project planning is started.

·         Explore: verify solution scenarios meet business needs and document delta scope and gaps.

·         Realize: customer specific requirements are configured and implemented. The solution is tested to check that it matches the agreed design.

·         Deploy: you will train end users, undertake data migration and provide support during the go-live.

·         Run: monitor and optimize the solution.

Tools used

Currently, the tools used to undertake implementations are different for on-premise and cloud solutions of SAP S/4HANA. The summary below applies for the New Implementation scenario and will be different for System Conversion and Landscape Transformation. This reference guide focuses on on-premise.

Topic

On-premise Projects

(and hybrid projects including cloud)

Cloud Projects
Activate SAP Best Practices Content SAP Best Practices Solution Builder is used to activate the SAP Best Practices. You can select what scope items to activate. The cloud solution including SAP Best Practices is activated by SAP in the cloud landscape.
Customer specific configuration Use Implementation Guide (IMG) to change and extend the configuration.  Changes can be tracked in SAP Solution Manager 7.2. You can use SAP S/4HANA Manage Your Solution app to configure certain solution parameters.
Test Processes SAP Solution Manager 7.2 can be used to track and manage the test process You can use SAP S/4HANA Manage Your Solution app to test SAP Best Practices processes.
Migrate Data Undertaken in the same way as a SAP ERP project You can use SAP S/4HANA Manage Your Solution app to execute data migration
Manage solution lifecycle SAP Solution Manager 7.2 is used to manage the implementation and operations SAP Solution Manager 7.2 is not typically used.
Access S/4 roadmap Roadmap viewer or project in SAP Solution Manager 7.2 Roadmap viewer or downloaded plan in Excel

On- Premise

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

SAP Solution Manager 7.2 is an on-premise system used to manage the implementation and operation of the SAP S/4HANA solution. SAP Best Practices S/4HANA content is available for SAP Solution Manager 7.1 and 7.2 but customers are advised to use SAP Solution Manager 7.2 which has new features to support SAP S/4HANA implementations.

SAP Best Practices Solution Builder is a tool that is part of the SAP S/4HANA on-premise software. As you will see later, the tool allows you to semi-automate the configuration of the SAP Best Practices processes.

Cloud

SAP uses Content Lifecycle Management to deliver new configuration for each new cloud release. The apps and tools for cloud implementations allow a customer to implement the SAP S/4HANA cloud solution within the boundaries defined by Content Lifecycle Management. They include:

·         Self-Service Configuration UIs (SSCUIs) where the customer can undertake configuration.

·         An environment for organizing and executing process-oriented testing activities for SAP Best Practices processes, based on pre-scripted test cases.

·         Access to the SAP Learning Hub where you can launch and share information in learning rooms in a collaborative fashion.

·         Expert configuration: this is used by SAP to undertake configuration on behalf of the customer where SSCUIs are not available.

 

SAP Solution Manager 7.2 provides lifecycle management for SAP and non-SAP solutions.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

As a customer, you can choose which capabilities to use in your project. The following capabilities may be used in your on-premise or hybrid implementation:

·         Business requirements and IT requirements: central storage of requirements along the SAP S/4HANA implementation lifecycle. Manage and approve requirements leading to agile developments.

 

·         Project management: plan and manage the schedule and resources for your implementation. Use the SAP Activate roadmap as your starting point and modify it to suit your needs.

 

·         Process management: SAP Solution Manager 7.2 provides a new way to manage your business processes with a new user interface and integrated process diagram editor. SAP Best Practices packages fully replace the former Business Process Repository (BPR) content. You can leverage the pre-configured SAP Best Practices processes for SAP S/4HANA.

 

·         Change and release management: provide change deployment control and risk mitigation. Changes to the SAP S/4HANA system and solution documentation are synchronized in one process.

 

·         Test management: test and deploy your SAP S/4HANA solution keeping track of all test scripts, test cases and test results.

benefits of using SAP Solution Manager 7.2:

·         Covers the entire S/4HANA solution lifecycle from implementation to operation. Once the solution is live, all the SAP Solution Manager 7.2 operational features such as monitoring and root cause analysis can be used.

 

·         Jump start your project using SAP Best Practices content for configuration and solution documentation.

 

·         Take advantage of a new user interface and new features designed specifically for SAP S/4HANA.

 

·         SAP Solution Manager 7.2 can run on a HANA database.

 

·         Enhancements to support hybrid projects that include on-premise and cloud solutions.

 

·         A faster and simpler approach to importing business content such as SAP Best Practices.

 

·         Improved solution documentation including process diagrams that can be published outside SAP Solution Manager 7.2 in the standard Business Process Management Notation (BPMN).

 

·         A single source of truth across project and support activities leads to faster decisions with lower risks.

 

·         Reduce project management and administration costs with transparency of project phases and integration into transport management.

 

·         Improve testing efficiency by knowing what to test when and managing test cases and test progress efficiently.

 

·         Improve management of custom code leading to lower costs.

Implement SAP S/4HANA on-premise with SAP Best Practices – Reference Guide

Activities during SAP S/4HANA new implementation

The table below provides a summary of the activities undertaken using SAP Best Practices and SAP Solution Manager 7.2 during each of the project phases. The rest of the reference guide provides more detail. Also, the table shows the systems involved and which roles the content is relevant for (functional team in the roles column refers to solution architects, functional leads and consultants).

 

Activities Roles  Systems Involved
Discover
Access to trial systems Administrator SAP S/4HANA and SAP Solution Manager 7.2
Access SAP Best Practices documentation Administrator and functional team Best Practices Explorer
Review SAP S/4HANA implementation roadmaps Project manager and administrator Roadmap Viewer
Decide whether to use SAP S/4HANA Software Appliance Administrator
Prepare
Define and setup system landscape (managed and managing system) Administrator SAP Solution Manager 7.2 , SAP S/4HANA
Choose SAP Best Practices packages and activation approach Administrator and functional team SAP Best Practices Explorer, SAP Solution Manager 7.2,SAP S/4HANA
Consider and clarify whether multiple SAP Best Practices packages will be used Administrator and functional team SAP Best Practices Explorer, SAP Solution Manager 7.2,SAP S/4HANA
Create solution Administrator SAP Solution Manager 7.2
Decide whether a template solution will be used Administrator SAP Solution Manager 7.2
Setup requirement management or Change Request Management (ChaRM) Administrator SAP Solution Manager 7.2
Using requirements management to control changes Administrator SAP Solution Manager 7.2
Using request for change to control changes Administrator SAP Solution Manager 7.2
Create project for project management Project manager and administrator SAP Solution Manager 7.2
Activate SAP Best Practices configuration in SAP S/4HANA using Software Appliance Administrator SAP Solution Builder, SAP S/4HANA
Activate SAP Best Practices configuration in SAP S/4HANA using SAP Solution Builder Administrator and functional team SAP Solution Builder, SAP S/4HANA
Import SAP Best Practices content into SAP Solution Manager 7.2 Administrator and functional team SAP Solution Manager 7.2
Importing multiple SAP Best Practices into SAP Solution Manager 7.2 Administrator and functional team SAP Solution Manager 7.2
Align scope with activated SAP Best Practices and complete the process alignment with the customer’s business processes. Administrator and functional team SAP Solution Manager 7.2
Test activation of SAP Best Practices configuration content in SAP S/4HANA Administrator and functional team SAP S/4HANA, SAP Solution Manager 7.2 (optional)
Working with SAP Solution Manager 7.0 or 7.1 Content Administrator SAP Solution Manager 7.2
Explore
Undertake fit-gap workshops and create business requirements and IT requirements Functional team and development team SAP Solution Manager 7.2 and SAP S/4HANA
Design customer adaptations Functional team and development team SAP Solution Manager 7.2
Finalize test strategy Administrator and test manager SAP Solution Manager 7.2 and SAP S/4HANA
Realize
Create change documents Administrator SAP Solution Manager 7.2
Document solution Functional team and development team SAP Solution Manager 7.2
Implement solution in SAP S/4HANA Functional team and development team SAP S/4HANA
Test solution Administrator and test manager SAP S/4HANA and SAP Solution Manager 7.2
Transport solution to quality assurance Administrator SAP Solution Manager 7.2 and SAP S/4HANA
Reporting Project team SAP Solution Manager 7.2
Prepare end user training Administrator and functional team SAP Solution Manager 7.2
Deploy
Transport solution to production Administrator SAP Solution Manager 7.2 and SAP S/4HANA

The following locations are valuable sources of information:

·         Presentation that summaries this reference guide

·         PDF version of this reference guide

·         Explore SAP Best Practices and Rapid Deployment Solutions: https://rapid.sap.com/bp

·         Implementation of SAP S/4HANA: https://open.sap.com/courses/s4h4

·         SAP S/4HANA SCN Cookbook: http://scn.sap.com/docs/DOC-64980

·         SAP S/4HANA Implementation and Configuration Learning room: register here

·         SAP Activate in Roadmap Viewer: https://go.support.sap.com/roadmapviewer/

·         SAP Solution Manager 7.2 EKT Learning Map

·         SAP Solution Manager 7.2: http://support.sap.com/solutionmanager

·         SAP S/4HANA transition scenarios white paper.

·         Information of cloud hybrid scenarios: http://service.sap.com/public/hybrid

I Hope the Details shared in this blog is more useful. Thanks to SAP
Regards,
G.V.Shivakkumar
Please use my earlier Blog on S4 HANA Simple Logistics
To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. shivakkumar Geetha venkatesan Post author

    Here is my few comments after reading the SAP websites related to S/4HANA EM.

    SAP S/4HANA- Enterprise Management  (Regret if i used Simple logistics here in this comment.. it is due to typo mistake**)

    S- Simplified/Suite 4- it is 4th generation.

    Actually SAP has given the Name SAP S/4 HANA Enterprise management and they used Simple logistics the name given during the development.

    1511- Nov 2015

    1610 Oct 2016 ….

    now current one is 1709(cloud version)…..SAP keep on releasing the newer versions…

    SAP S/4HANA Simple logistics is now renamed as S/4HANA Enterprise maanagement which combines all the functionality and modules. such as MM,WM,SD,PP,PM,QM,ARIBA,APO,EWM,GTS,SNP,BI,,etc. so S/4HANA EM has single HANA Database platform on which all this intgrated Modules/functionality sit together which reduces the redency in data, duplication and brings the concept called principle of one. for example in MM earlier tables MSEG, MKPF and related 26 aggregate tables are now replaced with single Table called MATDOC, similary in FI we have ACTDOC..etc..in SD credit management in A/R is now removed and S/4HANA is utilizing FSCM credit managmement, related to SD pricing KONV tables are now obsolete, output management is simplified, in case of PP we have MRP Live used in addition to classical MRP..(in S/4HANA both the MRP is used- classical and MRP Live) based on Planning Materials..MRP tables are simplified and faster execution of MRP which brings attraction to user groups. due to tight integration of modules in one single common plafform data extraction is more simplified and report run is more faster than the ECC, and even transaction exection times is reduced to greater extent. we can use of FIORI will bring the cusomer satisfaction and good user experince. Many advantages SAP introduced in S/4HANA. in case of ECC if we need to connect EWM, GTS, SRM,CRM we need to QRFC connection to transfer data here and there…but now no usage of QRFC’s.. in SD we have many innovations in the areas of COGS Split, Stock in Transit(SIT), Split batches..etc..Another one introduction of BRF from Netweaver to S/4HANA brings versatile usage of output management, PR, PO Approvals..etc.. we cannot tell in one single shot,, but once you experince it is really awesome.. Thanks to SAP.. SAP ARIBA functionality which tightly integrated customer and vendor in ARIBA cloud..lot many features.. I hope the details are more useful…

    SAP JAM developed by SAP function (Social network for a company) like Facebook which connects group.

    SAP S4 HANA called Digital core/ Digital transformation- using IOT we can connect sensors which trend volume of Data.

    Before Going to S4 HANA SLOG we cannot avoid HANA DB Information.

    SAP is in the Process of re-design or re-structing Products/suite to align with

    In-Memory (Hana) Real Time (Amount of Data Processing in memory itself)

    Internet of things- to connect with different consumer groups/process/systems/business across the world.

    Inter-Operability of UI (Desktop, Smart Devices)- Fiori

    Mobile Orientation for any design of device..

    Big Data- for better reporting in a common platform integrating all the business Process.

    Social Media Integration

    Business networks- Such as Vendor, Customer Integration with Banks, customer & Employees.

    SaaS Offerings- connecting SAP Products ECC, CRM, APO, SRM, PLM, EWM, SNP, SNC .Etc… HCM is now called SAP Success factor

    OLTP/OLAP Convergence- Keeping all the analytics sitting on transaction Level itself.

    SAP S/ HANA Supports 10 LOB’s (Lines of business) and 25 Industries.

    10 LOB’s

    SAP S/4 HANA Finance, SAP S/4 HANA HR, SAP S/4 HANA Sourcing and Procurement, SAP S/4 HANA Supply chain, SAP S/4 HANA Marketing, SAP S/4 HANA R & D, SAP S/4 HANA Asset management, SAP S/4 HANA Sales, SAP S/4 HANA Marketing & Commerce, SAP S/4 HANA Customer Service.

    Many people will have the confusion what is SAP HANA and SAP S/ HANA both are same or different? Answer is SAP HANA is a Platform or we can say Data base which was introduced in the year 2011 which is introduced as a replacement for the traditional existing databased which reduces the complexity and also bring some benefits which is not possible in current data bases such as Oracle, Sql server etc..

    In-memory computing benefits I mean instead of storing the data in hard disk instead it will directly access the RAM which increases the performance and fastness in transaction and reporting.

    Multi core processing –meaning that it will process multiple transactions @ the same time. Multiple process can be executed in Parallel.

    SAP HANA Called Columnar Database

    Third benefit would be SAP HANA can stores the data in rows as well as columns instead of the traditional data based can execute in Rows for processing high volume of Data.

    SAP S/4 HANA to function it needs SAP HANA database. It will not run in oracle or SQL as the traditional versions of ERP SAP..ECC.

    It is next generation business suite designed to run the transaction simple.

    Built on advanced in-memory Platform SAP HANA

    Offers personalized user experience with SAP Fiori. Here user experience in the sense. Menaing that when we check with the users on current GUI screen or transactions definitely they will said it is more complex and difficult and this is avoided in Fiori which works on any platform or any device- even in tabs and mobile more simpler which is more easy to operate and navigate b/w transacions.

    Deployable in both Cloud or on- Premise – Means SAP HANA when in cloud can reduce the Hardware/networking device cost and we need to pay only subscriptions to use the cloud. It again depends on clients likes/dislikes..

    In cloud server management is taken care by Third party and no technical people server team is required and cost will be saved.

    Let’s say one client is replacing the data base with SAP HANA but still If they use ECC EHP7 for the application then we cannot say it is a migration. They just utilizing the HANA databased for their operation. If they completely migrate I mean using SAP HANA data based and SAP HANA S/4 for their application then it is a complete processing the advantage is some process which is more complex in current ECC which is overridden in SAP S/4 HANA SLOG.

    Best example would be MRP in ECC. It is a general talk system talking more time on execution f planning run for a material in ECC. They simplified and execution time Is quick- how they achieved is by using SAP HANA Database.

    Second one is currently we have SAP ECC, BI, APO, SRM, EWM etc. In different different boxes and execution data would take more time – this is avoided in SAP HANA and it brings everything in common SAP HANA Platform and so we don’t have to depend on QRFC connection or RFC/Interfaces..Etc.. New dimensional components such Hybris, Arriba and everything will be in one single platform. This is achieved in 1511 as starting era in SAP S/4 HANA and later SAP moved to next version or gen 1610.

    So here MRP is stream lined, Credit management is streamlined and SO creation is simplified, Material ledger or Material valuation is simplified, Inventory valuation is simplified. So transaction processing is simplified and also wherever possible they increased the performance with the current existing ECC transactional system. SAP Jotted down the areas where users or clients or end users reporting issues they tried to avoid these errors and bug as the Market is moving from B2B to B2C and end customer satidifcation is more required for a company or service provide to grow in that terms SAP HANA is a next generation one.

    Principle of one– in current ECC we have many functionalities that are redundant. Same process but 2 functionalities. For example credit management. In current system we have AR SD Credit management and also FSCM Credit Management. Unnecessarily we have 2 functionalities for the same process. This is avoided in SAP S/4 HANA because all the components or modules in single platform so we can avoid red tendency… SAP removed AR SD Credit management and use only FSCM Credit management where some additional functionalities available compared to AR SD Credit management.

    Key Enables or Features

    Due to removal of redundancy in SAP S4 HANA the speed is 10X times the ECC.

    7X times throuput. Less throuput means less input and higher output.

    1800X times faster analytics and reporting (speed is More Faster in SAP S4 HANA).

    4X times less than the process times. Let’s say the PO creation time in ECC is 40 s but in HANA it is 10 S.

     

    One more example is Inventory valuation- we have 2 functionalities one is Inventory valuation and another one is activating the material ledger. So in SAP S/4 HANA Inventory valuation is removed and keeping the functionality activation the Material ledger mandatory.

    Built to drive instant, Value across lines of business-

    Not particular across the lines of business let us say P2P, OTC or finance.. but it is for common for all the lines of business I mean complete SAP.. in 1511 and now we have 1610 in usage.

    For example if you are posting GR in ECC normally we all know affected tables are MSEG and MKPF but we know from our experience that not only 2 there are so many table getting hit when posting Material doc these are called aggregate tables and this and when we process the transaction these tables get locked on processing of data and so we are unable to process second one till end of the first one. But this is avoided in SAP S4 HANA where using power calculation functionality and it is not going for aggregate tables.. so SAP S4 HANA calculation engine is very powerful and aggregate table concept is removed. New table was introduced called MATDOC which will hold all the data stored in aggregate tables… which will calculate and process all the transaction involved. This is applicable for Reporting also – we can depend on only MATDOC for reporting which simplifies all and reduces time of processing.

    SAP S4 HANA is using AGILE methodology called SAP Activate methodology which replaces our traditional water fall model- ASAP Methodology.. also major changes in respect to modules are MM SD PP and PS and in WM or CRM or SRM no major changes or it is same as the existing functionality in 1511 and in 1610 SAP included it SRM/CRM/APO..

    Related to Master data – no more XD01 or XK01 in SAP S4 HANA. We need to use business partner for Material and customer.

    Material master charcter length extended from 18 to 40 charcters..so all the integrated system utilizes this option- EWM, APO, PLM etc..

     

    Simplified SD pricing – KONV table is replaced by one another table. Also access sequence increased from 99 (ECC) to 999 in HANA.

    Unified credit management- as already mentioned we have CM with FSCM.

    Smarter solution in case SO fulfillment cockpit.

    Output determination is simplified – no complexity in configuration

    Here simple changes means table replacement and not covers functional changes.

    One more important thing SAP is more curious to completely migrate to SAP S4 HANA by 2025 for those who already having SAP in their premise but for fresh clients no issues all are from SAP S4 HANA scratch.

    In case WM SAP S4 HANA will not consider it more and future changes will be on SAP EWM and it supports SAP EWM only.

    Choice of Deployment- On premise, Cloud & Hybrid.

    ECC in premise, In-house, CRM in Cloud.

    Disadvantage in cloud is we are doing subscription and level of changes in the layout or development aspects is somehow stringent as cloud belongs to third party (it will affect other subscribers also)we have some limitation compared to on premise where ownership is ours and we can do the changes as per our requirement.

    In S4 HANA EM we have guided configuration in case of cloud edition. We cannot override the prescribed guided configuration because it will affect other subscribers in the cloud. (It gives a tour of the best practice for a particular undergoing implementation- it is a SAP Fiori UI apps. Even if the person not known to the enterprise structure in traditional ECC can able to get the guidance and do configuration).

    While in on premise you can do required config based on client requirements.

    I hope i have shared complete information. Please refer Simplification list released by SAP. which will give complete idea on S/4HANA Enterprise Management..

    Thanking you.,

    Regards,

    G.V.Shivakkumar

     

    (0) 
  2. shivakkumar Geetha venkatesan Post author

    SAP is always No-1 in ERP/SCM world because it is keep on researching, introducing new Products and Innovations that brings higher end customer satisfaction and Greater user Experience.

    Flexible, Simpler business process (Manual to Automation)
    better Decision making
    Improved customer experience
    Reduce cost
    Increase end user productivity
    Reduce risk
    Improve productivity ( asset utilization)
    Faster time to market.

    Thanks SAP..

    Regards,

    G.V.Shivakkumar

    (0) 

Leave a Reply