Error for SOAP to BAPI scenario

Hi All:
When I am trying to send the message from SOAP client to XI I am getting and Error and also the message is not reaching to MONI.
Is there anything that is required in in SOAP adapter or Modules setting??
Error :
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>WS-Security privileged action exception</faultstring>
 <detail>
 <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
 <context>XIAdapter</context>
 <code>PrivilegedActionException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:543)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.aii.messaging.srt.BubbleException: WS-Security privileged action exception [null "null"]; nested exception caused by: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.doValidate(WSSecurityExtension.java:173)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.invokeOnRequest(WSSecurityExtension.java:107)
 at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:50)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)
 ... 20 more
Caused by: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension.doValidate(WSSecurityExtension.java:157)
 ... 23 more
Caused by: com.sap.aii.af.security.impl.exception.MessageSecurityException: AccessControlException in Method: verify( Message, byte[], CPALookupObject ). The Code-Permission processing failed.
 at com.sap.aii.af.security.MessageSecurityContext.verify(MessageSecurityContext.java:347)
 at com.sap.aii.af.mp.soap.ejb.WSSecurityExtension$VerifyMessageLevelSecurity.run(WSSecurityExtension.java:417)
 ... 25 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thanks

Hi,
It looks like error because some security settings. Hope you have given the Adapter paarameters correctly.
You can check this SAP note:856597
Also you can try out with XMLSPy ..probably the error is because of usage of wrong port or authentication for that user.
Rgds,
Moorthy

Similar Messages

Error in SOAP to IDoc scenario

Dear Experts,
I have one SOAP to IDoc scenario where I am sending the request through Altova XML spy.
But I am getting the error "Only asynchronous processing supported for IDoc adapter outbound processg". but I have configured the QoS of Sender Communication channel as "Exactly Once(EO)" and I have activated the same.
In SXMB_MONI the "Type" of this scenario is also "Sync".
The created SOAP request URL is :" http://server:host/sap/xi/engine?type=entry&version=3.0&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX.
Here I am getting the error as "Only asynchronous processing supported for IDoc adapter outbound processg".
If I send the service usinng the URl "http://server:port/XISOAPAdapter/MessageServlet?channel=:BS_XXX:CC_SOPtoIDoc&version=3.0&Sender.Service=BS_EAN_DELE&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX",then I am getting HTTP 500 error.
Can you please suggest me where I have to change the configuration so that the "Type" will be async and the IDoc will be posted properly.
Thanks in advance.
Regards,
Amit Mandal

hi,
you can also do it like this:
http://server:host/sap/xi/engine?type=entry&version=3.0&ProcessindMode=Asynchronous&QualityOfService=ExactlyOnce
&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX.
and set use query string parameter in soap sender adapter
Regards,
Michal Krawczyk

"Unauthorized" error for SOAP receiver channel

Hi all,
I have a scenario in which I am calling a .NET web service from a UDF in which the XML payload is constructed manually. I have configured a SOAP receiver channel. Also, since the web service needs certificate authentication, I have checked the corresponding parameter in the SOAP channel and selected appropriate client certificate.
When I execute the mapping, I get the following error -
com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_RCV_IMWS_Change (Party: , Service: IMWS, Object ID: dda07d364ca73d4ab9e89e562a971b36) XI AF API call failed. Module exception: 'com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'. Cause Exception: 'invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized'.
Is this related to error in certificate authentication process, OR wrongly formed XML payload OR anything else ?
Regards,
Shankar

No. I didn't provide any login info. The web service doesn't specify username login requirement. Instead, it needs client certificate for authentication, which I provided in SOAP receiver channel.
I am testing the web service by executing the message mapping. The web service was executed successfully from its 'Test Page' like for SAP web services we have web service navigator. So it runs ok from that test page, but gives error when called from UDF.
Regards,
Shankar

Error in SOAP to file scenario

Hey guys
i m doing a SOAP to File scenario and getting the following error.
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
any idea where should i look ?
thanx
ahmad

Hey
i m still getting a red flag in MONI,the error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
i checked my mapping by copyin payload from MONI,its working fine.
thanx
ahmad

Business systems for Soap to file scenario

Hi Experts,
I am working on a soap to file scenario.Which type of business systems shall i create i.e Third party,As ABAP,As Java etc.Please suggest.
Thanks
Veeru

Hi,
Normally Business systems are created in SLD when you are provided with relevant system details. A business service is used in case of the system being an abstract unit.
In your case, it is better to go for Business service because you generally don't have such details for third party system.
Just go through this link for more understanding...
Difference between Business System and Business Service
Regards,
Chandra

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Turn of acknowledgment for IDoc - XI - BAPI Scenario

Hi,
i have a smal BPM where i am sending an IDoc from an
3rd PArty System -> XI (making some mappings) -> SAP
everything works fine, but in the end i get a Errormessage in the
MessageMonitoring on my runtimeWorkbench.
the error occure when XI try to send an acknowledgeMessage
back to my 3rd Party System.
I there a way to turn the request for Acknowledgement of?
Thanks 4 help,
Benjamin

Hi,
on my 3reParty System i am generating an IDoc,
an send it to an Abstract Asynchronus
Messageinterface on my XI IntegrationServer.
This works fine.
Also the synchron BAPI-Call to the SAP system works.
But in the end after all is done the XI system
try to send an acknoledge back to the 3rd PartySystem.
How can i turn off this acknoledgement?
I think i must turn it off in the beginning. this means i must turn it off on my initial IDoc-call.
but how can i do this?
thanks
Benjamin

SM58 Error For IDOC to IDOC Scenario

Folks,
I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) IDoc adapter inbound channel: Error Error when reading. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
Thanks
Manish

Hi Renjith,
I'm facing the same problem the flow is basically form BW to BO.
When they load the data at sender side the idocs are stucked with error status 2:
"Could not find code page for receiving system" in transaction BD87.
Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
1)Error in RFC connnection
2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
Also are many queues stucked in SMQ1 Outbound.
Please help. Many Thanks.

Database error for JDBC to Proxy Scenario

Hello SAP PI Gurus,
I am having a JDBC to Proxy Scenario .And the interface is running at 10 min of duration.
However, my other interface are running fine with the same details.
But for this interface, it giving the belwo error :
Database-level error reported by JDBC driver
while executing statement 'call proc_dtdc_prod_summary'.
The JDBC driver returned the following error message: '
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table
'dtdc_prod_summary_temp' already exists'. For details,
contact your database server vendor.
So increased the time from 10 min to 20 min to 30 min. But the erro remians.
So pls look into this and give your suggestion.
Regards,
Ravi

Hi Ravi,
Please check execution of your stored procedure is resulting with creation of Table : dtdc_prod_summary_temp.
Modify your stored procedure to just fetch records or insert records in the existing table. Or change the code to Create a table 'dtdc_prod_summary_temp only if it doesn't exits in the Table data base.
Regards
Praveen K

How to create Integration Flow for SOAP to RFC scenario?

Hello Friends,
We have Single Stack SAP PO 7.3 EHP 1 SP08 AS Java in our environment. We have a scenario where a RFC needs to be made available as SOAP Web Service. So we are using SOAP Sender Adapter and RFC Receiver adapter. We want to build this scenario with NWDS (Eclipse). We have imported the RFC and created data types, message types, service interfaces etc. But we are facing trouble in creating the Integration flow.
Please let us know if we need to create only one integration flow or need to create two integration flows (one for request and one for response) and what all configuration would be needed in Business Component and Communication Channel.
A step by step guide would be highly appreciated.
Best Regards,
Shreyansh Shah

Hi Shreyansh,
Found these links for you. Have a look at them and go through them. They should help you.
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/95/8969b91d50439296dbd0a8ded93da7/content.htm
Understanding Integration Flow - Process Integration Tools (Eclipse-Based) - SAP Library
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/e4/c9be6beab94f0b932e3c67f50e0093/content.htm
Regards,
Jannus Botha

Error in soap to rfc scenario

while checking the result in altovaxmlspy i m getting the following error "(122) JCO_ERROR_CONVERSION: Date '12/20/2002' has a wrong format at field FLIGHTDATE: Unparseable date: "12/20/2002"" . The BAPI being used is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL.
The date format visible in fldate field of SFLIGHT table is MM/DD/YYYY and while mapping in IR the source date format is dd/mm/yyyy and target format taken is mm/dd/yyyy.
pl help how to rectify the error in order to see the proper result

Hi Prateek
Date conversion while mapping has been done using std function " Date Trans" only.
" But the target date u mentioned is mm/dd/yyyy. Make sure that the RFC accepts the date in this format."
The crux of the matter is that i m unable to make sure the above quoted point . Pl help how to ensure whether the RFC accepts the date in this format .
Rgds
Edited by: shazia seemin on Jan 22, 2008 7:44 AM

IDX1 : Is it necessary for SOAP - XI - RFC?

hi,
I have designed an integration scenario in which my web application will send request using SOAP over HTTP protocol. The XI system will host a web service and by generating the WSDL i will generate the proxy class using which I will comunicate with XI system. There will be sender type SOAP adapter between My WebAPP and XI. I will send request through Outbound interface.
Further the Request will pass to SAP CE8 system from XI system and communication will be through RFC(BAPI) using RFC adapter and Inbound interface.
My Questions are :
1. I have configured RFC destination on CE8 using SM59 transaction. Do i need to configure on XI system an rfc destination using IDX1?(I will use BAPI request/response only).
2. In integration scenario there are two interfaces
My WebAPP -- Outbound Interface(Custom defined) -- XI
XI -- Inbound interface(RFC)
since this is a synchronous communication i think i just need these two interface. Right?
On Custom defined side, two message will be there 1 each for request and response.
On BAPI side, BAPI and BAPI.response will be used. Is my approach correct?
3. When specifying the technical system landscape i was asked to mention System and Host information for my technical system. What are these and how I can obtain them?
P.S. As I have sdn blogs + forums + sap help portal on my disposal ... can anyone suggest something free over the internet ?
Thanks in advance...

1. I have configured RFC destination on CE8 using SM59 transaction. Do i need to configure on XI system an rfc destination using IDX1?(I will use BAPI request/response only).
No You dont need to create one.
2. In integration scenario there are two interfaces My WebAPP -- Outbound Interface(Custom defined) -- XI
XI -- Inbound interface(RFC)
You dont need 2 interfaces. You need only one for SOAP and no need for RFC request. The one you import is sufficient.
If it is a synchronous you need 1 inbound response for SOAP. BAPI RFC has already has a response.
3. When specifying the technical system landscape i was asked to mention System and Host information for my technical system. What are these and how I can obtain them?
The host name is the host of the connecting systems. for SAP from 4.7 you can connect them to SLD directly but for non-SAP and SAP < 4.7 you need to mention host name of the particular system (since these does not connect directly there is no problem). Remember that SLD is a repository of systems information.
regards
Shravan

No mapping logic : soap to proxy scenario

Hi,
I have a soap to proxy scneario with no mapping logic.wanted to confirm certain things.
Wanted to confirm certain things.
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
2) in interface determination ,what i need to provide for interface mapping ?
3) sync proxy will be generated from one outbound message interface "( there will be only one outbound message interface which will be synchronous : which will be synchronous ?
4) in receiver business system , i need not put any message interface since we only have one outbound sync message interface
Thnx

how many message interfaces wil be needed for synchronous scneario without mapping ?
Two....one for Sender (Outbound) and one for receiver (Inbound)
in case ur answer is 2 for above ? proxy needs to be generated from outbound or inbound interface?
For your SOAP --> XI/ PI --> PROXY, scenario the proxy should be generated for the inbound interface
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
If both the source and target structures are the same , then you do not need to perform mapping....do not create message and Interface mapping .....you should however create Interface Determination with appropriate Source and Target interfaces.
2) in interface determination ,what i need to provide for interface mapping ?
Nothing.....including a mapping is not mandatory.
4) in receiver business system , i need not put any message interface since we only have one outbound sync message
interface
The message interface needs to be associated with the Business System.....it will be the inbound interface for SOAP --> XI --> PROXY scenario.
Regards,
Abhishek.

In HTTP to SOAP scenario. Error i get is "Invalid content type for SOAP"

Hi,
In HTTP to SOAP(synch) scenario. Error i get is "Invalid content type for SOAP"
When pass my data in the HTTP client, I get the following Error.
What may be the cause,How to reslove it.
Response am getting is below............................
Result:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/PLAIN</SAP:AdditionalText></SAP:Error>

hi ,
Just refer following 2 links
Re: Invalid content type for SOAP
Re: invalid content type for SOAP: TEXT/HTML
Regards,
AshwinM
Reward If helpful

Mapping related errors in SOAP Adapter scenario

Hello Friends
I have done this several times and in this particular case I am getting some errors.
Here is the scenario
External --- (SOAP) --- XI -
(RFC) -
SAP TABLE.
Program
I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
However, it is failing with some mapping errors.
Here is the error message I got in SXMB_MONI
Any help will be greatly appreciated.
<Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description>Main XML document</SAP:Description>
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>

Hi Ram,
This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
Thanks,
Bhargav.
Note:Award Points if found useful

Error for SOAP to BAPI scenario

Similar Messages

Maybe you are looking for