topic Re: error with workflow since hotpack in Application Development and Automation Discussions

error with workflow since hotpack

Former Member — Tue, 13 Dec 2005 15:55:03 GMT

We applied hotpacks 52-56 and the IDOCORDERS workflow as stopped working - it does not create the work item. I have re-activated the ALE Coupling to not avial..If I turn on the event trace - the 8046 (inbound idoc error) shows as launching with recievers found - but no work item - then another task TS20000051 shows as in error with Form of address key is not defined AM 117 in FM CHECK_OBJECT_TYPE_IDOCAPPL, it is supposed to start the work item and put the message in the recievers inbox - nothing from OSS yet - anyone have any ideas or suggestions?

I can use create event (SWUE), put in the object and idoc nunber and all is good - just getting old doing this manually....Thanks - janet

Re: error with workflow since hotpack

Former Member — Tue, 13 Dec 2005 16:07:49 GMT

Janet - do you have any custom development that was overwritten by the hotpacks? Did you go through transaction SPAU?

Rob

Re: error with workflow since hotpack

Former Member — Tue, 13 Dec 2005 16:13:42 GMT

Rob - There is no custom code - all standard SAP to send errored inbound idocs to the recievier. I have been thru spau, but found nothing...I can go into the task and see all the assigned recievers - everything looks good - just this wacky message on the form of address. Janet

Re: error with workflow since hotpack

Former Member — Tue, 13 Dec 2005 17:22:09 GMT

Hi Janet,

You might try comparing the function module CHECK_OBJECT_TYPE_IDOCAPPL before and after the hot packs. It seems to be telling you that something has changed and by doing this you might get some insight to what it different.

But the bottom line is that with no customization, and a standard SAP workflow that croaked after the application of the hot pack, I think OSS will be your best bet on this one.

Good luck.

Brent