cancel
Showing results for 
Search instead for 
Did you mean: 

Avoid Admins activating Logic files

Former Member
0 Kudos

Hello All,

We are on BPC MS 7.5 platform, we are having issues like logic files are activated without a proper track or .LGF and .LGX files are having different timestamp.

So, the questions, how can I avoid uses or admin team members from activating or creating logic files... they should be able to add/modify/process dimension members, but not logic files.

All our admin members are having all tasks profiles, I think segregating tasks profile to seperate tasks for a group of admin users will solve this problem.

Thanks

BI

Accepted Solutions (1)

Accepted Solutions (1)

former_member186498
Active Contributor
0 Kudos

Hi,

please remember that there is a specific link for BPC MS http://scn.sap.com/community/epm/planning-and-consolidations-for-microsoft.

If there are a lot of admins I will reduce them at all, if your script logics have issues also the other activities are at risk and the issue will be worst than this.

Answering to your question, script logic are in application but also add/modify/process dimension members are in the same application task so I don't think you can separate the profiles, if an admin has application task then it has the right to work on dimensions and scripts.

For more info see please the security guide https://websmp208.sap-ag.de/~sapidb/012002523100011012012009E

Kind regards

     Roberto

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Please refer to the security guide in the below link from help.sap:

https://websmp108.sap-ag.de/~sapidb/012002523100011012012009E

As per the guide, the dimension maintenance can be done by either primary or secondary admin. Whereas, the application maintenance (script logic maintenance) can be done by primary admin. If you dont want the user to be able to maintain the script logic, then you can remove him from the primary admin and put only in the secondary admin.

Alternatively, you can create a custom task profile for the user.

Hope this helps.