Lockheed Martin’s SAP Business Suite - ABAP Studio Martin’s SAP Business Suite ... Global Trade Services (GTS) Transportation ... • Development Steps to Migrate SAP ECC to SAP

© 2015 LOCKHEED MARTIN CORPORATION. ALL RIGHTS RESERVED.

Lockheed Martin’s SAP Business Suite

powered by SAP HANA Migration

Session: ITM122

Gary Norris – Lockheed Martin

https://sessioncatalog.sapevents.com/go/agendabuilder.sessions/?l=111&sid=26419&locale=en_US

https://sessioncatalog.sapevents.com/go/agendabuilder.sessions/?l=111&sid=26419&locale=en_US

2 © 2015 LOCKHEED MARTIN CORPORATION. ALL RIGHTS RESERVED.

• Lockheed Martin Corporation Overview

• SAP Implementation History at Lockheed Martin Aeronautics

• How Custom Are we at Aeronautics?

• Learning Points

– SOH Development Team Custom Code Migration Steps/Processes

– Analyze Custom code base for Hard Errors, Data Errors and Performance Errors

• Data Errors include incorrect program decision due to order of data retrieved from DB.

• Performance errors include slow run times and/or a material amount of resource consumption.

• Hard Errors include ST22 program abend, job termination with no error log, looping timeouts, etc.

– Determine Proactive solutions to mitigate potential errors.

– Fix all possible high risk errors before first ITC.

– Test, Test, Test and then Test Again.

• SOH Development Team Custom Code Migration Tools

• How to Ensure a Stable Suite on Hana Migration

• Lockheed Martin’s Overall Lessons Learned

Agenda


Lockheed Martin Corporation Overview

Information Systems

& Global Services

Missiles and Fire

Control

Space Systems

Aeronautics

Lockheed Martin Co.

Fort Worth, TX Marietta, GA

Palmdale, CA

YF-22 F-117

U-2

X-35

F-16

F-35C CV F-35A

CTOL

F-35B STOVL

C-5

C-130J

F-22

29,000+ Employees Across the Company and Around the World

112,000 Employees Worldwide

Operations: 572 facilities in 500 cities and

50 states throughout the U.S.;

Internationally, business locations in 70

nations and territories

Mission Systems

and Training


Lockheed Martin Aeronautics is known for building the most technologically

advanced military aircraft in the world. The most recent of these aircraft include

the 5th-Generation F-22 Raptor and F-35 Lightning II.

SAP Systems will enable LM Aeronautics to reach F-35 peak production goals and

is critical to the long-term success of the program.

1994 Lockheed Martin becomes a customer of

SAP

October 2006 Began SAP FI/CO

Project

October 2007Began MRP/Supply Chain

Implementation Deployment 2

January 2008SAP Financials Go Live

July 2009 MRP/Supply Chain Implementation Deployment Go Live

April 2015 SAP SOH Goes Live

Went live with SAP Financials

January 2013

SAP HANA Side Car Goes Live

Lockheed Martin Aeronautics: SAP Implementation History


External

Portal

Suppliers

Exostar

Users

PI Supplier Network

Collaboration

(SNC)

Computer Aided

Process Planning

(CAPP) *

Shop Floor

Management

(SFM) *

Global Trade

Services (GTS)

Transportation

Management

System (TMS)

MCA

(Spares Planning

Optimization)

Internal

Portal

BW Portal

Business

Warehouse

Lockheed Martin Aeronautics will transform business processes, systems and information through the implementation of SAP software, combined with significant process improvements, positioning us to meet the challenges of effectively producing the Joint Strike Fighter (JSF,) achieving horizontal integration and retiring high-risk, aging systems.

OneAero Vision

ECC

MCA

(Spares Planning

Optimization) HANA (Side Car)

HANA

Lockheed Martin Aeronautics: SAP Implementation History


Lockheed Martin Aeronautics: SAP Custom Code

Custom Z Objects in PRD Count

SXCI BADIs 125

User Exits 100

Core Mods (access keys issued, not including OSS notes) 746

DOMA - Domain 1,233

DTED - Data Element Definition 878

DTEL - Data Element 6,090

ENHC - Composite Enhancement Implementation 49

ENHO - Enhancement Implementation 451

ENHS - Enhancement Spot 7

IEXT - Enhancement 18

FORM - SAPscript form 8

FUGR - Function Group 1,240

FUNC - Function Module 1,408

METH - Method (ABAP Objects) 1,996

CLSD - Class Definition (ABAP Objects) 193

MSAG - Message Class 54

PROG – Programs/Includes 3,748

REPS - Report Source Code 1,770

SHLP - Search Help 229

SSFO - SAP Smart Form 76

SSST - SAP Smart Style 28

TABL - Table 2,817

TRAN - Transaction 1,648

ACTUAL lines of Z Code easily available to count in SAP

ECC Z Package Line Count 1,835,678

ECC Estimating Solution 137,267

SAP SNC (est.) 150,000

Enhancement implementations: Explicit/Implicit, Adobe

Forms, Smartforms, XSLT,etc. (10%) 200,000

Actual Z Code lines 2,322,945


• Development Steps to Migrate SAP ECC to SAP Suite On Hana

• Processes/Tools used to Migrate SAP ECC to SAP Suite On Hana

• How to Ensure a Stable Suite on Hana Migration

• Lockheed Martin’s overall lessons learned and results from their Suite on Hana Migration.

LEARNING POINTS


Development Migration Steps

1. Analyze Custom code base for Hard Errors, Data Errors and Performance Errors

• Data Errors include incorrect program decision due to order of data

retrieved from database.

• Performance errors include slow run times and/or a material amount

of resource consumption.

• Hard Errors include ST22 program abend, job termination with no

error log, looping timeouts, etc.

2. Determine Proactive solutions to mitigate potential errors.

3. Fix all possible high risk errors before first ITC.

4. Test, Test, Test and then Test Again.


• SAP Code Inspector

Based on recommended SAP best practices, Lockheed

Martin used the SAP Code Inspector (SCI) as a

fundamental tool of our custom code migration.

Lockheed Martin only used limited SCI parameters to

analyze our code base.

SAP SCI variant = “Functional_DB”.

Other “canned” variants available with NTW 7.4/SP5.

Only SCI Error and Warning messages were acted upon.

Analyze Custom Code Base


• Determine and identify needed ABAP corrections.

ABAP syntax changes needed to maintain

functionality and insure data accuracy (Data

Errors).

Without these changes, Suite on HANA results

may differ from current results.

Examples:

No longer use Oracle implicit sorting.

No usage of Oracle database Hints.

Order of data retrieved from database.

SCI Code Inspector Data Errors



• Post go-live problem with Select Single.

Problem related to explicit logic depending on

order of retrieved database output.

Data in Oracle (with index) always retrieved in

certain order.

With HANA the order of the data may be

different.

These are harder to detect, but can be

remediated by using Order By or Sort statement.




SCI variant parameters:

Security Checks

Critical Statements

Use of ADBC Interface

Robust Programming

Depooling/Declustering: Search SELECT for

Pool/Cluster-Tables w/o ORDER BY

Search Problematic statements for result of

SELECTION/OPEN CURSOR without ORDER BY




SCI code inspector results:

3240 Messages

451 Errors

172 Warnings

2639 Informational

Only Error and Warning messages were

remediated, based on SAP best practices




Performance Errors

Sidecar HANA work: Kernel Switches averaged = 72%, 2nd DB = 70%,

Views = 81%

For SOH: overall average was 70%, with some degradation when all the

stress ships were loaded. The 70% faster applies to both QE8/7 and the

PE1-Performance boxes.

In PE1-Perf, a nightly batch ran 1/3 faster (reduced overall batch processing

time by a third).

Lockheed Martin Aeronautics: HANA Historical Metrics



Required acceleration changes.

SAP best practices and HANA Sidecar experience

showed these problems highly likely to decrease

performance.

Example: a nested Select Single statement within

a Loop construct.

Remediation: use Select … For All Entries outside

the Loop construct. Remember this change

should not change functionality or the results.

Performance Errors



Potential acceleration changes.

These problems may cause a performance

decrease.

Example: a Select * From statement.

Remediation: use defined and specific field list to

retrieve only the data needed for processing.

Any program changes should only accelerate existing

functionality, avoid any functionality changes.


Performance Errors


Used STAD, ST03, ST03N reporting tools to find

potential acceleration candidates.

Produce reports of high database utilization.

Look for instances of high utilization plus greater

than 50% of total processing time consumed in

database query.

Collect baseline performance statistics.

Analyze performance acceleration candidates.

Select top 10 or 25 or n*.

Analyze individual candidates.

Rank candidates for remediation work.


Performance Errors


Use SAT or ST12 traces to analyze candidates for

specific changes needed.

Which tables are being most used.

Under-performing Select statements.

Select Single statements within Loop At logic.

Other Select statements within loop logic.

Possible candidates for joining tables during

queries.

Possible use of Select … For All Entries.


Performance Errors


Use SCI Code Inspector to help find problems.

SAP SCI variant = Performance_Checklist_HDB.

Performance_Checklist_XL includes loop checks.

Potential to use program scans to find specific logic

problems such as Select Single within Loop logic.

Look for effective use of Binary Search logic when

reading tables.

Look for corrections needed for Sort statement used

for Binary Search logic.


Performance Errors


Use of Order By Primary Key without retrieving all

keys fields, combined with For All Entries created

ST22 abend.

Use of Select Single logic within Loop construct trying

to access large table was potential time-out problem.

Found that use of database access within a Loop

construct can definitely degrade HANA performance;

these should be evaluated.


Hard Errors


Development Migration Steps

2. Determine Proactive solutions to mitigate potential errors

3. Fix all possible high risk errors before first ITC

4. Test, Test, Test and then Test Again.


SOH Development Team Migration Tools

SAP SCI Code Inspector (transaction code SCI)

Runtime check monitor (transaction code srtcm)

Please refer to OSS note 1931870 and the online help: http://help.sap.com/saphelp_crmhana/helpdata/en/3e/1365542d8041d9ac472f5496114428/content.ht

m?frameset=/en/ce/30e9746f3241559b8e4bd9d9ee0996/frameset.htm&current_toc=/en/e4/e3e6e3a

8514af2be58552a3ba40b1b/plain.htm&node_id=39&show_children=false

Custom Z syntax search programs

http://help.sap.com/saphelp_crmhana/helpdata/en/3e/1365542d8041d9ac472f5496114428/content.htm?frameset=/en/ce/30e9746f3241559b8e4bd9d9ee0996/frameset.htm&current_toc=/en/e4/e3e6e3a8514af2be58552a3ba40b1b/plain.htm&node_id=39&show_children=false






Don’t wait, Start today: Consider Hana Side Car (gain

experience, fix custom core processes)

Upgrade to more current SAP version if you haven’t upgraded

lately (consider EP7)

Start Custom Code Analysis Now

Proactively Mitigate as many Data Errors, Performance Errors

and Hard Errors as possible before migration

Test 100% of all programs that need to work the day you go live

Ensure a Stable Suite on Hana Migration


Do not expect HANA to return data ordered the same way

Oracle did!!!

Order By Primary Key best used with Select *.

Order By needs all key fields retrieved.

If all key fields not selected, better use Sort By instead of

Order By.

SCI code inspector is not fool-proof, analyze before

making code changes.

SCI may say to add an Order By, but is already a Sort.

Run SCI multiple times, including post-remediation, to

insure all needed changes are found.

Lockheed Martin Aeronautics: Lessons Learned


Test All Programs and Transactions that you want

to work 100%

Ensure that your management and functional

customers truly understand the risks of a true

database migration (it isn’t just an upgrade)

Lockheed Martin Aeronautics: Lessons Learned


Start early with your custom code analysis

Start early with your custom code repairs, be proactive

Test, Test, 100% of programs that need to work at go-live

If possible upgrade to EP7 in a non-SOH environment to test the

effects of the upgrade in code base so that upgrade code related

errors are not confused with SOH migration errors.

Ensure that your management and functional customers truly understand the risks of a true database migration (it isn’t just an upgrade)

BEST PRACTICES


Links:

Best Practices:

http://scn.sap.com/docs/DOC-46714


OSS Notes:

1885926

1912445

1920165

1935918

1931870

BEST PRACTICES








For any questions after this session please reach out to:

Questions??

• Gary Norris

• [email protected]

mailto:[email protected]


THANK YOU FOR PARTICIPATING

Please provide feedback on this session by completing a short survey via the event mobile application.

SESSION CODE: ITM122


SCI parameters:

Appendix: SCI Example


SCI example:



SCI example (cont.):








Lockheed Martin’s SAP Business Suite - ABAP Studio Martin’s SAP Business Suite ... Global Trade Services (GTS) Transportation ... • Development Steps to Migrate SAP ECC to SAP

Documents