TS00008031 Standard task would not create WI automatically, e xcept throu SWUS
Amy C Yu
sapcaamy at hotmail.com
Mon Dec 1 18:17:58 EST 2003
Hi Phil,
Thanks, the idoc edit worked even without the delegation of object type
IDOCAPPL or IDOCSDPICK.
BTW, why do I have to raise the event INPUTERROROCCURRED for object
IDOCSDPICK in the user exit, shouldn't the system raise that event when
there is a SDPICK idoc error since it is a standard task?
Amy
>From: "Soady, Phil" <phil.soady at sap.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: TS00008031 Standard task would not create WI automatically, e
>xcept throu SWUS
>Date: Mon, 1 Dec 2003 00:08:19 +0100
>
>To Edit an IDOC fro the display Method on IDOCAPPL.
>Double click on the page icon next to the data segment.
>In the detail screen see menu option Data Record--> Display/Change
>
>
>Phil Soady
>Senior Consultant - Business Technologies
>Professional Services
>SAP Australia
>Level 1, 168 Walker Street, North Sydney 2060, Australia.
>M +61 412 213 079
>E phil.soady at sap.com
>
>
>
>-----Original Message-----
>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Amy C
>Yu
>Sent: Sunday, November 30, 2003 7:03 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: TS00008031 Standard task would not create WI automatically,
>except throu SWUS
>
>
>Hi Fred
>
>I have created an object type ZIDOCSDPIC, delegated to supertype
>IDOCSDPICK, then I copied the program source from method InputForeground to
>ZInputForeground, which is dialog and synchronous. Then I released the
>object type and component. In the standard task 8031, I changed the object
>type to ZIDOCSDPIC and method to ZInputForeground.
>
>After generating the test case, the SBWP displayed the WI, but I could not
>find the icon where I can change the idoc instead of display the idoc.
>Could you tell me how to navigate to the change idoc screen?
>
>Thanks.
>Amy
>
>
> >From: "Kouw, FA - SPLTX" <fa.kouw at td.klm.com>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: TS00008031 Standard task would not create WI
> >automatically, except throu SWUS
> >Date: Fri, 28 Nov 2003 16:32:50 +0100
> >
> >Hi Amy,
> >
> >To change an Idoc in dialog you can use object IDOCAPPL (or
> >IDOCORDRSP), method 'InputForeGround'. We copied this method to
> >'Z_InputForeGround_Sync' to be able to define it as a synchronous
> >method (instead of asynchronous). Hope this helps a bit.
> >
> >Regards,
> >
> >Fred Kouw
> >
> >Amy C Yu wrote:
> >
> > > Hi Kjetil,
> > >
> > > Thanks for your reply and we are currently using 4.6C.
> > >
> > > Per your suggestion, I inserted the process code ZSPK for TS00008031
> > > in WE40, but my testing still did not generate the WI. Then I tried
> >process
> > > code SDPI and it still did not work.
> > >
> > > So finally in order to get around the problem, I have to activate a
> > > user exit using CMOD, this user exit is triggered for error handling
> > > within
> >the
> > > FM SD_IDOC_INPUT_PICKING. I added the code to call
> >SAP_WAPI_CREATE_EVENT
> > > to trigger the event for object type IDOCSDPICK and event
> > > INPUTERROROCCURRED. Then the WI appears in the inbox but the title
> > > in
> >the
> > > WI does not pick up the WI text from the task. I have to drill into
> > > the Idoc display to find the error message from the idoc. I can
> > > live with
> >this.
> > >
> > > I will probably create an OSS note to inquire about this problem, I
> > > shouldn't have to trigger the event myself.
> > >
> > > Then, my next problem is how to activate the change mode of the
> > > idoc, so that I can modify the idoc segment to correct the problem
> > > before reprocessing?
> > >
> > > Any clue?
> > >
> > > Thanks.
> > > Amy (415) 816-0862
> > >
> > > >From: Kjetil Kilhavn <kjetilk at statoil.com>
> > > >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> > > >To: SAP-WUG at MITVMA.MIT.EDU
> > > >Subject: Re: TS00008031 Standard task would not create WI
> >automatically,
> > > >except throu SWUS
> > > >Date: Wed, 26 Nov 2003 09:34:08 +0100
> > > >
> > > >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.
> > >
> > > _________________________________________________________________
> > > Set yourself up for fun at home! Get tips on home entertainment
> >equipment,
> > > video game reviews, and more here.
> > > http://special.msn.com/home/homeent.armx
> > >
> > >
> >_______________________________________________________________________
> >__________________
> > > This inbound message from KPN has been checked for all known viruses
> > > by
> >KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > >
> >_______________________________________________________________________
> >______________________
> >
> >
> >**********************************************************************
> >This e-mail and any attachment may contain confidential and privileged
> >material intended for the addressee only. If you are not the addressee,
> >you are notified that no part of the e-mail or any attachment may be
> >disclosed, copied or distributed, and that any other action related to
> >this e-mail or attachment is strictly prohibited, and may be unlawful.
> >If you have received this e-mail by error, please notify the sender
> >immediately by return e-mail,
> >and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
>its
> >subsidiaries and/or its employees shall not be liable for the incorrect
>or
> >incomplete transmission of this e-mail or any attachments, nor
>responsible
> >for any delay in receipt.
> >**********************************************************************
> >
> >_______________________________________________________________________
> >______________________
> >This outbound message from KPN has been checked for all known viruses by
> >KPN IV-Scan, powered by MessageLabs.
> >For further information visit: http://www.veiliginternet.nl
> >_____________________________________________________________________________________________
>
>_________________________________________________________________
>Has one of the new viruses infected your computer? Find out with a FREE
>online computer virus scan from McAfee. Take the FreeScan now!
>http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
_________________________________________________________________
>From the hottest toys to tips on keeping fit this winter, you ll find a
range of helpful holiday info here.
http://special.msn.com/network/happyholidays.armx
More information about the SAP-WUG
mailing list