Don't forget to join Upcoming ASUG BITI Webcasts
Catch the replay here BITI: Custom code adaptation for SAP S/4HANA
Plan journey for S/4HANA - what will you do with custom code?
The usual disclaimer applies that things in the future are subject to change.
What is SAP S/4HANA
Challenge for your custom code
Custom code adaptation
Custom code analysis
Summary and Outlook
"SAP S/4HANA is a new product line."
Important to learn how to deal with custom code
On the left see the SAP ERP side and the custom code that was developed on top of it
On the right, tried to provide compatibility views for database tables, but still need to adapt custom code
Red objects from custom code will not run, or crash
Every change is written in the simplification database, documenting impact and guidance for custom code
Can download from SAP and import into ERP system to analyze changes
You can use transaction SYCM to browse the simplification
System conversion at a glance as described in Olga's blog SAP S/4HANA System Conversion – Custom code adaptation process | SAP Blogs
Two phases shown above
Same tools as ERP upgrade - maintenance planner, software update manager but additional requirements such as unicode compatibility
Simplification item check will detect items relevant to convert
Custom code preparation includes custom code evaluation; 60% of code is not used any more productively
SAP recommends UPL to review custom code used - turn on usage analysis for 1 year to find out which custom code is used
Second step, S/4HANA checks, check custom code with simplification database to find changes in S/4HANA world impact your ABAP
After SUM is running, adapt custom code - SPDD, SPAU
Set back to standard
SCMON is recommended, as it is more precise
Recommend use ABAP Test Code Cockpit - 751, 752 release, use remote code analysis
Connect via RFC
Check logic is on central system
Integration of remote scenario
How to set up remote analysis Remote Code Analysis in ATC – Technical Setup step by step | SAP Blogs
Analyze ATC list, what needs to be adapted
After you run ATC, use ATC statistics view, offers better analysis, group findings by criteria, note number, reference object, application component
Code Inspector was previous version; can use code inspector variants in ATC
HANA checks are available
What is the problem here? Field was extended, 18 to 40 characters, and code above can lead to data loss
Need to adapt custom code, instead of custom data types
Code that implied on implicit order
Some functional adaptation can be done here
Quick fixes are available
Link to find out more: ABAP SQL Monitor: Implementation Guide and Best Practices
Which are the expensive SQLs
It provides drilldown capabilities
Summary of what was covered in the webcast (and the related blogs)
Above is a checklist
What you can do today in your SAP ERP - SCMON, ATC, gain skills in ADT and get familiar with S/4HANA technologies
More mass fixes
Screen shot shows how it looks like
Custom code migration Fiori app, integrates usage analysis app, and run ATC; will get more interesting analysis
Plan in Q1 - custom code service in SAP Cloud Platform - can check your on-premise system
Q: If we don't have a Central ATC system, can we accomplish the same checks in our development system?
A: Only if your development system is on SAP NetWeaver >=7.51 and has S4HANA_READINESS check variant installed, and ATC is configured for local use.
Q: SCMON is avaiable from which version?
A: SCMON is available with SAP NetWeaver AS ABAP 7.50 and for lower releases (>=7.00) per ST-PI Add-on.
Q: Is there any list of functional adaptations (like examples in presentation) that we can start doing without simplification DB or ATC check? This will be just to make sure that some portion of current and new custom code in our ECC 6.0 SP6, will adhere to S/4 HANA when we start getting ready for that implementation in 1-2 years.
- It is not that simple J. You need ATC checks in order to detect, if the usage of SAP code in custom code is critical for SAP S/4HANA (you must fix it) or not (you can leave it). Such analysis you get only with ATC checks based on Simplification DB. We recommend to set up ATC checks and check your code during development on regular base for SAP S/4HANA readiness. In this way you would develop “S/4HANA ready” and avoid custom code adaptations after S/4HANA implementation in 1-2 years.
Q: Excellent presentation. I have two questions: 1. Any performance impace of running SCMON in the production system? 2. Can you expand the statement 'consider migrating custom code to SAP cloud platform' (slide 29?
A: 1. The performance impact is not significant: maximum 5% CPU time on the application server
2. If you have in mind some use cases for Cloud with your custom code, you can consider moving such custom code applications to SAP Cloud Platform ABAP Environment
Q: Is Eclipse provided with S4/HANA, or is it an extra?
A: ABAP Development Tools in Eclipse (ADT) must be installed separately from the https://tools.hana.ondemand.com/#abap
Q: I remember hearing in SAP TechEd 2018 that ATC will come on SAP cloud platform to use instead installing it in landscape for system readiness check. Is there any timeline for that?
A: This is Custom Code Analysis Fiori App (see slides 31, 32 of the presentation), which is expected to be delivered on SAP Cloud Platform within Q1/2019
Q: Thank you Olga. Do ONLY need to use Eclipse based ABAP IDE connected to HANA system for auto correct ? That is it is not available in ABAP stack on ECC ?
A: Currently we provide Eclipse-based auto corrections only for SAP S/4HANA use cases, therefore you need SAP S/4HANA system. It is still possible to correct custom code with ABAP Workbench (SE80) but there are no auto corrections (see slide 22 of the presentation)
Q: We have activatd UPL in ECC this time. Is it possible to migrate UPL-data to SCMON? We want to analyse all data in SolMan in one area.
A: Generally the Solution Manager 7.20 collects either UPL or SCMON data depending whether the connected system is capable of SCMON or UPL. It is also possible to extract the SCMON data into Solution Manager BW. The existing already collected UPL data get also imported into Solution Manager BW and simply mixed with the new SCMON data.