AW: Background task in workflow acting funny

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi Bill,
 
in the past we have learned somnetimes that call transaction via BDC =
acts
different mostly at numeric and date vales depending the Batch-User.
 
There is a f.m. 'MATERIAL_MAINTAIN_DARK'. I think this is a fine =
variant for
changing Materilas in background.
 
regrads
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: billfranken at pcmc.com [mailto:billfranken at pcmc.com]
Gesendet am: Mittwoch, 9. April 2003 22:41
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: 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!