NO_MAPPINGPROGRAM_FOUND in SOAP to ABAP_PROXY scenar

[Former Member]

Hi everybody. I have read many threads regarding the NO_MAPPINGPROGRAM_FOUND issue but did not find an answer.

I have created a web service as an abap proxy on sap hcm system using the outside-in method. now i want to call this web service over xi soap adapter sending two parameters and getting back one output-parameter (xml file).

When sending a soap request to http://xisystem:50000/XISOAPAdapter/MessageServlet?channel=:SOAP_SENDER_CHANNEL:SOAP_SENDER&version=... I' getting the following error:

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGRAM_FOUND:
	at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:456)
	at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
	...</text>
            </s:SystemError>

The message audit protocol says:

...

SOAP: request message leaving the adapter (call)

...

XI-system error. ErrorCode: NO_MAPPINGPROGRAM_FOUND ErrorText:

ErrorStack: the interface mapping http://abc.de/XI/HR/WebService IM_INTERFACE is not contained in runtime cache.

...

I have checked and refreshed SXI_CACHE and found the interface und split-mappings.

the message exchange is synchronous and best effort. as sender service I am using a business service and as receiver service a the hcm as business system. message mapping and one interface mapping IM_INTERFACE are configured for request and response.

what could be the problem? i would be happy about any help!

[Former Member · Accepted solution]

Hi,

Try updating the Interface mapping and Message Mapping by changing the description or any other thing. Activate the objects. Go to Environment clear sld data cache and try again.

Thanks

amit

reward point if suggestion works

[sumesh_k2]

Please check your input test file.

Use this test file in message mapping and check if it works fine.

[Former Member]

you were right, I was using a wrong payload. now the configuration tests works fine.

but i still have the same problem sending soap requests to xi.

if the authentification settings in SOAMANAGER are set to http authentification and user-id/password I get the following error:

NO_MAPPINGPROGRAM_FOUND (described above)

I don't see through this. All I want to do is call a web service. 😕

Edited by: Stefan Tanck on Jul 3, 2008 4:44 PM

[Former Member]

hi everybody.

now it is working and it was working all the time before. this misleading erorr message came due to an insufficient authorization. when calling the web service/abap proxy with an user having SAP_ALL everything works.

for me this seems curious because before we gave me all the user roles mentioned in sap help and the tutorials:

SAP_BC_WEBSERVICE_ADMIN

SAP_BC_WEBSERVICE_ADMIN_BIZ

SAP_BC_WEBSERVICE_ADMIN_TEC

SAP_BC_WEBSERVICE_CONSUMER

SAP_BC_WEBSERVICE_DEBUGGER

SAP_BC_WEBSERVICE_OBSERVER

SAP_BC_WEBSERVICE_SERVICE_USE

which role is missing which is necessary for using web services via soap? does anybody know?

thank you for all your help!

[sumesh_k2]

Hi Stefan,

What URL have you used in SOAP receiver communication channel.

it should be something like http://<localhost>:80xx/sap/bc/srt/xip/sap/<webservice name>?sap-client=<>&wsdl=1.1

Local host and ABAP port where you have published the webservice.

did you test the ABAP web service via WSADMIN transaction?

[Former Member]

hi Sumesh,

my URL of the SOAP receiver communication channel is:

http://hcmsapsystem.de:80/sap/bc/srt/xip/sap/zmi_jobboerse_ib/099/zmi_jobboerse_ib/zmi_jobboerse_ib

I took this URL from the WSDL given in transacton SOAMANAGER. I can not test the service via WSADMIN because it is not showing up there (saying transaction is obsolete)

what I did test was in the Enteprise Service Browser in SE80. there I could send a soap request and became the right answer. BUT sending a soap request with SoapUI to the URL above brings: SRT authorization denied (though I did configure username and password).

it is the first time the hcm system is used for providing web services. we did configure the connection to the xi-system and therefore have access to the ESR via tranaction SPROXY/SE80. is there anything else what we have overlooked and what is needed to provide the web services via xi?

[Former Member]

Using Tools -> Test configuration in the XI Integration Directory shows this error message:

<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="1" type="T">Interface-Mapping http://abc.de/XI/HR/WebService IM_JOBBOERSE </Trace> <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_JOBBOERSE_RQ_ </Trace> <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_JOBBOERSE_RQ. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

MM_JOBBOERSE_RQ is my message mapping to map the request from the soap sender's outbound interface to the soap receiver's inbound interface (my web service / abap proxy). the outgoing and target messages are the same message types(DT_JOBBOERSE_RQ), containing on structure with two integer fields. with the graphical tool of the message mapping I connected the struture and the two integer fields. if I run a test there the mapping seems to work fine.

the proposed cache refreshs did not change anything.

[VijayKonam]

Interchange the SOAP channel and the SOAP sender in the URL used. it must be party:service:channel.

VJ

[Former Member]

hi and thanks four your help.

updating the interface mappings and message mappings did not help.

unfortunately I mistook channel and sender in the URL writing this post. in my configuration sender and channel have the same name and therefore must exist another problem.

i would be happy about any other ideas...

[Former Member]

Hi

Ensure that mapping program exists and is activated. If it exists then update the cache.

Use XIDIRUSER to refresh the cache.

For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full

For complete delta refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta

You can also refresh the cache using XI Administration page.

If this does not solve the issue, see Cache Update Problems section in [XI Troubleshooting Guide|http://www.riyaz.net/blog/index.php/2008/06/04/xipi-sap-xi-troubleshooting-guide/].

Regards,

Riyaz