In this article, I will show a practical example of self-association in CDS. You will learn how to define a simple hierarchy in your CDS and how to consume it in your ABAP code.
In his latest book “Enterprise Continuous Testing: Transforming Testing for Agile and DevOps” Wolfgang Platz mentions that API testing is the future of automated testing as it is the only part of enterprise system testing where in reality you can automate >85% of test cases.
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.
Are you using Micro Focus ALM (formerly HP ALM/Quality Center) to manage application delivery, lifecycle and testing in your company?
We have great news for you – Int4 IFTT can be easily integrated with ALM without installing additional components or libraries. Test execution is automated using VAPI-XP test script and doesn’t require Unified Functional Testing (UFT) to be integrated with ALM.
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.
Recently I encountered a basic router scenario. However the information I could use as a condition was not included in the message itself. I had to pass it to CPI, but didn’t want to enrich the message and mess it up. I figured out that custom header would be the great solution, however as it occurred, it wasn’t so easy (now it is of course).
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.