 S/4 HANA 1709 system vs noramal ECC

 SAP S/4 HANA On premesis vs SAP S/4 HANA On cloud version

 SAP HANA can be deployed on two delivery platforms: on-premise for maximum control
and in the cloud.

On Premise - Version
 SAP S/4HANA on-premise edition is an internal platform, located on your own servers,
maintained by your company. SAP upgrades are released annually but have to be
implemented and tested by your own team.
 High compliance with individual business requirements and customization.
 Deployment and maintenance is implemented and managed by IT staff of a customer.

On Cloud - Version
 SAP S/4HANA Cloud edition is Software as a Service (SaaS) hosted on SAP’s servers and
is maintained by SAP. Software upgrades happen on a quarterly basis.
 Predefined best-practice configuration with limited specialization.
 System infrastructure and maintenance are under SAP’s control.

 row and columns approach

 https://www.youtube.com/watch?v=jerczCx8nmQ
 https://blogs.sap.com/2013/08/15/hana-column-store-backgrounds-insert-only/

 ABAP HANA vs ABAP

1. The process of enhancing the existing code to HANA compatible is referred as
ABAP on HANA.
 ABAP 7.4 and 7.5 coding
https://blogs.sap.com/2015/10/25/abap-740-quick-reference/

 What is insert only approaxh

The downside of this compression technique is that updating the database directly becomes
more costly. Inserting, updating, or deleting a record would require decompressing the table,
performing the action, and then recompressing it again.SAP’s solution for this was to implement
an “insert-only” approach to database updates. While a database is in use, SAP would use two
versions of the database table: the original database table and a delta table. The original table
will have all of the original compressed records, while the delta will have the uncompressed
records that represent additions and changes.SAP is able to keep track of the latest (and
therefore most up-to-date) versions of a specific record by attaching a transactional ID. Then,
when it’s time to SELECT a record, the original table and delta tables are joined and only the
most recent record will be returned.
Once the table is no longer in use, the HANA system will consolidate the changes leaving only
the most recent records in the compressed version of the table.

 Code Push down technique in ABAP HANA

 Currently Top-Down approach is used in the CDS views and ABAP Managed Database
Procedures (AMDP).

 CDS(Core data service)

/https://blogs.sap.com/2017/09/09/abap-core-data-services-introduction-abap-cds-view/
 AMDB(ABAP Managed database procedure)
 BRF +(Business rules framework)
 Workflow Basics
 Adobe forms
 Odata(Open data)
 ABAP HANA Objects
 Reports(Oops ALV, ALV, Classical reports,events)
 Forms(Smartform)
 Forms(Adobe forms)
 BADI,Enhancemet points, Use exit,customer exit
 Module pool programming
 Conversions(BAPI,BDC,LSMW)
 Interface(Wesbservices, IDOC)
 Data Dictonary
 Webdynpro(FPM)
 SAP Notes
 Moduralazation technique( FM,Subroutines,Macros)
 Class and methods
 Reference variables
 commit and roll back, sap memory, abap memory,commit work.
 Debuging
 ABAP Performance, code inspector
 Preparing Technical documentaion(TD,UTP,Code check)
 Steps( Transition From SME, MOM,Review,FAT)
 SD Flow and MM Flow
 Background jobs