Result Processing step not working in Workflow

Thu Feb 28 07:57:29 EST 2008

Oh, and something else to try:
To make sure it's nothing in your method, create a simple dummy method
that takes a char as an import parameter and simply returns it as your
misbehaving parameter. Then replace your task with this one and test it by
binding T/F.
Cheers,
Mike

On Wed, February 27, 2008 9:18 pm, Sue Doughty wrote:
> Hi Shai,
>
>
>
> Thank you for your response.
>
>
>
> I am testing in the client that the development was done.
>
>
>
> I removed the initial values from the container elements and tried the
> workflow again and am getting the same results.
>
>
>
> Regards,
>
> Sue T. Doughty
>
> SAP Workflow Specialist
>
> Old Dominion Freight Line, Inc.
>
> 500 Old Dominion Way
>
> Thomasville, NC 27360
>
> Phone:  (336) 822-5189
>
> Toll Free (800 ) 432-6335, ext. 5189
>
> Email:  sue.doughty at odfl.com
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Shai Eyal
> Sent: Wednesday, February 27, 2008 3:29 PM
> To: sap-wug at mit.edu
> Subject: RE: Result Processing step not working in Workflow
>
>
>
> Sue,
>
>
>
> I recalled another weird situation I had. In case you development client
> is different than the one you carry the tests (but both on same
> server!!) run SCC1 to copy transport to test client. I know it should
> not be relevant for workbench requests but in certain BASIS level (which
> I can't remember) record in table that was suppose to be customization
> was recorded on workbench request.
>
>
>
> In addition, pay attention your container elements do not have initial
> values !!
>
>
>
> Please try & notify.
>
>
>
>
>
>
> Regards,
> Shai Eyal
>
> SAP Logistics senior consultant
> SAP Workflow specialist
> Mobile: 972-52-5816633
>
>
>
> ----- Original Message ----
> From: "sap-wug-request at mit.edu" <sap-wug-request at mit.edu>
> To: sap-wug at mit.edu
> Sent: Wednesday, February 27, 2008 21:45:27
> Subject: SAP-WUG Digest, Vol 39, Issue 72
>
> Send SAP-WUG mailing list submissions to
>     sap-wug at mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>     http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
>     sap-wug-request at mit.edu
>
> You can reach the person managing the list at
>     sap-wug-owner at mit.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
>
>
> Today's Topics:
>
>   1. RE: Condition step not working in Workflow (Sue Doughty)
>   2. RE: SAP-WUG Digest, Vol 39, Issue 71 (yogesh patil)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Feb 2008 13:20:16 -0500
> From: "Sue Doughty" <Sue.Doughty at odfl.com>
> Subject: RE: Condition step not working in Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>
> <082C942F46528B44B5463D3C2A1FF0F40E5BACF3 at corp-m-exch2.corp.odfl.com>
> Content-Type: text/plain;    charset="us-ascii"
>
> Hi Mike,
>
> I changed the data type to SY-INPUT and still get the same results.
>
> Thank you for the suggestion though.  I'm willing to try anything.  I
> hope that it is not something so simple that I'll feel really stupid
> when I find it.  :-)
>
> Regards,
> Sue T. Doughty
> SAP Workflow Specialist
> Old Dominion Freight Line, Inc.
> 500 Old Dominion Way
> Thomasville, NC 27360
> Phone:  (336) 822-5189
> Toll Free (800 ) 432-6335, ext. 5189
> Email:  sue.doughty at odfl.com
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Wednesday, February 27, 2008 12:13 PM
> To: SAP Workflow Users' Group
> Subject: RE: Condition step not working in Workflow
>
> Hmm, not too sure then. I thought I'd mention as it would be worth
> checking. Also make sure your data type is valid for the values. Try
> changing it to SY-INPUT just to make sure.
>
> On Wed, February 27, 2008 4:11 pm, Sue Doughty wrote:
>> Hi Mike,
>>
>> Thanks for your reply.
>>
>> I am not using a result parameter even though I tried that when it did
>> not work the way I had it at first.  Neither way works.  I can see in
>> the workflow log that my export parameter (ImageFound) is being
>> populated with the correct 'T' or 'F' value, but the Results
> processing
>> step is not being executed with an F value - it only executes when the
>> export parameter contains a 'T' value.
>>
>> I can't use a virtual attribute because the input parameters to the
>> method change with each call to the method (i.e., doctype and
>> imagedate).
>>
>> Regards,
>> Sue T. Doughty
>> SAP Workflow Specialist
>> Old Dominion Freight Line, Inc.
>> 500 Old Dominion Way
>> Thomasville, NC 27360
>> Phone:  (336) 822-5189
>> Toll Free (800 ) 432-6335, ext. 5189
>> Email:  sue.doughty at odfl.com
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
>> Of Mike Pokraka
>> Sent: Wednesday, February 27, 2008 10:44 AM
>> To: SAP Workflow Users' Group
>> Subject: Re: Condition step not working in Workflow
>>
>> Hi Sue,
>> Are you using a standard return parameter or a result parameter?
>> ("Result
>> parameter" checkbox on your method properties).
>> Result parameters behave differently, T/F must be defined within the
>> data
>> dictionary and become separate outcomes of the method.
>> Also, perhaps a virtual attribute might be easier if this is all that
>> the
>> method does...
>>
>> Cheers,
>> Mike
>>
>> On Tue, February 26, 2008 5:06 pm, Sue Doughty wrote:
>>> We are on 4.7, ECC 6.0
>>>
>>>
>>>
>>> I have a sub-workflow that executes a loop until a result flag is set
>> to
>>> T.  It executes a method that reads a table with some information.
> If
>>> the record is found, the result is set to T, if not it is set to F
> and
>>> the result container is set in the method.  The next step is a
>> condition
>>> to check the result.  If T, the loop and sub-workflow are completed,
>> if
>>> F, it waits and tries again after five minutes.
>>>
>>>
>>>
>>> My problem:  If the method executes and the result is T, the workflow
>>> works as designed.  If the method returns a result of F, the workflow
>>> stops at that step and does not move to the condition step to check
>> the
>>> result.
>>>
>>>
>>>
>>> I can see that the method is returning the result container.  If the
>>> Result = T, I can see that the Result container is sent back to the
>>> sub-workflow.  When I look at the step in the log, it says that the
>>> background item was created, started, work item processing is
> complete
>>> and the result processing is done with no errors.
>>>
>>>
>>>
>>> If the Result is F, I can see that the method is returning the result
>>> container, but the workflow container does NOT get set to the Result.
>>> When I look at the step in the log, it says that the background item
>> was
>>> created; started and work item processing is complete with no errors,
>>> BUT the Result Processing is NOT done.
>>>
>>>
>>>
>>> What am I missing?  Why is the Result processing being done for one
>>> result but not the other?
>>>
>>>
>>>
>>> Regards,
>>>
>>> Sue T. Doughty
>>>
>>> SAP Workflow Specialist
>>>
>>> Old Dominion Freight Line, Inc.
>>>
>>> 500 Old Dominion Way
>>>
>>> Thomasville, NC 27360
>>>
>>> Phone:  (336) 822-5189
>>>
>>> Toll Free (800 ) 432-6335, ext. 5189
>>>
>>> Email:  sue.doughty at odfl.com
>>>
>>>
>>>
>>> ****************************
>>> CONFIDENTIALITY NOTICE: The information contained in this message may
>> be
>>> confidential, privileged, proprietary, or otherwise legally exempt
>> from
>>> disclosure. If the reader of this message is not the intended
>> recipient,
>>> or an employee or agent responsible for delivering this message to
> the
>>> intended recipient, you are hereby notified that you are not
>> authorized to
>>> read, print, retain, copy or disseminate this message, any part of
> it,
>> or
>>> any attachments. If you have received this message in error, please
>> delete
>>> this message and any attachments from your system without reading the
>>> content and notify the sender immediately of the inadvertent
>> transmission.
>>> Thank you for your cooperation.
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> ****************************
>> CONFIDENTIALITY NOTICE: The information contained in this message may
> be
>> confidential, privileged, proprietary, or otherwise legally exempt
> from
>> disclosure. If the reader of this message is not the intended
> recipient,
>> or an employee or agent responsible for delivering this message to the
>> intended recipient, you are hereby notified that you are not
> authorized to
>> read, print, retain, copy or disseminate this message, any part of it,
> or
>> any attachments. If you have received this message in error, please
> delete
>> this message and any attachments from your system without reading the
>> content and notify the sender immediately of the inadvertent
> transmission.
>> Thank you for your cooperation.
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ****************************
> CONFIDENTIALITY NOTICE: The information contained in this message may be
> confidential, privileged, proprietary, or otherwise legally exempt from
> disclosure. If the reader of this message is not the intended recipient,
> or an employee or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that you are not authorized
> to read, print, retain, copy or disseminate this message, any part of
> it, or any attachments. If you have received this message in error,
> please delete this message and any attachments from your system without
> reading the content and notify the sender immediately of the inadvertent
> transmission. Thank you for your cooperation.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Feb 2008 19:44:49 +0000
> From: yogesh patil <yogeh at hotmail.com>
> Subject: RE: SAP-WUG Digest, Vol 39, Issue 71
> To: <sap-wug at mit.edu>
> Message-ID: <BAY112-W7E9C19D9D14B6B0952742B31A0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi Sue,
>
> Can you delete the result processing step and re-create the same and
> also the bindings (if there are not many dependent steps on the result
> processing step ), i know there must be dependencies after that step),it
> has worked for me before...so just give it a try....
>
> Thanks,
> Yogesh
>
>
>
>
> yogesh "not a failure but a low aim is a crime"> From:
> sap-wug-request at mit.edu> Subject: SAP-WUG Digest, Vol 39, Issue 71> To:
> sap-wug at mit.edu> Date: Wed, 27 Feb 2008 12:53:40 -0500> > Send SAP-WUG
> mailing list submissions to> sap-wug at mit.edu> > To subscribe or
> unsubscribe via the World Wide Web, visit>
> http://mailman.mit.edu/mailman/listinfo/sap-wug> or, via email, send a
> message with subject or body 'help' to> sap-wug-request at mit.edu> > You
> can reach the person managing the list at> sap-wug-owner at mit.edu> > When
> replying, please edit your Subject line so it is more specific> than
> "Re: Contents of SAP-WUG digest..."> > > Today's Topics:> > 1. Re: RE:
> Antwort: Number range object for Workflow task-ID's?> (Mike Pokraka)> 2.
> RE: Condition step not working in Workflow (Sue Doughty)> 3. RE: viewing
> IXOS images via the UWL (Zavier, Johnson)> 4. RE: Condition step not
> working in Workflow (Mike Pokraka)> > >
> ---------------------------------------------------------------------->
>> !
> Message: 1> Date: Wed, 27 Feb 2008 15:47:40 -0000 (UTC)> From: "Mike
> Pokraka" <wug at workflowconnections.com>> Subject: Re: RE: Antwort: Number
> range object for Workflow task-ID's?> To: "SAP Workflow Users' Group"
> <sap-wug at mit.edu>> Message-ID:>
> <63042.212.157.1.1.1204127260.squirrel at workflowconnections.com.mail.aais
> p.net.uk>> > Content-Type: text/plain;charset=iso-8859-1> > Hi Florin,>
>> It is particularly this situation which makes different prefixes
> useful as> it's easier to spot where/when something was created.> > In
> any case, transaction PF05 is what you're after, but I see you already>
> found the long way round.> > Cheers,> Mike> > > On Wed, February 27,
> 2008 2:14 pm, Florin Wach wrote:> > @Keith> >> > We have moved the
> development from one system to another, keeping the> > existing prefix
> (as this is a multi-multi-multi system client), but the> > number range
> wasn't copied (correctly).> >> >> > @Christian> >> > With transaction
> SNUM you can modify the number range's ne!
> xt free no.> >> >> >> > Best wishes and thanks for the help,> > Florin
>> >> > -------- Original-Nachricht --------> >> Datum: Wed, 27 Feb 2008
> 14:06:48 -0000> >> Von: "Gardiner, Keith (CISS IT)"
> <Keith.Gardiner at capita.co.uk>> >> An: "SAP Workflow Users\' Group"
> <sap-wug at mit.edu>> >> Betreff: RE: Antwort: Number range object for
> Workflow task-ID\'s?> >> >> Hi Florin,> >>> >> Why don't you have a new
> prefix code for your new development system.> >>> >>> >> Regards> >>> >>
> Keith Gardiner> >>> >>> >> -----Original Message-----> >> From:
> sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf> >>
> Of Florin Wach> >> Sent: 27 February 2008 14:03> >> To: SAP Workflow
> Users' Group> >> Subject: Re: Antwort: Number range object for Workflow
> task-ID's?> >>> >> hrm... I mean: "The next number, which is assigned to
> a new object". So> >> I don't want to change the ID of something
> existing, just to make sure> >> to get correct numbers for new
> workflows, as we have moved the> >> Dev.-System.> >>> >>> >>> >>
> -------- Original-Nachricht --------> >> > !
> Datum: Wed, 27 Feb 2008 14:56:48 +0100> >> > Von: "Christian Wallner"
> <C.Wallner at ats.net>> >> > An: "SAP Workflow Users\' Group"
> <sap-wug at mit.edu>> >> > Betreff: Antwort: Number range object for
> Workflow task-ID\'s?> >>> >> > Hi Florin,> >> >> >> > As far as I know,
> no :-(> >> >> >> > cheers,> >> > chris> >> >> >> >> >> >> >> >> >> >
> "Florin Wach" <florin.wach at gmx.net>> >> > Gesendet von:
> sap-wug-bounces at mit.edu> >> > 27.02.2008 14:47> >> > Bitte antworten an>
>>> > "SAP Workflow Users' Group" <sap-wug at mit.edu>> >> >> >> >> >> > An>
>>> > "SAP Workflow Users' Group" <sap-wug at mit.edu> Kopie> >> >> >> >
> Thema> >> > Number range object for Workflow task-ID's?> >> >> >> >> >>
>>> >> >> >> >> >> >> >> > Hi,> >> >> >> > (where) is it possible to
> change the numbers assigned to new tasks,> >> > such as
> WS901<numberCounter>, TS9xx<numberCounter>.> >> >> >> > So I'm not
> talking about the prefix numbers 9xx, but I'm looking for a> >>> >> >
> number range object.> >> >> >> > It doesn't seem!
>   to be the HRWFOBJECT> >> >> >> >> >> > Any help?> >> > Florin> >> > _
> ______________________________________________> >> > SAP-WUG mailing
> list> >> > SAP-WUG at mit.edu> >> >
> http://mailman.mit.edu/mailman/listinfo/sap-wug> >> >> >> >> >> > AT&S
> Austria Technologie & Systemtechnik AG Legal form | Rechtsform:> >> >
> Aktiengesellschaft Registered office | Sitz: Fabriksgasse 13, 8700> >> >
> Leoben, Austria Commercial Register Number | Firmenbuchnummer: FN> >> >
> 55638 x, Landesgericht Leoben> >> >> >> > This e-mail and any attachment
> may contain confidential and/or> >> > privileged information. If you are
> not the intended recipient (or have> >>> >> > received this e-mail in
> error) please notify the sender immediately> >> > and destroy this
> e-mail. Any unauthorised copying, disclosure or> >> > distribution of
> the material in this e-mail is strictly forbidden.> >>
> _______________________________________________> >> SAP-WUG mailing
> list> >> SAP-WUG at mit.edu> >>
> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >> This email has
> been scanned for all viru!
> ses by the MessageLabs SkyScan> >> service.> >>> >> This email and any
> files transmitted with it are confidential, and may> >> be> >> subject
> to legal privilege, and are intended solely for the use of the> >>
> individual or entity to whom they are addressed.> >> If you have
> received this email in error or think you may have done so,> >> you may
> not peruse, use, disseminate, distribute or copy this message.> >>
> Please> >> notify the sender immediately and delete the original e-mail
> from your> >> system.> >>> >>
> _______________________________________________> >> SAP-WUG mailing
> list> >> SAP-WUG at mit.edu> >>
> http://mailman.mit.edu/mailman/listinfo/sap-wug> >
> _______________________________________________> > SAP-WUG mailing list>
>> SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >>
>> > > > ------------------------------> > Message: 2> Date: Wed, 27 Feb
> 2008 11:11:09 -0500> From: "Sue Doughty" <Sue.Doughty at odfl.com>>
> Subject: RE: Condition step not working in!
>   Workflow> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-
> ID:>
> <082C942F46528B44B5463D3C2A1FF0F40E5BAB64 at corp-m-exch2.corp.odfl.com>>
> Content-Type: text/plain; charset="us-ascii"> > Hi Mike,> > Thanks for
> your reply.> > I am not using a result parameter even though I tried
> that when it did> not work the way I had it at first. Neither way works.
> I can see in> the workflow log that my export parameter (ImageFound) is
> being> populated with the correct 'T' or 'F' value, but the Results
> processing> step is not being executed with an F value - it only
> executes when the> export parameter contains a 'T' value.> > I can't use
> a virtual attribute because the input parameters to the> method change
> with each call to the method (i.e., doctype and> imagedate).> >
> Regards,> Sue T. Doughty> SAP Workflow Specialist> Old Dominion Freight
> Line, Inc.> 500 Old Dominion Way> Thomasville, NC 27360> Phone: (336)
> 822-5189> Toll Free (800 ) 432-6335, ext. 5189> Email:
> sue.doughty at odfl.com> -----Original Message-----> From:
> sap-wug-bounces at mit.edu [mailto:sa!
> p-wug-bounces at mit.edu] On Behalf> Of Mike Pokraka> Sent: Wednesday,
> February 27, 2008 10:44 AM> To: SAP Workflow Users' Group> Subject: Re:
> Condition step not working in Workflow> > Hi Sue,> Are you using a
> standard return parameter or a result parameter?> ("Result> parameter"
> checkbox on your method properties).> Result parameters behave
> differently, T/F must be defined within the> data> dictionary and become
> separate outcomes of the method.> Also, perhaps a virtual attribute
> might be easier if this is all that> the> method does...> > Cheers,>
> Mike> > On Tue, February 26, 2008 5:06 pm, Sue Doughty wrote:> > We are
> on 4.7, ECC 6.0> >> >> >> > I have a sub-workflow that executes a loop
> until a result flag is set> to> > T. It executes a method that reads a
> table with some information. If> > the record is found, the result is
> set to T, if not it is set to F and> > the result container is set in
> the method. The next step is a> condition> > to check the result. If T,
> the loop an!
> d sub-workflow are completed,> if> > F, it waits and tries again after
> five minutes.> >> >> >> > My problem: If the method executes and the
> result is T, the workflow> > works as designed. If the method returns a
> result of F, the workflow> > stops at that step and does not move to the
> condition step to check> the> > result.> >> >> >> > I can see that the
> method is returning the result container. If the> > Result = T, I can
> see that the Result container is sent back to the> > sub-workflow. When
> I look at the step in the log, it says that the> > background item was
> created, started, work item processing is complete> > and the result
> processing is done with no errors.> >> >> >> > If the Result is F, I can
> see that the method is returning the result> > container, but the
> workflow container does NOT get set to the Result.> > When I look at the
> step in the log, it says that the background item> was> > created;
> started and work item processing is complete with no errors,> > BUT the
> Result Processing is NOT done.> >> >> >> > What am I missing? Why is t!
> he Result processing being done for one> > result but not the other?> >>
>>> >> > Regards,> >> > Sue T. Doughty> >> > SAP Workflow Specialist> >>
>> Old Dominion Freight Line, Inc.> >> > 500 Old Dominion Way> >> >
> Thomasville, NC 27360> >> > Phone: (336) 822-5189> >> > Toll Free (800 )
> 432-6335, ext. 5189> >> > Email: sue.doughty at odfl.com> >> >> >> >
> ****************************> > CONFIDENTIALITY NOTICE: The information
> contained in this message may> be> > confidential, privileged,
> proprietary, or otherwise legally exempt> from> > disclosure. If the
> reader of this message is not the intended> recipient,> > or an employee
> or agent responsible for delivering this message to the> > intended
> recipient, you are hereby notified that you are not> authorized to> >
> read, print, retain, copy or disseminate this message, any part of it,>
> or> > any attachments. If you have received this message in error,
> please> delete> > this message and any attachments from your system
> without reading!
>   the> > content and notify the sender immediately of the inadvertent>
> transmission.> > Thank you for your cooperation.> >> >
> _______________________________________________> > SAP-WUG mailing list>
>> SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >>
>> > _______________________________________________> SAP-WUG mailing
> list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug>
>> > ****************************> CONFIDENTIALITY NOTICE: The
> information contained in this message may be confidential, privileged,
> proprietary, or otherwise legally exempt from disclosure. If the reader
> of this message is not the intended recipient, or an employee or agent
> responsible for delivering this message to the intended recipient, you
> are hereby notified that you are not authorized to read, print, retain,
> copy or disseminate this message, any part of it, or any attachments. If
> you have received this message in error, please delete this message and
> any attachments from your system without reading the content and notify
> the sender !
> immediately of the inadvertent transmission. Thank you for your
> cooperation.> > > > ------------------------------> > Message: 3> Date:
> Wed, 27 Feb 2008 10:11:33 -0700> From: "Zavier, Johnson"
> <JZavier at Suncor.com>> Subject: RE: viewing IXOS images via the UWL> To:
> "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:>
> <FDDCD89534C5E84C8E635452F3B8A0ABEC57B8 at MAILPRD013.network.lan>>
> Content-Type: text/plain; charset="iso-8859-1"> > Similar issue happened
> to me few years back and I remember it was rectified with upgrading the
> JAVA Viewer. > > thanks> Johnson Zavier> SAP ABAP/Workflow > 1724D>
> Suncor Energy Inc.> Work: (403) 693 1893> e-mail: jzavier at suncor.com> >
> -----Original Message-----> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mikko M?ki-Rahkola> Sent:
> Wednesday, February 27, 2008 6:53 AM> To: sap-wug at mit.edu> Subject: Re:
> viewing IXOS images via the UWL> > Hi Karl,> I remember bumping into the
> same problem a while ago so here are m!
> y comments..> > I assume you are using a before method IMAGE-DISPLAY o
> r similar on the task to display the invoice image just before launching
> a FI transaction, correct? If yes, the reason why you're most likely to
> get the error is because ITS isn't set up correctly.> > But don't worry
> about this problem - ITS and SAP GUI for HTML> (=webgui) based work item
> execution with a separate invoice image display will not meet your
> requirements even though it would be set up. The reason for this is that
> ITS/SAP GUI for HTML doesn't support multiple sessions which you require
> in order to display the invoice image in the first session and the
> transaction in the other session.> OSS confirmed this to me last autumn
> in a customer message.> > So you're basically left with two alternative
> options:> 1. SAP GUI for Windows> - in this option you will have to
> visualize(=display) the work item in the UWL with SAP GUI for Windows.
> This means that when you execute the work item SAP GUI for Windows is
> launched within the next step in another window (depending on your!
>   config) and you will get two SAP GUI sessions open, one with the
> transaction and the second with the invoice image.> - in order to
> accomplish this, you need to adjust the UWL item type configuration for
> the task you are executing. Basically the only thing required is setting
> the GuiType property to WinGui so it will launch wingui instead of
> webgui. For more details on this, please see the UWL config on
> help.sap.com and especially
> http://help.sap.com/saphelp_nw04s/helpdata/en/af/ce571400fa458a8ad8936fd
> d49d75a/frameset.htm> > 2. Direct IXOS lookup> - here you would have a
> custom action defined for the UWL item which would launch the invoice
> image with a separate click in another window and the transaction itself
> would be launched with wingui/webgui in another window when executing
> the work item> - the drawback is that this is more difficult and IXOS
> may not support it at all (not sure since I haven't worked with it that
> much) but basically here UWL would directly call the in!
> voice image in IXOS without a roundtrip to SAP ERP> - what this requir
> es is> 1. IXOS for example exposing the invoice image display through an
> HTTP interface meaning that you could display any stored invoice image
> by calling a specific URL with correct parameters and 2. the UWL
> configured to have a custom defined action against your task and the
> action to launch a URL with parameters (e.g. invoice image ID) fetched
> from the work item container> > A third option may also be to create a
> custom transaction which would show the transaction next to the invoice
> image, all in one session.> But this would of course require quite a bit
> of effort especially compared to the options above which can be done in
> hours instead of days or weeks.> > Hope this helps,> > Mikko
> M?ki-Rahkola> Nobultec Ltd> > > Date: Wed, 27 Feb 2008 14:47:31 +1100> >
> From: "Nietz, Karl K" <Karl.Nietz at BHPBilliton.com>> > Subject: viewing
> IXOS images via the UWL> > To: <sap-wug at mit.edu>> > Message-ID:> > > >
> <5372E2FBE781494DA8D1D34E71BC73177A02F2 at ENTMEL-XCH05.apac.ent.bhpbilli>
>> to!
> n.net>> >> > Content-Type: text/plain; charset="us-ascii"> >> >> > Hi,>
>>> > We have scanned IXOS images (invoices etc) attached to workitems in
> a > > backend 4.7 system. These are created via the ArchiveLink
> technology > > using transaction OAWD.> >> > We can see the workitems
> rendered in the Universal Worklist > > successfully but when we attempt
> to execute a workitem where the IXOS > > image is displayed, or click on
> the hotlink attachment for the IXOS > > image, an error occurs. It seems
> that the IXOS viewer cannot be > > started-up from within the UWL.> >> >
> Is it possible to configure the UWL or ITS so that IXOS documents can >
>> be viewed in the UWL?> >> > Karl Nietz> > Workflow Support Team
> Leader> > CSC Melbourne> > Ph: 61 3 86951157> > Mob: 61 434 181303> >
> _______________________________________________> SAP-WUG mailing list>
> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug>
> ------------------------------------------------------------------------
>>!
>   This e-mail contains confidential information. If you are not the int
> ended recipient or have received this e-mail in error, please notify the
> sender immediately and destroy this e-mail. Any unauthorized copying,
> disclosure or distribution of the e-mail or the information it contains,
> is strictly forbidden.> > > > ------------------------------> > Message:
> 4> Date: Wed, 27 Feb 2008 17:13:26 -0000 (UTC)> From: "Mike Pokraka"
> <wug at workflowconnections.com>> Subject: RE: Condition step not working
> in Workflow> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>>
> Message-ID:>
> <38396.212.157.1.1.1204132406.squirrel at workflowconnections.com.mail.aais
> p.net.uk>> > Content-Type: text/plain;charset=iso-8859-1> > Hmm, not too
> sure then. I thought I'd mention as it would be worth> checking. Also
> make sure your data type is valid for the values. Try> changing it to
> SY-INPUT just to make sure.> > On Wed, February 27, 2008 4:11 pm, Sue
> Doughty wrote:> > Hi Mike,> >> > Thanks for your reply.> >> > I am not
> using a result parameter even though I tried that when it!
>   did> > not work the way I had it at first. Neither way works. I can
> see in> > the workflow log that my export parameter (ImageFound) is
> being> > populated with the correct 'T' or 'F' value, but the Results
> processing> > step is not being executed with an F value - it only
> executes when the> > export parameter contains a 'T' value.> >> > I
> can't use a virtual attribute because the input parameters to the> >
> method change with each call to the method (i.e., doctype and> >
> imagedate).> >> > Regards,> > Sue T. Doughty> > SAP Workflow Specialist>
>> Old Dominion Freight Line, Inc.> > 500 Old Dominion Way> >
> Thomasville, NC 27360> > Phone: (336) 822-5189> > Toll Free (800 )
> 432-6335, ext. 5189> > Email: sue.doughty at odfl.com> > -----Original
> Message-----> > From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf> > Of Mike Pokraka> > Sent:
> Wednesday, February 27, 2008 10:44 AM> > To: SAP Workflow Users' Group>
>> Subject: Re: Condition step not working in Workflow>!
>   >> > Hi Sue,> > Are you using a standard return parameter or a result
> parameter?> > ("Result> > parameter" checkbox on your method
> properties).> > Result parameters behave differently, T/F must be
> defined within the> > data> > dictionary and become separate outcomes of
> the method.> > Also, perhaps a virtual attribute might be easier if this
> is all that> > the> > method does...> >> > Cheers,> > Mike> >> > On Tue,
> February 26, 2008 5:06 pm, Sue Doughty wrote:> >> We are on 4.7, ECC
> 6.0> >>> >>> >>> >> I have a sub-workflow that executes a loop until a
> result flag is set> > to> >> T. It executes a method that reads a table
> with some information. If> >> the record is found, the result is set to
> T, if not it is set to F and> >> the result container is set in the
> method. The next step is a> > condition> >> to check the result. If T,
> the loop and sub-workflow are completed,> > if> >> F, it waits and tries
> again after five minutes.> >>> >>> >>> >> My problem: If the method
> executes and the result is T, the workflow> >> works as designed. If the
> metho!
> d returns a result of F, the workflow> >> stops at that step and does
> not move to the condition step to check> > the> >> result.> >>> >>> >>>
>>> I can see that the method is returning the result container. If the>
>>> Result = T, I can see that the Result container is sent back to the>
>>> sub-workflow. When I look at the step in the log, it says that the>
>>> background item was created, started, work item processing is
> complete> >> and the result processing is done with no errors.> >>> >>>
>>>> >> If the Result is F, I can see that the method is returning the
> result> >> container, but the workflow container does NOT get set to the
> Result.> >> When I look at the step in the log, it says that the
> background item> > was> >> created; started and work item processing is
> complete with no errors,> >> BUT the Result Processing is NOT done.> >>>
>>>> >>> >> What am I missing? Why is the Result processing being done
> for one> >> result but not the other?> >>> >>> >>> >> Regards,> >>> >> !
> Sue T. Doughty> >>> >> SAP Workflow Specialist> >>> >> Old Dominion Fr
> eight Line, Inc.> >>> >> 500 Old Dominion Way> >>> >> Thomasville, NC
> 27360> >>> >> Phone: (336) 822-5189> >>> >> Toll Free (800 ) 432-6335,
> ext. 5189> >>> >> Email: sue.doughty at odfl.com> >>> >>> >>> >>
> ****************************> >> CONFIDENTIALITY NOTICE: The information
> contained in this message may> > be> >> confidential, privileged,
> proprietary, or otherwise legally exempt> > from> >> disclosure. If the
> reader of this message is not the intended> > recipient,> >> or an
> employee or agent responsible for delivering this message to the> >>
> intended recipient, you are hereby notified that you are not> >
> authorized to> >> read, print, retain, copy or disseminate this message,
> any part of it,> > or> >> any attachments. If you have received this
> message in error, please> > delete> >> this message and any attachments
> from your system without reading the> >> content and notify the sender
> immediately of the inadvertent> > transmission.> >> Thank you for your
> cooperation.> >>> >!
>> _______________________________________________> >> SAP-WUG mailing
> list> >> SAP-WUG at mit.edu> >>
> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >> >> >
> _______________________________________________> > SAP-WUG mailing list>
>> SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >>
>>> > ****************************> > CONFIDENTIALITY NOTICE: The
> information contained in this message may be> > confidential,
> privileged, proprietary, or otherwise legally exempt from> > disclosure.
> If the reader of this message is not the intended recipient,> > or an
> employee or agent responsible for delivering this message to the> >
> intended recipient, you are hereby notified that you are not authorized
> to> > read, print, retain, copy or disseminate this message, any part of
> it, or> > any attachments. If you have received this message in error,
> please delete> > this message and any attachments from your system
> without reading the> > content and notify the sender immediat!
> ely of the inadvertent transmission.> > Thank you for your cooperation
> .> >> > _______________________________________________> > SAP-WUG
> mailing list> > SAP-WUG at mit.edu> >
> http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > > > >
> ------------------------------> >
> _______________________________________________> SAP-WUG mailing list>
> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > >
> End of SAP-WUG Digest, Vol 39, Issue 71>
> ***************************************
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080227/9329472c/a
> ttachment.htm
>
> ------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> End of SAP-WUG Digest, Vol 39, Issue 72
> ***************************************
>
>
>
>
> Send instant messages to your online friends
> http://uk.messenger.yahoo.com
>
>
>
> ****************************
> CONFIDENTIALITY NOTICE: The information contained in this message may be
> confidential, privileged, proprietary, or otherwise legally exempt from
> disclosure. If the reader of this message is not the intended recipient,
> or an employee or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that you are not authorized to
> read, print, retain, copy or disseminate this message, any part of it, or
> any attachments. If you have received this message in error, please delete
> this message and any attachments from your system without reading the
> content and notify the sender immediately of the inadvertent transmission.
> Thank you for your cooperation.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>