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

Similar Messages

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

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

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.

IDoc error handling via WorkFlow. What is missing?

Hi All,
My problem is when an error occured I don't receive anything in the Workplace.
I did the following:
When I created the process code I gave an object type(based on IDOCAPPL) for the function module's IDoc part. For the start event I gave the INPUTERROROCCURED event and for the end event the INPUTFINISHED.
I created a standard task where the triggering event is the object type->inputerroroccured and the terminating event is object type->inputfinished and the object method is the object type->inputforeground. I use a standard role with a "Z" function module to determine the agent.
I tested the role with an IDoc number and it worked. It gave me back a position where is my userid is the only id. The concistency check shows me 2 red line: the missing IDoc Packet section (I think it's not needed) and at the Role assignment (I think it's good so I don't understand this).
So, Do you have any idea what is wrong?
Thanks for your help in advance.
Regards,
Gyula

Hi Gyula
Can you tell how you are actually raising that event .?
I assume that you have created a process code and attached it to some function module and therein wherever you are getting error(when you want to trigger workflow) you are raising an event for your object type and its event .
Since i cant check out your code , it guess you can try setting your task as General Task first to just get sure whether the event linkage is active for event or not and your workflow if at all is really getting triggered or not . If these things work fine with out then certainly your role determination function module needs to be checked.
Kind Regards
Shovit

HRMD_A IDoc Error Handling

We are distributing organization data to another system from our HR system using ALE with message type HRMD_A. In the target system, under transaction BD87, we have a few IDocs in status 51 and 52.
For status 51, I currently have the following error: "Error in subroutine read_namtb for structure of infotype", and also "HR: ALE inbound processing for HR master data" - This last one is the name of our distribution model. Neither error message gives much detail - How do I go about finding out the cause of the problem?
Fpr status 52, I also have the error "HR: ALE inbound processing for HR master data" - Again this is the name of the distribution model. Not sure what to do with these..?
What should be done about these? I can't reprocess either status, so what do I need to do to correct the problem?

Dear David,
Regarding status 51, the most common reason is that the link 007 between position and job cannot be distributed using ALE with the HR standard system. Please implement note 661605. It applies whenever relationship 007 is distributed. Remove the entries detailed in the note in T77AR as explained there in the source system. This way this additional segment will not be distributed and the IDOC will be able to be sent with no errors. So, please make sure that in the source system in T77AR Substructure for additional data and Screen additional data are empty (as they should be also in the target system).
Please can you check out table T77s0 for switch HRALX HRAC if it is activated in your target system? If not please set it up to 'x' and try again.
Best Regards
Christine Morin
Senior Support Consultant

Regarding BADI error handling

Hi,
I have a requirement to generate a reference code for a publication and when the publication is saved with out reference code it should display message on the portal.
So how can we handle error messages in the BADI or in the E-Recruiting portal.
Thanks in advance.
Thanks,
Anil

Hello Anil,
unfortunately the BADI for reference code generation is only called on request. When you activate a BADI implementation the button for generation appears on the screen and can be used.
But only when you press this button the BADI is called and within this call you can create an error message for example if you generate date or channel dependent reference codes and the user did not enter this data yet.
The BADI is not processed when saving the publication so you have no option to use it for raising an error message when saving an empty or not matching reference code.
The only solution I currently know for your problem is modifying the system. If you do not want to make a modification (as it has quite a lot of negative consequences) you could copy the bsp view parts of the publication tab into the customer namespace and change the behaviour to whatever you like as customer development. You replace the original tab with the customer one in the container sequence customizing.
Best Regards
Roman Weise

IDOC error handling.

I am using objects IDOCAPPL /IDOCWMMBXY for error handlilng for IDOCs
The scenario is somewhat like this....
Lots of IDOC's go into error and there are say about 400 workitems in the users inbox cause of the IDOC going into error.
Now all thesr Workitems are there because of some common error. Once the common error is resolved the IDOCs are reprocessed by a batch program.
Now the batch program posts all these idocs..
After this the WorkItem is still in the users inbox. I need to remove the WorkItem once the IDOC is posted externally.
Which event could i use over here...
any help on this ?

Hi Thomas,
How can you put 500 invoices into 1 IDoc? An IDoc is a container and can only accept one document details at a time! Do you mean to say you are trying to invoke 500 IDocs at a time but the mapping is 1 IDoc per Invoice?
Cheers,
Sougata.

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

Outbound Idoc Error Handling by creating workitem

Hi ,
I have a question regarding the Outbound IDoc.
What we need to implement is to create a workitem in SAP Inbox when there is a failure on the Outbound IDoc.
in a similar way as we do for the inbound IDoc's.
Is there is a standard way of achieving this ?
Thanks in advance

Hi Ankur,
Have you looked standard program <b>RBDCONCH</b>?
Regards,
Ferry Lianto

Inbound IDOC Error handling

Hi,
I am using message type PORDCR1 to create a purchase order. This is calling a BAPI_PO_CREATE1 to create the PO inside. Now I have coded some validation in user exit that is available in Pre processing. So when there is any any error i populate the table bapi_return.
Now what is happeing after executtion of user exit it continues the function module and find out if there are any more errors. After execution it shows all the errors.
My requirement is when ever i get an error in user - exit it should stop further processing and write that error in log.
Can anybody please suggest me how can we do this.
Thanks,
Neha.

Think this as your last option:
1) create and attach ZBAPI_PO_CREATE1 in ALE Config
2) COPY your User Exit code at the start and it it gets through then only submit BAPI_PO_CREATE1

Error Handling in IDoc

Hi Friends,
Can anybodytell me any procedure for Idoc error Handling (Restart and Recovery) of IDocs that occured in error status. What could be be the possible ways apart from BD87.Thanks in advance for ur gr8 help!!!

It really depends on they type of error.
For transactions that need data remediation, the preferred method of posting is via SAP Workflow (xaction So01 for the inbox).
For things that did not post due to missing config, etc. use BD87 (assuming the config now exists).
If you have specific questions post them and I will try to help.

BPM error handling

Hi,
I've read many messages on this forum regarding BPM error handling but am still a little confused.
In my scenario the BPM is quite simple. All it does is Call web service (synchrous) then transform and then call another web service synchronous.
Now , If any call to the two web services fails , I would like to be able to restart the two calls... now if they fail again, I would like to be able to restart the two calls again... until they work. But each time the restart would be done manualy in the BPM monitoring transactions.
The way I understand the error handling
if I put my synchronous send steps and transformations in a step and catch the exception they throw , I can send myself an alert and then throw another exception which I dont handle. This way , since that exception is not handled , it will set the process in error and I can restart the process later.
However , how can I set it up so that when I restart the bpm , both calls are done again and the same exception handling happens.
Now , when I restart, it seems only what comes after the block and the exception is executed. If I put the sync send calls in the exception handling branch, that will allow me to run the send steps once after an exception...
Thanks.

Even if I don't throw the exception and its a System error on the synchonous call, the BPM is in error but the next call will
go through...
I don't know what the point of EOIO was in that case ?
Even having an Exception branch is enough....you need not compulsorily have anything in it.....so when an exception occurs in your Sync step the control goes to the Exception Branch of the Block....but since there is no step defined in the branch nothing happens.....and the Control then passes to the next branch as in a normal flow.....
Since the Exception branch is defined the BPM will not wait/ stop/ error-out if any thing goes wrong in the Sync Send step.....it will continue....this is the normal behavior....an error entry will however be shown...if you want that your process stops if the Sync Send fails then have a Control Step (Action--> Cancel Process) in the Exception Branch
Regards,
Abhishek.

Regarding idocs error handling

Similar Messages

Maybe you are looking for