Professional Documents
Culture Documents
Agenda
ABAP Code Remediation
Transport blocking
Intel Information
Intel Confidential for
internal use
Technology
Custom variant
Y_HANA_DB_AND_ADDITION crated in
FI0 combining the FUNCTION_DB and
Intel Information
FUNTIONAL_DB_ADDITION
variant
Intel Confidential for
internal use
Technology
SQL Monitor
It is performance analysis tool / utility can be used not only but especially for the purpose of optimizing
custom code for SAP HANA.
Traces each and every SQL statement coming from an ABAP program - this includes OPEN SQL, native SQL
and SQL statements coming from the ABAP kernel
SQL Monitor can run in a productive system without disturbing business processes and can be run before
HANA migration
Allows downloading SQL Monitor data in order to import it in a development system where the code corrections are
done.
Description
Search problematic statement for Binary search, Delete after filling internal table without
167
32
676
result of SELECT/OPEN CURSOR
sort order, or loop to search an internal table without sort
without ORDER BY
by.
Test Existence of a Program
Program does not exist in system but entry in available in
5
TADIR table
Scan a Program
Include Programs are missing
10
Critical Statement
Certain statements that are critical for security or that
38
113
547
records. When that happens, program will read the
complete DB table
Analysis of WHERE condition in
Where clause check for UPDATE AND DELETE statement
3
2
UPDATE
and DELETE
Analysis of WHERE condition for Examines the WHERE condition of the SELECT statement
37
57
SELECT
for not using Where clause, Index fields, etc.
Priorities 1 and 2 indicate serious problems that usually need to be fixed as quickly as possible, since they may
243
243 1438
affect the correct functioning of a program.
Lower priorities indicate less severe quality problems.
Intel Information
Intel Confidential for
internal use
Technology
ATC Demo
Intel Information
Intel Confidential for
internal use
Technology
Intel Information
Intel Confidential for
internal use
Technology
Critical statements
DB hits are used to improve the performance. DB hints are Database specific and need to
remove as it will not be required with HANA DB. This change will happen with HANA DB
migration.
We have seen code for inflight projects as well as prod fixes land into
PROD without checking for HANA compliance
15
16
Intel Information
Intel Confidential for
internal use
Technology
17
Demo
Intel Information
Intel Confidential for
internal use
Technology
18
Q/A
Intel Information
Intel Confidential for
internal use
Technology
19
Back up
Intel Information
Intel Confidential for
internal use
Technology
Sprint 1 Timelines
Time lines Sprint 1
ww10 ww24
Remediate code in DEV, Unit Test
Pre-Test in CONS can run parallel to remediation
Each remediated object will move to CONS as soon as its remediated, unit-tested AND Pre-Test in CONS is done
To ensure a consistent completion of above deliverables, use status that we have in the remediation
spreadsheet. These statuses are captured in object remediation workflow i.e. object Development status =
Ready for Test and Test Status = QC test case & pre-test completed.
Post-Test done in CONS once code migrated
WW24/WW25 ALL Post migration CONS Testing must be done
ww27 ww28
CONS Post-Test on HANA DB to ensure remediated code works on HANA DB
** SAs will be quite busy here with regressing testing as well for MR, so need to ensure Post-Test happens fairly
quickly
ww29.3
ww29.2 Go/No Go
Prod Migration
Intel Information
Intel Confidential for
internal use
Technology
21
22
Intel Information
Intel Confidential for
internal use
Technology
Critical Statement
Back
Intel Information
Intel Confidential for
internal use
Technology
Intel Information
Intel Confidential for
internal use
Technology
Back
Intel Information
Intel Confidential for
internal use
Technology