ABAP is more than just a programming language, is a powerful development tool if programmers really know its capabilities. Thanks to our close collaboration with SAP in the development of add-on HCM-Pse we know in depth the tools of quality, performance, accessibility, usability and customizing that ABAP contains, differentiating our developments as those who may conduct a typical software factory.
Usually when an analyst is faced with the definition of a program does not take into account the volume of data to address what causes poor performance levels in the custom development. This is the first step toward a collapse of the processes and lousy response time in the system. In turn when a developer is faced with the development of the process, should take into account the do’s and don’ts typical abap code such as the use of parallel cursors instead of nested loops. ABAP Workbench provides powerful tools such as extended code check, code inspector or checkman, compulsories in all the developments made by Provide. Another crucial aspect is the interaction with the database, for its optimization is key the creation of new indexes (and it use depending on the database system) and regeneration and periodic updating of existing ones.
As Internet and Intranet systems have evolved, various code pages have enabled national characters to be displayed, but collaboration on the Web has led to a huge number of language-specific, platform-dependent code pages that must all comply with each other. This compliance is only possible through Unicode – a widespread, accepted international standard that supports virtually all of the world’s scripts. Implementing the Unicode standard enables a single software product or a single web site to be accessed across multiple platforms, languages, and countries without the need for re-engineering. It allows data to be transferred across many different SAP and non-SAP systems without corruption. To meet these requirements, the ABAP Workbench provides tools for Unicode checks to ensure.
SAP has developed an internal accessibility compliance plan to enable individuals with disabilities to use SAP NetWeaver and other SAP solutions. As part of this plan there are several guidelines (activate accesibility in the sap logon and use the tools provided by SAP) that must be taken into account when making customer developments and frequently omitted.
You may find that the standard applications do not offer some of the functionality you need. The R/3 enhancement concept allows to add your own functionality to SAP’s standard business applications without modifying the standard code (make easy to Upgrade). There are two main ways for creating an enhancement:
- Use of available customer exits within the standard applications (customer exits are not available for all programs and screens).
- As part of the enhancement concept, it is possible to enhance ABAP source code, without modifications, using source code plug-ins. You can execute enhancements to implicit and explicit enhancement options. The Enhancement Builder tool for defining explicit enhancement options and for implementing enhancements is integrated in the ABAP Editor.
Source Code Plug-in Technology: Although source code plug-ins are displayed in the same source code as the respective enhancement options, the plug-ins are actually stored in other include programs managed by the Enhancement Builder.
ENHANCEMENTS vs. MODIFICATIONS
Advantages of source code enhancements:
- No modifications.
- No object key is needed.
- Are switchable by the switch framework.
- Fewer upgrade effort.
Disadvantages of source code enhancements:
- Exist only at special source code lines (implicit, explicit).