What is difference between SAP ECC, HANA and S4 HANA?

SAP-ECC → is —ERP Central Component— Solution from SAP. It is part of older SAP Business Suite (consists of ERP/CRM/SRM/PLM) from SAP. The latest version from SAP is ECC 6.0 (EHP7). ECC 6.0 could be installed on any RDBMS (ORACLE/DB2/DB6/MSSQL etc.)

SAP-HANA →is SAP’s In-Memory Solution based on Proprietary Database. It is supposed to give high performance since the DB is In-memory

S/4HANA → Is the new 4th generation Business Suite offered by SAP only on HANA Database. It is Optimized to take benefit from HANA Platform and provide simplification across processes.

“S” stands for “Simplification” and “4” stands for 4th generation or “next” generation. S/4HANA is available in On-Premise and Cloud. It also offers SAP-FIORI as SAP Mobility Option for end users front-end.

S/4 HANA is the latest version of the SAP enterprise software where SAP  has moved away from  primarily on-premise based ECC version . The difference between both the versions are :

• ECC version has a choice of database of Oracle, SQL server or SAP ‘s HANA but for S/4 HANA , the underlying DB can only be SAP’s HANA DB
• S4HANA versions for Finanace & logistics have much lesser tables than ECC So, it ‘s about making the product more compact & easier & faster to implement .
• S4HANA is SAP’s answer to various best of the breed cloud-based products and taking the product to more SMB companies . ECC  version was more of an on-premise product which SAP was trying to adapt to today’s mobile first, cloud first environment . S4HANA is a radically different product to adapt to this new paradigm shift.

SAP Basis Transaction codes Working status in S/4 Hana 1610

High performance speed of SAP S/4 Hana with in-memory Hana Database, in which there lot new enhancements done and more & more optimization done in this platform rather than SAP Netweaver  and other. In this Article give you the status of Transaction codes working status in S4_Hana 1610 On-premise.

Basis Transaction Codes with status :

Here, so far only one Transaction code become Obsolete, i.e., SM01 and Also for some transactions SU25 & SU24 required to apply new correction of standard SAP Notes.

SM01 – It is Obsolete.

SU25 & SU24 – Required corrections as per Basis component. For more information see the Sap-Note 2234192.

New Tcodes in S4 Hana-1610 :

• STC01
• STC02
• SRT_TOOLS
• SRT_ADMIN
• SRT_UTIL
• SWU3

T-codes which are working fine :

1. SM51
2. Rz03
3. SM50
4. SM12
5. SM13
6. ST22
7. SM36
8. SM37
9. SM21
10. SU53
11. SM04
12. SMLG
13. ST03N
14. ST06
15. ST02
16. SE01
17. SE09,SE10
18. STMS
19. STMS_IMPORT
20. SU0
21. SU01
22. SU10
23. SUIM
24. USMM
25. SPRO
26. RZ10
27. RZ11
28. RZ20
29. SM59
30. SICF
31. SMICM
32. AL11
33. SE03,SE06
34. SCOT
35. SO01
36. SBWP
37. SMWO
38. SM30
39. SE16N
40. SE38
41. NWBC
42. BRF+

 Fiori Related :

Here also, I will provide some fiori based transaction codes. These executable transaction code are helpful to troubleshoot the web or Odata services issues or RFC related or some other issue. Every Fiori Administrator should know all these things.

1. /IWFND/MAINT_SERVICE   –   Active & Maintain Services
2. /IWFND/ERROR_LOG   –   SAP Gateway Error Log
3. /IWBEP/ERROR_LOG   –   SAP GW Back end server Error log
4. /IWFND/GW_CLIENT   –   SAP-Gateway client
5. /IWFND/APPS_LOG   –   Applications log
6. /IWFND/CACHE_CLEANUP   –  Front end cache cleanupAnd
7. LPD_CUST
8. ESH_COCKPIT

About SAP S/4 HANA

• SAP S/4HANA : SAP Business Suite 4 SAP HANA is business suite that is built on SAP with Operational Database System and in memory computing platform, its called SAP HANA and user experience with SAP Fiori.
• SAP R3 based business suite and related product were designed to run on several database platform, like Oracle, SQL, DB2
• SAP S/4HANA consists of two editions : SAP S/4HANA On Premise and SAP S/4HANA Cloud
• Implementation SAP S/4HANA :

A. New Implementation : An new SAP customer (different legacy systems) or an existing SAP Business Suite          customer who wants to start with a new installation of SAP S/4HANA. Also allows to migrate master and  transactional data from legacy system.

Main Steps :

1. Installation of SAP NW server ABAP 7.51 based on SAP HANA
2. Installation of SAP S/4HANA
3. Installation of SAP Fiori for SAP S/4HANA
4. If needed : migration of legacy data

Configuring after installed SAP S/4HANA :

1. Follow SAP Activate and SAP Best Practise
2. Use SAP  Activate and SAP Best Practise as templates for system configuration and make changes using the Implementation Guide (IMG)
3. Use only the IMG to configure system

B. System Conversion : an existing SAP Business Suite customer wanting to change  system to an SAP  S/4HANA.

Some prerequisites :

1. System has to be on Unicode
2. Dual stack systems are not supported, have to do a dual stack split
3. For a single step approach, start release must be SAP ERP 6.0 EHP 0 – 8.
4. Run with the Maintenance Planner for pre-check and custom code migration worklist early on in the system conversion project.
5. Software Update Manager
6. Installation of SAP Fiori for SAP S/4HANA
7. Hardware CPU min 2 core , Memory min 128 GB|

   C. Landscape Transformation : an SAP Business Suite customer who wants to consolidate the existing system        landscape into a SAP S/4HANA system landscape

   • A new installation of SAP S/4HANA needs to run on the SAP HANA database. It also requires the SAP Solution Manager, which can run on any database
   • Simple SAP S/4HANA Deployment :

     
     SAP Business Suite landscape with an embedded SAP S/4Hana System