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

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

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

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

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

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

Error handler for event based messaging framework

I've been very interested in using the event based messaging framework (described here http://forums.ni.com/t5/LabVIEW/Community-Nugget-2009-03-13-An-Event-based-messageing-framework/td-p...) for my next large application.
My main concern is the fact that it seems like typos would be very difficult to debug since you need to ignore unknown commands to make this system work.
To solve this problem I've been considering the idea of having a single message error handler VI which will store all valid commands and check all sent commands to see if they are valid. Each VI would send out a register message on startup with their name and all messages they can send and receive. The message error handler would store these and then check all future messages to be sure it is a valid message, throwing an error if it is not.
My basic problem is this: for this to work the message error handler VI would have to be started before any messages are sent so that it can capture all the register events. If this is a VI that will be continuously running the entire application how can I ensure it starts first since I cannot wait for it to complete? (I.e. the usual method of running an error out wire or using a sequence structure will not work since everything will then wait for it to complete which will not happen until the program is ready to shut down)
I'm assuming the answer might be to use an asynchronous call but I'm not very familiar with this method.
Any help is appreciated. Thanks.

Could you just use the error handler as a subVI inside a case structure that is only called when you have new message to be checked? I'm not sure I understood the exact functionality you are looking for, so sorry if this does not apply.
Zach P.
Product Support Engineer | LabVIEW R&D | National Instruments

Error Handling Framework

Can anybody point or give me a good document on Error handling (Monitoting and Alerting) Framework in XI.
Thanks in advance.
Mukesh

Hi Sudhir,
Suppose the below is an Error XML message in Monitor in transaction sxmb_moni. Can we Catch these kind of error log messages and send an alert for it. Please suggest any kind of way thru which we can catch these kind of error messages. The below is just an example of an RFC destination 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=
<SAP:Category>XIAdapter</SAP:Category>
<SAP: Code area=IDOC_ADAPTER>ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1:Port ABCDE, client, RFC destination contains errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace= />
<SAP:Stack>Error: Transaction IDX1: Port ABCDE, Client, RFC destination contains errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help will be appreciated.
Regards
Ashish

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

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.

Difference between soa Error handling framework 10g & 11g

Hi,
Is there any document available which shows the difference between soa Error handling framework 10g & 11g
Thanks..

Hi,
Please find the documentation links here..
http://wiki.oracle.com/page/Application+Integration+Architecture
Foundation Pack Product Documentation - Metalink Note 824495.1
You can refer to the developer guide "E14750-01.pdf" and Chapter 13 for error handling related information.
Regards,
Narayana

Can error handling framework use fault policies and BPEL catch blocks

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

AIA Error Handling framework

Hi,
We have an AIA implementation where we are not using HWF for error handling. Now we have another project coming up where we would like to leverage this functionality. Was wondering if there is a way to activate HWF for few integrations only not at the server level.

Hi,
You can expose your HWF as a web service and use your new service after invoking this WS.
Is it what you are looking for.

Error in Control Framework in smart forms programms

IN VF02 smartforms ENTRY form , I add a function about save PDF at local PC. When I print the smartfomrs,There is ERROR message in update modules.
IN SM13 can see the ERROR message.
Function Module: RV_MESSAGE_UPDATE
Status :Update was terminated
Error details: FES 022: Error in Control Framework
THE CODE:
FORM processing USING proc_screen
                CHANGING cf_retcode.
******I ADD THE CODE
       PERFORM DOWNLOAD_AS_PDF USING lf_fm_name
                                     ls_control_param
                                     ls_composer_param
                                     ls_bil_invoice
                                     nast
                                     repeat
                                     ls_bil_invoice-HD_ORG
                                     ls_spoolid
                                CHANGING cf_retcode
ENDFORM.
IN DOWNLOAD_AS_PDF FORM ,I USE FUNCTION : P_fm_name(smartforms function)   CONVERT_OTF   GUI_DOWNLOAD
WHY the UPDATE MODULE have ERROR MESSAGE???
How do I solve this problem？？？

Hello,
Your error message is related to GUI_DOWNLOAD, which is a frontend function.
You simply cannot use it in background, because it puts a file on the
frontend PC where you start the function (WS = WorkStation).
Note that GUI_DOWNLOAD is intendted to be used for dialog user
and will not run at BACKGROUND.
You can review SAP Library: ABAP Programming (BC-ABA)
->Saving Data Externally
->Working with Files
    ->File Handling in ABAP
Regards,
David

Forward Error Handling (FEH) framework?

Similar Messages

Maybe you are looking for