Hi Arnold,
yes "AMOUNTDECIMALPOINT=," (try without spaces) should be enough and check if "ROUNDAMOUNT=" without values.
Kind regards
Roberto
even without spaces it made no difference and I tested both with and without "ROUNDAMOUNT=", neither made any difference.
So I changed the way data is exported from the source system in a way that I already get a . in the file instead of a , and now it works.
AMOUNTDECIMALPOINT option allows to specify a nonperiod decimal point for countries that use a different character, such as a comma. The character specified in this option must differ from the character specified for the DELIMITER.
May be you had the same delimiter.Just a thought
Thanks
Eashwari
Hi Eashwari,
The DELIMITER in the file is a semi-colon (;) which is also specified in the transformation file. So unless BPC cannot differentiate the two, that should not be the problem.
Thanks,
Arnold
Hi Arnold, What are the value that you have set into 'DELIMITER' or 'OUTPUTDELIMITER' ? You need to be aware that 'AMOUNTDECIMALPOINT' should not have same value with 'DELIMITER' or 'OUTPUTDELIMITER' because the decimal character should not be a character which separates dimensions. Regards, Anouar
I am not sure if the comma ( , ) is allowed or not to be used for the option 'AmountDecimalPoint'.
If you want to use the comma ( , ) as decimal point character, you can use this workaround:
===========<Transformation file =========================
*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER=
VALIDATERECORDS=NO
OUTPUTDELIMITER=:
ROUNDAMOUNT = 7
*MAPPING
*CONVERSION
*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER= :
VALIDATERECORDS=No
OUTPUTDELIMITER=:
AmountDecimalPoint = ,
*MAPPING
*CONVERSION
Hi Anouar,
The DELIMITER is set as a semi-colon (;) and I have used a comma as a delimiter in the past without any problems.
Thanks,
Arnold
