BPC10.0 writing to secured dimension with other user using BADI

[former_member209263]

Hi all,

We have a business requirement where a user who belongs to Division A, needs to run a calculation (BADI) which writes data to other Divisions (which he does not have write access to).

Previously in BPC7.5 we were able to achieve this by using class ZUJR_IMPERSONATE, as per how to guide

http://scn.sap.com/docs/DOC-4234

However in BPC10.0 this class no longer works, and I can't find a corresponding how to guide for BPC10.0.

Does anyone know if there is a new version of ZUJR_IMPERSONATE that works on BPC10.0?

Or has anyone managed to adapt this class to work in BPC10.0?

Thanks in advance.

Regards,

Carlton

[former_member186338 · Accepted solution]

Hi Carlton,

First of all "needs to run a calculation (BADI) which writes data to other Divisions (which he does not have write access to)." - there is some logical issue in this statement Actually user is able to change data (with the help of badi...). May be it's better to properly set a security?

If you still want to run some code on behalf of another user - then:

It's for 7.5 but applicable for 10...

Vadim

[former_member209263 · Accepted solution]

Hi Vadim,

Thanks for your response.

The background of the business requirement is that each user is only supposed to be able to budget for and report on their own divisions. This has been achieved by securing the division dimension, and achieves 90% of the requirement.

However there is also a business requirement whereby each division can "transfer" resource costs to other divisions. For this we have written BADI code which writes "transfer" records against other divisions, so that these transferred costs are included when reporting the total budget of that other division.

So the challenge is to allow users to write to 9 accounts for their own division only, but also to write to 1 special "transfer" account for ALL divisions. Is this achievable using BPC10.0 security?

p.s. I've managed to adapt class zujr_impersonate so that it works with BPC10.0 interfaces, so problem solved.

Cheers,

Carlton