RFC-to-SOAP-Scenario: XIServer:NO_MAPPINGPROGRAM_FOUND

[Former Member]

Hey guys,

We've implemented in SAP PI 7.11 a RFC-to-SOAP-Scenario. The whole scenario is sync. WSDL and RFC are imported objects.

Now we're going on to test in backend and call the related remote function module via se37.

The error message is (from xsmb_moni)::

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code> 
  <SAP:P1>Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:P1> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:Stack>Mapping program is not available in runtime cache: Object ID A2DC458230C93030AE8B43396EEC43DB Software Component 83222F30FC9011DF8643DD3AC3E93CB3</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

What we've already done:

-> Cache refresh

-> server restart

-> soap fault mapping

-> dummy changes

-> mapping is available in sxi_cache

-> function module is not dumping in backend

Any ideas how we can go futher with this?

Thank you very much and greetings,

Stefan

[Former Member]

Hello Stefan,

I have the same scenario and the same error for certain RFC - SOAP interfaces, but not all of them. I have tried so many solutions listed in this forum and other forum posts.

If you have resolved, please share the solution that worked for you.

Regards,

Aaron

[Former Member]

Hi @all,

thank you for all your responses.

We found out that this message also comes up in case of an configuration error in transport management during the java stack. In our case the transport system is nearly not configured. Our transport system catches errors due to the business system in approval stage (we've got a 3-stage environment with PI, dev, approval and prod).

This is our new basis approach to solve this.

I'll be right back to you and going to tell you if that solves this error.

Regards,

Stefan

[Former Member]

Hi,

we're back with (I'm afraid) still the same error.

The thing with the transport system doesn't solved our problem.

Any ideas, what that could be?

[Former Member]

We still still have the problem as well... any further suggestions are appreciated.

We are on PI 7.11

[Former Member]

FYI...

Apparently, this error message can sometimes be misleading.

I found in another thread that this message came after a short dump in the ABAP function. After viewing ST22 in our backend system I noticed short dumps corresponding to the times when I make the SOAP call.

[]

We can call SE37 with the same parameters and there is no ABAP error. So the search for root cause continues, but maybe this info will help someone.

-Aaron

[Former Member]

In our case the ABAP Short Dump error was caused by user settings which were different between the PI account used in the RFC channel. When running the function directly the number formats would be returned with decimals, but in the service account it would try to return with a comma instead of decimal.

So the PI error message regarding NO_MAPPINGPROGRAM_FOUND was very misleading, and the fact we tested the RFC running OK directly in SE37 made us look in other areas for a long time.

Regards,

Aaron

[Former Member]

Hi @all,

our issue is solved.

The initial problem was an exception that was thrown by the webservice: no method found. The meaning of method was our request we sent.

And this "no method found" exception occures because of the namespace we used automatically during the import of wsdl.

We solved this problem without using the wsdl-import.

We've created message types (with their corresponding data types) for request and response.

During the creation of the message type we removed the xml-namespace suggestion from screen.

Thanks to all for the good help and I hope that our issue could solve some other issues with this problem,

Stefan

[Former Member]

Hi Stefan,

As usual, the error NO_MAPPINGPROGRAM_FOUND occurs when the BAPI has dump error, or the RFC destination called in BAPI has something wrong, you said that there is nothing in dump error (tcode ST22), so you should check over the message in SXI_MONITOR or in the RFC destination configuration.

Hope this helps,

Thien

[aashish_sinha]

Hi,

Please check whether you have created a response mapping and properly referenced it in your operation mapping

For the RFC exception error >> Please check if you have any new fields added in RFC , re Import the RFC definition in PI .

Aashish

[GabrielSagaya]

Have a complete cache refresh with transaction SXI_CACHE.

Also try with the below URL

http://host:port/CPACache/refresh?mode=full

[Former Member]

Hi,

we've done a single refresh and a cache-refresh via sxi_cache, also with the URL suggested.

But the error is still there.

Regards,

Stefan

[RKothari]

Hello,

Try to Inactive the RFC adapter and activate it again.

Also check if the RFC destination INTEGRATION_DIRECTORY_HMI is working fine.

-Rahul

[Former Member]

Hi,

we've checked the sm59-destination INTEGRATION_DIRECTORY_HMI fails.

It gives an internal server error, http-response: 500.

The path prefix is /dir/CacheRefresh

Maybe the path prefix works not out.

Regards,

Stefan

[markangelo_dihiansan]

Hello,

Please do as Aashish has suggested, maybe the FM is giving out an exception and you do not have a mapping program for that (e.g fault mappings).

Hope this helps,

Mark

[RKothari]

Hello,

For internal server error 500, please check the SAP notes 804124, 807000.

Please try providing the path prefix as: /dir/hmi_cache_refresh_service/ext and test the same.

Also, check the PIISUSER is not locked.

-Rahul

[RKothari]

Hello,

Please try to test the scenario using Test configuration in ID.

Check if there is any issue with interface determination ??

-Rahul

[Former Member]

Hi,

See NOTE 1523941 - PI mapping errors: RESOURCE_NOT_FOUND and NO_MAPPINGPROGRAM_FOUND

You must reactivate or reimport your mapping.

Regards,

Carme.

[Former Member]

Hi,

thank you for your reply.

We've done this but without any effects.

We've re-imported the whole mapping.The error is still the same.

Many Greetings,

Stefan

[baskar_gopalakrishnan2]

This error might be dump error in BAPI. I already faced similar problem. Please look at the below link...

[Former Member]

Hi,

thank you for your replies, we've checked out the function modules for dumps, there are none.

We've tested the configuration with "test configuration" - the status is green for all steps.

But one thing is strange: No sender agreement and no receiver determination could be found - but there are existing.

We've done a dummy change in both objects and activated them, these objects could'nt be found during the configuration testing.

The no_mappingprogram_found-error still exists.

Regards,

Stefan

[Former Member]

>

> Hi,
> 
> thank you for your replies, we've checked out the function modules for dumps, there are none.
> 
> We've tested the configuration with "test configuration" - the status is green for all steps.
> But one thing is strange: No sender agreement and no receiver determination could be found - but there are existing.
> We've done a dummy change in both objects and activated them, these objects could'nt be found during the configuration testing.
> 
> The no_mappingprogram_found-error still exists.
> 
> Regards,
> Stefan

Have you tried to refresh the cache for single Mapping ObjectID?