12-11-2012 07:35 PM
I am updating financial data using web service in 9.14 and have enountered the following issue.
When updating 600 financial records for a project, the following error was thrown 'You cannot update cost in base currency. You can only update cost in local currency'. However, when updating the same project with a 300 financial records, the web service was able to process it successfully.
The same code is working fine in 9.12.
According to http://support.openview.hp.com/selfsolve/document/
Does anybody know how to explicitly set local currency in FinanceServiceClient.java?
12-12-2012 05:27 AM
This error could be because two reason.1st thing that we define base currency in PPM but if you are working for different region then currency could be different.so you need to check out that.
2.You need to check that webserivce always get authenticate by Admin user only if any project PM is different and admin user dont have access of FM then also it could be the error.
I also faced this issue and resolved in this way
12-13-2012 05:26 PM
Thanks for your reply.
I have checked my code and configuration and can confirm that:
1) the base currency matches with the region
2) webservice is authenticated using Admin user
I am only getting the error message when updating more than 600+ records. Otherwise the project is able to update successfully.
01-09-2013 02:57 AM
May be it is applied to Planned or Forecasted value as well, you need to check this.
-- Remember to give Kudos to answers! (click the KUDOS star)
05-04-2013 05:54 PM
I encountered the same issue while developing a WS client that clears existing values from FS.
The following statement (that worked perfectly in previous versions of the product), fails:
The following statement worked and accomplished what I needed (although in a computationally inefficient mannger):
It certainly seems to be an HP bug.
10-30-2013 05:53 AM
The problem is occurring because there is already a non zero base currency set for this value, and when you then try to set the value to zero, PPM Web Services generate the error.
The workaround seems to be that when attempting to set the value to zero, you also have to set the base value to zero – even though modification of the base value is what was supposed to be prevented.
This a defect in the web services code, following the 9.14 update.
But, until that can be resolved, when attempting to set a zero value, the workaround is to clear the base currency as well!
This is a defect QCCR1L49994 and applies to 9.22 i.e. the fix is expected in 9.22