Forward Error Handling

Hi,
Does anyone know where I can find more information on SAP Forward Error Handling? The only info I have found so far is here [<clicky>|http://esoadocu.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?sap-unique=125551&sap-params=cGFja2FnZWlkPURDQkQzMTVCNkQ3MjU1RjE5QUYyMDAxNDM4QzNCQzA4JmlkPTYyMTEwMEJBRkQ4NDQzQjBCNjkyN0FERjNGNkQ3MkZBJnBhY2thZ2VpZD1ERTA0Mjg0Njg3QkVCREYxOTUxNTAwMUE2NEQzRjQ2Mg%3d%3d]
I have found the correct place in the IMG but there is not much additional documentation there either.
Thanks
Manish

Goto SAP service marketplace and search for
SAP Reference Implementation Guide -> Cross-Application Components -> Processes and Tools for Enterprise Applications -> Enterprise Services -> Error and Conflict Handling .
Your link is not correct, I found one: http://esoadocu.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?sap-unique=122005&sap-params=cGFja2FnZWlkPURDQkQzMTVCNkQ3MjU1RjE5QUYyMDAxNDM4QzNCQzA4JmlkPTYyMTEwMEJBRkQ4NDQzQjBCNjkyN0FERjNGNkQ3MkZBJnBhY2thZ2VpZD1ERTA0Mjg0Njg3QkVCREYxOTUxNTAwMUE2NEQzRjQ2Mg%3d%3d
Reards,
Gourav

Similar Messages

How to activate Forward Error Handling in SRM

Hello Gurus,
I got an requirement to activate Forward Error Handling in SRM. I have searched on SDN but didn't find appropriate answer on it.
Even I found some link: PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
It explains me some points like activating FEH from SRM in SPRO. I have activated the same, plz check the screen shot:
It also follows some development for the same.
Here my concern is, should I follow this document? Does it applicable to all to all the scenarios?
Step 8: it assign object id and type what does it mean...
Does any one can explain me in detail..... Please provide me any document to configure the FEH in SRM.
I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
I have made some configurations like:
The view FEHV_ACTIVE must have the status active.
In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
As stated in in the link :
http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
Resulted, the “Process” button get activated in the XML Post Processing screen.
But can I reprocess my XML with edited value from there..?
All the configuration part of PI is already done .
I wanted to know about the FEH Part. what are the steps i am missing or where i am going wrong ?
Please let me help.
Thanks
Regards
Karan

Dear Raz,
I have gone with above mentioned note, it explains about creating Custom Proxy and configuration with PI scenario. Even the link in my previous post, explains about the custom proxies and configuration..
I think I should must be descriptive about my issue.
I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
I have made some configurations like:
The view FEHV_ACTIVE must have the status active.
In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
As stated in in the link :
http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
Resulted, the “Process” button get activated in the XML Post Processing screen.
But can I reprocess my XML with edited value from there..?
Can any one tell me, what are the steps I am missing here. As this is my first time to implement FEH, I am confused.
Please let me help.
Regards,
Chandan

How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?

Dear all
How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?
Thanks
Regards
karan

Hello
These are the following errors
1. Trace level="1" type="T">no interface action for sender or receiver found</Trace>
2. <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!
3.
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</
Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>Trace level="3" type="T">Error of the prevous version:</TraceTrace level="3" type="T">Error ID APPLICATION_ERROR</Trace>
tThere are repeating errors also.
TThanks
Regards
kkaran

Forward Error Handling (FEH) framework?

Hi all
Forward Error Handling (FEH) framework - can any one expalin this?
Muthu

Hi,
Forward Error Handling (FEH) is a framework in SOA for performing error processing in
asynchronous communication on the receiver side. Please check the troubleshooting document.
https://service.sap.com/sap/support/notes/1270081
Regards,
Masa

Forward Error Handling - File interfaces?

Hello Experts,
Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
Thanks.

Edit 1 May 2015: Added inbound
Just a slight correction.
FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
Message was edited by: Eng Swee Yeoh

Forward Error Handler - Add component to table '

Hello,
I've been configuring SOA. Note '1270081 - Trouble shooting SOA Services' explains monitoring of SOA including FEH. It says that you need to maintain an entry for every system in table: '/n/SAPPO/LOGSYS'. In our case SRM <> R/3 we would need to configure 2 entries, one entry per system.
The above table does not excist in any of both systems. However i did find the following tableview: /SAPPO/VLGSYS. Should we use and configure it here? What does this configuration do / why is it required?
Kind regards,
Tim

Tim,
Rather than table, did you try it as Transaction ..
/n/SAPPO/LOGSYS
It's works.. also try transaction /n/SAPPO/PPO2.
Regards,
Sandeep Parab

General Error Handling - use of FEH (PPO/ECH)

We are investigating the usage of Forward Error Handling, known with SAP as PPO (Post Processing) and ECH (Error Capture Handler) to be able to re-process errors (automatically or manually) from incoming messages.
I am interested in talking with anyone who has implemented this. General questions are:
- how have you found it to work in real life?
- configuration/set-up straight-forward?
- what scenarios have used it in?
- incorporated into your custom services?
But am interested in any comments.
I am posting this within the PI forum as it ties into the fact we async scenarios inbound to SAP, typically from our PI system, and when those scenarios encounter an error we are looking for a way to have a business/end user - friendly interface for reprocessing the error. Implementing a proxy scenario, and thus having the errors show within sxmb_moni/sxi_monitor, is probably not going to work for us - too technical. I am also aware of an add-on, AIF I believe, but our company is not interested in installing that.
There are 4 blogs out there that I am aware of - 2 from Tobias and 2 from Michal. Very informative. I am finding some config not as ours though. Am really interested in anyone has really implemented and used this in a prod environment.
Regards,
Keith

I think I am exactly at the same position as you in figuring out the usage of FEH in an environment. I just completed a small document (for internal purpose) that I prepared gathering all the information from those blogs, SCN and TechEd. Here are my 2 cents:
>>- how have you found it to work in real life?
We haven't implemented it yet. But we believe it will be quite useful in handling business specific errors. We are trying to find out if it can be merged with the existing BPEM infrastructure to generate BPEM cases.
>>- configuration/set-up straight-forward?
Yes, the blogs should be quite useful to provide this information.
>>- what scenarios have used it in?
Most importantly it will be used for standard service implementation where we consume enterprise services from ES workplace. These services have FEH capability built in (they have FEH method implemented within). The scenarios are of course inbound abap proxy.
>>- incorporated into your custom services?
We are still in design phase. But if you ask me about it, i would say yes you can and I think you should use it for custom ones as well.
Kind regards,
Prateek Raj Srivastava

Handling forwarding errors

Hi,
          Is it possible to checkfor the existance of a JSP page / servlet?
          I want to achieve something like this in a servlet...
          forward to page1.jsp
               if failed(page not exist), forward to page2.jsp
                    if failed(page not exist), forward to page3.jsp
          However, using RequestDispatcher.include() to a non-existant page seems
          to hang waiting for something.
          Using RequestDispatcher.forward() to a non-existant page just sends a 404
          to the client.
          If either would throw an exception, I could catch it and forward to my next
          required page. Am I missing something obvious, or does the JSP spec not
          allow for this kind of thing?
          Thanks,
          Martin.


Thanks Anirudh,
In Flash Builder, try doing
if(this.hasOwnProperty("d") && this["d"] == 1){ }
I was just throwing this error as an example of throwing an error, and not looking to fix it in particular. We have a large and complex application which is used by many people. Unfortunately, some of our users are experiencing runtime errors that are stopping the execution of the script - and we do not know exactly where those are. They may be easy to fix once we can locate them. Unfortunately, we have not been able to reproduce them locally.
If the flash player encounters an error in the constructor of the sprite/movieclip which is the main class, it will not be able to continue. If this error had occurred in an event handler, then you'd be able to continue.
Can you tell us more about the rules of uncaught runtime error handling? For example: when I compile this code - the sprite is not shown on the stage and the second trace is not executed - despite having moved the code to an event handler function.
package
import flash.display.MovieClip;
import flash.display.Sprite;
import flash.events.Event;
import flash.events.TimerEvent;
import flash.utils.Timer;
import org.osmf.events.TimeEvent;
public class ErrorTest extends MovieClip
public function ErrorTest()
var t:Timer = new Timer(100, 1);
t.addEventListener(TimerEvent.TIMER, eventHandler);
t.start();
protected function eventHandler(e:Event):void {
trace("1");
if(this["d"] == 1){}
trace("2");
var s:Sprite = new Sprite();
s.graphics.beginFill(0xFFCC00);
s.graphics.drawRect(0,0,200,200);
addChild(s);
I'd like to publish our application such that it would ignore all run time errors. Are there any compiler or other options to achieve that.
Ideally we'd like to collate the errors such that end users could open a hidden text field and copy the error messages and send them to us.

Error handling in overridden methods in AbstractPageBean

Hi,
I'm writing a small app in JSF. One of the pages populates a bunch of text fields from an XML file whose name is passed into the app as an initialization parameter. The purpose of the page is to allow editing of the fields.
It seemed that the prerender() method was the right place to initialize the fields in the form. I have an application-scoped bean trying to open the XML file. I don't want the app to barf on initialization if the file doesn't exist, because the application contains the logic to create the file. So it just sets the appropriate forward target ("file does not exist" page, or maybe XML parse error) and lets the pages that use those bean properties decide when and if they need to display the initialization error page.
I would like to throw an exception from the prerender() method in my page, and have the error handling specified in web.xml. The problem, of course, is that I can't throw my own exception from prerender().
So, have I got the wrong place to initialize my form, or do I have to throw a javax.faces.FacesException, or have I got this whole error-handling thing wrong?
Any advice would be gratefully received.
Many thanks.
Regards,
Mike
public void prerender(){
        // Get ApplicationBean1 to forward the request if we fail to
        // initialize properly.
        ApplicationBean1 ab1 = getApplicationBean1();
        HttpServletRequest req = (HttpServletRequest) this.getFacesContext().
                getExternalContext().
                getRequest();
        HttpServletResponse res = (HttpServletResponse) this.getFacesContext().
                getExternalContext().
                getResponse();
        if(!ab1.isInitialized()){
            //The initialization code for ApplicationBean1() sets the
            //target when it detects an error and then forwards the
            //request to that target upon invocation of the forwardRequest
            //method
            ab1.forwardRequest(req,res);
        // These are the input components
        tfClonebase.setValue(ab1.getClonebase());
        tfDhcpdconf.setValue(ab1.getDhcpdconf());
        tfNamedrev.setValue(ab1.getNamedrev());
        tfNamedzone.setValue(ab1.getNamedzone());
        tfPxelinux.setValue(ab1.getPxelinux());
        tfXmldir.setValue(ab1.getXmlDir());
    }

Well, I'm certainly no expert, but prerender() is called, as you might expect, just before rendering takes place (but only if the page will actually be rendered). This means it won't be called for a page that handled a postback but then navigated to a different page. Good place to handle initializations that happen before rendering.
So my thinking was that I could initialize stuff before there's anything in the response, making it easier to bail out if something goes bad.
But I really can't work out the right way to bail out: I can't throw my own exception because the prerender() is overridden from AbstractPageBean. So I suppose I could create a MikesBadInitException e and throw it inside a new javax.faces.FacesException(e). But I'd like to specify an error-page in my web.xml for MikesBadInitException, and don't want to handle all javax.faces.FacesExceptions, if you get my drift.

Step by Step documents for Process Chain Error Handling with Screen Shots

Hi
Is anybody having Step By Step Documents for Process Chain Error Handling with Screen Shots ?. Please forward it to me to my e-mail [email protected] . I will reward points to u immediately.
bye
Aamira Khan

Hi,
You can find lots of topic related to process chain issues in SDN.Please make a search in SDN.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&query=process+chain&adv=true&sdn_author_name=&sdn_updated_on_comparator=ge&sdn_updated_on=&sortby=cm_rnd_rankvalue
Regards.

ESB error handling and notification features

Hello everyone,
I am newbie to oracle SOA ESB. I am an oracle apps guy.
This being my first post to this forum, I have a lot of questions. :-)
For a small intergration requirement, we are looking for a good integration tool
Some requirements are:
1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
2) Pick the data from apps tables and insert them into another database. Not much translation required.
After some research, found ESB to be a good fit.
Before actually start using it, we wanted to do a couple of POCs.
So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
Some error conditions:
1) Unavailability of ftp server or Database server.
2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
My initial thoughts on error handling are:
Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
Data mismatch: NOtification to be sent with the error details.
I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
Please suggest me of some documents if any related to my questions.
Would be really great if you can give me a straight forward solution to all the above problems
Hope this forum would be a great help to me.
Cheers,
Robert.

I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
cheers
James

/SAPSRM/CL_OFFLINEAPP_INBOUND error handling

Hello gurus,
I hope someone may enlighten me with a question I have on the Offline Approval inbound process...
We're running SRM 7.0 SP9, and in order to configure the inbound processing of the offline approval we have to go to SO50, add the exit /SAPSRM/CL_OFFLINEAPP_INBOUND etc. All good so far!
The question: how is the error handling done, and most importantly how may we add our custom logic? I see there is a method called HANDLE_ERROR (where I could add an enhancement implementation) - which seems to not be called anywhere and doesn't have any import/export parameters! Therefore this is no good for me I guess (unless someone proves me wrong?)
Basically my client wants to add an entry to RZ20 alert / or a normal log in SLG1 whenever an offline approval fails (if immediate processing fails for any other reason). By standard I think it forwards the reply e-mail to the SAP Business Workplace inbox of the user.
Has anyone done something similar? I have checked the forums and done several xSearches on the SAP Marketplace, however just hitting dead ends...
Many thanks!
Adi

Hi Adi Abu-Taha Zitawi,
Hope all is well.
I actually have the same question as you. The standard error handling functionality seems to send a message back to the "wf-batch" user if there is an error. Also, this message is pretty useless since it does not even contain the shopping cart #. This is also not an ideal solution because a business user has no visibility of these messages.
What / how did you end up resolving this business requirement? Did you implement the solution mentioned above?
cheers,

Error handling workflow not getting triggered

Hi all,
I'm creating a outbound IDoc. And for error handling workflow.. I created a organization structure in PPOME and assigned users. I gave this position number thus created in the partner profile in post processing permitted agent tab.
But when the Idoc is in error, this is not coming to my inbox.
Can someone please help me with this.. and let me know what went wrong.
Thanks in advance.

Here you need to be careful,
if the agent assignment is not maintained properly, there may be a chance everyone in the organization will get the item.
I hope you have created a single workitem for error handling. goto additional data-> agent assignment-> maintain. make sure the attribute is defined as general forwarding allowed. or you maintain the role/position/user/whatever.as the possible agents. still you dont get the result, debugging the default rule in the task ->default rule -> agent.
hope this helps.
with regards,
Sudhahar R

Asynchronous Error Handling in Flex

Hi,
When going through the Error Handling in Flex from Adobe site, i got confusion in understanding Asynchronous Way of
Error Handling Mechanish in FLEX .
Here the authro Mentiones an example related to File Uploading that is for FileReference class .
I am not quite familiar with File Uploading , so i could not able to gran this concept .
Please let me know what is this Asynchrnous Way of Error Handling in FLEX , because as far is synchronous is concerned it is straight Forward Mechanism .
Please help me in understanding this Concept.

Hi,
This type of error handling means that you will listen for events on the calling instance such as a file reference object. You will use the method addEventListener() and listen for events such as IO_ERROR or whatever event the instance will dispatch on error.
See the documentation for specific error events of each class that acts as a service.
The async part means that the error if thrown will happen after the line and method executes where you called your service.
Mike

IE / Spry Bug with custom error handler

Ok, as I was looking through SpryData.js I noticed these
wonderful lines:
Spry.Utils.loadURL.callback = function(req)
if (!req || req.xhRequest.readyState != 4)
return;
if (req.successCallback && (req.xhRequest.status ==
200 || req.xhRequest.status == 0))
req.successCallback(req);
else if (req.errorCallback)
req.errorCallback(req);
In particular the "errorCallback()" method interested me as I
wanted to introduce my own error handler. As I went about testing
this I came up with a quick try of:
var url = "/cfcs/mycfc.cfc?method=IsValidPath&path=" +
encodeURIComponent(sl.value + sd.value);
var optionsObj = new Object();
optionsObj.errorCallback = ShowError;
Spry.Utils.loadURL("GET", url, false, ValidateForm,
optionsObj);
And this works great in FF, but not IE. When I cause an error
to occur from ColdFusion I pass a status code of "500". In FF the
error code causes my "ShowError" function to fire, but not in IE. I
tracked it to this bit of code in SpryData.js:
Spry.Utils.loadURL = function(method, url, async, callback,
opts)
var req = new Spry.Utils.loadURL.Request();
req.method = method;
req.url = url;
req.async = async;
req.successCallback = callback;
Spry.Utils.setOptions(req, opts);
try
req.xhRequest = Spry.Utils.createXMLHttpRequest();
if (!req.xhRequest)
return null;
if (req.async)
req.xhRequest.onreadystatechange = function() {
Spry.Utils.loadURL.callback(req); };
req.xhRequest.open(req.method, req.url, req.async,
req.username, req.password);
if (req.headers)
for (var name in req.headers)
req.xhRequest.setRequestHeader(name, req.headers[name]);
req.xhRequest.send(req.postData);
if (!req.async)
Spry.Utils.loadURL.callback(req);
catch(e) { req = null; Spry.Debug.reportError("Exception
caught while loading " + url + ": " + e.message); }
return req;
Apparently running (req.xhRequest.send(req.postData);) in IE
will throw an error if the requested page throws an error status
code. This causes the try/catch in the Spry function to catch the
IE error and never allows my own error handler to run. Hopefully a
fix for this will be in the works because I really like the idea of
being able to use my own error handler.
--------Edited after initial post.--------
Ok, I figured out another item of interest. My requests
earlier were set to "async = false". If I set "async = true" then
it does work. I realized that because I was using sychronous mode
and IE was throwing the error, it was preventing the call to the
"Spry.Utils.loadURL.callback" method from occuring, while asynch
mode uses the onreadystatechange to call the function and thus
causes my own error handler to function. I am still interested to
know if there is a bug here somewhere and if it is just IE or Spry
or both. Looking forward to reading any posts.

Hi WraithBudde,
Thanks for all the details. In my opinion this is indeed a
bug in Spry for the synchronous case. I'll file a bug and fix it.
> You know you love me.
Heh, yeah, I love anybody who takes the time to report bugs
... especially when they've narrowed it down to the exact set of
lines in the source.
Once again ... THANKS!
--== Kin ==--

Forward Error Handling

Similar Messages

Maybe you are looking for