WF condition check issues

[Sample, Rick]

Hi Krishna

Added the EX and works fine.

Rick

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Krishna K Kammaje
Sent: Friday, March 04, 2011 9:22 AM
To: SAP Workflow Users' Group
Subject: RE: WF condition check issues

Hi,

I had this problem.

I was using condition statement &ZBUS7051.approvalreqflag& EX.  (The possible values were 'X' and '')
The statement was working as expected in Dev and Q, but was giving unexpected results in Prod. (Our Production system is much faster that Dev and Q, does it point to something?)

To overcome this problem, I changed the possible values to 'T' and 'F'. Then I used "wait for condition" for&ZBUS7051.approvalreqflag& EX to ensure the attribute is populated.
Only after that I compared the values.

Let us know your findings.

Thanks
Krishna Kishor Kammaje




From:        "Sample, Rick" <Rick.Sample at graybar.com>
To:        "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date:        04/03/2011 19:44
Subject:        RE: WF condition check issues
Sent by:        sap-wug-bounces at mit.edu
________________________________



Hey Mike,

Thanks for input.

That BOR.attribute must be set to 'B' to start the WF in question. So, that values 'was' B for Blocked. (VBUK-CMGST I think?)
VKM1 Release block, set to <whatever?> space, INITIAL, ?
Seen this before, but can't recall.

If I can't find my notes, I am going to just put in:
zBUS2032.Overall CreditStatus = 'D' or zBUS2032.Overall CreditStatus = or
zBUS2032.Overall CreditStatus = '' or zBUS2032.Overall CreditStatus = ' '
and call it a day.

But I hate trying to explain multiple trasnsports and then the question comes up... why it works in dev not Q? We shouldn't be guessing why works in one client and not another.

I will poke around in SDN and respond when I get back in ofc and in the client in question. There is a reason, I will find it.

Rick

> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Friday, March 04, 2011 7:53 AM
> To: SAP Workflow Users' Group
> Subject: Re: WF condition check issues
>
> Blanks are always a minefield, as it depends on what you're doing with the
> container. Unused parameters will start out not existing in the container, once a
> value is assigned (even if blank), they come to life. If a value is not returned
> because it doesn't exist then it will be false, since ' '
> (space) is not the same as '' (nothing).
> Although when evaluating an attribute it should always work, so that's a bit odd -
> does your attribute code put a space into the return value?
>
> If possible try to reverse logic to check for copnditions that don't involve blank, or
> use 'EX' operator to check existence.
>
> Regards,
> Mike
>
>
> On Fri, March 4, 2011 1:23 pm, Sample, Rick wrote:
> > Hi all,
> >
> > I have a minor issue. I have a WF condition check on a standard BOR
> > attribute.
> > > >
> > Seen this before, but don't recall where / what I need to change.
> >zBUS2032.Overall CreditStatus = 'D' or zBUS2032.Overall CreditStatus =
> >
> > No value in VBUK-CMGST evaluates correctly in dev, but false in Q.
> > Rick
> >
> > _______________________________________________
> > 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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110304/433e0a62/attachment.htm