Slides of my talk at SAP d-code && TechEd 2014 in Berlin about introducing ABAP in Eclipse into productive teams and environments.

1. SAP ABAP Development Tools
FROM SANDBOX TO REAL PROJECTS

2. So we have a new development environment…
… why should I as an ABAP developer have a closer look?
Martin Steinberg | EXP17795 | SAP d-code 2014

3. Technical variety
is increasing

4. Martin Steinberg | EXP17795 | SAP d-code 2014
Technical variety
is increasing

5. So much for the developers –
… but why should a company enable those tooling?
Martin Steinberg | EXP17795 | SAP d-code 2014

6. Making your developers happy 
Martin Steinberg | EXP17795 | SAP d-code 2014

7. Sounds good -
… but how do to start?
Martin Steinberg | EXP17795 | SAP d-code 2014

8. Martin Steinberg | EXP17795 | SAP d-code 2014
Developer-driven
Curious
early
adopters
Co-
operates
with SAP
Basis guys
Uses ADT
beside the
ABAP
Workbench
Shows
others
Trys out
the new
stuff
- daily work
- projects

9. Martin Steinberg | EXP17795 | SAP d-code 2014
Developer-driven
trying
showing,
feedback
teaching
A good starting
point for creating a
culture of
knowledge
exchange
Learning by
teaching
e.g. concept of
lectures and hands-
on-sessions

10. Martin Steinberg | EXP17795 | SAP d-code 2014
Organization-driven
• Developer base willing
to use ADT will grow
continously as they see
the advantages and
other colleagues using it
• Risk of uncontrolled
growth
Increasing
attention
• Authorizations (e.g. AMDP)
• Architecture (e.g. code
pushdown) rules & guides
• „best-fit“ into your technology
strategy (e.g. SAPUI5, BOPF, SAP
HANA…)
• training
• hardware requirements (RAM)
Formalization
needed • Desktop infrastructure
(e.g. VDI, local install…)
• Pre-configured Eclipse,
e.g. integration of other
plugins like MyLyn or
own ones
• Local update site
Roll-out
planning

11. But consider these two rules:
Martin Steinberg | EXP17795 | SAP d-code 2014

12. Do not force anyone to use ABAP in Eclipse
Martin Steinberg | EXP17795 | SAP d-code 2014

13. Do not prevent anyone to use ABAP in Eclipse
Martin Steinberg | EXP17795 | SAP d-code 2014

14. Co-existence and respect are important.
Martin Steinberg | EXP17795 | SAP d-code 2014

15. A short summary
• Enable your developers
• co-existence is important
• allow innovation and new approaches
• Be well prepared
• Eclipse strategy by your company (e.g. non-SAP depts, SAPUI5, SAP HANA Studio…)
• Pre-configured Eclipse with local update-site
• authorizations and OSS-notes
• Slightly integrate
• Adjust your development and architecture guidelines (e.g. for ABAP Doc, code-
pushdown,etc.)
• Integrate ADT into your development process by using ADT SDK, or 3rd party tools

16. Some links
SCN-space ABAP in Eclipse
http://scn.sap.com/community/abap/eclipse
AiE plug-in for transport of copies
built with ADT SDK by Christian Drumm
available on github
blog on scn: http://bit.ly/1xnFE2T
AiE plugin for SAPlink
by Uwe Fetzer, Gregor Wolf, Abdulbasit Gulsen, et al.
https://www.assembla.com/spaces/saplink-for-abap-in-eclipse/wiki

17. Related sessions
hands-on-sessions
DEV265: Building an End-to-End App from SAP HANA via ABAP to SAP Fiori
DEV165: Code Better with ABAP in Eclipse
DEV264: Custom ABAP Code – Get Ready for SAP HANA
lectures
DEV201: Overview of ABAP 7.4 Development for SAP HANA
DEV204: DEV264: Custom ABAP Code – Get Ready for SAP HANA
DEV202: Core Data Services - Next Generation Data Definition and Access on SAP HANA
mini-codejam
CJ626: ABAP in Eclipse

18. MARTIN STEINBERG | SAP MENTOR
Thank you very much for your attention and have a pleasant
SAP TechEd && d-code
Martin Steinberg | EXP17795 | SAP d-code 2014
sbg.martin@gmail.com
@SbgMartin