Skip to Content

Let me preface this post with the comment that most of my documentation is mostly geared towards Basis admins with little PI experience.  I try to put together common issues that I see, make general directions on how to resolve that particular type of issue and share with the rest of the people with whom I work.  this document is also for a non-production system.  In a production environment you would need to be working with your function team before resending an IDoc with WE19.

One of the issues that I have encountered in our environment with custom IDocs is that we get a help desk ticket or issue from our project team saying that the IDocs are not getting to their destination.  When you check in sending system everything looks fine (e.g. in WE05 the status is 03 or green light).  This means that the IDoc is leaving ECC correctly but somewhere in PI there is an issue.

To start the troubleshooting, in the sending system grab an IDoc number of an IDoc having an issue.  Once you have that IDoc number, in your PI system go into IDX5 and search for that IDoc number, in my example below I used IDoc number 487746.

Capture.PNG

Ensure you change the date range to account for the date of the IDoc.

Next you’ll see the correlating XML message of IDoc for which you searched.  Double click on that entry to bring up the XML data.

Capture1.PNG

In the XML message you can se the error in the bottom right window.

Runtime exception occurred during application mapping
com/sap/xi/tf/_MM_ZOTM_TPSDLS01_Stage_Roadnet_Del~;
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target
element
/ns0:MT_XMLSQL_Roadnet_Delivery/StatementName/dbTableName/access/G~

Capture2.PNG

Typically when you see an application mapping error this is caused by someone changing the IDoc structure.  With custom IDocs ECC and PI do not update the mappings automatically when the structure is changed.  This has caused issues for us numerous times.  It’s a lot of coordination between your ABAP and PI developers as well as good communication between those teams and the Basis team.

So from here we go back into ECC and run transaction BD64.

Go to the environment menu then generate partner profiles.

Capture3.PNG

Select the PI Model view, in this case QP1CLNT001

Capture4.PNG

Click Execute

Capture5.PNG

Run transaction WE19 and enter the IDoc number for which you previously searched.

Capture6.PNG

Click Execute the click Standard outbound processing on the next screen.

Capture7.PNG

Click the green check box.

Capture8.PNG

Now when you check in your PI system in SXMB_MONI you should see the newly created IDoc has been processed without error.

Capture10.PNG

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Tejas Bisen

    Hi Tony,

    Very Informative Blog.

    Deleting the IDoc Metadata from IDX2 in SAP PI and then reprocessing the IDoc from ECC system should have the same effect.

    Thanks & Regards,

    Tejas Bisen

    (0) 

Leave a Reply