cancel
Showing results for 
Search instead for 
Did you mean: 

WF generated an error message for all users when an IDOC could not be send to the target system

Former Member
0 Kudos

Hi everyone

we distribute EXCHANGE_RATE & GLMAST from our production system PT1(100) to our quality systems QT1(100) and QT(150)

PT(100) -> QT(100)

PT(100) -> QT(150)

After copying production PT1 to QT1, it was decided to create only the client QT(100).

PT(100) -> QT(100)

After the copy, the Partner Type "LS" QT_150 was deleted in PT1(100) in oder to avoid distributing the message type EXCHANGE_RATE/GLMAST to the non-existing client QT(150).

We forgot to delete the entries of QT(150) in the distribution model (BD64) of PT1 and that's probably the reason why we got an idoc generated in PT(100) for QT(150). The IDOC is in the outbound queue in PT1 with the error message "Entry in outbound table not found"

The issue is that the idoc error generated a workflow and many users have received the error message in their SAP Business Workplace Inbox


I have read in the SAP online help that standard task 'TS00007989' is associated with the idoc error event.

What I don't understand is, why the users get an entry in their SBWP Inbox? Is there a way to avoid that message in the inbox of all users?

Thanks in advance!

M.

Accepted Solutions (1)

Accepted Solutions (1)

pokrakam
Active Contributor

Normal behavior.

First, WF error handling is presumably set up (WE46). Then there are three levels of IDOC responsibles/admins you can maintain:
per message, per partner profile, and global. If any of them are not configured/empty then it will go up to the next level. If the global EDI admin is empty it will go to possible agents defined on the WF task. If that is set to 'General Task' then that's everyone in the system.

One option in workflow setup is to enable General Task for all IDOC WF tasks. I assume someone performed this, and I assume you have not defined any IDOC admins or responsible users anywhere.

The good news is you can cancel the offending tasks using SWIA. They should then disappear from everyone's inbox.

Then I suggest you maintain administrators...

Answers (1)

Answers (1)

Former Member
0 Kudos

Thanks a lot Mike