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

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

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

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

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Outbound idoc error message

Dear all,
When i am manually create a direct request for POS outbound, the system shows the error message as below. It cannot generate an outbound idoc. Do anyone know how to detect this error and how to solve this problem?
Error message:
Processing Status
Recipient: XX01
IDocs created
     None
     Trigger file for status ID: 00000000260056
     does not have to be created       No messages needed
Thanks and regards
Chris

Dear all,
i have solved the problem. thanks you for your attention.
Chris

Outbound IDoc Error status 26

Hello All,
I have got one issue in outbound IDoc scenario. ( Basic type is ORDERS02 ). The IDoc failure status shown in WE02 as 26 (Error during syntax change of IDoc outbound). To solve this I am trying to Repeat Output through VA02 ( as this is related to salesorder) , it does not give the same error status 26 . Rather it gives status as 30 i.e. IDoc Ready for dispatch which I then process through BD87 gives status 03 i.e. Data passed to port OK .
I repeted this for 4-5 times, everytime I do not get any error status (as that was occured at the very first time) .
Kindly suggest what should be done to overcome this.
Thanks in anticipation...

Hi Ubhaka,
In that case you should check the segments associated with the message type.Also, check the partner profile settings.
At first (when you got the error) what was IDOC generation method - was it through VA02 or some custom/standard program? If the methods were different for generating Idocs then check the program.
Hope that helps!
Regards,
Saba

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.

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

Database Constraint Error Handling on create/edit (Struts ADF)

Hi,
In our project we use Struts ADF (JDeveloper 10.1.3) technology. And we're facing the following trouble with it.
If we try to create a record that violates say Unique constraint in the database, then during commit procedure of the AppModule's Transaction an exception occurs.
We handle this exception with our extension of DCErrorHandlerImpl. And we have to do the rollback action because the Transaction became invalid and we cannot do the commit since there was an error.
But unfortunately appModule.getTransaction().rollback(); forces ViewObj to loose all of the newly created rows. Because of this, after pressing submit with the same (violating) data once more our edit form shows the first row in a rowset.
Are there any ideas about what we may be doing wrong?
Any standard approaches on database constraint error handling?
The "before/after commit/rollback" approach is very effort-consuming because we have a lot of views in our app and tracking all of them may become a nightmare in future.
Thanks in advance.
Regards,
Larry

Hi Steve!
I'm using Postgree.
Here is StackTrace
06/06/27 09:52:24 Commit
oracle.jbo.DMLException: JBO-26041: Failed to post data to database during "Insert": SQL Statement "INSERT INTO public.test_tb(id,name,org_code) VALUES (?,?,?)".
     at oracle.jbo.server.BaseSQLBuilderImpl.doEntityDML(BaseSQLBuilderImpl.java:481)
     at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:5731)
     at com.yukon.adf.postgre.entities.PostgreEntityImpl.doDML(PostgreEntityImpl.java:22)
     at com.yukon.adf.postgre.entities.PostgreSequenceEntityImpl.doDML(PostgreSequenceEntityImpl.java:58)
     at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:4531)
     at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:2993)
     at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2804)
     at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1968)
     at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2170)
     at view.actions.ListTestPageController.onCommit(ListTestPageController.java:32)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.adf.controller.v2.lifecycle.PageController.invokeEventMethod(PageController.java:110)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.handleEvent(PageLifecycleImpl.java:950)
     at oracle.adf.controller.v2.struts.lifecycle.StrutsPageLifecycle.handleEvent(StrutsPageLifecycle.java:238)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.processComponentEvents(PageLifecycleImpl.java:322)
     at oracle.adf.controller.v2.lifecycle.PageController.processComponentEvents(PageController.java:54)
     at oracle.adf.controller.v2.lifecycle.Lifecycle$3.execute(Lifecycle.java:275)
     at oracle.adf.controller.v2.lifecycle.Lifecycle.executePhase(Lifecycle.java:116)
     at oracle.adf.controller.v2.lifecycle.LifecycleProcessor.execute(LifecycleProcessor.java:100)
     at oracle.adf.controller.v2.struts.actions.DataAction.execute(DataAction.java:123)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1485)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:527)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:332)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
## Detail 0 ##
java.sql.SQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
     at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
     at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
     at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
     at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:330)
     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:282)
     at oracle.jbo.server.BaseSQLBuilderImpl.doEntityDML(BaseSQLBuilderImpl.java:352)
     at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:5731)
     at com.yukon.adf.postgre.entities.PostgreEntityImpl.doDML(PostgreEntityImpl.java:22)
     at com.yukon.adf.postgre.entities.PostgreSequenceEntityImpl.doDML(PostgreSequenceEntityImpl.java:58)
     at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:4531)
     at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:2993)
     at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2804)
     at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1968)
     at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2170)
     at view.actions.ListTestPageController.onCommit(ListTestPageController.java:32)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.adf.controller.v2.lifecycle.PageController.invokeEventMethod(PageController.java:110)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.handleEvent(PageLifecycleImpl.java:950)
     at oracle.adf.controller.v2.struts.lifecycle.StrutsPageLifecycle.handleEvent(StrutsPageLifecycle.java:238)
     at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.processComponentEvents(PageLifecycleImpl.java:322)
     at oracle.adf.controller.v2.lifecycle.PageController.processComponentEvents(PageController.java:54)
     at oracle.adf.controller.v2.lifecycle.Lifecycle$3.execute(Lifecycle.java:275)
     at oracle.adf.controller.v2.lifecycle.Lifecycle.executePhase(Lifecycle.java:116)
     at oracle.adf.controller.v2.lifecycle.LifecycleProcessor.execute(LifecycleProcessor.java:100)
     at oracle.adf.controller.v2.struts.actions.DataAction.execute(DataAction.java:123)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1485)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:527)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:332)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)

Sales Order Outbound IDOC - Restricting Items being created with a Segment

Hi,
I have a requirement to restrict segments being created for Items (Child) in Sales Order Outbound IDOC based on conditions in the Items (Parent & Child). Can you please suggest me a suitable solution?
Basic Type: ORDERS05, Message Type: ORDRSP. What is the IDOC Function Module to be used to create Outbound IDOC for Sales Order?
Appreciate Your Help.
Thanks,
Kannan
Edited by: Kannan SA on Jan 3, 2008 3:03 PM

Hi,
if the segments are mandatory then you can't trigger the idoc without those segments.
Otherwise, you can read the segment and clear all the data in it, the segment will not be attached to the outbound idoc.
Where to do it? Search the CALL CUSTOMER-FUNCTION '002' for the outbound idoc for example IDOC_OUTPUT_INVOICE for Invocing.
Regards,
Baburaj

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

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.

Outbound Idoc Error Handling by creating workitem

Similar Messages

Maybe you are looking for