Workflow for Idoc errors

Hi,
I am new to workflow, I got a requirement for idoc error handling in workflow.
If the idocs fail a notification needs to be sent to an appropriate personnel. If it fails due to configuration or technical issue then the notification needs to go to the tech personnel ( A distribution list ) . If it is a data error then notification needs to go to functional personnel ( distribution list ).
Here i have created a WF using Object IDOCAPPL. Please let me know how i can handle this condition and want some document on orginization structure.
I have refered to documents in Saptechinical and Sdn.Plz let me have some other ideas and documents.
thanks
Arun.

You can create a custom rule and inside that you can have your own condition and populate the users accordingly.
Distribution list..you can create in SBWP itself.

Similar Messages

  • WORKFLOW FOR IDOCS

    hi all
    are there any standard w/f for idoc error handling.
    i have a senarios in which a series of mails have to be send to different people when idoc error occurs witha workitem.
    any pointeers will be really helpfull
    regards
    navjot

    hai
    these are some of the standard workflow
    TS00008068----
    Process code does not exist;
                               Error during forwarding to ALE services
    TS00007989----
    Error during forwarding using RFC;Error writing file
    TS30000078----
    Conversion error in EDI subsystem
    TS30000020----
    Inbound: Error reading file; Outbound:
                               Error generating IDoc from an MC record
    TS70008037----
    No process code in the additional partner profile MC  parameters; Error when writing the application data in the IDoc.
    hope it will be helpfull for u.
    regards
    rose.

  • Error monitoring through workflow for idoc with message type ORDRSP

    Hi All,
    Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
    Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP  fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
    Regards
    Suchandra

    Hi All,
    Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
    Regards
    Suchandra

  • Outbound Idoc error handling through workflow

    Hi,
    I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
    How this task can be triggered when outbound idoc error occurs in the system?
    Kr,
    Vithalprasad
    Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

    Hi,
          Have a look
    Outbound IDoc Error Handling via Workflow
    Outbound idoc error handling through workflow

  • Idoc error meesage contains empty quotes ' '

    Hello All,
    We are generating Picking confirmation to customer delivery Idoc using E1VPDLH segment and extended this segment to include Vendor/Creditor
    For triggering a workflow for an error message, I entered a non existing Vendor through WE19. I expect the error could be "Vendor not exist" or something like that.
    And reprocess the IDoc through the program RBDMANIN. Now the Idoc has status 51 and returns a message ( ' ' has not been created).
    I think SAP tries to fill a message in the empty quotes. Can someone explain about this? Why it is giving an empty ' ' quotes

    Hi,
    1) Check the  Autorization & Security Roles
    2) Might be due to error in the Application / Web service is not able to process the request message.see that the request message you are sending to the applicaton is valid .
    I hope this will help you
    Regards
    Agasthuri Doss
    Regards
    Agasthuri Doss

  • Triggering workflow upon idoc fail

    Hi Gurus,
    I have to trigger emails to users thru workflow whenver an idoc fails. Please teach me how can I achieve this.
    Your help is highly appreciated.

    Hi
    Here is the link for idoc error handling workflow.
    [idoc error handaling|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/609e6465-15de-2a10-859d-da7bcbca54a3]
    [idoc description|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8088e6fc-5637-2b10-c189-9733fa621cf1]
    Regards
    vijay

  • STATUS 51 error not directed to inbox (Idoc error)

    Hi all,
    When the single step Task is triggering for Idoc error ie,Status 51 the workitem is not going to the Users inbox.
    The task has been assigned to User in PPOMW.
    Note: The workitem is going for other Status.
    Kindly guide with your points.
    Thanks and Regards,
           Sridhar

    Hello,
    Can you check the task attributes?
    Also, can you please maintain the user assignment in the Task itself, through the path Extras>Agent Assignment>Maintain.
    I think when you maintain the agent assignment in the task itself that would do the job correctly.
    Cheers.
    Abhijit

  • Vendor Confirmation workflow ( TS00008075 ) issue for IDOCs in Error ( 51 )

    Hi All,
              When IDOCs (Basic type: ORDERS02, Message type : ORDRSP ) goes in error with status 51 & comes to SAP system it calls event  u2018INPUTERROROCCURREDu2019  which is correct but it creates problem when it get re processed as it triggers event u2018INPUTSUCCESSu2019 resulting in firing vendor confirmation workflows to respective user ( this batch job re process each ORDRSP IDOC twice a day & hence 2 workflows per IDOC in error to clientu2019s inbox by triggering event u2018INPUTSUCCESSu2019).
    Could you please tell me why these IDOCs are triggering event u2018INPUTSUCCESSu2019 in case of error ( status 51 ) when they get RE PROCESSED. These kind of Idocs must only trigger u2018INPUTERROROCCURREDu2019  once  and should not create anything when these get reprocessed. Please note that these issues arise after EHP4 upgrade. Please let me know if any setting is there for triggering Vendor COnfirmation workflow ( TS00008075 ) when IDOCs in error get re processed.
    Please help us , thanks.
    Regards,
    Kartikey Rawat.

    Hello Kartikey Rawat !
                        INPUTSUCCESS  event gets fired just because it is configured as terminating event in the task.
                        If you don't want this event to get fired, either you can deactivate it  or delete the bindings related to the event  INPUTSUCCESS(doing so should not affect other two terminating events that may be required for you scenario) .
                        If you want know why it is fired, you can get to know in debug mode or check whether the event is defined through  related function modules configured in WE57,BD51,WE42 AND WE20 transaction codes.
                        In WE05 or WE02 transactions, you will get error description.Based on it too, you can figure out the reason.
    Regards,
    S.Suresh

  • Custom inbound Idoc error handling/ Workflow

    Dear Experts,
            I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
    Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
    I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
    Thanks for your time.
    -Amit.
    Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
    Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

    Vittal,
    1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
    2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
    Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
    So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

  • Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

    Hello All,
    I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
    Br,
    Sri

    Hi !
    Becaus alle this happens in beckgound, things are a bit difficult but solvable....
    What you should do is a "Authority trace" ... as follows....:
      - Go to the ST01
      - Mark "Authorisation Check"
      - Swich the trace on for your Workflow user
      - Execute the Workflow until the error uccurs
      - Go back to the ST01
      - Press the "Analyze" button and see what error occurs
    Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
    Regards
    rainer
    Some Reward poins would be nice if that helped....

  • Workflow for inbound idoc failures

    Hi Gurus,
    Can anybody please point me to a place where i can start to see how i can setup workflow to notify users via SBWP whenver there is an inbound idoc error happens. We want to derive the standard functionality to its fullest even before thinking of putting any custom code. I'm specifically looking for hte order acknowledgemetns and shiipping notifications errors of idocs coming from the vendor
    Thanks
    anusha
    Edited by: anusha vemulapati on Jul 2, 2011 4:43 PM

    Hi Anusha,
    The simplest way is to link the partner profile to a specific user ID. This is done in trs WE20 - you have the link to the WF recipient both generally for the partner (on the initial screen of WE20 when the partner has been selected) and specifically for the different message types - double-click on the inbound message type and choose the tab "Post processing - permitted agent".
    You link the partner profile to a specific user by choosing the user type = "US" (user") and then specifying the user name below it. If you want several users to receive the same WF, you can link the partner profile to another user type, e.g. O = Organisational unit. Then you link the users to the organisational unit in trs PPOME.
    As far as I remember, the WF for IDoc's in error is activated in the standard system, i.e. the setting above shall be sufficient.
    BR
    Raf

  • Workflow for INBOUND IDOC

    Hi,
    I want to set you a workflow for one IBOUND idoc coming via edi partner. I want to use the organization units and then assign the user to it. what are the steps required for setting up a new workflow totally from the start for a IDOC / Message type and config.
    Thanks in adv
    /Manik

    STEP 1.       USE   SALE -> Error Handling                 
    STEP 2.   Go To  Basic Workflow  Settings.Use Auto-customise button to allow the system to configure most of the options.
    STEP 3 
      a)Go to SAP MENU -> TOOLS-> BUSINESS WORKFLOW ->
    DEVELOPMENT ->DEFINITION TOOLS->TASKS
      b) Create a customised task putting IDOCCLFMAS for example   as object type and    INPUTFOREGROUND  as object method.
    c)Associate the triggring event InputErrorOccurred with the standard task.
    d)Associate the terminating event InputFinished with the standard task
    e) Assign appropiate agent to the customised task. For this GO TO
         Additional data -> Agent assignment -> Maintain
    STEP 4  --  Go to transaction WE20.In the partner profile of the message type CLFMAS enter for the post  processing permitted agent.Enter the agent type (Organisational unit,Workcenter,Job,Person,Position or User),agentId and the language.
    STEP 5- In case of any error in processing of Idoc a workflow notification is sent to concerned agents.The message is sent to the inboxes of concerned persons which indicates which interface has erred,the associated IDOC number ,status of the IDOC and the date and time of error.
    Regarding the complete set up you can check the workflow tutorial in help.sap.com.
    regards
    Aveek

  • Handling outbound IDOC errors through workflow TS00007989

    Hi,
    I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
    I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
    Moreover i couldnt find any trigerring events for the above task.
    Can any one help me with a step by step guide for achieving this.
    Regards,
    Krishnakumar

    Hi,
    the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
    And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
    If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
    Hope this helps.
    venu

  • IDOC errors Notify thru Workflow

    Hello Experts,
    I want to report an error notification; if an Idoc fails. What are the steps for this Configuration?
    Also if I want to sent some notification on success/fail status of Idoc, how do I configure workflow for the same. What are the steps involved here? Please provide your expert guidence.
    Rewards for sure
    Thank you.
    Regards,
    Vishal
    Message was edited by: Vishal Tyagi

    Hi Vishal,
          You can use Bussiness Object (IDOC* and F4) and the event available to trigger the work flow from which you can then send a mail to the concerned person.
          If you need to do this through any program then get all the error IDOC from EDIDS table and can send a mail through 'SO_NEW_DOCUMENT_SEND_API1'. Then you can schedule this program periodically which will be sending a mail.
          But both differs, if you need to notify whenever the an IDOC is created then you have to go for WOrkflow or if it enough if you report on DAily or hourly basis then you can use the second option.
          Hope this might have helped you.
    Thanks,
    Prashanth

  • Idoc error handling for error status 51

    hi all,
    I am trying to set up inbound idoc error handling. For that I have activated task TS00008068.
    This task gets triggered for all error statuses except error status 51.
    Could you please help me understand why it doesn't trigger the task for error status 51?
    KR,
    Vithal

    Standard task 8068 is triggered for IDOC syntax, partner profile issues etc. The error message 51 is probably coming in from an inbound function module.
    Firstly there isn't a single standard task that will be triggered for all errors. Each IDOC error, depending on the events triggered, will fire a predefined standard task. For example, you're trying to process an order inbound and the IDOC is successfully created and passed on to application. Then the inbound FM will attempt to create an order and probably fail at determining a sales order or a ship to etc due to a missing setup. Then a different event is triggered which is attached to standard task 8046. That is different from 8068.
    Here is small subset of error 'vs' tasks:
    Message       Workflow Task
    SHPCON      TS20000051
    INVOIC      TS00008057
    ORDERS      TS00008046
    SDPICK       TS00008031
    WMMBXY TS00008009
    So you have to choose the IDOC which you want to activate WF task. Then look at the event that is associated with it. Then make sure the event is linked to the message type and routing is active.

Maybe you are looking for