Question:
We have a requirement to convert a KYF in the cube that is in DOC Currency to the currency of the comp code.
I am trying to do this in my update rules using translation keys and here's what I have done based on the SAP Net doc.
1. Assigned 0CURRENCY as an attribute on the BEx tab in the comp code info obj definition. So its should use this attribute to determine the currency of the comp code.
2. In my translaiton key I have defined for the target currency to use 0COMP_CODE and this is part of my comm structure.
When I run the update however I get a error that says invalid target currency - error 109. We did some update simulation from PSA and found that the target curr is blank although the comp code value is filled in . Master data is also populated for the comp code.
Have I missed any steps ? We are on 30b supp pack 10 .
Please provide any inputs in case you have come across this ASAP.
Thanks.
As an extension of the above it seems that you cannot do curr converison in update rules at the ODS level using translation keys . It does not give you that option as it does in the cube . Anybody come across this before ?
Thanks again.
ST
Answer:
I found the problem . It had to do with the activation of the data in the infoobject that was being used to get the dynamic target currency .
Answer:
ST if you are still reading this forum, I would really like to talk to you.
We are experiencing this in our QA environment and we go live this weekend and can not get to the resolution of the problem.
We are at Hot Pack10 just as you were and getting the error 109 message. please respond with some more detail if you can.
Answer:
Explain your problem in more detail and maybeI should be able to help you .
Its been almost 2 months since I finished my project but if I remember correctly we did not use translation keys in the update rules as we had some issues with the date for translation. So we ended up writing routines .
But if you prefer to use translation keys in your update rules the target currency can be dynamically determined from an attribute of an infoobject that is part of your comm structure. For ex : if 0COMP_CODE is in your comm structure you can define 0COMP_CODE as the infoobject to get the target currency . I don;t think COMP_CODE has to be necessarily part of your data target .
You have to maintain the currency infoobject on the BEx tab as an attribute for ex : as an currency attribute in 0COMP_CODE only if you are doing dynamic currency translation in BEx and in this case 0COMP_CODE has to be part of your cube . Here when you run a report the target currency is dynamically determined based on the value of the company code in your query by reading the currency attribute from the comp code master data .
Hope this helps or maybe confuses you even further. Currencies and Dates are always a big challenge to work with .
ST