How to lock the scope of transactions in SOLAR02?

[Former Member]

We would like to lock down the transactions we have identified as being in scope in the Transaction tab in SOLAR02 and prevent anyone from entering new transactions. However, we do want to still allow the ability to run those transactions from SOLAR02. Additionally, we still need to retain the ability to add IMG objects on the Configuration tab. Thanks.

[Former Member · Accepted solution]

Hi Alan-

If your concern is to truly narrow the activity in Solution Manager to what is in scope for your project, you would want to restrict the IMG activities rather than the SAP transactions.

If you are using Solution Manager to drive what is being configured in your satellite systems, scope creep would only occur if the project team is able to get to IMG tables which are out of scope for your project. I don't think scope would be affected if non-relevant SAP transactions were maintained. I'm not sure there is a way to define the scope of SAP transactions anyway, but you can do so with the IMG entries when you create and generate the Project IMG.