4 weeks ago
Hello everyone,
Maybe I'm doing something wrong, but I am at a total loss currently. I have a TEST space and a PROD space and a SAP space. In the SAP space I have my currency conversion objects, which I have shared with both the TEST and PROD space using the currency conversion views creator built into SAP Datasphere. I have also created the currency conversion views from the SAP space in the TEST space and put them in a package that I import in the PROD space.
In the screenshots below you can see how I shared the currency conversion tables with the other space
And this is how I created the views from the SAP space in the TEST space.
Everything works as it should in the TEST space, but when I import all of my packages into the PROD space, I get a insufficient privilege error. I can fix this by basically deleting the currency conversion columns and creating them again, but if I import the package again because of changes in the TEST space, I have to do this all over again. So this isn't a long term solution.
Does anyone maybe know what I am doing wrong or how I can make sure the currency conversion doesnt break when I transport objects between spaces.
Request clarification before answering.
It is strange.
When creating currency conversion views in DEV and PRD (shared from SAP_CONTENT), both spaces have their own objects, like “SAP.CURRENCY.VIEW.TCURX”, etc.
Currency conversions created in DEV should use the DEV views (accessing to SAP_CONTENT tables), and when exported to PRD, they should access the ones in PRD (accessing to SAP_CONTENT tables), without problems because they use the same technical name in DEV and PRD.
If that is not the case, and you get the permissions failure, I would say it is because somehow from PRD it is trying to access the DEV currency conversion views, as if it “remembers” something like "DEV". "SAP.CURRENCY.VIEW.TCURX" instead of just ”SAP.CURRENCY.VIEW.TCURX" (withouth the space)
As a workaround, you could share those views from DEV to PRD to make that call work, but it doesn't seem very robust.
Another option, if you are using currency conversion in the graphical views, would be to do them with the CURRENCY_CONVERSION() function instead of the “wizard”, that should work like any other function and referencing the tables as “SAP.CURRENCY.VIEW.TCURX” should be transparent and work in PRD as well.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @TheFizzlee
You're getting the "insufficient privilege" error in PROD because the currency conversion tables (TCUR) weren’t shared* from the SAP space to the PROD space, even though they were shared to TEST.
How to fix.
This ensures PROD has access to the TCUR tables behind the views; otherwise, imports will work, but runtime access will fail.
Let me know if it works
With regards
Chuma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Thanks for the response.
I've actually tried this but it didn't fix the issue. Also tried unsharing and sharing again but I keep running into this problem. Also tried both transporting the views from TEST to PROD and just creating the views again in PROD but both seem to give the same problem.
User | Count |
---|---|
41 | |
15 | |
10 | |
9 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.