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.

Similar Messages

SOAP to Proxy scenario communication error

Hi Friends,
 Now i am developing SOAP to Proxy scenario, i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 403 Forbidden</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
 
 Error: You are not authorized to view the requested resource.
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
I have tried with the same WSDL earlier it was working fine, now its not working and throwing the above error.
Kindly suggest me to overcome from this issue.
Regards,
Senthil.

Hi Senthil,
Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.
Regards.

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

Need Mapping logic for the following scenario

Hi everyone,
I need a mapping logic for the following scenario.
For the same order no with same material no, the quantity should be summed and only one idoc should be created.
For the same order no with different material no, no need to sum the quantity and only one idoc should be created.
For example:
Source Structure:
Ord No      Mat No      QTY
12               1               2
13               1               3
13               2               1
12               2               4
15               1               5
14                3              7
12               1              6
Target Structure:
Ord No      Mat No      QTY
12               1               8
12               2               4
13               1               3
13               2               1
14               3              7
15               1              5
Thanks in Advance

Try the graphical mapping as shown below using concat with a space as delimite and UDF to split the value again by space.
1. Idoc node
(RootContext)
OrdNo
     |concat[ ] -> sort[asending] -> SplitByValue -> collapseContexts -> Idoc
MatNo                case sensitive    [ValueChange]
(RootContext)
2. OrdNo
OrdNo(RC)
     |concat[ ] -> sort[asending] ->SplitByValue->collapseContexts->SplitByVale-> UDF to fetch ordno -> OrdNo
MatNo(RC)           case sensitive    [ValueChange]                [eachValue]   (return var1.split(" ")[0];)
3. MatNo
OrdNo(RC)
     |concat[ ] -> sort[asending] -> SplitByValue ->collapseContexts->SplitByVale-> UDF to fetch ordno -> MatNo
MatNo(RC)              case sensitive    [ValueChange]                  [eachValue]   (return var1.split(" ")[1];)
4. Qty
               [asending,case sensitive]
               -- sortByKey -----> formatByExample -> sum ->Qty
OrdNo(RC)           |          |          ^
     |concat[ ] -> |            Qty(RC)          |
MatNo(RC)           |                |
               --sort[asending]-> SplitByValue
                   case sensitive    [ValueChange]
Regards,
Sunil Chandra

Soap to proxy scenario Getting exception caught with cause error

Hi Experts,
MY scenario is soap to proxy i am getting below exception message in advanced engine configuration in ICO.
OAP: request message entering the adapter with user J2EE_GUEST
09/10/2014 11: 06: 03 346 XI Information Packaging (Bulk Mode) is not Enabled, Proceeding to the Normal Processing.
09/10/2014 11: 06: 03 346 XISOAP Information: Received an XI message for processing
09/10/2014 11: 06: 03 598 Error SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
OAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
09/10/2014 11: 06: 03 598 Information SOAP: response message to continuing 7477aafa-38da-11e4-beed-00000028af0a
09/10/2014 11: 06: 03 599 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 599 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
payload is contains some special charters in which is in protiguse language
example.
• AWPJ SERV DE TERCERIZ and
dot is the special char
same payload while testing using sproxy tcode dot "•" is converting in " # "symbol and with out error its successfully updating the database in ECC.
while testing using the same payload using soap ui removing the dot symbol from the field its successfully processing and updating the database.
is this interface is failing in PI level ? or ECC i am not getting dump in ecc.
is there any special character conversation in sap pi level.
where this message exactly failing is in PI level or in ECC level?
Help us find the solution.

Hi Ravinder,
When you mark the option Do not use SOAP envelope the adapter will not generate the SOAP envelope therefore you need to set an extra mapping in the Request to wrap the SOAP envelope. For example with XSL:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
 <xsl:template match="/">
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body>
 <xsl:copy-of select="/"/>
 </SOAP:Body>
 </SOAP:Envelope>
 </xsl:template>
</xsl:stylesheet>
Later in the response you will have the SOAP envelope tags. (You can do a first try without java mapping only to see in the monitoring the response with the junk character).
When you determine the junk character you can try to use and to modify the next java mapping SAP PI - Deciphering apostrophes in XML - Process Integration - SCN Wiki to deal with your problem.
Hope this helps.
Regards.

MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

Hi,
Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.
Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?
Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.
When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.
Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.
I have found below errors on RWB (approx 250 message have below errors).
How this high CPU consumption can be resolved?
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>
</SAP:Error>
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>
</SAP:Error>
Kind regards,
Altuğ Bayram

Hi,
Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error
you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...
re you making use of AAE for this scenario..which can improve the performance than using classic scenario.
performance depends on the hardware of the server also...
Check the sizing Guide of the PI 7.1 on SDN.
Check the below link it may help you..
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
HTH
Rajesh

UNCAUGHT_EXCEPTION in SOAP TO PROXY scenario dump in ECC system.

Hi Experts,
My scenario is saop to proxy .while performing testing the scenario using saopui. iam getting client_send_failed error in sxmb_moni.
but data processed to ecc system and updated the data in database level and giving dump in ecc system.
i am getting dump like below.
UNCAUGHT_EXCEPTION.
we increased the size of instance profile parameters also upto 500 mb .in rz10.
still getting dump.
Please give the solution for above.
Regards
Ravinder.s

Hi All,
We resolved the issue using below notes and my system is newly upgraded its not accepting asynchronous scenarios with quality of service as BE in sender communication channel.
1966422 - XI runtime: Dump: synchronous proxy calls asynchronous interface
Thanks for all.

Issue in Soap to Proxy scenario

I am unable to generate wsdl file in sender agreement in pi 7.1v? If I try to generate, getting error.
How to generate wsdl?

hi,
If we are using sender interface in multiple scenarios at that case we are not providing Software Component version in sender agreement.
u2026u2026u2026u2026u2026u2026.
How to generate wsdl?
Tools -> display wsdl -> provide specified parameters
thanks

SOAP - Proxy Scenario

In my SOAP to Proxy scenario I have a proxy that will return "true" or "false" depending on the logic in my method. When I execute the proxy it returns the false value for cases that are false in SAP. The scenario does not return the "true" value when the logic is true in SAP. If I go into SAP and run the method, both the true and the false logic paths work and the method returns the correct value. If I hard code the variable in the method to "test" and execute the XI scenario it will return the word "test" for both cases, true and false. I have the same scenario in my XIQ system and it works fine.
So, what I have done...
I have flushed the cache, that did not work.
I have rebooted my XI system that has the problem.
I have compared my XI broken system with the one that is working and there are no differences.
Does anyone know how I can see what is truely being sent back to the SOAP side? Is there a way to debug the ABAP code from the XI / SOAP side?
Any help would be greatly appreciated.
Thanks
Skip Ford

Hi Ford
When you try with SAP its working right. Did you see that response in XI. If not then no need to touch XI.
Take the payload and try to debug the proxy. You will come to know if it really returns the true value or there is a data issue itself and no problem with XI and SAP.
Check in XI mapping as well. if the value from source is moving to target or not. If you make any changes or found problem do regenerate and activate proxy.
Thanks
Gaurav

SOAP- Proxy scenario, issue with WS adapter

Hi guys,
i've set up a soap->abap proxy scenario (on 7.1) and want to use the new WS adapter. unfortunately I'm facing some issues. The proxy has been generated properly and I also set it up in soamanager. I tested it from XML Spy and it works fine. So there shouldn't be any problem with it.
But when I try to run the scenario, I get following error:
WS_ADAPTER_SYS_ERROR
<sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException><sap:ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException></sap:ExceptionChain>
System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when processing Web service
I checked the /sap/xi/engine service on both - PI & ECC and it is activated.
Any hint, what could be wrong?
Thanks a lot,
Olian

Hi,
"ICM_HTTP_CONNECTION_FAILED" this error is relaed to ICM. Does your Type H connection "INTEGRATION_SERVER_HMI" works fine.And check integration engine configuration in SXMB_ADM.
And here is a similar thread.
Re: HTTP to Enterprise Services.
Regards,
Reyaz

SOAP to Proxy error PI 7.1

Hi Experts
Working on the SOAP to Proxy scenario, XML message is coming, I am transforming the message from xml into HTML by using the XSLT mapping
I receive the following errror while testing, Can anyone tell how to trace the error
<?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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks
PR

Hi,
Please have a look at the following links and see if it helps
Exception handling Proxy to SOAP
SOAP to Proxy test scenario 7.1 PI
How To Debug XML Serialization Error With Deployable Proxy
Best Regards

Send Message SOAP to Proxy failed - No standard agreement found for

Hello to all,
we have a SOAP to Proxy scenario.
The Service Interface have 6 Operations.
When I implement 2 Operation it works fine. Now I have implemented all Operation.
When I send a request I get following Error:
I have checked the Interface determination. It is ok. I have Sender, Receiver and all Operations.
Where could be the error?
Please help us.
Thanks and regards
Martin
Edited by: Martin Weidauer on Nov 9, 2010 4:45 PM
Edited by: Martin Weidauer on Nov 9, 2010 4:47 PM

Martin,
Please perform the following..
1) Please go thru this link.
Re: Error CO_TXT_OUTBINDING_ERROR in SXMB_MONI
2) Perform a full CPACache refresh using PIDIRUSER.
http://XiHost:Port/CPACache/refresh?mode=full
3) Kindly check Note No.'s in service market place ::
1284103, 1278244, 1278273 .
Just perform and let me know...
Regards
Veeru

SOAP to proxy scenarion error An error occurred during the processing of proxy E 00 001 The message can not be processed in plugin mode HTTP

Hi all
My scenario is soap to proxy scenario .while testing using soap to proxy i am getting " An error occurred during the processing of proxy E 00 001 The message can not be processed in plugin mode HTTP: in sxmb_moni sap pi .
Some times this interface is failing and some time its successfully processing.
While testing with successful xml data also i am getting the same error in sxmb_moni.
I modified the proxy inbound code where passing error message and still i am getting the same message.
Please suggestion the same for error solving.
Regards
Ravi.

Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
#   End operation: Render, elapsed time = 89 ms.
#   Begin operation: UsageRights, elapsed time = 89 ms.
#   End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be?

Soap - XI - File Scenario

Hi experts,
I need your help on this.
XI will receive a synch soap request with the following input parameters: date and supplierNo. With that input parameters XI has to find and retrieve (from a File Server) all the documents of that supplierNo for that specific date.
Do you know how to develop such scenario?
Thanks in advance
Pedro Leal
Edited by: Pedro Leal on Feb 13, 2008 6:17 PM

Hi Pedro !!
Based on your scenario description, maybe the best solution is to create a SOAP<->XI<->Proxy scenario where the Proxy could be ABAP or Java. I suggest a Proxy, because the receiver file adapter only writes files and the sender only picks files up based on a time interval and not on demand.
For example, the Java Proxy server could receive the request from XI, search the files and send them back as response. You need to check file sizes and if files content is XML or binary and maybe other details to see if this scenario only will we enough, or if you may need a BPM or more than one scenario, one for "prepare the files" and one that takes the "prepared" files and thru XI sends them back to the target as a response in a synch or async manner.
Regards,
Matias.
ps: please award points if helpful.

Soap to proxy - synchronous error

hi
i am working on soap to proxy scenario.
i am getting an error in message monitoring
Exception caught by adapter framework: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = DYNAMIC_CALL_FAILURE ErrorCategory = XIProxy Parameter1 = Parameter2 = ZCL_SI_SALES_ORDER_CREATE1 Parameter3 = SI_SALES_ORDER_CREATE Parameter4 = Additional text = ErrorStack = Error during proxy processing
Message E TD 604 cannot be processed in plugin mode HTTP
[http://sap.com/xi/XI/Message/30^Error "DYNAMIC_CALL_FAILURE"]
what could be the issue in it ?

Hi
It is data issue, you need to debug the proxy for more detail about this error. Take the payload and debug the proxy in SPROXY. Also check below sap note.
1876952 - XI runtime: Determining dump in receiver system
Regards,
Praveen.

No mapping logic : soap to proxy scenario

Similar Messages

Maybe you are looking for