How to check if your assets have been created by the SOAP API in UPA?

[wallace_yao]

Introduction

In S/4HANA Private Cloud with Universal Parallel Accounting (UPA), Asset Accounting has published quite a few APIs. Some of them are asynchronous SOAP APIs for users to create and change asset master records. It is because they are asynchronous that right after calling those APIs, you cannot know whether their assets have been created or changed successfully. You have to call the comfirmation services to check the status. (See more details about the APIs from Asset Accounting in UPA in this official help documentation.)

Alternatively, you can check it manually. This short article describes this tool in details. (For more information about Asset Accounting as of S/4HANA 2022, please refer to this article.)

Monitoring Tool

This monitoring tool in the backend has the t-code SRT_MONI. It is especially helpful for customers with backend access. Here are the steps.

• Start SRT_MONI, and enter your interested time frame in the selection screen
• You will get a list of all messages occured in the system within that time frame.
• To get results from Asset Accounting only, filter it on the column 'Sender Interface Namespace', by the service name 'http://sap.com/xi/FI-AA'. (You are looking at the outbound confirmation service. So, AA is the sender.)
  
• Now, you get a shorter list.
• The green and red lights only tell if the system has been configured with a message recevier. They do not really tell us if the APIs have been executed successfully or not. A green light may contain an error from the API, while a red light may show a successful information from the API.
  
• Click on the individual message IDs to check out the concrete information.
• Click on a message ID, you will come to the following screen with concrete errors about why the asset could not be created.
  

No Messages At All?

In SRT_MONI, sometimes it can happen you cannot find any message from the outbound confirmation service at all, even after some time after calling the SOAP API. This often means your request does not trigger the SOAP API. 

One hint is to check the message ID of your sending request. Has the same ID been used in a prior request to that SOAP API already? If it is the case, this should be the root cause. The UUID should be unique in each request.