There is a phase in development cycle when the programmer needs to optimize his final product. This post focuses on those transactions which help developers to analyse, debug and optimize already finished reports and programs.
This part of series is focused on transactions that allow an ABAP developer enhance the original SAP reports with his own modifications. You will find here the list of transactions – possibilities how to extend SAP reports, internal logic within function modules, classes or dictionary objects.
All SAP users, including ABAP developers, has to struggle with remembering short t-codes that has their special purpose. There is no surprise when a developer comes across new interesting transaction that was a missing piece in his ABAP development tools. That’s why I put together these series of various SAP transactions for ABAP developers.
I want to share some great sites and other sources which helped me the most and where you can start with OpenUI5 / SAPUI5. Even though when I started this blog, it was meant to be more about ABAP, but OpenUI5 is future for SAP developers, so why not to play around with new cool technologies.
After the first part of this tutorial, we have created and run an OData service that can write/read data to/from a SAP database table. In this part, I will explain how the frontend of an OpenUI5 application works. Whole source code can be found in my github repository. You will actually see the running demo application at the end of this article.
When you want to hide some URL parameters from users, there is a simple way how to do it. Be aware that more experienced users can read it anyway, so this is not a way how to send confidential data, just to make URL address not readable at first sight.
For this problem, we can use base64 encoding. There are functions in various programming languages for encoding and decoding base64.
var enc = btoa("Hello world");
Instead of Hello world we will get string SGVsbG93IHdvcmxk.