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

Similar Messages

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 treking through workflow

Hi All,
I am working on a requirement where we need to trek IDOCs through workflow. I have got a standard task(TS30000206) which does error handling for outbound IDOC. If i send 10 outbound IDOC and 9 are processed successfully they should be changed with the success status. But the 1 which could not get the response/acknowledgment back in 24 hours should be marked as failed??
My question is How can i setup a workflow to error out the IDOCs which are unable to make the postback/ackn within 24 hours?
Your quick response is highly appreciated....
Thanbks
Ritesh

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

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

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

Handling 404 error through web.xml

In my application i made the following entry in web.xml:
<error-page>
    <error-code>404</error-code>
    <location>/error.jspx</location>
</error-page>
error.jspx is a jspx file and exist in the public_html folder and has following entry:
<f:view>
    <af:document id="d1">
      <af:form id="f1">
      <af:outputText value="Hello There error occured" id="ot_11" />
      </af:form>
    </af:document>
</f:view>
when a 404 occurs in the application, i am getting following application in the log:
<[ServletContext@3806419[app:j2ee-app module:retailer path:/retailer spec-version:2.5]] error-page location: "/error.jspx" for the error-code: "404" does not exist. Serving the default error page.>
Any suggestion what to do next?

on more thing,
404 errors are handled by web.xml using following:
<error-page>
   <error-code>404</error-code>
   <location>/login/404errorPage404.html</location>
</error-page>
but in case of 500 errors or nullpointers i treid a no of options, but neither one worked:
<error-page>
<error-code>500</error-code>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>javax.el.ELException</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>java.lang.Exception</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
<error-page>
   <exception-type>java.lang.Throwable</exception-type>
   <location>/login/500errorPage500.html</location>
</error-page>
Any advise?

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

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.

Outbound Idoc through Workflow in CRM

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

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.

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.

Handling Multiple Error Messages through EXIT_SAPMM06E_012 for ME28

Dear Team,
After Executing ME28, system will give List of PO's that are to be Released . User will select Multiple PO's and
Press Release button in Application toolbar. once it is relased, User will press save Icon for all released PO's.
Once Save icon is presed, I need to do Validation for Multiple PO's in the user Exit EXIT_SAPMM06E_012 and capture my
ErrorMessages for all Released PO's for which Validation fails.
Here in the given user Exit, one PO will be processed at a time as PO is defined as Import Parameter but it will handle all PO's
and give the output in status bar saying 'Relased Saved' for all PO's which succesfully gonethrough.
once we execute ME28, system is showing list output with PO's to be Released(As system is handling with Write statments). In this case, we dont have scenario of PBO and PAI Modules( where user can correct error if any validation fails) like we have for ME22,etc.
I have Written simpel Error Message in the User Exit.
once i tried to trigger my user exit by Releasing and Saving with One PO, Error Message is displayed ( as information Message
appears) and if i Press Exit button in Error Message, it is coming out of Transaction.
Is there any Possibilty to Handle Multiple Error Messages ( in my case for Valdiation Failed Po's) in ME28 ,after Releasing and Saving , and also user should not come out of Transaction once Error Messages are Displayed.
Thanks and Regards
Suresh

Hi Suresh,
there is a tekpo table to handle all po items. you can put it in loop and do validations.
if any errors through, there may be a ex_messages table of type bapiret2.
or
try like this: MESSAGE E368(00) WITH TEXT-001 TEXT-002.
thanks
srinu
Edited by: srinu rao on Sep 22, 2009 3:43 AM

Regarding idocs error handling

HI . i want to learn idoc error handling on sap xi side because my current project is in PRODUCTION They implemented lot of idocs so is there any documents(guides ) regarding error handling of idocs for both sender and receiver side.

Hi
Please refer File to IDOC Scenario..
the 2nd post (Troubleshooting IDOC scenario) from Swarup Sawant , you will get a very good understanding
as lots of reference links are attached with different scenarios.
Regards,
Srinivas

TS30000020 - IDOC error message

Hi All,
In our production system, we had some workflows got stuck up with SWF_RUN 609 error message. So i tried using SWPC
transcation to resume those workflows. I worked fine. But some did not show up in SWPC and so i used SAP_WAPI_ADM_WORKFLOW_RESUME Fm to resume, it also didnt work. So i searched through sdn and some other sites and found out the standard report "RSWWERRE - Report for restarting workitems with temporary errors", and tried that. My workflows got resumed. But over 2500 new workflow with TS30000020 and description "EDI: Incorrect status for inbound IDoc" got triggered without any agents and it went all users. Iam not aware of IDOC. Can anyone suggest why this has happened and how should i overcome this?
Regards,
Kevin.
Edited by: kevin.jk on Jul 27, 2011 7:54 AM

Hello,
RSWWERRE is normally scheduled to run periodically (usually every 20 mins) to handle temporary errors.
I'm not sure about how these IDOC workflows got started. If they're not necessary then you can logically delete them.
If you look in the IDOC workflows, when does it sya they started? Recently?
regards
Rick Bakker
hanabi technology

Handle Idoc errors through workflow

Similar Messages

Maybe you are looking for