topic EDI Errors - Production Issue in Application Development and Automation Discussions

EDI Errors - Production Issue

Former Member — Wed, 29 Oct 2008 21:40:30 GMT

Hi EDI Experts,

I want to know, whenever an inbound ORDERS idoc gives data related errors - Material number/Partner Number not valid, i mean in production, what should we do in production??

Ultimately application document will not be posted. But How can this issue will be taken care of by an EDI end user.

Do end user have the access to WE19??

How to handle EDI errors in production??

Please post some helpful replies. I'll be thankful to you.

Thank you,

Creasy Matt

Re: EDI Errors - Production Issue

Former Member — Wed, 29 Oct 2008 21:58:54 GMT

End users can process the errors in Workflow if you configure that, or you can give them access to WE02 / WE05 / BD87 etc to correct and reprocess the IDOCs

Re: EDI Errors - Production Issue

Former Member — Thu, 30 Oct 2008 16:58:52 GMT

Thanks for your reply.

I don't know how to configure the workflow.

Do we have to add WE19 also to the TCode List you have mentioned.

Thanks once again,

Creasy Matt

Re: EDI Errors - Production Issue

uwe_schieferstein — Thu, 30 Oct 2008 17:06:57 GMT

Hello Matthew

In our company we use different strategies to handle such errors:

(1) In one subsidiary error in inbound ORDERS IDocs (e.g. wrong EAN) are corrected (on SAP-XI we replace the wrong EAN with an existing Dummy EAN). The ORDERS IDoc will always be processed yet there is a VOFM condition defined that in such a case an ORDRSP IDoc is sent to SAP-XI. This response is converted into an e-mail addressed to the users that have to deal with these sales orders.

(2) In another subsidiary the erroneous IDoc fails within the ERP and then the colleagues adjust the IDoc data in their system (e.g. delete E1EDP01 segment containing wrong or obsolete EAN). Of course the customers have to be informed about these changes of their PO's.

In any case the users should have authorizations for dealing with IDocs and understand the basics of this technology.

Regards

Uwe

Re: EDI Errors - Production Issue

Former Member — Thu, 30 Oct 2008 17:07:01 GMT

Nope, WE19 is the test tool, and using it might cause duplicate transaction data to be posted in SAP, as well sending the duplicate txns out to partners / other systems

Re: EDI Errors - Production Issue

Former Member — Fri, 31 Oct 2008 19:08:31 GMT

Hi Uwe,

Thanks for your time and reply.

In the second situation, how to remove the E1EDP01 segment. Using WE19?? I hope user will not be having access to WE19.

One more thing, if we remove E1EDP01 segment, i am sure the inbound IDoc will not create application sales order.

How do you deal with this?

Thanks and Regards,

Vamsi

Re: EDI Errors - Production Issue

Former Member — Fri, 31 Oct 2008 19:24:53 GMT

You can give your users access to IDOC change , and based on the transaction they use they can do it in Workflow Inbox, WE02 or WE05. They cant use WE19 as that would be a new IDOC than changing the one in error.

The scenario Uwe mentioned was just for example, say your partner mgith have sent 2 E1EDP01s in error, then you mgith want to remove one of those.

Re: EDI Errors - Production Issue

uwe_schieferstein — Sun, 02 Nov 2008 18:25:18 GMT

Hello Vamsi

If there is at least a single E1EDP01 segment left the IDoc can be processed successfully.

Regards

Uwe

Re: EDI Errors - Production Issue

Former Member — Wed, 05 Nov 2008 11:42:30 GMT

Hi,

Use BD87 transaction in produciton systems.You can remove unwanted segments and fileds using this

ramesh