Copying and pasting ABAP report programs from one system to another normally leaves one obvious casualty: selection screen texts. Here I show you how to include them in the source of a program to make them portable.
The ABAP platform provides a centralised model of development that solves several of the challenges of mainstream business software development practices.
In a previous post I showed you how to build a SOAP message payload search using a SAP HANA fulltext index. Here I will show you how to create an ABAP source code search using the SAP HANA database (though it should work with any database that has a fulltext index feature by tweaking the SQL statements).
I thought it might be worthwhile sharing some of the tips and tricks I have learned over the years. This technique is one I am particularly fond of, as I found how to do this after scratching around in system programs for a long time.
So I have been busy with the ABAP Lisp interpreter. The main focus now is the integration to ABAP. When I first started out with it, I had a vague idea in my head of what I wanted the interpreter to be able to do.
Since announcing the ABAP Lisp interpreter on SCN last week, I have made a few commits to the ABAP LispÂ repo. I was rather chuffed to get some positive response on the article, and it does provide a bit more motivation to keep working on it.
One of the problems ABAP developers face from time to time is the need to store arbitrary values for processing. These values do not always justify creating a new table, and there is no convenient place to store such values.
We have had the capability to process JSON in ABAP for some time now (refer to this blog post for an introduction). The problem is that it does not satisfy all the use cases without some effort and, therefore, there is still some scope for writing a custom JSON parser in ABAP. I recently wrote one again.
After having played around with Elasticsearch for indexing PI payloads and indexing ABAP source code, and especially after seeing the new (and now just-released) Kibana 4, it occurred to me that Elasticsearch would actually be great for business intelligence reporting.
Sometimes source code modules get very big. You can argue that this should never be the case, if you modularize your code properly, but the fact is that they do. And when they do, they sometimes become difficult to read.