Please provide more details for the action you are performing which causes the error. Any further detail will be helpful for me to assist you.
1 of 1 people found this helpful
Supply conversion ratios in the ARSystem Currency form for all possible conversions.
Create currency ratios from every allowable currency to every functional currency and vice-versa.
The following procedure describes how to create currency exchange ratios for converting allowable currencies tofunctional currencies.
- Open the AR System Currency Ratios form in New mode
- Create two entries for each pair of currencies i.e. one for allowable to functionaland and other for functional to allowable.
For more details you can refer Form and Application Objects Guide.
I receive the very same error message when trying to re-assign a task in ITSM 8. Is it really necessary to configure entries in the form AR System Currency Ratios to be able to reassign tasks?!
Haven't found any info in the knowledgebase about this.
In the ITSM environment I currently work with only EUR is used as currency so I don't see why this need to be configured. The currency fields people not use either, they all keep null values.
Error message generated by the filter CHG:CRQ:CalculateTotalActualCost and the first Set Fields action.
Any hint much appreciated
We faced a similar issue at a client site when trying to update an existing Task for a Change record.
Such an error also comes when you assigning value (manually or via workflow) to a currency field using a currency which is no available to that field (e.g. setting AUD value to a field which has USD and does not have AUD as a allowable/functional currency)
It turned out that the Set-field destination fields "Actual Cost" and "Budget Cost" field on the Task form did not have AUD as a currency in our case, but the source fields on the CHG form had AUD as default.
So if the system was fine without any currency conversion ration records, and now you are getting the ARERR 360, it would be worth while looking at the workflow log to find out currency mismatches.
Another note to add to this - after adding entries to the Currency Ratio form within a Server Group environment, you must allow a few hours to allow the Server Group members to synchronise and cache this new data.
To resolve an issue on a recent customer site, I did a distinct scan of the CHG:Infrastructure Change form on currency fields to find all currency values that had been used, then added the respective currency ratios to the form.
I had forgotten about this issue we have, thanks Sumeet and Ash for keeping the thread alive, your comments made me receive notifications about the thread and I begun the troubleshooting again I've now found and fixed this in our environment.
Filter generating the error message is: CHG:CRQ:CalculateTotalActualCost
The cause here was:
In the old ITSM 7.6 system in the form CHG:Infrastructure Change and the field Actual Cost Static Total (302224400) the Default Value for the field was 0 USD.
In the upgraded staging environment with ITSM 8 the Default Value for the same field is 0 EUR.
During testing, when trying to update a task connected to a change created in ITSM 7.6 this error occurred. Updating a task connected to a change created in ITSM 8 worked fine.
After a test updating a failing task/change using the following SQL it worked fine, and I'll identify and fix the rest as well.
CHG_Infrastructure_Change SET Actual_Cost_Static_TotalC = 'EUR' WHERE Infrastructure_Change_ID =
Message was edited by: Karl-Johan Halleni
Pleasure Karl, glad that you were able to resolve your issue!
Hi Karl, I did not find the "0 EUR" as default value for the mentioned field on a 8.0 fresh box. So was it customization done before upgrading? Just curious here.
During install of the ITSM 7.6 environment the currency was set to EUR (I've checked logs and install documentation). For some reason some currency fields was not set to the EUR format but was still with the USD format.
During the upgrade to ITSM 8 the currency was set to EUR and this time the currency field(s) received the correct format/currency.
Yes, it seem strange but this is what I've found