cancel
Showing results for 
Search instead for 
Did you mean: 

Deleting the system

Former Member
0 Kudos

Compliance Calibrator 5.2 issue:

We have development system ECC 6 system D01 and it is connected to the GRC . Now we have done sod analysis and USER sync up.

I have been assigned to remove that system and then do P01, but when i go there to delete the system it says cannot do it , since there is data for the connection.

How i can clean the system , i mean the data from the system.

Second question for multiple systems ,i mean D01 , Q01 , P01 , which are connected to the system , will GLOBAL ruleset will work on all of them ? I saw somewhere the function risk is tied to the system also ??

Is anybody running this for multiple systems i mean 46C , ECC , BW system and how does the ruleset look like.

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

i there a script to remove the users , since they don't have a system attached and when i switch connectors . they are changed , well the script to clean the tables is very useful on lower level, i will assume the users table is not included in it, so anyone know the user tables.

Former Member
0 Kudos

hi christian,

your question "i have connected the P01 system also , with D01 everything is fine , but the ruleset still only works for D01 only , When i check functions there is still the D01 system tied to it . And risks has global in it.

Do i have to change anything on the system , since the SOD report does not bring anything for P01."

ANSWER

-


As somebody correctly pointed out, you can use the Export rules functionality to effectuate renamed connectors. Example; you had PRD, now you have PRO

However, if you have an extra connector, than you need to add information in your functions. You had only D01 tied to it, and now you would also need P01. Well, in that case you can either go ahead manually changing the functions, but that is of course a very time-consuming activity. Another way is to download your rule set through the same Export rule set functionality and start manipulating this text file.

A nice trick is to copy-paste all VIRSA_CC_FUNCACT entries in one XLS sheet and all VIRSA_CC_FUNCPRM in a second separate sheet. Thanks to the tabs in the text files, you will paste in separate columns. Than, you are free to copy-paste the already available entries for D01 and replace D01 with P01 in the target. Then, sort your columns on function - system. Finally, very simply insert your end results in a the ruleset.txt and upload-generate in SAP GRC.

good luck !

sam

Former Member
0 Kudos

There is a sql script available from support that will allow you to delete your data from GRC.

Former Member
0 Kudos

HI you use export and import functionality in rule architect tab of the CC...

First export the rules.... in source system give the name of new system where u want the rules to be....

than click on get rules button....After some time you will get pop up .... first open that txt file and than save in you local system...

Now Impor the file by import option on rule archite.... Just give the location of the txt file....

Once the job is done your rules will move to new system

Parvee

former_member196034
Participant
0 Kudos

rem This is for Temporary Rule fix and DONOT use it in future

rem Contact VIRSA Support for any issue

rem Pass only the system that are required to delete

SPOOL C:\DATA_CLEANUP.TXT

prompt Delete system specific rules in Action Rule Table

delete from <SCHEMA>.VIRSA_CC_ACTRULE

where vsyskey = '&1';

prompt Delete all System specific Alert details

delete from <SCHEMA>.VIRSA_CC_ALLASTRUN

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_ALLISTDTL

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_ALTCDLOG

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_AUTHMAP

where vsyskey = '&1';

prompt Delete system specific rules in Critical Action Rule Table

delete from <SCHEMA>.virsa_cc_cract

where vsyskey = '&1';

delete from <SCHEMA>.virsa_cc_cractt

where vsyskey = '&1';

prompt Delete system specific rules in Critical Permission Rule Table

delete from <SCHEMA>.virsa_cc_crprm

where vsyskey = '&1';

prompt Delete system specific rules in Critical Profile Table

delete from <SCHEMA>.virsa_cc_crprof

where vsyskey = '&1';

delete from <SCHEMA>.virsa_cc_crproft

where vsyskey = '&1';

prompt Delete system specific rules in Critical Role Table

delete from <SCHEMA>.virsa_cc_crrole

where vsyskey = '&1';

delete from <SCHEMA>.virsa_cc_crrolet

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_dataexd

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_fldmap

where vsyskey = '&1';

prompt Delete system specific rules in Function Action Table

delete from <SCHEMA>.virsa_cc_funcact

where vsyskey = '&1';

prompt Delete system specific rules in Function Permission Table

delete from <SCHEMA>.virsa_cc_funcprm

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_funcsys

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_lastrun

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_lsysgrp

where vsyskey = '&1';

prompt Delete system specific rules in Org User Mapping Table

delete from <SCHEMA>.virsa_cc_orgusers

where vsyskey = '&1';

prompt Delete system specific rules in Permission Rule Table

delete from <SCHEMA>.virsa_cc_prmrule

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_supp_det

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_supp_hdr

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_supp_text

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_syscract

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_syshmap

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_sysrule

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_syssapobj

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_sysusr

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_textkey

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_usrmap

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_xsrulemap

where vsyskey = '&1';

delete from <SCHEMA>.VIRSA_CC_xsysgrp

where vsyskey = '&1';

prompt Delete System details

delete from <SCHEMA>.virsa_cc_system

where vsyskey = '&1';

delete from <SCHEMA>.virsa_cc_systemc

where vsyskey = '&1';

delete from <SCHEMA>.virsa_cc_systemt

where vsyskey = '&1';

commit;

prompt Truncating VIRSA_CC_GENOBJ Table

truncate table <SCHEMA>.virsa_cc_genobj DROP STORAGE;

prompt Truncating VIRSA_CC_GENOBJT Table

truncate table <SCHEMA>.virsa_cc_genobj DROP STORAGE;

prompt Truncating VIRSA_CC_GENUSR Table

truncate table <SCHEMA>.virsa_cc_genusr DROP STORAGE;

prompt Truncating VIRSA_CC_GENACT Table

truncate table <SCHEMA>.virsa_cc_genact DROP STORAGE;

prompt Truncating VIRSA_CC_GENPRM Table

truncate table <SCHEMA>.virsa_cc_genprm DROP STORAGE;

prompt Truncating VIRSA_CC_GPRMLIST Table

truncate table <SCHEMA>.virsa_cc_genobj DROP STORAGE;

prompt Truncating VIRSA_CC_SYSUSR Table

truncate table <SCHEMA>.virsa_cc_sysusr DROP STORAGE;

prompt Truncating VIRSA_CC_ACTVL Table

truncate table <SCHEMA>.virsa_cc_ACTVL DROP STORAGE;

prompt Truncating VIRSA_CC_PRMVL Table

truncate table <SCHEMA>.virsa_cc_PRMVL DROP STORAGE;

prompt Truncating VIRSA_CC_CRACTVL Table

truncate table <SCHEMA>.virsa_cc_CRACTVL DROP STORAGE;

prompt Truncating VIRSA_CC_CRPRMVL Table

truncate table <SCHEMA>.virsa_cc_CRPRMVL DROP STORAGE;

prompt Truncating VIRSA_CC_ROLEVL Table

truncate table <SCHEMA>.virsa_cc_ROLEVL DROP STORAGE;

prompt Truncating VIRSA_CC_CRROLEVL Table

truncate table <SCHEMA>.virsa_cc_CRROLEVL DROP STORAGE;

prompt Truncating Management Tables

truncate table <SCHEMA>.virsa_cc_MGALERTS DROP STORAGE;

truncate table <SCHEMA>.virsa_cc_MGCRTR DROP STORAGE;

truncate table <SCHEMA>.virsa_cc_MGMTBU DROP STORAGE;

truncate table <SCHEMA>.virsa_cc_MGMTTOT DROP STORAGE;

truncate table <SCHEMA>.virsa_cc_MGRISKD DROP STORAGE;

truncate table <SCHEMA>.virsa_cc_MGRISKS DROP STORAGE;

SPOOL OFF

koehntopp
Product and Topic Expert
Product and Topic Expert
0 Kudos

I would like to advise you to open a support message before you start messing around with scripts. They may be different by DB or OS.

Support will be able to provide you with the suitable script for your installation, which you can then run directly in Risk Analysis and Remediation.

former_member184114
Active Contributor
0 Kudos

Hi,

Yes its quite apparent that, when a system has associated data, you cannot delete. But on the other hand, instead of deleting the system, you can define new connection to P01 and go ahead. It doesnt matter.

Kindly reward points if helpful

Regards,

FAisal

achristian17
Participant
0 Kudos

Hi Navdeep,

I'm not sure why you're looking to delete this info.

Answer to your 2nd question is yes. You could run the risk analysis specific to any one of the system or all of the system with global ruleset. 46C & ECC yes but check for the compatibility of your back-end RTA & front-end system(5.2 okay). For BW there are no pre--defined ruleset and you may need to define your own ruleset and you've to generate that.

Regards,

Asok

Former Member
0 Kudos

hi christian,

i have connected the P01 system also , with D01 everything is fine , but the ruleset still only works for D01 only , When i check functions there is still the D01 system tied to it . And risks has global in it.

Do i have to change anything on the system , since the SOD report does not bring anything for P01.

regds

navdeep

Former Member
0 Kudos

Another question is Interface Controller does not exist for Component Instance VirsaXSR3_01 error message comes when i have connected the SRM system to it, this CC only do i have to load the VIRSANHR 5.2 addon abap component on the SRM system , i mean is this a requrement for all the component systems

regds

navdeep

Former Member
0 Kudos

Hello Navdeep,

Please review the documentation related to uploading rule set. You have to define you connectors before you upload the rules. There are also steps you have to perform for each system before you generate the rule set. Review this CC config guide and you can call me if you want to discuss.

Regards,

Harinder