Compliance Calibrator for multiple SAP systems

Question

I was wondering if anyone could assist me with my query.  We are currently performing an implementation of Virsa CC for a client and have begun to configure a CC DEV system they have installed with their custom SoD rule set.  The DEV CC system (sitting on a stand alone NetWeaver box) is "connected" to four SAP systems (DEV, QA, HR DEV & HR QA).  When we are building "functions" (i.e. raise purchase orders) in CC it asks us to define a SAP system when we are entering the transaction codes.  We've been configuring the functions with SAP DEV as the system, however when we run the analysis of results we would like to get results from QA as well.  It appears that the risk analysis only works for the system that you have defined the functions in (i.e. we get results for users in DEV but not for users in QA).
My questions are as follows:
- Do you need to define all the systems you wish to run a risk analysis for within the function (i.e. function = Raise purchase orders. DEV ME21 & QA ME21)?
- If so, is there an easy way to convert our functions so that they point to QA as well (we've noticed that we can't edit the SAP system once the function is saved)?
- Is it possible to export the functions and then define the SAP system when importing them back into CC (we've noticed with the SAP delivered rule set that SAP DEV was automatically defaulted)?  This is particularly relevant as we would like to export the rules from the DEV CC system and import them to the PROD CC system without having to manually create the rule set again; and
- Is it possible to export the rules and manually change the SAP system reference and import them back into CC (i.e. do a "replace all" DEV to QA)?
Any help would be greatly appreciated.
Thanks,
Alexi

Answer 1

In order to perform what your are trying to do in CC 5.2, you will need to go to configuration and setup a logical system, such as SAP R/3 and define all the appropriate systems for the logical system.  Then, when modifying the functions, you will need to set the tcode (action) to the logical system defined, such as R/3 or APO, etc. 
The cross-system functionality only comes into play if you want to analyze the SOD where a conflict would occur if a user had access to one function in one system (for example - purchase order processing in APO) and a conflicting function in a different system (for example - Vendor Master in R/3). 
If you simply want to check who has violates a risk against multiple system - the logical system is the best way.  You can have an logical system by system type - R/3, BW, APO, SRM, etc.
To convert this over, you can export the rules and during the export you have to define the new system when exporting the file.  If that doesn't work, I'd just delete everything out, and use the upload files to reload the rules with the correct data.