Scribd
Upload
174 views

Mapping Errors - SAP Blogs PDF

Uploaded by

Sujith Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
174 views

Mapping Errors - SAP Blogs PDF

Uploaded by

Sujith Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

7/6/2019 Mapping Errors | SAP Blogs

Products
Products Industries
Industries Services and Support
Services Support Training
Training Community
Community Developer
Developer

Partner
Partner About
About

 
Ask a Question Write a Blog Post Login

Former Member
June 17, 2013 3 minute read

Mapping Errors
Follow RSS feed Like

1 Like 2,192 Views 1 Comment

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 ne (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.

https://blogs.sap.com/2013/06/17/mapping-errors/ 1/7
7/6/2019 Mapping Errors | SAP Blogs

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.

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~“

https://blogs.sap.com/2013/06/17/mapping-errors/ 2/7
7/6/2019 Mapping Errors | SAP Blogs

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 pro les.

Select the PI Model view, in this case QP1CLNT001

https://blogs.sap.com/2013/06/17/mapping-errors/ 3/7
7/6/2019 Mapping Errors | SAP Blogs

Click Execute

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

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

https://blogs.sap.com/2013/06/17/mapping-errors/ 4/7
7/6/2019 Mapping Errors | SAP Blogs

Click the green check box.

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

Alert Moderator

Assigned tags

https://blogs.sap.com/2013/06/17/mapping-errors/ 5/7
7/6/2019 Mapping Errors | SAP Blogs

SAP Cloud Platform Integration for process services | custom idocs | ecc | message mapping | pi |

Related Blog Posts

XI/PI: Throwing Generic Exceptions from any type of Mapping


By Michal Krawczyk , Apr 26, 2007

Message Mapping Simulation in SAP Cloud Platform Integration


By Gautham Krishna , May 26, 2017

XI: How to test your mapping (in real life scenarios)


By Michal Krawczyk , Sep 16, 2005

Related Questions

SAP PI POS Interface Store Connectivity software component of the Integration Repository.
By Sridhar Gautham , Jan 04, 2017

CPI Mapping - Dynamic Target Mapping ?


By Abraham Jabaz Nithin Kumar , Jun 21, 2018
Unable to test Mapping using "Data Mapping Test Editor" in NBPM -> NWDS 7.3
By Suniel K , Apr 06, 2019

1 Comment

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

Former Member

February 22, 2015 at 11:12 pm


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 e ect.

Thanks & Regards,

Tejas Bisen

Like (0)

https://blogs.sap.com/2013/06/17/mapping-errors/ 6/7
7/6/2019 Mapping Errors | SAP Blogs

Share & Follow

Privacy Terms of Use

Legal Disclosure Copyright

Trademark Sitemap

Newsletter

https://blogs.sap.com/2013/06/17/mapping-errors/ 7/7

You might also like