Well, actually it is but in slightly different approach. We all know what ALPHA conversion is and how it looked like before ABAP 7.4 – unfamous CONVERSION_EXIT_ALPHA_INPUT and CONVERSION_EXIT_ALPHA_OUTPUT. There may be some newbies among us so let’s remind what it does – if you want to perform SQL query in ABAP very often you need to convert your data to internal format (or in the opposite direction when you take care for user experience and want to get rid of leading zeros). In the ancient times you would do something like this:
It is very common when system-to-system data replication should occur according to a particular schedule. Scheduled jobs define recurring tasks that run in the background. We will provide a scenario where we automatically run the Flowgraph which was created in the previous blog.
SAP PI/PO is equipped with a set of standard APIs which among many other things allow the maintenance of Integration Directory objects. This API can save you a big amount of time in certain circumstances and it is really good to know it’s usage.
In Int4 IFTT installations with large number of test cases or test cases with big payloads speed of data growth can become a challenge.
To reduce the data footprint of test cases database we are introducing payload compression.
This feature, available from Int4 IFTT SP12, transparently compresses new test cases payload at saving time and decompresses it on demand when payload is displayed or used during test case execution. Read More
In this short blog, I would like to show you how to use a CASE expression in the new Open SQL.
I have learned about it from my colleague, Michal Jakubowicz, who recently conducted a full 4-days workshop about ABAP Programming for SAP Hana.
The CASE expression in new Open SQL is available on ABAP 7.4 SP08. In this blog, we will focus on the scenario, in which we will select different columns in one select statement, based on the content in another column.
According to the best practices, flowgraphs have names with prefix FG_ and include runtime behavior and subject area:
As you remember in order to create test cases you had to create configuration object manually per tested interface, where you would define all rules and parameters. Not anymore! As of Service Pack 11 release 006 you will be equipped with SAP PO Wizzard which would handle this task automatically.
SAP Process Integration is the most common SAP middleware platform so far. Its widely used to connect various SAP and non-SAP systems, providing a single point of integration. According to SAP PI dual stack installations (ABAP and JAVA) will be supported by SAP only until the end of 2020. Very likely in the next couple of years there will be an increase in the number of SAP PI migration projects as SAP XI/PI dual stack installations will need to be migrated to a single stack JAVA only SAP PO architecture.
Since SP11 integration with change management software is available. Int4 IFTT will create automatically incidents regarding particular test case, update their status, close existing and creating new ones. You will be also enabled to manage incidents directly from test cockpit manually.
With this feature Continuous Testing implementation is easier and there is not chance to overlook the defect. Check this blog to learn more!