IDoc Error Processing workflow

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Hi Rajesh,
Using the same BOR object and event for two different idoc types is not necessarily wrong. There are ways to differentiate the responsible agents based on the idoc type if needed.
Here is how I would solve this:
Prerequisite: you need to make sure that event IDOCINVOIC.INPUTERROROCCURREDMM is triggered when your BBPIV01 iDoc is in error. To check that, you can activate the event trace and test your idoc (activate with tx SWELS, display with tx SWEL).
If the event does not trigger then you need to find out which event is getting triggered (using the event trace as well).
Now the serious business:
1. Create a copy of standard task TS00008057 that will be used for when BBPIV01 iDocs are in error.
2. Link this task to your event IDOCINVOIC.INPUTERROROCCURREDMM in transaction SWETYPV
3. Check in SWO1 if you have an attribute that gives the idoc type (or anything else which you can use to determine wich workflow should start in each case).
If not you need to create a subtype of IDOCINVOIC and in the subtype create an attribute that returns the iDoc type. Then you would need to delegate IDOCINVOIC to your subtype.
4. Create start conditions (tx SWB_COND) in which you check that TS00008057 starts only when idoctype is INVOIC01 and your new task starts only when idoc type is BBPIV01.
Cheers,
Patrick

Similar Messages

  • Handle Idoc errors through workflow

    How  to handle inbound idoc  errors  through  workflow and How  to handle outbound idoc  errors  through  workflow
    Thanks,
    Asha

    in transaction SALE go to menu Basic Settings/Perform Automatic Workflow Customizing
    then in WE46 you can assign a workflow task to various errors
    in partner profiles (WE20) you can assign post processing agent per partner/message type

  • 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 error processing using  WORKFLOW

    Hi ,
    I tried to post an error IDOC of message type  FIDCC2 using  "INPUTFORGROUND" method of  Idoc object IDOCFIDCC2.I am using foreground from error for processing the idoc from the error status screen. For some Idoc it is going to the application and I can correct data and for some Idoc it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this? ,It would be a great help.
    Thanks

    Hi Siridhar,
    Thanks for your reply . The message says application error  ie it is calling application and trying to post.
    For some error this calls the application in  foreground and processing. Is there processing status of IDOC that it will not allow to process foreground.
    Regards
    Radha

  • IDOC Error Notification - WorkFlow

    <b><u>ALE-IDOC Master Data Distribution</u></b>
    We have a busines requirement to email/notify an agent when an incoming idoc has an error-status. Please let me know how to proceed with this.
    Thanks in advance!

    Hi,
    if you are using the Inbound FM to process the IDoc, then you can very well use the work flow.
    after processing the IDoc you will come to know the status of the IDoc .if any errors are there you can generate workflow.
    Regards
    vijay

  • 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.

  • BBPIV IDoc Error Processing

    Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
    When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
    In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
    I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
    Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
    Thanks,
    Rajesh

    Use Transaction WE42 to identify the process code that is linked to your idoc type.
    After you identify the process code, go to the detail screen and next to the "Identification" field you will see a button (ALE table). Click this button and it will take you to another detailed screen.
    I assume that your Idoc Processing Type is  via Function Module.
    There will be a separate tab or block called "IDoc"
    Choose the correct Object Type and in the fields Start event and end event configure the following values
    INPUTERROROCCURRED INPUTFINISHED respectively.
    You also need to create a agent (intended users to receive the errored Idocs via SAP Inbox) and map this info back in WE20 transaction.

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • IDOC Error V1 042 - Sales document X is currently being processed by user X

    Hello Experts,
    I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
    I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
    I added a couple of minutes of wait time between the file processing but that did not help.
    Please let me know if you have faces same situation and what solution did you apply.
    Regards,
    PS

    Hopefully you have fixed this by now, but for anyone else who might be looking at this problem.  We had this problem and we had the 2 programs check to see if the other was already runing.  If so the program would submit itself for a number of minutes, different for both programs, and then exit.  We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit.  This was necessary because re-scheduling could put a program in conflict with itself.  I hope that this may help someone.  We used the join V_OP and searched for the program name, not the job name.
    Kevin

  • 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.

  • 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

  • AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

    Hi Gurus,
    We are configuring the AES filing.
    we've done the EDI  configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
    Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
    All suggestions are welcome.........
    Thanks in Advance.

    Hi Shiva,
    Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
    Cheers
    Harsha

  • Idoc Error Handling through workflow

    Hi all,
      I want to send the Error Notification for a particular person for whom the task orders is assigned in the organization chart.
    What all the things I need to do.
      I have created the org chart and I have assigned the task to a user under a position.
      I have linked the Idoc error event in Tcode SWETYPV .
      What  all the things I am supposed to do.
    Regards
    Kumar

    Please go to transction WE20, pick the Partner / Idoc that you would like to assign the Org. chart to.
    Then you should configure "post processing :permitted agent" Tab with the Organizational unit.
    Then double click the process code associated with the Idoc Type and click the button next to the Function Module associated with this process code.
    Check  IDoc Tab and see if Stanard Event INPUTERROROCCURRED is present in the field called start event.

  • Workflow tasks related to error processing when u201Cinvoices received via EDI"

    Hi all,
    Please tell me the process like how an workflow tasks related to error processing when u201Cinvoices received via EDI".
    Give me in details the inform.
    Thanks in advance
    Chakri

    Hi Sven,
    Please implement SAP Note: 1321676 in your backend system to solve the current issue.
    But later you will have to implement SAP Note: 1380788 also in your backend system to solve some other issues.
    Regards,
    Binson

  • Concept Question about EDI and Error Processing

    Hello All,
    This is a concept question, I was wondering how others would approach this scenario.
    Let's take this scenario. In EDI often the transmission for a purchase order comes in with an invalid material number. Normal error processing is for the EDI team to research the issue (find the correct matnr), edit the idoc and reprocess the Idoc.  I would like to move that type of error processing out of the hands of the EDI folks and into the hands of the business users.
    How would they correct the material number? It has to be more intuitive than editing an IDoc, it has to be an easy and intuitive user interface. This process has to also work for many types of EDI transmissions both inbound and outbound.
    There would be many ways to handle this: create a report with an editable grid that would change the idoc during input and create the order with the corrections, convert the idoc to xml and use simple transformations, use an xsl report...etc.  You get the point. 
    How would you approach this?  Before I start the design I want to make sure I've given all the options due consideration...all options, webdynpro, transformations, regex, you name it...all is available, except there is no XI. 
    Personally I'm leaning towards an editable grid and processing buttons that would post the idoc in background...but I do that type of thing all the time and I may be in a rut and neglecting better design options.
    Thanks for your input,
    Greg

    <b>Paul:</b> So it runs the transaction silently in BDC format, until the error occurs, then opens up in dialogue to allow the user to change the invalid material, and then continue on with processing.
    This works when the processing function module uses BDC. But even then I think this is possibly nice from user perspective, but a nightmare from auditing perspective. I.e. correct me if I'm wrong, but I'm pretty sure there's no log indicating that the user changed the material number. Thus for anybody comparing the IDoc contents against the posted document (including change history) there's no trail that shows this change. Of course you can assume that this is what must have happened, but I personally prefer if I can track in the system what happened and have proof for that.
    <b>Reddy:</b>
    <ol>
    <li>it can be run daily basis, which should select all idocs which are in status 51 with message number (..related to wrong material number). report output should inlcude :idoc number-wrong mat no- space for new material to be entered by business against wrong 1. And there should be one button for RUN.</li>
    <li>After RUN, the material number should be changed to new 1 in segments and idocs should be reprocessed.</li>
    <li>repeat the run until business enter right mat num.</li>
    </ol>
    Design seems to limited to me (takes care only of one error message). Might work if that's the main pain point and this is the only one the user is dealing with. Otherwise I'd expect pretty soon they start complaining about having to use different tools for the possible errors. I'd keep the report more general, but allow this special form of processing only for a given error message (otherwise it's a normal re-process as triggered for example via BD87).
    Also, I assume that when you talk of changing the IDoc you mean that you actually keep an original copy around (like SAP does when you edit an IDoc). Often this is required from an auditing perspective. I'm not sure why you wouldn't want to check the material number <em>before</em> trying to process the IDoc to avoid wasting system resources (but maybe I misunderstood the step).
    Anyhow, in theory you could also achieve all of this via workflow. You can add custom columns to the work item overview in the inbox, only issue here is that it doesn't scale well (so issues with larger volumes).

Maybe you are looking for

  • How to stop autoplay of videos?

    June 2013: videos on websites start playing without my permission, how to stop this? What I tried: I uninstalled Adobe Flash (disabling Flash add-on didn't work), existing "stop autoplay" add-ons are no longer working according to reviews, tried solu

  • Stop the Sales Orders flow between R/3 and CRM systems.

    Hello Experts, I am facing one middleware related issue. I am creating a quotation and Order in Crm system an those are replicated to R/3. But I am creating some orders in r/3 and those are alos replicating to CRM, I want to stop the flow of Orders b

  • How to move same position to another org unit

    Hi experts, I have one question.Currently one position in my company shared by 2 department. How to create same position with same id for the 2 department. I have try to create it, but the second one will auto generate next position id.Thanks

  • I downloaded a season pass but the itunes store didn't upload all the episodes. how can i get the missing episode?

    has this happened to anyone else?

  • Force re-H&J

    The script I've been using in CS3 (sorry, I can't remember if it came from Peter Kahrel or jongware) to place multiple Word files into one big story doesn't seem to work in CS4. So I've been using this script in CS3 and then opening the file in CS4.