TS00008031 Standard task would not create WI automatically, except throu SWUS

[Kjetil Kilhavn]

First of all: you have provided a lot of details - excellent! You forgot
your SAP R/3 version though :-)
 
IDoc processing is not something I have worked much with, we only set up a
quite simple error processing scheme once. So bear in mind that your
thinking may be two levels higher than mine. It seems that your solution is
much more advanced than ours was.
 
As far as I can see from your descriptions you haven't been in WE40 to set
up the system process code responses. You may have and just forgot to
mention it, or it may already be set up, but I would check that it is set
up at least for code EDII. The IDoc procesing doesn't generate events to
process errors (at least that's how I recall it), it uses the setup in this
table to start the task or workflow directly.
 
By setting up something in WE40 you can do your own processing and create
the desired event when the conditions match, otherwise proceed with
standard IDoc error processing. You mention the check function on the
IDocAppl event inputErrorOccurred. Since the tasks set up in WE40 does not
involve events there are no check functions. What you can do is start a
modified task which triggers a generic event or which acts as a check
function. If you trigger a generic event you will of course need a check
function (or start condition) on your solution. If you implement a check
function in your business object you can trigger exactly the event you want
and may manage without a check function.
 
Hope this may help a little.
--
Kjetil Kilhavn
 
 
 
 
 
                    Amy C Yu
                    <sapcaamy at hotmail.co        To:     SAP-WUG at MITVMA.MIT.EDU
                    m>                          cc:     (bcc: Kjetil Kilhavn)
                    Sent by: SAP                Subject:     TS00008031 Standard task would not create WI automatically, except throu SWUS
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    26.11.2003 01:17
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
Here s more info about my problem, I hope someone can help me, I am
desperate :(  :(
 
I need to use the standard task 8031 to trigger WI for inbound idoc input
error for message type SDPICK, but the event is not triggered. I can create
the WI using SWUE or SWUS with no problem.
 
This is what I have done:
In OOCU, I have activated TS 00008031 WE IDOCSDPICKINPUTERROROCCURRED and
TS
20000051  WE IDOCAPPL  INPUTERROROCCURRED.  TS 20000051  IDOCAPPL is the
supertype of TS 00008031 IDOCSDPICK.
 
In PFTC_CHG, I have changed the status of task group 20000011 and 20000010
to implement.  20000011 contains the task group 20000010; 20000010 contains
the standard task 8031, which has status implement too.  I have assigned
 job  to 20000011, I am the agent for the job.
However, TS20000051 does not have any agent assignment.
 
In SWE2 and SWE3, I have activated IDOCSDPICK s INPUTERROROCCURRED and
INPUTFINISHED;  and IDOCAPPL s INPUTERROROCCURRED, INPUTFINISHED,
ERRORPROCESSCOMPLETD.  However, IDOCSDPICK s IDOCSDPICK_IN_START and
IDOCSDPICK_IN_END are deactivated.
 
In SWU0 event simulation, object type=IDOCSDPICK, event=
inputErrorOccurred,
it showed that there are 2 object types IDOCAPPL and IDOCSDPICK, and 2
tasks: TS 8031 and TS20000051, both showed no errors after I activated them
and removed a check function module from IDOCAPPL inputerroroccurred.
 
In SWU3, the customizing is complete for the  Workflow runtime system
Only.
  Since we are not using the  WF development environment , so no prefix
numbers for standard object types and custom tasks.
 
In WE46 global parm, I turned on the Synchronous Processing.
I turned on the event trace SWELS and workflow trace SWU8.
 
I used WE19 to create my error inbound SDPICK idoc, after the idoc with
error is created with status 51 (application error).
 
SBWP does not show any WI in my inbox.
 
So I used SWUE to  create event  using Object type=IDOCSDPICK,
event=inputErrorOccurred and my newly created idoc, the returned status
showed  Event created   at least one receiver found
Then in my inbox, the work item showed up, when I drill down on it, it
showed 2 error messages:
- I051(W8) 1 errors occurred in binding assignment to EXCEPTION
- W139(W8)   Element EXCEPTION not in source container
It seemed that something is missing and did not create the event.
 
SWEL showed the 2 receiver types TS 8031 and TS20000051 are OK with no
error
SWU9 showed trace information only at the time when I use SWUE to create
event, but not when I use WE19 to create the error idoc. The WF trace
showed
ConBindErrors for the above I051(W8) and W139(W8) errors:
ContBindErrors
    I051(W8) 1 errors occurred in binding assignment to
APPLICATION_VARIABLE
           W139(W8) Element APPLICATION_VARIABLE not in source container
    I051(W8) 1 errors occurred in binding assignment to EXCEPTION
           W139(W8) Element EXCEPTION not in source container
    I051(W8) 1 errors occurred in binding assignment to MESSAGEID
           W139(W8) Element MESSAGED not in source container
    And the same I051 and W139 errors for MESSAGENUMBER, MESSAGETYPE,
MESSAGEVARIABLE1, MESSAGEVARIABLE2, MESSAGEVARIABLE3 and MESSAGEVARIABLE4.
 
Questions:
1. Why doesn t the system create the WI automatically when the inbound idoc
failed with status 51?  The SDPICK inputerroroccurred event is not
triggering the task TS8031.
 
2. In SBWP, when the user selects the WI and drills down to the Idoc with
status 51 (application not post due to data error), there is no  change
icon that allows the user to modify the erroneous fields in the idoc
segments before reprocessing the WI. How can I activate the  change  mode
of
the Idoc? In the 4.6C release  CA210 class chapter 8 Workflow and IDoc
exercise, it indicated that the IDoc display screen can be changed to
 change  mode to allow modification to the data record segment.
 
3. What s the difference between status  Release  and  Implement  in
PFTC_CHG?
 
4. Is it OK to remove the check function module from IDOCAPPL
inputerroroccurred?  It was giving me error in the SWU0 complaining about
 result depending on a check function module .  Since TS 20000051  IDOCAPPL
is the supertype of TS 00008031 IDOCSDPICK, do I have to activate it too?
 
5. Is it true that we can only activate  triggering event  and  terminating
event  of standard task in the configuration client (client-independent)?
In other client-dependent clients, I got  not modifiable  error.
 
Thanks in advance.
Amy
 
_________________________________________________________________
Need a shot of Hank Williams or Patsy Cline?  The classic country stars are
always singing on MSN Radio Plus.  Try one month free!
http://join.msn.com/?page=offers/premiumradio
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.