Start conditions and currency handling (version 46C)

Sat Sep 17 04:54:08 EDT 2005

Natasha, you need to read the whole thread (message). 

The topic is currency independent start conditions, not start conditions
using virtual attributes. As I mentioned earlier in the thread it is no
problem as long as the start condition is that the value should be
non-zero.

Jocelyn, you mention SRM. We are on 46C, so there may be some
differences if you are on 6-something.

In the condition editor, when a default currency is set, the field that
is used in the condition is labelled with the currency. I interpret this
labelling as having to ensure that the value of the attribute is in the
default currency. See the attached image which shows one of the
conditions SAP delivers as example.

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 Baunach, Natasha R
Sent: 16. september 2005 19:31
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

Yes, you can use virtual attributes in your starting conditions.  I have
used it in EBP 3.0.

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

But in my particular case there attributes are not table attributes,
they are virtual. Sure, they have been picked from the same table, but
would SAP reckognize that (more advanced than I 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: 15. september 2005 15:00
To: SAP Workflow Users' Group
Subject: RE: Start conditions and currency handling (version 46C)

Kjetil,
We use the currency option in start conditions in SRM. 
All dictionary definitions of type CURR have to have a matching CUKY
reference which tells the system where to read the currency code -
usually another field in the same table. 

Start condition currency conversion always uses the current date as the
conversion date, i.e. the date the event was created, and I'm pretty
sure it uses type M conversion -i.e. the average rate.  

But if you really want to know... you can always set up your start
condition, and use SWUE to start the event in debug mode, then step
through the debugging.  I've done this before now when we had a couple
of buglets with the start condition conversion and you can see what's
going on if you are sufficiently persistent. 

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

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Thursday, 15 September 2005 8:50 PM
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
>  
> 
> -------------------------------------------------------------------
> 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.
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> 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

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

_______________________________________________
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

-------------------------------------------------------------------
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.png
Type: image/png
Size: 6608 bytes
Desc: example.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050917/2c07d67e/attachment.png