Fault message in asynchronous ABAP Proxy

Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says <i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i> But this is not working.
Am I missing something?

Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech

Similar Messages

Timeout Error in Call Transaction on Asynchronous Abap Proxy

Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

Exception using fault message in java server proxy.

Hi All,
I am trying to use Fault message inside my server proxy code in Asynchronous java server proxy. I am referring the below mentioned link :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702?quicklink=index&overridelayout=true
I successfully deployed my SDA file but while running the scenario(http-XI-ftp in PI7.11) i am getting the folowing exception under MDT:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean ServerProxyFTTest3.
I am using the following library refernces under application-j2ee-engine.xml file: com.sap.aii.af.sdk.lib, com.sap.aii.proxy.svc, com.sap.xi.util.misc,com.sap.guid,com.sap.exception all of type "weak".
I have checked almost all the forums related to fault messages in asynchronous java server proxy but couldn't find much help.
Request you all to help me.
Thanks
Amit

Hi Rajesh,
I am deploying my SDA file on Non Central Adapter Engine.
I have also registered my interface using:
http://ISVSAPPISB:51000/ProxyServer/register?ns=http://infosys.com/poc&interface=SI_Proxy_IA&bean=localejbs/ServerProxyFTTest3&method=sIProxyIA
But still i ma getting the same exception.
Hi Gabriel,
I implemented my scenario using the same. But in addittion to the librarry referneces mentioned over there i have added one more refrence in it "com.sap.exception" of type "weak". My structure is like this:
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.sdk.lib</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="service"> com.sap.aii.proxy.svc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.xi.util.misc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.guid</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.exception</reference-target>
</reference>
</application-j2ee-engine>
Please help.
Thanks
Amit

Is Asynchronous ABAP proxy client possible without XI ?

Hi there,
Does anyone of you know if it is possible to create an asynchronous ABAP proxy client, without XI, thus directly in a SAP ERP 60 ABAP ?
Karim

Hi Anton,
thanks for your answer, it confirmed what I was thinking (asynchronous not possible in that case).
Now this leads me to a second question:
I would like to implement the scenario "acknowledge only and receive full answer later".
As you indicate: "...additionally to your webservice client you have to provide a webservice, which the receiver calls once it completes your request..."
In order to do this, I must practice as follows:
The service I call is using the WS-Addressing specifications.
Therefore, the information regarding the webservice that will be called when the request is completed should be sent as a special SOAP WS-addressing parameter, that should be indicated in the header of the SOAP Message, here is an example:
(001) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
                xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
(002)   <S:Header>
(003)    <wsa:MessageID>
(004)      uuid:6B29FC40-CA47-1067-B31D-00DD010662DA
(005)    </wsa:MessageID>
(006)    <wsa:ReplyTo>
(007)      <wsa:Address>http://business456.example/client1</wsa:Address>
(008)    </wsa:ReplyTo>
(009)    <wsa:To>http://fabrikam123.example/Purchasing</wsa:To>
(010)    <wsa:Action>http://fabrikam123.example/SubmitPO</wsa:Action>
(011)   </S:Header>
(012)   <S:Body>
(013)     ...
(014)   </S:Body>
(015) </S:Envelope>
You can see that the WS-A specific part is in the header of the SOAP Message, not in the body, so not covered by the WSDL.
Question: Is it possible to include this in the header of the SOAP Message generated by the ABAP proxy client ???

Adapter specific message attributes in ABAP proxy

Dear all,
i have a short question. I have a file to ABAP server proxy scenario. When picking up the file i write communication data from the adapter in the message header using dynamic configuration and route the message to a abap proxy.
My question is: Do i have access to the header data in the proxy, or do I have to make a message mapping and put the header data into the payload of the message?
Kind regards
Florian

Hi,
here is a blog about your scenario:
File to R/3 via ABAP Proxy
Hope it helps.
Regards
Patrick

Fault Message generated in ABAP Inboud Async Proxy not visible XI Moni

Hi
    I developed a ABAP Inbound AsyncProxy, which raises an exception using a fault message type. The SMB_MONI in the Business System is displaying the message as Application Error. But the XI Monitor is showing it as sucesfully processed.
    How do I monitor application errors from XI Monitor when I am sending Asynchronous Messages using ABAP Proxies?
    The business system in context is R/3 Enterprise System which is has got the APINT patch on it.
Thanks in advance...
Regards
KP

I'm developing a Java Proxy and I'm experiencing the same problem. The exception is raised by my Java Proxy and it can be checked in RWB Message Monitoring of my central adapter engine. It can alse be checked in the MessagingSystem.
Unfortunately, no message is returned to SAP XI, at least, I cannot see anything in SXI_MONITOR (SXMB_MONI).
The point is: does ir make sense to generate a fault message in xml just to be checked in an html monitor? The xml tags don't appear correctly in html format and I had to debug my application in order to find out that the exception was correctly returned.
If anyone here have advanced in this issue, please let me know.
Best regards,
Ricardo Bochner.

Fault message handling in abap client proxy

Hi experts,
i have scenario like this SAPECC---XI---WEBservice
i was decided to using the ABAP CLIENT proxy in sender side and soap adapter communication in receiver side
i will be get the wsdl file form client
problem is i am in bit of confusion like am i need to create fault message for this asychronous scenario?
how can i create the fault message for this scenario(that WSDL) and how the abaperwill handle those error
thanks in advance

Hi.
You can use fault message but it won´t return a error to your ABAP Proxy because your interface is ASSYNC. The fault message generated will stop in Adapter Engine.
If you need a return of the error, you have to change your interface to Sync mode.
To get more information, follow the link below:
Fault Message Type
http://help.sap.com/saphelp_nwpi711/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
Best Regards.
Bruno

Fault Message in Asynchronous

Dear Friends,
In Message interface there is a option to select synchronous or asynchronous. If we select synchronous the fault message appearing and if select assynchronous the fault message disappearing, then in this case how can we do fault handling.
Thanks
Prem

hi
A fault message is a message that describes an application-specific error situation.
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
· In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
· The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

Fault message handling in syn proxy

Hi Experts,
I have implemented Proxy to Web service synchronization scenario and implemented request response and fault message mapping.
But when the scenario is getting the Application error the fault message is visible in sxmb_moni but not visible in the proxy or not being forward to proxy ?
Can you help if there is any more config or any other follow up is required, all the mapping and other part of fault message is as per PI standard only including the proxy ABAP code?
regards,.

Hi,
But when the scenario is getting the Application error the fault message is visible in sxmb_moni but not visible in the proxy or not being forward to proxy ? - In your R/3 system by transaction SXMB_ADM, then integration engine configuration - specific configuration - in RUNTIME add parameter for logging and tracing and set it to maximum level...........also LOGGING_SYNC parameter should be enabled................
then re-run your scenario..........then for a application fault msg in SXMB_MONI of XI, you should see a fault msg in SXMB_MONI of your r/3 system.
Regards,
Rajeev Gupta

Is EOIO messaging possible using ABAP Proxy in WAS 620?

Hello,
I am trying to implement an outbound EOIO interface using ABAP Proxy on a SAP R/3 470 running on WAS 620. We have XI 3.0 running on WAS 640. I followed the SAP documentation available at http://help.sap.com/saphelp_nw04/helpdata/en/c9/74246d8ad2447799063d39013e9a11/frameset.htm
I find that the interface IF_WSPROTOCOL_ASYNC_MESSAGING required in this exaple does not exist in our R/3 system. I also notice that proxy classes generated on WAS 640 have the superclass of CL_PROXY_BASIS. But the proxy object generated in WAS 620 have no superclass at all.
Does anybody know how I can get EOIO interfaces to work on the WAS 620? Did you use these objects? Can I import / install them somehow? Or, is EOIO just not possible in WAS 620?
Please let me know.
Regards
Cerish Chemparathy

HI,
have a look at this link to the ABAP Proxy Runtime based on WAS 6.20 (Xi 2.0) http://help.sap.com/saphelp_xi20sr1/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
There is a help entry called Guatanteeing the Order of Asynchronous Messages. Seems that you somehow can set a queue id for this messages and as long as theses messages are all in the same queue, the order will be maintained.
Your observations are right, there are differences between the Proxy Runtime in WAS 6.20 and in WAS 6.40 and as far as i know, there is no way to downport the 6.40 runtime to 6.20. You will need to stick with wath 6.20 offers.
Regards
Christine

Integration Engine Message Id in ABAP Proxy

Hi,
I have a scenario sending to XI from CRM using an ABAP Proxy.
I need to get the message id generated in the local Integration Engine when a message is sent via the ABAP Proxy or received into the ABAP Proxy.
I see there is a way of doing this in XI and also thought I had found a way of getting it in the proxy in CRM but this does not seem to work correctly even though i can see the message ID being created in the proxy call to XI.
I am trying to get the message id immediately after the proxy call to XI.
Kind regards
Colin.

Hi Colin,
as far as I know, it is possible. Have a look at the online help on abap proxies and check out the determination of message id:
http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
Hope that helps,
regards, jaime

Asynchronous ABAP proxy

hello everybody!
i'm working with PI 7.1
i create a interface ABAP proxy -> PI -> file
so is a async interface.
every step was created succesfully.
When i try to call proxy from my abap program or from test tool in SPROXY transaction i don't see any message in monitor.
No file arrived, no errors in log , (SM58, ST22, SM21, integration monitor)...nothing.
i tryed to change the Service Interface and set Syncrounous mode.
so now the file is arrived!!!!!! but... i have error in message monitor because (correctly) it's expecting a return mapping.
where is the problem? can i use this scenario?
thanks!
PS: I prefere find a solution without use the sync async bridge.

yes of corse:
in IR
MessageType_IN
MessageType_OUT
MessageMapping between the 2 MT
a service interface SI_SP2FS_OUT Outbound and Async
a service interface SI_SP2FS_IN Inbound and Async
a Operation mapping between SI_SP2FS_OUT and SI_SP2FS_IN
In ID
Communication Channel to FTP folder
Receiver determination with follow parameter:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
receiver party : *
receiver communication Component : *
Configured receivers: FTP_DEV
Interface Determination:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
Receiver Agreement:
sender communication Component : SAP_DEV
receiver communication Component : FTP_DEV
receiver Interface : SI_SP2FS_IN
receiver namespace : http://mynamespace
In R3 abap side i created proxy pointing to SI_SP2FS_OUT with SPROXY transaction.

Fault message in Asynchronous messages - SXMB_MONI in PI problem

Hello,
I am working on File to Proxy asynchrnous interfaces. I am using fault message type on inbound message interfaces.
I have done all the configuration according to below link
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
After raising the exception, I can see messages are being failed in ECC , but in PI moni, message status is successfully status.
I want PI message status "Application Error".
Any idea.
Thanks in advance.

Just letting you know fault message is not something message could not be processed or due to system error mesg failed or so.
Using fault message to show business errors for the application. Example if the request message does not have purchase order number, then fault mesg could be "Purchase order is missing". In this case, Pi will respond with fault message. But this is successful processing end to end.
Basically you get response from ECC as fault message not wrong in it. SO PI will show only success log.
Dont confuse messages failing due to system downtime or network issues or firewall issue with application or business logic errors. Hope that helps.

ICM_HTTP_CONNECTION_FAILED message in SM59 (ABAP Proxy Connection)

Hi All,
Recently, i got a problem with our XI server, suddently the ABAP proxy connectiont to XI from another SAP server was failed. i was check from sm59 the HTTP connection return me ICM_HTTP_CONNECTION_FAILED.
i already check the port and calling this link http://demokl:8001/sap/XI/engine?type=entry from the other server it is working fine. but still got problem from SM59.
Please help.
Regards
Fernand

Hi jagadish,
These are my parameters :
Connection Type = (H) HTTP Connection to ABAP System
Target host = demokl (hostname)
Path Prefix = /sap/XI/engine?type=entry
Service       = 8001
Language   = EN
Client        = 300
User          = PIAPPLUSER
Previously was working fine, but suddently go problem. but i was trying to create HTTP connection from XI Box itself it is working fine but from others box didn't work.
i have check the port it is open.
Please help
Regards
Fernand

Fault message in asynchronous ABAP Proxy

Similar Messages

Maybe you are looking for