Start conditions and currency handling (version 46C)

Wed Sep 21 01:15:12 EDT 2005

Blush, blush.... 

You are of course spot on. I tested all three cases again, and can
confirm that it works as you described.
The additional attribute is on the event container level. The business
object attribute name is used with "(NOK)" appended, and the currency
icon is used instead of the ordinary attribute icon.

Thanks for your patience and persistence!
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: 20. september 2005 10:26
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

Kjetil,
Just make sure you selected the correct attribute - i.e. the
automatically generated one with the currency converted. 
When you turn on currency conversion for your start condition, go back
into your start condition, you should see some extra automatic
attributes appear with the usual name but with the start condition
currency added to the end. 

E.g. if your original attribute was called "TotalValue" and you turned
on currency for start condition = EUR when you go back into the start
condition you should see a new attribute appear "TotalValue(EUR)"
from memory this attribute appears at the highest level of the start
condition display, not within your object, but
look around.   If you don't see it first time, try saving the start
condition, and restarting SWB_COND again. 

You need to swap your original attribute with the the automatic currency
converted attribute in your condition. 

Then it should work. If you just use your original attribute, it will
just treat the value as a number without currency conversion.

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Kjetil Kilhavn
Sent: Tuesday, 20 September 2005 1:48 AM
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

I second the comment to Mike's reply, I can always work around it using
a boolean virtual attribute, and that is not the point of this
discussion. 

As I mentioned in a follow-up to another reply, I have tested the
currency conversion in our system - and it doesn't happen. But as I also
mentioned there, there may be additional functionality available in more
recent versions. Guess I will just have to wait a couple of years for
our main system to be upgraded :-(

Here's (the most important part of) what I wrote in that other reply:
Take for instance an accounting document. The currency key is in the
header (BKPF), whereas the amount(s) are in the items (BSEG), and
BSEG-WRBTR has a reference to BKPF-WAERS in the "Currency/quant.
fields".

I tested this by creating two virtual attributes on ZBSEG. One with
reference to BSEG-WRBTR and one with reference to BKPF-WAERS. I then set
up a start condition on an existing workflow, with default currency NOK
and requiring the amount in document currency to be > 5.000 NOK.

1) document currency NOK and amount 2.000
   workflow does not start, so test is OK

2) document currency NOK and amount 10.000
   workflow starts, so test is OK

3) document currency USD and amount 1.100 (~7.000 NOK)
   workflow does not start, so test is not OK

As far as I can observe there is no currency handling. If that is the
case, meaning currency translation has to be handled by me, myself, and
I, this is not any different than other numeric fields as far as I can
tell.

PS: That doesn't mean I don't like start conditions. It just means
amount conditions is a potential pitfall and not quite as neat as I
first thought.
--
Kjetil Kilhavn, Statoil KTJ IT BKS

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: 19. september 2005 16:34
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

Kjetil,
You shouldn't have to create a special "AmountinLocalCurrency"
attribute. 
Conversion is at current (i.e. event creation) date using exchange rate
type M. 

Mike, Re woods/trees - the whole point of start conditions is to add
clarity by removing programming.  So yes of course that approach will
work but is something of a backwards step clarity-wise, and therefore
should be avoided except in moments of extreme hair-pulling complexity
(and yes I've had some and have used that approach, but only where mere
attributes would not suffice). 

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Tuesday, 20 September 2005 12:10 AM
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

Hi Kjetil,
Just in case we're suffering a woods/trees moment, a simplistic approach
is of course to code the whole condition into an attribute. An instance
where I've used it was something like a table with company code, limit
and currency. The attribute simply told WF whether it required approval
or not.
Cheers
Mike

Kjetil Kilhavn wrote:
> Well, I thought it would be neater to be able to say that for all
companies, no matter which local currency the company has, there is a
limit of i.e. 5.000 NOK (which happens to correspond to ca. 650 EUR -
but that isn't really important in this context). Then, when an object
type had an amount, SAP should automatically convert it to the default
currency using the current date and some configurable rate type, and
compare the amount with the limit. Why would I want to have to create an
additional attribute on every object type for the sole purpose of
ensuring that the amount is in a specific currency.
>
> I don't ask much :->
> Have a good weekend.
> --
> Kjetil Kilhavn, Statoil KTJ IT BKS
>
>
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
Of Mike Pokraka
> Sent: 15. september 2005 12:50
> To: SAP Workflow Users' Group
> Subject: Re: Start conditions and currency handling (version 46C)
>
> Hi Kjetil,
> Isn't that why we see attributes like 'AmountInLocalCurrency'?
> Thru your attrib would convert it into a predefined standard which
shall
be followed.
> An alternative is to code your comparison value into a virtual
attribute
which reads it from customizing or wherever and converts it to the
currency specified by your currency attribute. Thus your condition would
be If OBJ.ClearedAmount < OBJ.Tolerance
>
> Cheers
> Mike
>
> Kjetil Kilhavn wrote:
>> I am working on a (thank you Sarbannes-Oxley for keeping me employed)
solution to notify about cleared inventory differences.
>> When an inventory difference is cleared, the cleared amount is not
available in the inventory record (object type BUS3021). Thus I have
created two virtual attributes for the amount and the currency which I
>
>> find from the material documents created when the difference is
> cleared.
>> As it is now, the requirement is that the workflow should start if
the
>
>> amount is non-zero. If the requirement changes I suppose absolute
values can be handled using OR between e.g. > 20 and < -20. However, how
can I specify the currency field for the amount attribute?
>> I haven't found any place in the condition editor to indicate that
the
>
>> condition I am setting up is an amount condition, so how will the
condition editor know that my currency attribute belongs to my value
attribute in order to determine if the amount has to be translated to
the condition currency?
>> As far as I know there are no structures containing amount +
currency,
>
>> the closest I have found is T001R_BF (in our system 5433 structures
contains currency key - I must admit I have not checked them all).
However, even if I use a structure with amount and currency, how will
the condition evaluation function know which translation date and
exchange rate type to use?
>> When the argument about currency handling was served in an earlier
thread I accepted that happily, but now I have begun wondering what it
>
>> really means that there is currency handling. SAP's delivered
examples
>
>> seem to indicate that the amount has to be converted before it is
served to the condition editor, but I don't think they would call that
>
>> currency handling unless the marketing people have taken over the
> whole show.
>> --
>> Kjetil Kilhavn, Statoil KTJ IT BKS

Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855

-------------------------------------------------------------------
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.