Standard architecture of Smart Data Integration product consists of three main parts:
a) Hana Index Server
b) Data Provisioning Server
c) Data Provisioning Agent
Setting up an API test in Int4 IFTT for an SAP PO scenario with a message split can be a bit tricky due to the fact that message processing staging can be set up in a different way for each ICO. In case we want to regression test our SAP PO scenario we may need to consider the following steps:
Have a look at the picture above. What if, this huge jam was a result of a failing interface to or from the warehouse. Whether the root cause of the error is in communication, mapping, or anything else, you could quickly find out using the interface monitors, like the ones provided by SAP PI or SAP AIF. But on the other hand, from those monitors you would not see the implication that these errors have on the company’s business processes. Yes, in this case probably looking out the window would be enough😊 But, it is not always that obvious.
Some weeks ago our company took participate in the Poznan Business Run. This is almost a tradition for our company, because we are part of this charity event every year!
The event was quite huge – over 3500 runners (700 teams) competed in this race! We are proud of our two teams, because both teams completed race as the fastest 30% of all teams!
As you know, int4 love events. There’s another opportunity to meet our team in person at SAP Teched Barcelona in 2018 (23rd-25th October). We will be presenting our SAP certified automated regression testing and service interface virtualization software – IFTT.
Thanks to int4 IFTT you can fully automate testing of all your SAP PO/ SAP AIF/ SAP CPI/IDOC flows in both the middleware and at the SAP backend system. If you want to learn more visit our P01 booth ! Moreover, we have a suprise for you there- our experts will be available for you at our booth everyday from 13:00-14:00 to answer all of your SAP PI and SAP AIF related queries.
Recently, during my last AIF project, we encountered a challenge and we wondered if it is possible to save the payload of the response message for the outbound synchronous proxy interface in SAP AIF. We found a solution, but since that time many of our colleagues working with SAP AIF encountered the same challenge and that was the reason why we decided to write this blog with our proposed solution. This blog is written in cooperation with my colleague, Krzysztof Łuka.
Imagine the situation when you have to configure the outbound synchronous proxy interface in SAP AIF and you have to save the content of the request and the response messages. If it comes to the content of the request message – there is no problem. You may encounter a challenge if you want to save also the response of the synchronous message.
In this blog we will focus only on the SAP AIF part – we won’t describe how to create objects on SAP PO side. We will use the ABAP report to send the request message with the message ID from ERP system to SAP PO. We expect to receive back in the synchronous response the SAP PO message key that is related to the message ID we sent in the request.
This is how sample synchronous request message looks like (with the message ID):
And below you can see the synchronous response message with message key from the above request:
First, you have to generate and activate Service Consumer that will be used in order to send the request from ERP to SAP PO.
Then you have to copy the name of the class for the generated Service Consumer. In our case, it is /INT4/CO_SI_O_GET_MESSAGE_LIST.
This class is necessary in order to create SAP AIF interface.
In next step go to AIF Customization ( /AIF/CUST transaction ) and go to Interface Development -> Define Interfaces. We will have to create new entries: one interface for the request message and the second interface for the response message.
First, create a new entry for the request message. Type OPRGMSG001 as the interface name and 1 as the interface version.
Then Provide your Service Consumer class (in our case it’s /INT4/CO_SI_O_GET_MESSAGE_LIST ) in the class Proxy Class Outbound field and choose the proper method that will trigger sending a message to PO.
Once you provide proxy class outbound – automatically RAW Data Structure and Record Type in Raw Structure should be filled. Please provide the same structure in SAP Data Structure as was filled into RAW Data Structure and mark Move Corresponding Structures checkbox, as it is visible on the screen below:
As a next step, we have to create another entry in Define Interface node. This time we have to do it for the Response Message.
Add a new entry with Interface Name: IPRGMSG001, interface version: 1. In Proxy Class Inbound provide the class of your Service Consumer. In our case, it is /INT4/CO_SI_O_GET_MESSAGE_LIST. Then click enter and again your Raw Data Structure should be filled automatically. Right now we are interested in the response message and because of this, we have to provide the type of the structure that is used as the exporting parameter of our class for the service consumer. In our case it is /INT4/MT_GET_MSG_LIST_RES as it’s visible on the screen below:
Use the same structure in SAP and RAW structure and mark Move Corresponding checkbox. Please also make sure, that you have chosen specific proxy method as shown on the screen below:
Right now we have to make sure, that proper Engine is used for both of our interfaces. Go to AIF Customization (transaction /AIF/CUST ). Then open Interface Development -> Additional Interface Properties -> Specify Interface Engines node and set for both interfaces Proxy as Application Engine, XML as Persistence Engine, AIF Index Tables as Selection Engine and AIF Application Log as Logging Engine.
The last step is to create ABAP Report, that will trigger sending the message from ERP to SAP PO.
Create a new program in transaction SE38.
In order to make this program simpler – we will hardcode the message ID that will be sent to SAP PO. We are using function module /AIF/SEND_WITH_PROXY to send the data out from ERP. We have to provide a namespace, interface name and interface version of our interface we created in AIF. In this step, you have to provide an interface used for the request message ( ‘OPRGMSG001’).
In the RESP_SAP_STRUCT changing parameter we have to provide a structure of the response, that we used in the IPRMSG001 SAP AIF interface. Then in the SAP_STRUCT changing parameter, we have to provide filled with the data structure for the request interface.
In the end, we have to use method /AIF/IF_PERSISTENCY_ENGINE~UPDATE of class /aif/cl_persist_engine_xml in order to store the response payload in SAP AIF. While using this method we have to provide details of the second interface in SAP AIF, that will store the response message.
Please see the whole code snippet for this program below:
CONSTANTS: lc_ns TYPE /aif/ns VALUE 'ZDEMO', lc_ifname TYPE /aif/ifname VALUE 'OPRGMSG001', lc_ifver TYPE /aif/ifversion VALUE '1', lc_ns_resp TYPE /aif/ns VALUE 'ZDEMO', lc_ifname_resp TYPE /aif/ifname VALUE '1PRGMSG001', lc_ifver_resp TYPE /aif/ifversion VALUE '1'. DATA: lv_msguid TYPE sxmsmguid, lv_error_msg TYPE string, ls_request TYPE /int4/mt_get_msg_list_req, ls_sap_resp TYPE /int4/mt_get_msg_list_res, ls_xi_data TYPE /aif/xmlparse_data, lt_bapiret TYPE TABLE OF bapiret2, lo_data TYPE REF TO data, lo_xml_pers TYPE REF TO /aif/cl_persist_engine_xml. ls_request-mt_get_msg_list_req-message_id = 'fd9b26f7-7456-11e8-a1b1-00000069c71a'. ls_request-mt_get_msg_list_req-archive = ' '. IF ls_request-mt_get_msg_list_req-message_id IS NOT INITIAL. CALL FUNCTION '/AIF/SEND_WITH_PROXY' EXPORTING ns = lc_ns ifname = lc_ifname ifversion = lc_ifver appl_log_function = 'AIF_SEND_WITH_PROXY' do_commit = 'X' iv_persist_xml = 'X' IMPORTING ximsgguid = lv_msguid TABLES add_return_tab = lt_bapiret CHANGING resp_sap_struct = ls_sap_resp sap_struct = ls_request error_string = lv_error_msg EXCEPTIONS persistency_error = 1 status_update_failed = 2 missing_keys = 3 interface_not_found = 4 transformation_error = 5 general_error = 6 OTHERS = 7. ENDIF. "Persist response message GET REFERENCE OF ls_sap_resp INTO ls_xi_data-xi_data. ls_xi_data-msgguid = lv_msguid. ls_xi_data-ns = lc_ns_resp. ls_xi_data-ifname = lc_ifname_resp. ls_xi_data-ifver = lc_ifver_resp. CREATE OBJECT lo_xml_pers. IF lo_xml_pers IS NOT INITIAL. GET REFERENCE OF ls_xi_data INTO lo_data. TRY. CALL METHOD lo_xml_pers->/aif/if_persistency_engine~update CHANGING cr_xmlparse = lo_data. CATCH /aif/cx_error_handling_general . ENDTRY. ENDIF.
Right now we can run the report. If the proxy call was successful we should see a new entry in transaction /AIF/ERR with the payload in the outbound interface OPRGMSG001 with the request message and new entry in with the payload of the response message in interface IPRGMSG001.
Below you can see the request message with the content. Message text automatically contains the information in which interface the response was processed:
In order to make sure that the response is visible we’ll go to the second interface for the response message. As you can see on the screenshot below – response message with the payload is there:
How do you like this approach to save the message payload? Please let us know in the comments!
PS. I have a big pleasure to invite you on SAP Teched at Barcelona that will take place in October. As the INT4 team we will be one of the exhibitors and we will be presenting our SAP certified automated regression testing and service interface virtualization software – IFTT.
If you want to learn more about this tool or if you want to ask me or Michal Krawczyk SAP AIF or SAP PO related question we will be available for you at our booth everyday from 13:00-14:00 everyday! See you there!
We’re happy to announce that we’ve been approved to become an official exibitor at SAP Teched Barcelona in 2018 (23rd-25th October).
We will be presenting our SAP certified automated regression testing and service interface virtualization software – IFTT.
With the use of int4 IFTT you can fully automate testing of all your SAP PO/AIF/CPI/IDOC flows in both the middleware and at the SAP backend system. All will happen without source system access as we provide an unique service interface virtualization concept without the need for additional hardware or software.
With this great news we also have a suprise for you. Two of our experts and SAP Press book authors SAP Mentor – Michal Krawczyk and Mateusz Nowak will be available for you at our booth everyday from 13:00-14:00 to answer all of your SAP PI and SAP AIF related queries. Please come to our booth to have a chat about SAP integration anytime during the day and have an amazing teched experience.
I can bet, that if you use SAP AIF you are familiar with AIF Monitoring and Error Handling (transaction /AIF/ERR ). Here, we can monitor and perform actions for specific interface. In addition to this transaction SAP AIF also gives us opportunity to monitor all interfaces in one place. In this blog we are going to set up interface in SAP AIF Interface Monitor (AIF/IFMON transaction). Let’s imagine the situation, that you are responsible for monitoring several interfaces. Monitoring interfaces in /AIF/ERR transaction is very helpful, although it still can be time consuming if you just want to have a quick overview what is going on in all interfaces you are responsible for.
Nowadays, every single day we have to cope with many different interfaces and technologies. The number of the interfaces that we have to carry on is constantly growing.
When you use SAP AIF (SAP Application Interface Framework) you can monitor all interfaces from one place and that saves a lot of time!
That’s the reason why some of our customers use very ofter SAP AIF only for the monitoring purposes. Today I would like to show you how quickly you can enable monitoring IDoc interfaces in SAP AIF in less than 3 minutes!
Please let us know if you like such short videos!