Guidelines for Testing Journal Entry API with SOAPUI and Checking Response Message
In this blog post you will learn how to test Journal Entry APIs with tool SOAPUI and check their response message.
To learn more about Journal Entry APIs at Guidelines for API Journal Entry – Post.
1 How to Install SOAPUI
I use SOAP Open Source for testing, you can download the latest version and Installation Guides via the URL below.
Latest SoapUI Open Source Downloads:
SoapUI Installation Guides:
2 How to Test Synchronous API with SOAPUI
- Log on to the SAP Fiori launchpad as Administrator.
- Under Communication Management, choose the Communication Arrangements tile.
- Open your communication arrangement, and download the WSDL for the corresponding Inbound Services. Read more at Guidelines for configuring Communication Scenario Finance – Posting Integration (SAP_COM_0002).
4. Open SOAPUI and click New SOAP Project
5. On the New SOAP Project screen, click “Browse” to find your WSDL, then click OK.
- Open Request and input your payload into the request.
- Click Auth, and choose Add New Authorization
- On Add Authorization screen, choose Basic then click OK
- Input your communication user and password, which are maintained in Communication Arrangement
- Click to submit request, then response will display in the right window
3 How to Test Asynchronous API with SOAPUI
- Please follow the procedure 1 to 9 in Paragraph 2.
- Click WS-A in SOAPUI request, and check Enable WS-A addressing and Generate MessageID
- Remember the ID in the structure of MessageHeader. It is used to identify your request in Message Dashboard (Message Dashboard is introduced in the subsequent section). You could change this ID as a meaningful text.
- Click to submit request. As it is asynchronous API, response does not display in the right window. It need to be checked in Message Dashboard.
4 How to Check Response Message
4.1 How to Check Response Message for Synchronous API
- For synchronous API, it can check response message directly in SOAPUI in most cases. However, because of some typos or missing of necessary substructure or fields in payload, response like
‘Web service processing error; more details in the web service error log on provider side (UTC timestamp 20181206081109; Transaction ID 7317F91553620380E005BF87F1D17D3D) The error log can be accessed by service provider from SAP backend’
is returned. In this case, it is requested to access SAP backend to check the error message.
For cloud customer, they need to ask for assistance from SAP Support to check the error message in SAP backend.
- Log on to the backend system, and enter Transaction SRT_LOG
- On Select Error Log Entries screen, it is suggested to search by Transaction ID stated in response, such as Transaction ID 7317F91553620380E005BF87F1D17D3D or fill User Name to narrow down the result. User Name is the backend user of the communication user
- On Web Service Utilities: Error Log screen, the error entries are listed
4.2 How to Check Response Message for Asynchronous API
- For asynchronous API, it can check response message in Fiori App Message Dashboard. Pease follow the subsequent procedure to enable API monitor in Message Dashboard
- Log on to the SAP Fiori launchpad as Administrator. Make sure Administrator is assigned with role SAP_BR_CONF_EXPERT_BUS_NET_INT in advance.
- Under Message Monitoring, choose Assign Recipients to Users tile
- Click to assign AIF Recipient to business user
- Enter the Recipients. It supports to choose them from drop down list.
FINAC_RECT_JOURNALENTRY_IN for Journal Entry – Post (Asynchronous)
FINAC_RECT_JECHANGE_IN for Journal Entry – Change (Asynchronous) and its outbound service
FINAC_RECT_JECLEARING_IN for Journal Entry -Clearing (Asynchronous)
6. Assign business user with the role which includes business catalog SAP_CA_BC_COM_ERR_PC
7. Log on to the SAP Fiori launchpad with business user.
8, Under Message Monitoring, choose Message Dashboard tile
9. Set the period of dates, then click message number at the corresponding interface
10. By means of ID to address the message log
5.1 Typo in payload
- Some typos in payload structure could be identified by using Validate of SOAPUI. Please use this function to make sure there is no such kind of error in payload.
- Some warnings like those in screenshot below can be ignored