SAP HANA

&
SAP NetWeaver
Application Server for
ABAP 7.5 Overview

1
History and Journey towards 7.5

The integration journey of ABAP and SAP HANA (for combining the best of both
worlds) started in 2012 with the early enablement with AS ABAP 7.x for side-by-side
scenarios, with SAP HANA as sidecar.

The next and major milestone of this journey was reaching the full market readiness
with AS ABAP 7.4, which is the first AS ABAP release heavily optimized for SAP HANA,
thus allowing an easy leveraging of SAP HANA’s power in ABAP-based applications. It is
the first go-to-release for ABAP for SAP HANA.

With AS ABAP 7.5, another major milestone has been reached by providing the
foundation of the next SAP Enhancement Package for SAP Business Suite 7 and SAP
S/4HANA, the next generation business suite, on-premise edition!
 CORRESPONDING CL_ABAP_CORRE
VALUE
SPONDING
 TEST TEST
SEAM_Example1 SEAM_Example2
INSERT Subquery
 Why do custom code needs to be managed while
migrating to S4 HANA?

• Not all the Custom code that is in ECC system will be compatible with
the SAP S/4 HANA system.
• So we need to validate the existing custom code in order to make it
compatible with the S/4 HANA suite.
• Custom code management can be segregated into two distinct parts:
1. Decommissioning the unused Custom Code
2. Making the Custom Code ready for HANA system
 Decommissioning the unused Custom Code :
• SAP recommends that we should decommission the unused custom
code first i.e., we should not try to make change to code to make it
HANA ready first.
• The reason being simple, that will eventually help us and we don’t
have to work on objects which are not used anymore.
• There are few tools that are useful in identifying the custom codes
that are not in use anymore.
1. UPL(Usage Procedure Logging)
2. SQLM (SQL Monitor)
3. SCMON(ABAP Call Monitor)
• Once the unused custom code is identified, we can proceed with the
decommissioning of the custom code with the tool called CCLM
Custom Code Lifecycle Management.
 Making the Custom Code ready for HANA system :
• Even though SAP has come up with new tables (in order to reduce data
footprint & to have a single source of truth), it still supports all the old
tables.
• So it should support all the custom codes. Well, it does support the old
custom codes except the following few cases.
– Custom codes, which relies on DB specific features or using native
SQL or Hints is not supported in SAP HANA.
– Default Sorting is not guaranteed in SAP HANA. So we need to make
a few changes.
• When the above 2 cases are found, we need to make changes into the
custom code.
• SAP has come up with a tool custom code check for HANA i.e., ABAP Test
Cockpit(ATC) with Remote Code Analysis.
• For the SAP HANA migration SAP provides new static checks integrated
in the Code inspector.
 ABAP Test Cockpit(ATC)
• Bugs in the custom ABAP code can be quite expensive when they
impact critical business processes, which is why quality assurance of
custom ABAP code is receiving more and more attention in business.
• To overcome this, SAP has came up with an inbuilt tool ABAP Test
Cockpit(ATC), which has become SAP’s main internal quality
assurance tool for ABAP.
• ATC is an ABAP check framework which allows running static checks
and unit tests for ABAP programs
• Usage scenarios:
• Check single object from the Development Workbench
• Check multiple objects from the Development Workbench
• Checks on transport objects from the Transport Organizer
• Schedule checks from transaction ATC

S/4 HANA POC

 Benefits of ATC:

• ATC is the single point of entry for all static code check tools.

• ATC comprises a 4-eye principle exemption process to handle

findings effectively.

• ATC is fully integrated in the ABAP development workbench with a

high usability for developers and quality experts.

• ATC is not only a check tool but supports essential QA techniques like
Q-Gates or regression testing in a consolidation system.

S/4 HANA POC

 Code Vulnerability Analysis(CVA):

• This add on is available for carrying out security checks.

• CVA carries out a static analysis of the ABAP source code and reports
possible security risks.
• If we want to enable the execution of the security checks, additional
license costs are incurred.
• In the system, the security checks are sometimes called “Security
Analyses in Extended Program Check (SLIN_SEC)”.
• SAP’s recommendation is to use these security checks through ATC
only.

S/4 HANA POC

 Several CVA checks:

• Hard-coded user name

• Possible SQL injection (WHERE condition)

• Possible directory traversal

• Possible system command injection

• Possible ABAP command injection

• etc,…..

S/4 HANA POC