Background task in workflow acting funny

[Soady, Phil]

Hi Bill
 
When you run in foreground, YOUR decimal point settings are used.
When WF-BATCH is running in background HIS decimal point setting is used.
If the figured is being converted from CHAR to P anyway in a binding,
it will work while the user has decimal and NOT decimal comma.
 
I would look to the decimal settings on WF-BATCH in SU01.
 
hth
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: billfranken at pcmc.com [mailto:billfranken at pcmc.com]
Sent: Thursday, April 10, 2003 6:41 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Background task in workflow acting funny
 
 
I am having a problem with a workflow background process - we have a task that has a method (call function) to update the standard price on the material master - the call function does a bdc call trans for transaction MR21 - I have tested this function separately, in a program running in foreground, in a program that runs in background, and in workflow in foreground - It runs fine in all of these processes - but when I run the workflow task in background the MR21 call trans fails - It says the price field is not numeric - the field value is '97.63' - but if I put in a value of '9763' the process works fine - It appears that the decimal point is causing the error - its as if the transaction does not recognize that the field is USD - ( I do select the proper variant for USD ) - I checked WF-BATCH and it has all of the proper authorizations - Why would this call trans work everywhere except in workflow background?
 
I would appreciate and direction on this matter.
 
Thanks in advance!