sap abap development tools - introduction in productive environments (exp17795, d-code 2014)
TRANSCRIPT
SAP ABAP Development ToolsFROM SANDBOX TO REAL PROJECTS
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
Technical varietyis increasing
Martin Steinberg | EXP17795 | SAP d-code 2014
Technical varietyis increasing
So much for the developers –
… but why should a company enable those tooling?
Martin Steinberg | EXP17795 | SAP d-code 2014
Making your developers happy
Martin Steinberg | EXP17795 | SAP d-code 2014
Sounds good -
… but how do to start?
Martin Steinberg | EXP17795 | SAP d-code 2014
Martin Steinberg | EXP17795 | SAP d-code 2014
Developer-driven
Curiousearly
adopters
Co-operateswith SAP
Basis guys
Uses ADT beside the
ABAP Workbench
Shows others
Trys out the new
stuff
- daily work- projects
Martin Steinberg | EXP17795 | SAP d-code 2014
Developer-driven
trying
showing, feedback
teaching
A good startingpoint for creating a culture ofknowledgeexchange
Learning byteaching
e.g. concept oflectures and hands-on-sessions
Martin Steinberg | EXP17795 | SAP d-code 2014
Organization-driven
• Developer base willingto use ADT will growcontinously as they seethe advantages andother colleagues using it
• Risk of uncontrolledgrowth
Increasingattention
• Authorizations (e.g. AMDP)
• Architecture (e.g. codepushdown) rules & guides
• „best-fit“ into your technologystrategy (e.g. SAPUI5, BOPF, SAP HANA…)
• training
• hardware requirements (RAM)
Formalizationneeded
• Desktop infrastructure(e.g. VDI, local install…)
• Pre-configured Eclipse, e.g. integration of otherplugins like MyLyn orown ones
• Local update site
Roll-out planning
But consider these two rules:
Martin Steinberg | EXP17795 | SAP d-code 2014
Do not force anyone to use ABAP in Eclipse
Martin Steinberg | EXP17795 | SAP d-code 2014
Do not prevent anyone to use ABAP in Eclipse
Martin Steinberg | EXP17795 | SAP d-code 2014
Co-existence and respect are important.
Martin Steinberg | EXP17795 | SAP d-code 2014
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
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
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
MARTIN STEINBERG | SAP MENTOR
Thank you very much for your attention and have a pleasantSAP TechEd && d-code
Martin Steinberg | EXP17795 | SAP d-code 2014
@SbgMartin