ABAP Proxy Outbound Error

hello everybody,
i have the next scenario ABAP Proxy->XI->RFC, the problem is that in the sender system I'm getting the next error in SXMB_MONI of sender system:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="401" p2="Unauthorized" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 401 : Unauthorized</SAP:Text>
</SAP:ErrorHeader>
the status is system error, can anyone help me with this error, cause messages are not aariving to Integration Server, thanks in advance.
Regards,
Julio Cesar

Hi Julio
Check Following Steps:
1:Have you insterted the correct URL of your Integration Server?
XMB.TargetURL=http://<host>:<ICM_Port>/sap/xi/engine?type=entry
2: Is the user and password correct?
XMB.User=XIAPPLUSER
XMB.Password=*****
3: Are the read permissions in the source directory correct?
file.sourceDir=/usr/sap/...
4: Be sure you use the ICM Port in my case 8000, e.g.
XMB.TargetURL=http://server:8000/sap/xi/engine?type=entry
If you use SLD information also include
XMD.SLDConfiguration=SLDaccessor in the file.
Check also that the XI user has the right profiles in the XI ABAP instance.
Thanks
Abhishek Mahajan
***Reward points if helpful*********

Similar Messages

Outbound Client ABAP Proxy Timeout Error

Hello everybody we have the next scenario:
R/3 Client Synchronous ABAP Proxy->XI-> Synchronous RFC
and we are having problems cause the Sender R/3 is not waiting for the RFC in the Receiver system to process so XI is in log status fot this messages, is there a parameter to increase the time for R/3 Sender to wait for the Call method sentence to complete succesfully??????, thanks in advance.
Regards,
Raul Alvarado

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

ABAP Proxy outbound not showing in sxmb_moni

Hi All,
All my ABAP proxy scenarios are inbound, however I need to do a outbound ABAP Proxy scenario.
So, I created a Assyn interface in Integration Builder and created a proxy on outbound message interface in SPROXY. (ZCO_ITF_FILE_***).
R/3 --> SQL server
In my simple example I created a program in se38 as shown below
DATA prxy TYPE REF TO ZCO_ITF_FILE_***.
CREATE OBJECT prxy.
DATA it TYPE ZMTP_FILE_***.
TRY.
    it-MTP_FILE_***-id = '12'.
    CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
commit work.
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
ENDTRY.
I want to send just one field called ID.
The program works fine, the "commit work" is called but It doesn´t reach the XI. It doesn´t appear in SXMB_MONI.
As I said before I have Inbound Abap Proxies interfaces, so, I got the sxmb_admin configured.
What am I missing ?
Thanks
Diego

Hi
Thare are no error in SMQ2. The message shwon is
Cl     | User      | Func. Module             | Queue       | Date          | Time      | Status Text
310    ABAP01 SXMS_ASYNC_EXEC   XBTS0005     26.05.2009 11:23:59 Transaction recorded
When I press F6 the message goes to XI. the message reach the sxmb_moni in XI.
But in XI I am facing with another error (the receiver could not be determined).
Thanks
Diego

ABAP proxy Creation error

Hi All,
I'm trying to create a synchronous ABAP proxy out of my outbound interface. When I do that I get an error saying that
Cannot generate proxy (object <attributename="type"> missing in WSDL, see long text)
Now when I remove the reponse message from the interface and make it asynchronous, I'm able to create it without any trouble. So the trouble lies in the reponse message which is a XSD file imported as an external definition. Request message is also an external definition.
The reponse WSDL is as follows:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:ebay:api:PayPalAPI">
 <wsdl:types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:ebay:api:PayPalAPI" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified">
 <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/" schemaLocation="DoDirectResponse.xsd" />
 <xsd:import namespace="http://schemas.xmlsoap.org/ws/2002/12/secext" schemaLocation="wsse.xsd" />
 <xsd:import namespace="http://www.w3.org/1999/XMLSchema-instance" schemaLocation="xsi.xsd" />
 <xsd:import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="ebl.xsd" />
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="RequesterCredentials">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref="ebl:Credentials" />
 </xsd:sequence>
 <xsd:attribute ref="xsi:type" use="required" />
 </xsd:complexType>
 </xsd:element>
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="DoDirectPaymentResponse">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref="ebl:Timestamp" />
 <xsd:element ref="ebl:Ack" />
 <xsd:element ref="ebl:Version" />
 <xsd:element ref="ebl:Build" />
 <xsd:element ref="Amount" />
 <xsd:element ref="AVSCode" />
 <xsd:element ref="CVV2Code" />
 <xsd:element ref="TransactionID" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="Amount">
 <xsd:complexType>
 <xsd:simpleContent>
 <xsd:extension base="xsd:decimal">
 <xsd:attribute name="currencyID" type="xsd:NCName" use="required" />
 <xsd:attribute ref="xsi:type" use="required" />
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 </xsd:element>
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="AVSCode">
 <xsd:complexType>
 <xsd:simpleContent>
 <xsd:extension base="xsd:NCName">
 <xsd:attribute ref="xsi:type" use="required" />
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 </xsd:element>
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="CVV2Code">
 <xsd:complexType>
 <xsd:simpleContent>
 <xsd:extension base="xsd:NCName">
 <xsd:attribute ref="xsi:type" use="required" />
 </xsd:extension>
 </xsd:simpleContent>
 </xsd:complexType>
 </xsd:element>
 <xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="TransactionID" type="xsd:NMTOKEN" />
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="RequesterCredentials">
 <wsdl:part xmlns:generateduniqueprefix15="urn:ebay:api:PayPalAPI" name="RequesterCredentials" element="generateduniqueprefix15:RequesterCredentials" />
 </wsdl:message>
 <wsdl:message name="DoDirectPaymentResponse">
 <wsdl:part xmlns:generateduniqueprefix16="urn:ebay:api:PayPalAPI" name="DoDirectPaymentResponse" element="generateduniqueprefix16:DoDirectPaymentResponse" />
 </wsdl:message>
 <wsdl:message name="Amount">
 <wsdl:part xmlns:generateduniqueprefix17="urn:ebay:api:PayPalAPI" name="Amount" element="generateduniqueprefix17:Amount" />
 </wsdl:message>
 <wsdl:message name="AVSCode">
 <wsdl:part xmlns:generateduniqueprefix18="urn:ebay:api:PayPalAPI" name="AVSCode" element="generateduniqueprefix18:AVSCode" />
 </wsdl:message>
 <wsdl:message name="CVV2Code">
 <wsdl:part xmlns:generateduniqueprefix19="urn:ebay:api:PayPalAPI" name="CVV2Code" element="generateduniqueprefix19:CVV2Code" />
 </wsdl:message>
 <wsdl:message name="TransactionID">
 <wsdl:part xmlns:generateduniqueprefix20="urn:ebay:api:PayPalAPI" name="TransactionID" element="generateduniqueprefix20:TransactionID" />
 </wsdl:message>
</wsdl:definitions>
I would be really grateful if I could get a resolution as I'm badly stuck because of this issue.
Thanks
Arvind

Hi Arvind,
Check the following,
1. The tag <part name="" type=""> is not supported with ABAP Proxies.
Cannot generate proxy
2. Check for recursion - Cannot generate ABAP proxy
3. keep in mind tht ur application system is based on 6.40 or higher versions.
Regards,
Prateek

ABAP Proxy PARSE_APPLICATION_DATA ERROR

Hi Guys,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SNC target system.
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
<SAP:P3>/1SAI/TXSF8E9D07F84DB493AAA0A Line 3340</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)ProductActivity(2)Item(3)ShipToLocation(1)StandardID(2)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/TXSF8E9D07F84DB493AAA0A Line 3340 An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)P An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A Data loss occurred when converting 00900012300355698</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance
Regards
San

Hi Folks,
I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
<?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>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find the fault message has got following values
<?xml version="1.0" encoding="utf-8" ?>
- <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
- <standard>
<faultText>Proxy Class (Generated)</faultText>
- <faultDetail>
<severity>information</severity>
<text>Start of inbound processing: ProductActivityNotification (ID )</text>
<id>000(/SCA/BIF_PROACT)</id>
</faultDetail>
- <faultDetail>
<severity>error</severity>
<text>Message ID is missing</text>
<id>032(/SCA/BIF_MI)</id>
</faultDetail>
</standard>
</n0:ProductActivityNotificationFault>
Will you please focus bit light on this error message please?
Regards
San

ABAP Proxy PARSE_APPLICATION_DATA ERROR - Deserialisation error

Hi All,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SAP target system.
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
<SAP:P3>/1SAI/SASF1B34BDF7BC867BECB1E Line 127</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SASF1B34BDF7BC867BECB1E Line 127 An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E Data loss occurred when converting ON</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The error is shown for the field GBDEP. It is of type char(3) both in the source system and the target system.
Still i am getting this error.
Kindly help me in resolving the issue.
Regards,
Sridevi S

Hi Klaus,
 Thanks for the t-code.
 I couldn't figure out any issue in that program. Below is the line of code in the program for the field GBDEP which is same as for the other fields.
 <tt:cond s-check="not-initial('ROOT.GBDEP')">
 <tt:ref name="ROOT">
 <GBDEP tt:ref="GBDEP">
 <tt:deserialize>
 <tt:assign to-var="_C_NIL" val="' '"/>
 <tt:d-cond>
 <tt:attribute name="xsi:nil">
 <tt:read var="_C_NIL" map="xml('true', '1') > val(C('2'))"/>
 </tt:attribute>
 </tt:d-cond>
 </tt:deserialize>
 <tt:cond-var check="_C_NIL!='2'">
 <tt:value maxLength="3"/>
 </tt:cond-var>
 </GBDEP>
kindly help.

ABAP Proxy configuration Error (Not able to connect R/3 to IB )

Hello All...
I am trying to configure the connection from R/3 to XI using the ABAP proxy generation.For that I have followed the steps given in the below blog
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
We created all the credentials required for the XI and R/3 side configuration and its working fine individually when we have tested for the connection and also assigning this at SXMB_ADM,but in integration engine configuration,when I am trying with the URL dest://<RFC destination(http).Its giving error and in sproxy at R/3 its giving that no integration engine is connected to Business system.
Whats worng with my configuration.How can I resolve this.
I am having R/3 system WAS 6.40

Hi,
But when I am giving the path prefix as you have specified I am getting an Error Query String Not Allowed.
I think thats the warning not error. Just press enter again and go to the logon detail Tab and give the userid password
And how can give the SLD details using the SLDAPICUST.
go to transaction SLDAPICUST and give the following details:
Alias name :any name u want
Prim: check this box
Hostanme: give the Hostname where your SLD (XI server name if you are using the XI SLD)
PORT: Java Port
UserId/Password: for XIAPPLUSER
I think you are missing on the configuration. I think its better if you go through the weblog again.
Regards
Vijaya

FILE TO INBOUND ABAP PROXY - " LOOP_IN_MESSAGE_ROUTING ERROR "

Hi ,
Getting the following Error in *FILE TO INBOUND ABAP PROXY* which is updating a Database table in R/3.
<?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>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.01.lgscms</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How to rectify the Error..
Regards,
Ravi

Hi Ravi !
Check if the url for the receiver is
http://<host>:<port>/sap/xi/engine?type=receiver
or
http://<host>:<port>/sap/xi/engine?type=entry
if using XI 3.0
Regards,
Matias.
Edited by: Matias Denker on Feb 25, 2008 2:12 PM

Forwarding ABAP Proxy Application errors to CCMS of ECC

Hi All,
We are using fault messages for inbound ABAP proxy interfaces to capture application errors, and we can see the error in the monitoring of ECC. However, Is there a way, we can forward it to CCMS of ECC (and not XI), because we want to use an external tool linked to CCMS via SOLMAN to get alerted in case of application errors.
thanks,
Karthik

Solved on my own.
If you need information please contact [email protected]

ABAP Proxy outbound doesn't work

Hi All,
I want to develop an ABAP Proxy to SQL server scenario.
So, I created a interface in Integration Builder and created a proxy on outbound message interface in SPROXY.
When i execute sender program in R3 , it works fine, but It doesn´t reach the PI system.
Outbound message t doesn´t appear in SXMB_MONI in R3 nor Pi system.
What is wrong?
Thanks, in advance
Carme

Our basis team has changed the hostname of our R3 QAs system , but no changes are made in SLD of Pi system.
I think this could be the cause of this issue.
¿can anyone confirm this point?
If yes, ¿what must i do to recover this functionality?
Thanks,
Carme

ABAP Proxy Activsation Error

Hi:
I am tryign to activate an ABAP Proxy in an ECC backend, and I get an error 'No Vendor Specified' with no further details, and the activation is terminated. Has anyone seen this, and what needs to be done to fix this.
BTW:I am using SAP PI 7.0(SP13) as the middleware and ECC6.0 (Basis SP16). I can see and generate my proxies and all objects. All my dictionary objects can be activated individually, and the Messages. However, its only the proxy that does not get activated.
Thanks

Hi,
check the connections in the ECC like
Regarding Proxy Scenario We need 3 connections
STEP1:
1.TCP\IP connections
1.1.LCRSAPRFC
1.2.SAPSLDAPI
2.Settings are to be done in SLDAPICUST transaction
3.Http Connection: -
3.1.PI_INTEGRATIONSERVER
Purpose of LCRSAPRFC:
In order to get the interface details in SPROXY transaction.
Purpose of SAPSLDAPI
To connect to SLD and get the respective business system name maintained in SLD,
Purpose Of SLDAPICUST
Next Execute transaction SLDAPICUST to maintain the SLD access data.
Purpose of PI_INTEGRATIONSERVER
Create a destination of type H in transaction SM59.This connection is used to send the message to the Integration server
Check all these connections are there or not in ECC.
Thanks.

PI to ECC via ABAP Proxy - Outbound Queue for HTTP

Dear Experts,
Is there any Outbound Queue for HTTP?
I've a interface scenario where the receiver is SAP ECC and the receiver adapter XI ABAP proxy. As I see in the communication channel the transport protocol used is HTTP. So I think could there be an outbound queue to manage HTTP connection when PI send the data to SAP ECC?
Just like when we are sending IDocs to ECC via tRFC, we could check if the IDoc has really been sent to ECC by checking in tcode SM58 (Outbound tRFC).
In case for ABAP Proxy via HTTP, is there any similar connection to SM58 (IDoc via tRFC)?
Thank you,
Suwandi C.

Hi Kandasami,
Thank you for the reply. I will check for it.
Hi Jens,
Yes, I mean somewhere after the SXMB_MONI in PI and before SXMB_MONI in ECC, is there any queue in between those two?
Thank you,
Suwandi C.

ABAP Proxy Inbound 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="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1>DFBD3A3045C011DCACF800145ED17196</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message-Id DFBD3A3045C011DCACF800145ED17196 ist im gerufenen System bereits vorhanden (Pipeline CENTRAL)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

Hi Jeong !
Check this thread:
Duplicate Message
Regards,
Matias.

Abap Proxy Generation (Outbound)

Hi All,
I trying to create the ABAP Proxy(OUTBOUND)
I have created the message interface in XI and created outbound proxy in R/3 by using SPROXY Tcode.
Created the ZProgram by calling class.
Please see this link
http://www.directupload.net/show/d/807/823PgPdG.jpg
what is wrong here ?
Regards,
Fth

they are only warnings, what happens if you go ahead activate and run the program?
Regards
Raja

ABAP proxy exception to SOAP fault and vice versa not getting mapped

Hi there,
I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
The behavior we are observing is as follows;
When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
2. What can we do in order to change that situation?
3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
Many thanks for your replies.
Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

Problem was caused by some differences in namespaces between source and target.

ABAP Proxy Outbound Error

Similar Messages

Maybe you are looking for