How SAP S/4 HANA is different from SAP ECC?


Now a days, every companies or business are migrating from SAP ECC to SAP HANA technology to run their business. This SAP HANA helps business to fetch the required data from system without any delay because SAP HANA runs only on HANA database. SAP HANA uses in-memory capabilities which reads the data from system faster than traditional database. On the other hand, SAP ECC can run on Oracle, IBM DB2 etc. which fetch data from hard disk.

SAP HANA fetch the data from in-memory database which reads the data faster than SAP ECC because the data resides in RAM that is why HANA system read the data instantly and show the relevant data at the same time.

SAP HANA read the data through column based technology in which system reads the data from affected column from query.

OLTP and OLAP capabilities are available in the same system. They offer real time reporting and predictive analysis.

There will be no aggregate (total), index, and history tables in SAP S4HANA. This is due to dynamic aggregate creations on the fly based on line item tables.

What is Single Source of Truth and SAP S/4HANA Universal Journal?

In information systems design and theory, single source of truth (SSOT) is the practice of structuring information models and associated data schema such that every data element is mastered (or edited) in only one place. 

SAP S/4HANA combines data structures of different components such as FI , AA , CO , CO-PA and ML into a single line item table. This table is ACDOCA, also known as the Universal Journal. The presence of the universal journal eliminates several aggregate and index tables. Now, data insertions occur into a single table instead of several tables. Hence reducing the data foot print by a huge margin.

In addition, the MATDOC, the new line item for inventory management, eliminates 26+ tables. Material documents are stored in MATDOC but not in MKPF or MSEG tables.

Business Partners and Material Number Extensions in SAP S/4 HANA?

In SAP S/4HANA, Customer and vendor master data need to be integrated/migrated as Business Partner. Customer-vendor integration (CVI) is a mandatory step to run business with SAP S/4HANA.

We create customer and vendor master data from different Tcodes but we call Business partner in S/4 HANA instead of customer and vendor master data. So, we create Business Partner from Tcode BP and we can extend this BP to customer or vendor as per requirement.

One key difference between SAP ECC and SAP S/4HANA is that the Material number can now be 40 characters instead of the existing 18 in SAP ECC. This is an optional feature. Therefore, impacts of this extension on interfaces, custom coding, and other SAP applications must be evaluated. This must be done before switching to 40 characters. You can refer to note number 2267140 for more details.

Leave a Reply

Your email address will not be published. Required fields are marked *