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

Similar Messages

  • Using the general error handler on an embedded rt target

    I would like to know how the general error handler can be best employed
    with Labview RT on a Compact Fieldpoint controller.  Clearly no
    dialogue options are valid so how can error information be accessed
    remotely - is there an error log file available on the controller?

    I think there are plenty of ways to handle errors with Labview RT on a Fieldpoint controller.
    Usually I use the general error handler vi to catch the error and get the error message (sure, no dialog), then write the eroor message into a log file (ordinary text file created on the controller), and/or send the eroor message through TCP/IP network to the host. You can use FTP to open, read and tranfer the log file at host. Hope help.
    Xu

  • OUTBOUND- ERROR HANDLING USING WORKFLOW

    Hi Gurus,
                   Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
    1.Value not found for Custom IDoc fields.
    2. Partner Profile not maintained correctly.
    3. Syntax error in IDoc.
    4. IDoc ready for dispatch (ALE Service).
    Regards,
    Chiranjeevi.

    Hi,
    FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
    Have a look at WE46 transaction.
    Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
    It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
    Hope this helps
    venu

  • How to add sound to the general error handler

    I'm looking for an easy way to create an audible indication (a beep or something) when the general error handler displays an error message.  Anyone have any suggestions??
    Solved!
    Go to Solution.

    Hi Bill,
    I thought this was an interesting idea, so I wrote up the code and posted it on the NI Community here: Simple Error Handler with Beep.  If you have any cool VIs that you'd like to share, you can post them on the community as well to share them with others.  Thanks!
    Stephen Meserve
    National Instruments

  • General error handling operation

    Hi,
    I did not find a comprehensive explanation how error handling works in TestStand, only bits and pieces about the callbacks (perhaps I looked at the wrong places).
    Anyway, I made some experiments with SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - intentionally leaving out ProcessModelPostStepRuntimeError to reduce complexity - and came up with the attached flow chart. I would like to know:
    if that shows the correct operation of TestStand error handling (we are currently using 4.1, about to switch to 2010 or 2012, so it would also be interesting to know if anything changes with the new versions)
    if it is always the case that the combination of ErrorReported=True und Error.Occurred=True after the error handler leads to termination of the execution? I could not find any setting governing that (the "goto cleanup immediately" setting of the sequence was off;
    Best regards
    Peter
    Attachments:
    TestStand_ErrorHandling.png ‏36 KB

    Hi Peter,
    1) Every step has :
    error.code   - to set the error code
    error.occured - boolen if set true displays a popup error message to the user
    error.message - the popup contains this message
    when you set error.occured=true it will bring up a popup message with the error.message and error.code.
    Please note that this may not be acceptable in the manufacturing environment where operators may not be trained to check for errors.
    The general practice in manufacturing is to fail all important steps that errors out so that the final result is failed.Then do a offline analysis.This is done by step.results.status = "Failed".You can also populate step.results.ReportText with proper values so that your test report reflects the type of error/failure.
    2) Regarding the  SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - they are optional error handling methods if you want to act on errors.
    3)Every step has an option ( look for properties-->post actions).On Pass or On fail destinations can be set for each step.Cleanup is always executed except in cases of abort.
    4) In the menu configure-->Station options-->execution there is an option for runtime errors ( one of them is run cleanup).
    Hope the above information helps.

  • Error handling using BPM

    hi all
           I would like to do an error handling scenario using BPM in XI. As i haven't done it before, can somebody give me links to good blogs and materials in this regards.
    Thanks
    Sumayya

    HI,
    Check the below links
    monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
    Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
    Also see the below BPM related links
    check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
    /people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Many other examples can be found under the following link at help.sap.com
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    And some weblogs
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    /people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    /people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    /people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
    Also have a look at these seminars,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
    Regards
    Chilla

  • IDoc error handling using workflows

    Hi,
    I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
    All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
    Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
    And I have heard that there is a workflow process which would help me to do this.
    All your answers would be highly appreciated.
    Thank you in advance,
    Sid.

    Hi,
    First Step:
    You have to maintain the e-mail-address in SU01 for required users.
    Second Step:
    SCOT Configuration
    Third Step:
    Depends on your SAP Version do configuration SWNADMIN
    Or  excuting the report RSWUWFML2 as the background job.
    Thanks and Regards,
    Prabhakar Dharmala

  • General Error handling

    I've managed to get myself confused with error handling in Forms 6i.
    If I have a trigger that does a 'commit-form' like this
    commit_form;
    IF NOT form_success THEN
    RAISE form_trigger_failure;
    END IF;
    EXCEPTION
    WHEN OTHERS THEN;
    END;
    and the commit_form fails due to a mandatory field being missing (or similar) then what happens first?
    Does my ON-ERROR trigger fire?
    Does the form_success check fail and raise form_trigger failure?
    Does my exception block get used?
    Or does more than 1 happen??
    I could - of course - find the answer to this through debug but I'm looking for a more generic answer if possible.
    Thanks - Sean.

    What happens first?  The forms validation process runs and informs user that the field is required.
    Does On-Error fire?  Yes, if you have one in your form.
    Does the form_success check fail and raise form_trigger failure?  Yes -- but ONLY if your On-error raises Form_trigger_failure.  If it does not, you have lots of problems.
    Does my exception block get used?  Yes.  Raising Form_trigger_failure causes control to pass to the exception handler.  But I never use an exception handler except when I code SQL commands.
    Now...  After commit_form, you should also check Form_Status.  Read the help topic on the Form_Success built-in.
    My standard C00_Commit program unit does this:
      COMMIT_FORM;
      IF :SYSTEM.FORM_STATUS <> 'QUERY'
      OR NOT FORM_SUCCESS THEN
        RAISE FORM_TRIGGER_FAILURE;
      END IF;
    END;

  • How to implement general error handler in labview projects

    Thanks,

    Hello,
    You may also find these links useful:
    Custom Error Handling In LabVIEW
    http://zone.ni.com/devzone/conceptd.nsf/webmain/de​4f036f22c4b9f286256fee0010b6fd
    LabVIEW Introduction Course - Six Hours (has a section on error handling)
    http://zone.ni.com/devzone/learningcenter.nsf/03f7​c60f17aad210862567a90054a26c/55974411828f779086256​...
    Hope this helps!
    Charlie S.
    Visit ni.com/gettingstarted for step-by-step help in setting up your system

  • General Error message using Kubota Actions?

    I keep getting a "general error message" when attempting to use an action from my Kubota Dashboard. I'm using CS6 version 13.0.6 on a Mac computer. Anyone familiar with this issue? It works fine on my older laptop using CS6 version 13.0 and same Kubota Action palette.

    Now my angles are out of sync and I can only see 2 at a time in the viewer window when there are supposed to be 3 but it switches between which 2 it wants to show. I have only a little experience with the multiclip settings. Is there something I need to do when re-opening a project with multiclip?

  • Errors Handle using VB

    Hi all,
    we have an automated procedure (using VB and BW functions) for the production of a large amount of reports .
    the issue we face is that whenever a short dump is being produced (for any reason) , the VB loop stuck and someone has to logon again. of course the process continues at the broken step.
    is there anyway to trigger such errors (with for ex return codes ) so we could relogon and continue the automation?
    thanks in advance.

    Hi Panayiotis,
    I am certain that this can be done.  But, without knowing A LOT more about what (exactly) you are doing (and how), I am not sure what is the best approach to suggest.
    In general, it would seem to me that what you want is an asynchronous routine that monitors the local environment and reacts to changes.
    For example, when BW dumps, it almost always generates a trace file (a text file) giving some (usually incomprehensible) explanation of the problem that occurred.  It would be simple to have a routine monitor the active directory for the appearance of such a text file and take action based on its appearance.
    Another example ... your automated procedure could generate a text log of its own ... a progress report of sorts.  You could have a routine that monitors this progress report.  If there is no update after a certain period, it would shut down Excel and restart your process from the last successful step.
    Hope this helps.
    - Pete

  • Steps for ALE/EDI error handling using workflow

    Hi
    I need to handle errors in outbound IDoc generation using workflow. Can you please let me know the steps to be used for this. Step-by-step answer would be appreciated.
    Thanks

    Seetha,
    I have this already..
    IDOCPACKET                                                           
    Object type                         IDPKWMMBXY             
    End event                           MASSINPUTFINISHED      
    IDOC                                                          
    Object type                         IDOCWMMBXY             
    Start event                         INPUTERROROCCURRED     
    End event                           INPUTFINISHED          
    Application object                                                                      
    Object type                         BUS2017                           
    Start event

  • Error handling using fault message type in outbound synchronous ABAP proxy

    Hi,
    We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
    Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
    Source Structure
    Req_Proxy
        req (0..unbounded, string)
    Response Structure
    Resp_SOAP
      Resp (0..Unbounded)
           respString (0..1, String) (carries the actaul response message)
          status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
    And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
    Please calrify.
    Thanks.
    Rohit

    For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
    for valid and 2 for invalid accordingly.
    Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
    Regards,
    Abhishek.

  • IDOC Error handling using workflow for Inbound process.

    I have a custom idoc which I am processing using a custom inbound function module with the help of a custom process code. I have made the config in BD51/bd67/We42/We57and doing the coding in the inbound function module to handle workflow. But i am still unable to get the workflow item in my inbox. I have set my userid in the partner profile as the agent to receieve the workflow.
    Is there any other config that needs to be done vis-a-vis workflow ? like..assignement of some standard task,etc etc ? The message type I am using for the IDoc is zWMMBXY .
    Pls advice..thanks

    Seetha,
    I have this already..
    IDOCPACKET                                                           
    Object type                         IDPKWMMBXY             
    End event                           MASSINPUTFINISHED      
    IDOC                                                          
    Object type                         IDOCWMMBXY             
    Start event                         INPUTERROROCCURRED     
    End event                           INPUTFINISHED          
    Application object                                                                      
    Object type                         BUS2017                           
    Start event

  • General Labview Error Handler question discussion

    Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler. 
    And I cannot wrap my hand around these two features.  While I have been using Labview I have always used the Labview error cluster.  When would you use these two features?  As I feel the cluster error is much help. 
    Maybe it is my defnition that I have confused: 
    The general error handler will display a dialogue box describing the error that will be passed and shuts down the code? 
    The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated.  "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error."   How is this not the same as an error cluster?  
    If anyone has any simple code examples for this or knowledge I greatly appriciate it. 
    Caleb

    Jacobson wrote:
    Psireaper9 wrote:
    The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated.  "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error."   How is this not the same as an error cluster?  
    You are correct that they give the same information.  The difference is that if you want to use an error cluster you will need an indicator on your front panel.  If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
    Think about all the programs you normally use (excel, chrome, etc.).  As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
    I use the simple error handler with no user interaction to extract the error text.  Is there an easier way of doing that?

Maybe you are looking for