SAP LBN-GTT: How to solve GTTMSG idocs with error message EA391 – No IDoc saved...
source link: https://blogs.sap.com/2022/04/19/sap-lbn-gtt-how-to-solve-gttmsg-idocs-with-error-message-ea391-no-idoc-saved-in-target-system-soap-http/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
SAP LBN-GTT: How to solve GTTMSG idocs with error message EA391 – No IDoc saved in target system (SOAP HTTP)
Hi colleagues,
I am writing this article to help some SAP Consultants around the world, like me, implementing SAP LBN-GTT.
After we finished main settings related to GTTMSG idoc (responsible to send combined Events Messages and Tracked Processes from SAP ERP to SAP LBN-GTT), we noticed that they failed in status 02 (Error passing data to port) with Error Message EA391 – No IDoc saved in target system (SOAP HTTP), during our tests.
Log from WE05 transaction
Solution:
After we internally consult with SAP, we received the information that RFC User (under Logon & Security tab) must be the same SAP LBN-GTT “Technical User ID” configured in Manage Business Profile App in LBN side, as highlighted in yellow below:
SAP LBN-GTT Manage Business Profile App
SM59 transaction.
After we perform the adjustment in this configuration, we were able to successfully process GTTMSG idocs and information from SAP ERP arrived at SAP LBN-GTT side.
SAP LBN-GTT View Logs App.
I hope this information can help you in case you face this issue in the future.
Thanks! 
“The more we share, the more we have” (Leonard Nimoy)
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK