Error:MAPPING>RESOURCE_NOT_FOUND

[Former Member]

Hi Experts,

I have a scenario from RFC TO SOAP,it runs fine but rarely I get an error *"MAPPING">RESOURCE_NOT_FOUND*.Not sure what is causing this problem.Can you help me with this guys

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">RESOURCE_NOT_FOUND</SAP:Code>

<SAP:P1>com/sap/xi/tf/_Z_*****************Reqto_*****************~</SAP:P1>

<SAP:P2>http://*************************************~</SAP:P2>

<SAP:P3>b374a530-c9d7-11dc-c8b9-c6ce0a200ca4</SAP:P3>

<SAP:P4>-1</SAP:P4>

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to find resource com/sap/xi/tf/_Z_*************Reqto_***********~ (http://***************************************~, b374a530-c9d7-11dc-c8b9-c6ce0a200ca4, -1)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Thanks

Points will be awarded

Edited by: guest xi on Apr 9, 2008 1:40 PM

[Former Member · Accepted solution]

Hi,

I have faced a similar problem when JCo (to carry out mapping) from Integration Engine to Java stack used to fail.

You can look into Trace for more details.

Regds

Pushkar

[Former Member]

Hi,

Can you please let us know how this issue got resolved as we are also getting same issue.

Your reply will be highly valueble for us.

Thanks

Hamja

[Former Member]

Hi Guets

The first step is refresh cache -. Note 741214.

sds

Marco Zerbini

[Former Member]

Hi Marco,

It can be because of cache if we develop a new mapping and the cache is not updated.

But if it is works sometimes and sometimes it doesnot, we can assume that Mapping is present in the cache.

Regds

Pushkar

[Former Member]

OK.

Last week i have same problem here.

Im my case i checked in transaction SMGW for wrong gateway (AI_RUNTIME and AI_DIRECTORY) registrated in xi system, in my case the DTR site.

sds

Marco Zerbini

[Former Member]

Hi,

I have developed the scenario a week back and it works fine,I only get this error very rare and it works fine after I run it next time,may be as you guys mentioned it could be cache problem or gateway problem.Not sure how to rectify this.I do not have access to SMGW.

Thanks

[henrique_pinto]

The problem can be related to two cases:

1. in case you have load balance in your system, if the cache is not correctly replicated to all systems, this error may occur. To solve this, execute a CPA full cache refresh;

2. if you have some Java system wrongly registering to this ABAP Integration Engine stack. This can occur for example when you do an homogeneous system copy. The Java stack of the new copied system will contain all the same information from the previous system, hence pointing to the old ABAP stack. You can evaluate that with SMGW in the ABAP stack of old system (Integration Engine where the messages error out). Once you identify the Java stack that is wrongly connected to this ABAP stack, go in the Visual Admin of that Java stack, JCo RFC Providers service, and maintain the proper logon data (pointing to the newly created ABAP stack, not the old one).

Regards,

Henrique.

[david_fryda2]

Hi Henrique,

I've got the same problem.

I've done the CPA refresh but didn't help.

What should I do with SMGW transaction ?

In my case, the transaction displays an empty table.

Thanks.

Regards.

[Former Member]

Hi,

People do not contribute just for the sake of points on SDN.

Regds

Pushkar