XI Contents : Error Handling : Syncronous Proxy - WebService Scenario

Hi,
I am working on Syncronous : Proxy <-> XI <-> WebService Scenario.
I am using Standard XI Contents from XI and SAP side.
Meaning : All the design objects like Message Interface / Message Types / Data Types etc are NOT created by me, but I am using from Standard XI Contents EA-HR 600. I did all the Configuration of the Scenario by using these Design objects.
In short , I can not change any of the Design object as it belongs to SAP.
Now, the scenario works fine. But I need to cater for Error handling.
Any suggestion.
I can not create fault messages as it is SAP's objects.
Thanks.
Dk

Thanks for suggestions.
Now my comment on these suggestions:
Option1 by Bhavesh. Copy Contents to my namespsce : I can do that, but here I need to tell you something. I have used Contents (Design Objects) and I didnt have to even create or activate any proxy ( I was amzed to see that ). Now, coping all the contents to my namespace will give me flexibility to add Fault Message (which is currently not avilable in standard content). but..but..I will have to create and generate / activate the proxy. ( Am I right?). Then where should I use this proxy? How my application will talk to this proxy? (I am not sure if I made my point clear). Currently I dont have to worry about communication between this HR application with standard Proxy ( which belongs to standard contents).
Option2 by Jai. Webservice changes : Webservice is not developed by me. I am consuming it. but I can ask this vendor who is WebService owner to change his webservice to suit my needs. But it wont solve the problem as I do not have Fault message at XI side.
I can consider Option1 by Bhavesh, if the proxy problem is solved.
Thanks,
DK

Similar Messages

Osb - bind error handler to proxy service

Hi!
I have got a proxy service which polls a POP3 server to download emails and process them.
My question: How could I bind an error handler to proxy service for noticing when the POP3 server is not available?
So I would like to put an alert when the OSB looses the connection to email server. I tried to put an error handler to top component on message flow but it doesn't work...
Could anyone help me?
Thanks!
Viktor

For poller transports (email/File/FTP etc) it is not possible to catch errors of transport layer, in your service error handler. Re: OSB - Error Handler in FTP Transport for TransportException
Thanks
Manoj
Edited by: Manoj Neelapu on Jun 28, 2010 3:51 PM

ABAP Mapping for Error handling in Proxy to JDBC

Hi All,
I am working on a proxy to jdbc scenario in which we have to throw validation errors to NWPM(Net Weaver Process Monitor Tool)
I am following the below steps,
step 1 - In message mapping a UDF is created to catch errors and store them in a variable using dynamic configuration
step 2 - writing abap mapping for handling this thrown exception and im reading the dynamic configuration in the abap class and raising exception. The exception format expected is
SAP:Error SOAP:mustUnderstand="" 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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1>ZPI_THROW_EXCEPTION</SAP:P1>
<SAP:P2>001</SAP:P2/>
<SAP:P3>Mandatory field is missing[BUKRS] </SAP:P3>
   <SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have written the following ABAP code to achieve this:
method IF_MAPPING~EXECUTE.
DATA l_record type mpp_dynamic.
DATA error type String.
getting dynamic configuration value
filled in by any previous mapping
CALL METHOD DYNAMIC_CONFIGURATION->GET_RECORD
EXPORTING
    NAMESPACE = 'http://sap.com/xi/XI/System/ERROR'
    NAME      = 'ERROR'
RECEIVING
    RECORD    = l_record.
error = l_record-value.
*raising exception with our message
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
   TEXTID =
   PREVIOUS =
    ERROR_CODE = '001'
    ERROR_TEXT = error .
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
   TEXTID =
   PREVIOUS =
    ERROR_CODE = '003'
    ERROR_TEXT = error .
endmethod.
I am gettign the following message for our code:
SAP:Error SOAP:mustUnderstand="" 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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could you please help in finding the solution for getting currect error message from ABAP class?
Edited by: SwethaC on Jan 21, 2011 8:18 AM

The error is due to RFC Call fail from PI system to your ECC Application System.
Check your RFC Destination for ECC System type 3 in PI System.
When you are receiving data from ECC System using Proxies & again you are going to ECC System for Validation.
Why you are not doing this validation on ECC System only in your proxy code ?
In your proxy code, it will be much better for performance to check your data there on same system.

Problem related to error handling in Proxy for Inbound

Hi All,
I have a requirement to process the inbound interface , which internally updates the HR Infotypes.
I need to handle all possible erorrs and store it in the custom table.
Can anyone please guide, as to how to catch the errors and wht type of errors can be there.
How to do that?
Any help will be gr8.
Regards,
Heena

Hi Heena,
the thread has been moved to ERP - Payroll as the application experts my be able to provide the list of error codes.
Regards
Kenny Scott
XI/PI Forum Moderator

How to create a generic error handling proxy?

Hello,
i have few services proxies.
I want to create a generic error handling osb proxy which does only errorhandling.
This proxy would be called by all my services.Now suppose my services proxies would throw any error,the control will pass to error handling block of proxy..from there i will call this generic errorhandling proxyusing a service callout or publish action.In this proxy i want to do all my error handling based on 'n' conditions.and i want to pass the message to the fault variable of services proxy..kindly suggest ways..*main challenge is passing the message to the fault variable of services proxy*

Hi,
For generic error handling framework or common error handling framework...create a bpel process which takes the error details payload and sends the inf/data as email to the particular receipients.
create business process with bpel process and proxy using business service.so wen ever error occurs at stage or route or proxy level ..call error handler action in OSB.Assign error handler details to the bpel input payload.
FOR EX:
<soap-env:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<com:test>
<com:ProcessInfo>testDetails</com:ProcessInfo>
<com:BusinessProcessName>testprocess</com:BusinessProcessName>
<com:BusinessProcessInstanceId>{fn-bea:uuid()}</com:BusinessProcessInstanceId>
<com:BusinessProcessStep>ReqLayer</com:BusinessProcessStep>
<com:ErrorCode>{string($fault/ctx:errorCode)}</com:ErrorCode>
<com:ErrorType>Technical</com:ErrorType>
<com:StatusCode>Error</com:StatusCode>
<com:ImplementationCode>OSB</com:ImplementationCode>
<com:ErrorDescription>{string($fault/ctx:reason)}</com:ErrorDescription>
<com:ErrorDateTime>{fn:current-dateTime()}</com:ErrorDateTime>
<com:Node>{string($fault/ctx:location/ctx:node)}</com:Node>
<com:Path>{string($fault/ctx:location/ctx:path)}</com:Path>
</com:test>
</soap-env:Body>
this assign the error details values to the bpel process.

Error Handling

hi,
I have an IDOC -> XI ->SOAP scenario.
How do we handle error handling in the below scenarios i described:
1. If i have an error in transmitting the xml to the receiver SOAP. How can i send an error email notification?
2. A retry or resend has to occur for 8 hours i.e., we keep trying for 8 hours and if it fails then we need to notify through email. How can we do this?
3. At the first failure transmission an email has to be notified and failure after 8 hours another email notification has to be sent so 2 emails will be sent for a failure transmission? Is this possible through XI?
How can we achieve the above?
Thanks,
Tirumal

Hi Tirumal,
Configure 2 alerts.
One to be triggered when there is the error in tramsmitting the SOAP XML.
Next to be triggered after the retry for 8 hours. If you are using the BPM with wait, then you can associate the Alert with the Exception block of your BPM and trigger the same.
Also, from SP14, Alerts can be triggered for errros in both integratioon engine and adapter engine.
To create alerts , this blog can help you out,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
If you are on Sp14, implement the note 913858.
If you are below SP14, then also check this blog,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Regards,
Bhavesh

Send a email while error handler Oracle Service bus 11g

I need to be send an email while error handler in proxy service message flow.
Error Handler Node -> stage -> report action
before or after report action, I need be to send a email
Could you please help this issue? I appreciate your help.
Thanks,
sdev

Add Alert to your Error Handler and set Alert Destination with your email set in.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html#wp1108089
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/alertdestinations.html

CF8 Webservice error handling

As my title tells you, I have a problem regarding error
handling in webservices.
I've set up an application.cfc where I've implemented
generalised error handling.
Whenever a coldfusion error occurs, this is the place the
error would be caught and properly handled.
I.E.: Don't give the whole stacktrace and the raw coldfusion
error message.
The problem is that, in the case of a SOAP request, the whole
onError method seems to be discarded.
It won't invoke this method. I've tested this using a
<cflog in the onError method.
Sometimes even, when the schema is incorrect it generates an
AXIS exception.
But there's no real way in coldfusion to catch or even handle
this exception.
Does anyone else know about a way to do this in coldfusion?
How can I catch those exceptions on my server and properly
handle them before returning the SOAP fault envelope?

We are implementing synchronus web services(proxy to web services) to sync master data with the external systems
In the above scenario it will be better to intimate the error details to the source system, i.e. option 2.....this will ensure that the source system application (developers/ monitors) are aware that something has gone wrong while processing data in the target.
Option 2. Send the the fault message(system error) to the source let the source system fail the message by not handling
the error, so that you get the alert with the stsndard alert configuration
Ultimately it is the business requirement which needs to be followed.....how does the business want to handle it....is the error required at the source
Regards,
Abhishek.

Error handling in abap proxy

Hi,
In my scenario, I have written code in the execute_synchronous method of the abap proxy in ECC. I want to capture all possible errors that might occur here and for all of them i want to capture the message id and the text and send it out. what kind of possible errors/exceptions can occur and how to handle them. My proxy class simply selects data from multiple tables in ECC and returns the same.
thks

Hi,
for outbound proxies the error handling should be done within R3 itself and there is no need to send errors to XI or receiving system for that matter. You would want someone from R3 side to take a note of it.
For Inbound proxies, you will have to implement the Fault messages
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.
For more information on the same.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In your case, since you said that you are selecting data from some tables, the possibility is that an entry is not found in the DB tables you will have to simply populate the fault message data and raise an expection CX_FM. It also depends on what error handling requirements from the Business .
regards,
Advait.

Error in SXMB_MONI for HTML to Webservice Scenario

Hi Experts,
I am facing following error Error in SXMB_MONI for HTML to Webservice Scenario
"Runtime exception occurred during application mapping com/sap/xi/tf/_MM_EmailRequest_To_ValidateEmail_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog."
Only one field is used i.e. email address and mapped properly in IR but still the error is persisting, Please suggest some way out.
Regards,
Nitin

Hi,
Mapping internall follows the SAX parser. Please check if you are trying to process the data of large size.
generally while parsing the large data this exception get raised. Even though there is just one field, what is the data size you are trying to pass.
Thanks
Swarup

Client ABAP proxy error handling. Please help!

Hi Experts,
   I have following scenario:
   SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
   This is Asynchronous.
   What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
   Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
   Please help.
Thanks & Regards
Gopal

Hello Gopal,
Correct, it should be an automatic entry into the queue!
refer below for a detailed understanding!
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
/people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
/people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
/people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
Regards,
Jilan

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

IDOC to SOAP asynchronous scenario Error handling

Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
Manish

Hello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh

Error Handling on RFC - XI - File Scenario

I have an R/3 RFC -> XI -> FILE scenario that works, but does not adequately handle the error of my R/3 to XI connection being down.
The RFC call is async since I was under the impression that I had to do a "to file" scenario that way.
    CALL FUNCTION 'ZXO_SAP2RFC'
      IN BACKGROUND TASK
      DESTINATION wa-rfc_dest_1
      EXPORTING
        request          = request
        rfc_header       = rfc_header.
    COMMIT WORK AND WAIT.
    IF sy-subrc <> 0.
      [error handling]
If my rfc destination is down (for example when XI is down), this RFC call is still getting a sy-subrc of '0' (so my error handling does not kick in).
Any suggestions?

Hi Keith,
your scenario is working correctly. If XI is down you will find your message queued in transaction SM58, where you can restart it manually. Usually there should be standard job for report RSARFCEX, which is periodicly trieing to restard the message.
Asynchr Call (tRFC) means that your program continues completly undependent from that call.
Make a test: Change temporary the called machine in SM59 destination to senseless value and execute your programm. Your message should be in SM58. Then correct the destination and wait a few minutes...
Regards,
Udo

XI Contents : Error Handling : Syncronous Proxy - WebService Scenario

Similar Messages

Maybe you are looking for