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.

Similar Messages

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

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

~messageline.dim always 1, even when more than 1 message generated in ABAP

Can anyone help explain how the ITS ~messageline gets populated. In my transaction I am creating a number of warning messages. However, the ITS is only displaying 1 each time.
I am using the following code, but ~messageline.dim is always 1.
`repeat with m from 1 to messageline.dim` `messageline[m]``end`
Thank you
Karen

G'day Karen,
I had a similar problem with my ALV in the ITS template.
My solution was that I had added too many Service Parameters to my service in transaction SICF.
The only parameters I have for my service are:
~TRANSACTION (my transaction code)
~THEME 99
With only those parameters against my service, everything started to work, having more than 1 entry show up in my ALV and the scrolling...
Hope this helps.
Cheers,
Mick.

Messages are not visible in moni

Hi PI mates,
i have peculiar problem in my porduction environment. Here is the brief description.
" Communication channel is picking up the file and archiving but not processing the file to the Integration Server but cannot see the message and message ID in MONI and communication channel
It is not showing any message (Error/successful/Queue). This is in PI7.1
When I test the same interface in Development server it is working fine. This problem is occurring only in PROD"
i have changed the version of channel also but same problem..nex thing i gave wrong data that time it is giving error messages in Monitor and communication channel moni.
Kindnly look into this and give me solution if any of you faced kind of problem.
Regards,
Allamudi Loordh.

Hello Allamudi,
Can you elaborate more on your issue.
1. Are you not able to view any type of messages in SXI_MONITOR. I mean sync and Async.
2. Please check this blog from Michal
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1629
3. You can see asynch messages in MONI, but are not able to view Synch messages, then
in SXMB_ADM --> Integration Engine Configuration --> Specific Configuration --> Add the parameter ,
Category --> RunTime LOGGING_SYNC set to 1.
4. Also check you pipeline configuration in SXMB_ADM.
I hope this should resolve your problem.
regards,
Younus

Doc Uploaded by ABAP Class CL_SA_DOC_FACTORY= UPLOAD_DOC not visible

I am uploading a document in Solution manager through the below code.
CALL METHOD CL_SA_DOC_FACTORY=>UPLOAD_DOC
EXPORTING
    I_DOC_TITLE              = 'TEST'
    I_DOC_TECH_NAME          = 'TEST'
    I_DOC_TYPE               = 'AD'
    I_DOC_STATUS             = 'RELEASED'
    I_DOC_BLUEPRINT_RELEVANT = 'X'
   I_FOLDER_ID              = 'DF1223E3C88613F1BDD70011258C9477'
   I_FOLDER_TITLE           =
    I_FOLDER_TECH_NAME       = 'TCLSUPPORT'
    I_FOLDER_RESPONSIBLE     = SY-UNAME
RECEIVING
    E_IOBJECT                = eobj
EXCEPTIONS
   CANCELLED                = 1
   FOLDER_ERROR             = 2
   ERROR                    = 3
   others                   = 4
CALL METHOD eobj->SAVE
EXPORTING
RECEIVING
    E_LOIO             = eresult
EXCEPTIONS
   CANCELLED          = 1
   ERROR              = 2
   others             = 3
eresult structure gives:
CLASS      SOLARGEN
OBJID       DF1BC08D3D729FF1BDD70011258C9477
But when I go to SOLAR01 and then to my project document in not visible there.
Tables SA01PHIO and SA01LOIO are getting updated with OBJID but document not visible through SOLAR01

Hi Abhinav,
Did you perhaps every find the document that you uploaded?
I am experiencing the same problem and would be interested in your solution.
Thanks,
Miguel

ESS- ABAP Webdynpro- table column not visible

Hi,
We are using SAP travel management for expense approvals. In the package PTRM_WEB_UI, you will find the component FITE_VC_RECEIPTS. In the VIEW - RECEIPTS_VIEW you will find in the table that there is a column called "Short Info". However this column in not visible in the portal.
There is no personalization done to hide this column.
The visible property of this column is set to "visible".
In portal content directory if i right click....this column is not even available to be added/removed.
Please help me understand why this column in not visible and how can i make it appear in portal.
Thank You!

Any input?

Based on fault message ABAP coding required.

Dear Experts,
I design a scenario with Proxy to JDBC Synchronous interface, in that i kept fault message to catch the technical errors which are throwing by Oracle system like " unique constaint violated, can't insert value into a particular field ". This type of error messages we can able to get in sxmb_moni of PI system as below shown, but we need the same message in SAP system. For that what we have to do in ABAP as well as PI sides. Below highlighted error message wants in SAP Screen.
Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PDI_PIPE' (structure 'Statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_PDI_PIPE'. Cannot insert duplicate key in object 'dbo.PDI_PIPE'.</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Kindly suggest me..
Thanks & Regards,
Srihari.

Hi,
We can easily implement fault message coding in ABAP server proxies, but in case of JDBC not sure you can implement this.
one sulution is write a stored procedure in receiver side and you can have a flexibility to send error message as a response(in vaid exml format).
using standard insert statement/anyother data base operation without stored procedure not posible to capture these kind of errors in to falut messages and sending back to ECC may be not possible.
regards,
Raj

SOAP Adapter - Using Fault Message

Hi all,
I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
Thanks
Gary

Dont think this is possible in standard.
As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
For the fault message mapping you need not add the SOAP Envelope.
Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
Regards
Bhavesh

Fault Message Types

Hi experts
i have a following scenario. the scenario is SOAP to XI to ECC, and from XI to ECC RFC's are being used. i have doubt about the fault message types?
what are fault message types and why should they be created???
for the above required scenario does"fault message types are to be created or not" plz let me know.
Thanx in advance

Hi,
>>ii have doubt about the fault message types? what are fault message types and why should they be created???
According to help.sap.com http://help.sap.com/saphelp_nwpi71/helpdata/EN/dd/b7623c6369f454e10000000a114084/content.htm
Fault message types are designed for application-specific errors that occur at the provider (inbound side) and that are reported back to the sender or persisted in monitoring.
1) 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.
2) 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 acknowledgment (see Acknowledgments).
>>for the above required scenario does"fault message types are to be created or not" plz let me know.
You can send the exception of RFC in Fault message type. (Provided the RFC raises an exception)
Regards
Suraj

BPM synchronous send step - Fault message extraction

Hello Experts,
I am developing a BPM with Asynch RFC -> synch Webservice -> Asynch RFC scenario.
I have defined fault message in the synchronous interface used in the send step for web service, and also defined
exception branch where an alert is thrown.
In the alert, i want to send the fault text from the fault message. How can i do that??
Thanks

Hi Mona,
SOAP adapter doesnt support fault messages.
check stephan's reply @ How catch the SOAP Fault Message ?
> SOAP adapter does not support fault message.
> Any fault is treated as error.
> fault messages are only supported for XI messages (ABAP or Java proxies) and RFCs.
Fault message handling is not possible inside BPM.

Posting a message directly to abap engine

Hi all,
I'm developing an adapter and I wish to post directly my message to an abap engine via http, not passing through the http adapter; does anyone know how to make it? Which is the receiver service's parameters? and how to communicate using the abap proxy engine(of course via java, not via XI service)
thanx
Paolo

hi,
I belive you can copy a service from SICF
and put your class in the handler list
you can try copying adapter_plain
and the default CL_HTTP_PLAIN_INBOUND
handler and replace it with your code
but I've never done it yet so I don't know
if this is a suitable way
more:
http://help.sap.com/saphelp_nw04/helpdata/en/c6/839c4eea6f374b8e230ef4b152b110/content.htm
Regards,
michal

CX_SY_MOVE_CAST_ERROR in SPROXY Class after creating fault messages in PI ?

Hi All,
We created a SOAP to Proxy synchronous scenario and everthing works fine.
Now we have created a fault message in PI and regenerated the proxy in ECC, after regenerating the proxy, if i debug the proxy from service registry, breakpoint gets triggered in proxy class and iam getting an exception "CX_SY_MOVE_CAST_ERROR" at the status bar (but not dump). After executing the proxy class i could get the required response in service registry but with the exception ( Connection IO Exception. Check nested exception for details. (Invalid SOAP Response. Runtime can not find return parameter <(http://hostname.com/soaptoproxy)MT_Soap_Response>.). In MONI i could see this as a successful message. Can anyone tell me reason for this exception both in proxy class and in Service registry ? I also regenerated the proxy class after creating fault message in PI.
Thanks,
Sivakumar.C

Hi,
Thanks. I have tested in locally in SPROXY and i found that exception occurs in the constructor method of exception class, which was created by adding Fault Messages in PI. Any Suggestions ?
Thanks,
Sivakumar.C
Edited by: kumar.sappi on Feb 6, 2012 12:19 PM
Edited by: kumar.sappi on Feb 6, 2012 1:49 PM

Sending back fault message from receiver to the sender

Hi,
Can somebody explain me, how to capture fault message generated by the receiver system back to the sender system?
I have a synchronous scenario, RFC -> XI -> Web Service.
When web service returns successful response, it gets mapped properly to an internal table of RFC. But, when web service returns fault message (as parameters passed to the web service are incorrect), RFC gives dump. Below message is shown in sxmb_moni.
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: com.ucas.hei.link.exception.WSException: Data access error: Incorrect userId/password. at com.ucas.hei.link.xml.ReferenceData.getRefInstUcas(ReferenceData.java:2338)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Has anybody worked with this type of scenario? Please help me.
Thanks & Regards,
-Smita

Hi Smitha,
if you are calling a webserive from XI and the websevice call results in a soap exception, as of SP13 i am sure there is no way to capture this exception.
Work around approach would be to define exceptions for your sender RFC and hence when an exception is raised in XI, sender RFC will not dump instead you would have the defined exception caught.
CALL FUNCTION 'XYZ'
     EXPORTING
     IMPORTING
     EXCEPTIONS
       OTHERS          = 1.
cheers,
Naveen

Fault Message Mapping for SOAP Scenario

Hi ,
I have configured a Proxy to SOAP synchronous scenario. The scenario is working fine. Now I need to map the fault message and display the message in SAP in case of any errors. I have used the standard Fault message. But I dont have any message from the WSDL which I can map to the standard fault message. Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same.
Thanks
Amit

>>> Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same?
Fault message is to provide meaningful message to the other end if there is a validation error or business exceptions or so...
a) You are importing WSDL of the third party and using it in soap receiver target side.
b) Normally it is best practice to create a WSDL which contains request, response and fault message. if your wsdl has fault message type declared then you can map the wsdl fault message with your proxy side fault message(which you can create). Please note you rely on the third party wsdl. Third party WSDL must have application logic coded to support fault message in case of application error occurs. Example if there is a validation that does not go through then their application logic must populate data in the fault message of wsdl. Then only if we map the wsdl fault msg to our proxy fault msg, we get meaningful fault details.
If your target WSDL does not support fault mesg, it is not going to be helpful at all.

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

Similar Messages

Maybe you are looking for