An insider s guide to writing robust, understandable, maintainable
Short summary:
Our guidelines cover formal as well as conceptual. rules for ABAP programs. The same holds for Web Dynpro ABAP versus classic ...
Long summary:
An insider s guide to writing robust, understandable, maintainable, state-of-the-art ABAP programs: Part 1 fundamental rules and formal criteria No portion of this publication may be reproduced without written consent. 3 Put your integrated WebSphere environments into production fast You know the situation you need to accomplish some given task, and youre going to need to write some ABAP code to do it. If youre new to ABAP, you research the available ABAP language documentation and you are very likely overwhelmed by the wealth of information and possibilities you find. How do you approach your search for ABAP guidance? Do you delve deeper into the subject and try to find out the best way to do it, or do you just look for the first snippet of code maybe in existing programs that seems appropriate and simply cut and paste? And if youre an experienced ABAP developer, youll probably solve your task in the same way you have done it for years now. And in both situations ABAP neophyte or graybeard in the end youll probably be satisfied if your coding somehow just works. Why should you care about alternatives or new features of ABAP if your primary task has been fulfilled? This article is intended to provide an answer to this question. The need for an ABAP programming guide as presented here stems, for the most part, from the fact that ABAP is a vibrant, evolving language. Although you may have been able to program in ABAP for almost 30 years, the development of the language itself has always continued in parallel. New developments in ABAP continue either through additions to the existing feature set or replacement of (and An insiders guide to writing robust, understandable, maintainable, state-of-the-art ABAP programs Part 1 fundamental rules and formal criteria by Andreas Blumenthal and Horst Keller (Full bios appear on page 26.) Horst Keller Knowledge Architect, SAP NetWeaver Application Server ABAP, SAP AG Andreas Blumenthal Vice President, SAP NetWeaver Application Server ABAP, SAP AG Dedication This article is dedicated to the memory of Axel Kurka, who for many years pushed ahead SAP technology, and especially ABAP technology, in his roles as Developer, Development Manager, Product Manager, and last but not least as Dr. ABAP in the SAP Technical Journal. Axel died much too early in August 2005, but his actions have influenced SAP technology forever. This article originally appeared in the January/February 2006 issue of SAP Professional Journal and appears here with the permission of the publisher, Wellesley Information Services. For information about SAP Professional Journal and other WIS publications, visit www.WISpubs.com. SAP Professional Journal January/February 2006 4 www.SAPpro.com ©2006 SAP Professional Journal. All rights reserved. thereby making superfluous or obsolete) current features. The issue of superfluity and obsolescence is often especially troublesome for programmers new to the world of ABAP. For instance, why are there two ABA ...
Source: www.sdn.sap.com
Related
The Official ABAP Reference, Horst Keller. The Official. ABAP. ®.
Reference ...... the ABAP Reference. This
new, second edition reflects the complete.
scope of ABAP elements produced ...,
more
The ABAP Quick Reference, ding into the environment—please refer
to the The Official ABAP. Reference Book.
This holds true particularly for the
terminology used ...,
more
XML Data Exchange using ABAP, exception handling, you should refer to
The Official ABAP. Reference ( Horst
Keller: SAP PRESS 2004 ). CALL
TRANSFORMATION transformation ...,
more
