Upgrade of GRC 5.2 to GRC AC 5.3

Hello,
During an upgrade of GRC AC 5.2 to GRC AC 5.3, when we uninstall GRC AC 5.2 and install GRC AC 5.3 on the same server,
1- Do we lose all existing configurations of GRC 5.2 eg. workflows, connectors, rule sets etc and will I lose existing request data?
"OR"
Will GRC 5.2 uninstall will keep all the previous data & configurations of GRC 5.2? intact?
2- I assume rule export/ import under utilities of rule architect from AC 5.2 to AC 5.3 will overwrite the existing ruleset?
3- I assume rule download/ upload from AC 5.2 to AC 5.3 will append the existing ruleset and will not overwrite it.
Please let me know, if my assumptions in (2) & (3) are right.
Thanks,
Haleem.
Edited by: abdul haleem on Apr 9, 2010 12:33 AM

Abdul,
Here is my response:
1- Do we lose all existing configurations of GRC 5.2 eg. workflows, connectors, rule sets etc and will I lose existing request data?
"OR"
Will GRC 5.2 uninstall will keep all the previous data & configurations of GRC 5.2? intact?
Everything will stay the way it is. You won't lose any data after the upgrade as the uninstallation does not allow you to remove data from the database.
2- I assume rule export/ import under utilities of rule architect from AC 5.2 to AC 5.3 will overwrite the existing ruleset?
That is correct. If you import new ruleset it will fully overwrite existing ruleset.
3- I assume rule download/ upload from AC 5.2 to AC 5.3 will append the existing ruleset and will not overwrite it.
There is not role download utility. You can upload fresh rules by uploading different different files via configuration -> rule upload.
Please let me know, if my assumptions in (2) & (3) are right.
Alpesh

Similar Messages

Upgrade to GRC AC 10 and Integration with BI

Hello,
I am running a study to integrate GRC Acces Control 5.3 and business warehouse 7.02 and should install it to production soon.
We also have an upgrade to GRC 10 in the pipe.
I understood with OSS note 1667517 that no business content is delivered with this latest GRC AC version (version 10.0)
When the GRC upgrade will be done, do you know if I will be able to load and use reports created/activated with GRC AC 5.3 ?
Thank you
Seb

Hi Jyoti,
When UNinstalling 5.2 have you uninstalled virsa~ccxsysdb.sda file.?????
As per the Upgrade guide we should not uninstall virsa~ccxsysdb.sda.
you need to redeploy the Database file named "virsa~ccxsysdb.sda" of CC 5.2 with the overwrite option in the SDM
Regards
Gangadhar
Edited by: gangadhar hm on Sep 18, 2009 12:21 PM
Edited by: gangadhar hm on Sep 18, 2009 2:17 PM

Which option is the best - Upgrade from GRC 5.3 to 10.1 or migration from GRC 5.3 to 10.1

Hi All,
One of my client is expecting to use GRC 10.1. Currently they have GRC 5.3 and want to upgrade to GRC 10.1
Can anybody give me benefits of both options - Upgrade vs Migration then it would be great ?
Thanks,
Aditi Shah

Hello Steve,
Migration you deploy Java component and extract data form 5.3 and import in 10.
still lots of work to be done like and implementation as there are pre-requisite.
second approach does not need to extract all data from 5.3 system(apart from Ruleset,if at all its required)
I never migrate workflows better to create new one identical and faster i believe .
Second approach is little time consuming but good from my point of view.
In java stack people normally go with 2 system landscape .
there has been client where in ABAP people go with 3 system landscape.
now where tricky consulting part play and which data to be imported where.
and few other points needed to be looked like when you use tools and import data.
you actually import all transaction data which contain all active and inactive
expired.
in you go with 2nd option you will have only valid data to start with.
Regards,
Prasant

Upgrade to GRC AC 5.3 , CC deployment issue

Hi
We are inthe process of upgrading from GRC 5.2 to 5.3.
I have undeployed CC,FF, AE SCA's as recommended in the installation/upgrade guide and deployed new SCA's , all the files for FF, AE, RE are depolyed successfully except VIRCC_0.SCA keeps throwing errors. Any suggestions ? Here's the info from logs
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: <<< Analyze table VIRSA_CC_XSYSGRP >>>*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: <<< Analyze table VIRSA_CC_XSYSGRP >>>*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: predefined action is: >>>null<<<*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: predefined action is: >>>null<<<*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: No action required for table*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: No action required for table*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Runtime XML of VIRSA_CC_XSYSGRP successfully written*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Runtime XML of VIRSA_CC_XSYSGRP successfully written*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Runtime XML of VIRSA_CC_XSYSGRP successfully written*
*Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Runtime XML of VIRSA_CC_XSYSGRP successfully written*
***Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Analysis and adjustment of tables finished with errors*++
***Sep 17, 2009 10:35:02... Info: 10:35:02 2009-09-17 dbs-Info: Analysis and adjustment of tables finished with errors*++
*Sep 17, 2009 10:35:02... Error: Aborted: development component 'grc/ccxsysdb'/'sap.com'/'MAIN_AC53VAL_C'/'2650256'/'0', grouped by software component 'VIRCC'/'sap.com'/'MAIN_AC53VAL_C'/'1000.530.700.5.0.20081121095959''/'0':*
*No further description found.*
*Sep 17, 2009 10:35:02... Info: Starting to save the repository*
*Sep 17, 2009 10:35:03... Info: Finished saving the repository for 453 ms.*
*Sep 17, 2009 10:35:10... Info: Starting: Initial deployment: Selected software component 'VIRCC'/'sap.com'/'MAIN_AC53VAL_C'/'1000.530.700.5.0.20081121095959''/'0' will be deployed.*
*Sep 17, 2009 10:35:10... Error: Aborted: software component 'VIRCC'/'sap.com'/'MAIN_AC53VAL_C'/'1000.530.700.5.0.20081121095959''/'0':*
*Failed deployment of SDAs:*
*development component 'grc/ccxsysdb'/'sap.com'/'MAIN_AC53VAL_C'/'2650256'/'0' : aborted*
**Edited by: Jyoti Tyagi on Sep 17, 2009 8:13 PM**
Edited by: Jyoti Tyagi on Sep 17, 2009 8:16 PM
Edited by: Jyoti Tyagi on Sep 17, 2009 8:18 PM

Hi Jyoti,
When UNinstalling 5.2 have you uninstalled virsa~ccxsysdb.sda file.?????
As per the Upgrade guide we should not uninstall virsa~ccxsysdb.sda.
you need to redeploy the Database file named "virsa~ccxsysdb.sda" of CC 5.2 with the overwrite option in the SDM
Regards
Gangadhar
Edited by: gangadhar hm on Sep 18, 2009 12:21 PM
Edited by: gangadhar hm on Sep 18, 2009 2:17 PM

Effort to upgrade from GRC 5.2 to GRC 5.3

Hi,
We're looking to begin an upgrade of GRC 5.2 to GRC 5.3 and I've been going through all of the upgrade documentation and the associated notes for the current GRC 5.3 version. I was wondering for those that have done this upgrade if you can tell me approximately how many hours it took to not only install but test and deploy. I'm starting to build the project plan and want to know what I'm going to be looking at from an effort standpoint.
Any help that can be provided is appreciated.
Thanks!
Elizabeth

Elizabeth,
It does not take much time to install and deploy, since you are only replacing the front-end application. If you have an experienced Basis person, then it should not take more than 1 day to install, and maybe 2 days for post-installation.
Breakdown (assumes best-case scenarios):
Replace 5.2 with 5.3 front-end: 1 day
Upgrade to 5.3 RTA's in target systems: 1 day
Post-install configuration: 2 days
Testing: will depend on customer and what functionalities they are using and want to use in AC5.3
AC5.3 possesses new functionality, like UAR/SoD Review. So if that needs to be configured, you will have to build that into your project plan. In addition, you will need to build your testing scenarios and that will depend on your customer/client.
Ankur
SAP GRC RIG

Steps for upgrade to GRC 5.3

HI Folks,
I would really appreciate if I can know the steps for GRC upgarde to 5.3 from 5.2. The only components we use are CC and firefighter.
Is there any need to backup anything before the upgrade except the database and filesystem?
Regards,

Hi,
Check this upgrade guide at service marketplace, might be useful to you-
https://websmp103.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718186&
Goto SAP GRC Access Control 5.3-Upgrade Guide - SAP GRC Access Control 5.3
Regards,
Sabita

GRC 10.0 Upgrade & Functionality - 4 Questions

Hi Forum,
We are currently evaluating upgrading to GRC 10.0 from 5.3 and also start using SPM. Currently, we only use RAR. Can you guys help me with following 4 questions?
1. We have a number of different firefighter roles used by different teams and approved by different approvers. Can we have separate requester and approver lists for different firefighter accounts in GRC 10.0 SPM?
2. Do we have to implement GRC 10.0 Portals for SPM approval workflow?
3. We have license for all GRC modules. Does this also include Continuous Transaction Monitoring with Oversight or is a separate license required for this?
4. Does GRC 10.0 support automatic archiving of AC-RAR SoD reports? - When I start a weekly background job, can it be automatically archived into an archive folder of my desigantion?
Thanks so much for your input.
Joerg

hi Joerg
1.Yes, you can have different approvers per firefighter ID and have the requestors assigned to different ones as well.
2.You do not need to install portal but you will need to facilitate some access to the front end components through activating the NWBC Netweaver Business client or using a web browser to view the internet facing services in SICF.
3. I don't believe that your GRC license automatically entitles you to the Oversight product suite as they are still separately marketed, however the GRC Process Controls and Risk Management modules can be included if you have a full enterprise GRC license from SAP.
4. You could certainly manage to archive the reports using standard SAP ABAP functionality (SARA). However, If you mean the standard Batch risk Analysis, then I think you'll find that the offline content is overwritten with the latest and only the summary data is retained in the historical data tables for trend analysis. From an audit perspective, historical detailed data is not partuicularly useful since they are more interested in current exposure. Auto archiving of the SPM logs is available as standard.
Regards,
Simon

Why upgrade from Compliance Calibrator to GRC?

Hello Experts- My company has yet to implement GRC 5.3. We already utilize SAP Compliance Calibrator by Virsa Systems 4.0, which works fine, so what would be the benefit of upgrading to GRC? Is it really necessary? Is it just to stay current? Also, is it true that GRC will be moving from Java back to an ABAP stack? If so, when is the new ABAP version of GRC set to be available?
Thanks for your advice and opinions.

Regarding the upgrade from 4.0 to 5.3 I concur with Alpesh and Varun.
Regarding the upgrade to 10.0, current plans are for Ramp-up to be available in December 2010 with general release scheduled for mid 2011.
According to the latest material from SAP, they are only supporting a migration path as follows:
4.0 -->5.3 --> 10.0
There is no supported upgrade path from 4.0 directly to 10.0.
It should be noted that it is a significant change in architecture and therefore not a simple migration path. SAP are recommending an upgrade to 5.3 followed by a migration to 10.0 for the technical side of things.
5.3 does still have some significant advantages over 4.0 and therefore is still an option. owever, if you wish to register your interest, SAP are seeking ramp up customers so I would suggest you contact your Consultants or account management within SAP to discuss the options if you are considering it.
Simon

Problem with RFC for Risk Terminator - GRC 5.2 SP12

We are having a problem with the RFC connection for Risk Terminator in one of our SAP environments. It is working in our 'DV3' environment, but not in our 'RT3' environment. Everything is set up just the same in both environments and all SAP Adaptors show green.
This was working in RT3 when we first upgraded to GRC 5.2 last November, but it now gives me an error when I do an update with PFCG and it calls RT. The error message and our Basis support group both say the RFC needs to be 'registered', but our SAP Support contact during our upgrade said it does not, and I can't find any documentation that says this is required also. Plus it was working before even though it was unregistered.
What is causing this problem and how do I resolve it?
Also, if these RFCs do not have to be registered, is there some documentation that states this that I can show to our Basis group?
Thanks.

What about the question of the RFC needing to be registered? This is the solution our Basis group thinks is required, so it will be hard to get them to do anything else until this issue has been addressed.
Thanks.

GRC CUP Error creating request. Approver not found

Hi,
We just upgrade from GRC CUP 14 to GRC CUP 15.6 support pack.I already performed post upgrade steps and when i try to create a request i am getting approver not found.i didnot change workflow.In stage for role approver we have approver determinator "role".
system log report
com.virsa.ae.workflow.NoApproverFoundException: No approvers found for req no : 493, for reqPathId, 662, for path, PROD_APPRV_PATH and approver determinator : Role
     at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1469)
     at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.handleWFForNewPath(WorkFlowRequestCreateHelper.java:278)
     at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.createNewWorkflow(WorkFlowRequestCreateHelper.java:167)
     at com.virsa.ae.workflow.bo.WorkFlowBO.saveNewWorkflow(WorkFlowBO.java:120)
     at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:579)
     at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:381)
     at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.createRequestHandler(EUCreateRequestAction.java:135)
     at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.execute(EUCreateRequestAction.java:68)
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please let me know solution ASAP.This is high priority.
Thanks
Yakoob.

It looked like some old request stuck in DB.But, not sure about it.I tried by changing the number ranges in configuration by giving the current request number in "from number",but it didn't work.
This is strange some time it gives "error creating request: path not found." and once this error gone then "error creating request : approver not found".
To avoid this i created one more stage by custom approver determinator with application attribute and approver assiged.This stage, i assigned before role approver stage then it worked,Request get created and request get provisioned.
i don't understand why it's not working,if i assigned role approver stage first in a path of workflow.role approver (approver determinator:"role" standard one, "approver" gets from configuration:roles:create role:role approver OR upload from role import).
Please help
Thanks
Yakoob.

GRC 10.1 Simplified Access Request and Remediation View Issues

Hi Everyone,
We recently upgraded our GRC 10.0 environment to 10.1, SP 5 and am having the following issues--has anyone else also experienced?
In the simplified access request form, it keeps telling me to enter a “valid user ID”—even though the ID is valid and works fine in the normal access request screen. Also tried to search and then select the ID in this field with the same error.
In the SoD Remediation view, I keep getting “No Data Found”, even though in the detail view, there are risks the same request:
I’ve checked the following things:
I’ve used IE 8, IE 9, FireFox, Chrome, and the NWBC to see if any of these fix the issue
I double checked the 10.1 “upgrade guide” to make sure Gateway configurations are correct
It looks like we are on the latest support packs:
Any help on this would be greatly appreciated!
Thanks,
Brett

Hi Brett,
For Remediation issue you can check the below thread.
http://scn.sap.com/thread/3574790
Regards,
Neeraj

SAP Workflow and GRC 10.1 Workflow

Hi all,
We are in the midst of upgrading our GRC system up to 10.1 and some questions are coming up about the workflows. In short are GRC workflows and SAP workflows the "same thing", i.e. if someone outside of the upgrade project were to learn how to create/maintain workflows within GRC 10.1 would they be able to turn around and run the same transactions within an ECC 6.0 environment and create SAP Business workflows? From what I have seen so far in my searching is that, they have the same basic principle but very different implementation/maintenance.
Any documentation that you are aware of from SAP showing this would be helpful as well.
Thanks

The basic mechanism is the same, but the GRC workflows are more fixed (they leave less room for the workflow to be changed) have build in screens, and relay on the BRF engine to determine approvers etc.
Workflows in the ECC give you a lot more room for implanting the workflow however you wish (use a decision task, asynchronous tasks, develop your own custom approval screen etc.) and some time required you to implement changes to the workflow object (set a user status, release a document etc.) and don't usually use the BRF.
So I would have to say that the answer is no, someone who learned how to implement the GRC workflows will not be able to turn around and immediately create workflows in the ECC.

Does anyone have "Best Practices" to move GRC 5.2 to its own environment?

Hello,
Has anyone else put the GRC applications on a shared server and then decided to move them? We have been running Access Enforcer, & Compliance Calibrator on a box shared with Solution Manager. We now have permission to put it on a separate server. We have been looking for "Best Practices" for making this type of change. If you have experience doing these would you be willing to share knowledge?
Also, what little we have advise or knowledge we have found indicates "there is no way to do a J2EE system copy from a dual-stack system into a J2EE-only system." Does anyone know if this is true?
We want to move the GRC 5.2 to its own environment before we upgrade to GRC 5.3...

Hi Renee,
There is not best practice or methdology to move GRC AC 5.2 easily. AC 5.3 has import/export functionality in place to move most of the data from one environment to another. I will recommend you to upgrade to AC 5.3 and then move everything to new server.
Another way is to ask your BASIS person and see if he can backup and restore DB on another server.
there is no way to do a J2EE system copy from a dual-stack system into a J2EE-only system." Does anyone know if this is true? This is true.
Regards,
Alpesh

For GRC 5.3 can I use the SAP GRC 5.2 rule set

We are going for an upgrade to GRC 5.3, I have a small concern here....
Can I use the same ruleset what I used in GRC 5.2 to SAP GRC5.3 ...?
because when I checked ruleset at permission level in GRC 5.2 it displays first object of an action from one function conflicting with first object of an action from another function, where as in GRC 5.3 it displays all objects of an action from one function vs all objects of an action from another function....
How will it impact analysis in GRC 5.3 with old rule set...?
appreciate your response & thanks in advance.

Hi,
Here you will find the documentation to get Upgrade/Configuration Guides.
[https://websmp103.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718172&]
SAP BusinessObjects Governance --> Access Control ---> SAP GRC Access Control 5.3
There you will find a Upgrade guideline.
Cheers,
Martin

GRC Unlock Account - BUG ?

Hi All,
This is regarding an issue we found in our GRC system.
A UserID has been locked in ECC system sometime back.
For example: Valid From - 01-Jan-2014 and Valid To - 05-Jan-2014
UserID is in locked state and validity dates are as mentioned above.
Now User wants this account to be unlocked and raising a GRC Unlock Request.
User is selecting the system during Unlock Account creation and system is added with validity dates as shown below.
Valid From - Today's date
Valid To - 05-Jan-2014 [Existing UserID Valid To date in ECC system]
According to me validity dates for the system should be added as shown below
Valid From - Today's date
Valid To - 31.12.9999
Is this a bug? or Is this the standard behaviour? I hope this would be issue for most of the customers.
Please provide your suggestions on this.
Regards,
Madhu.

Hi Alessandro and Colleen,
Thanks for your inputs.
Actually the issue is, the same unlock process is working with VALID TO date as 31.12.9999 in GRC 5.3.
Now after upgrading to GRC 10.0, this was changed. Hence users are raising it as a concern.
I understand that system cannot recognize VALID TO date as it can be any date depending on customer requirement, but since it was working in 5.3 client is expecting the same in 10.0
While raising termination requests they are updating valid To date to the same day and submitting the requests.
For the terminated users, later if they need access again, Unlock account request is being raised and here they are not selecting any VALID TO date as it was updating with 31.12.9999 Valid To date in GRC 5.3 and now it is updating with VALID TO date based on SU01 record.
We raised this to SAP and I assume that this could be desired behavior as mentioned by you. Once SAP also confirms we will include this in our training material to make users used to it.
If there was any update from SAP will keep you posted.
Regards,
Madhu.

Upgrade of GRC 5.2 to GRC AC 5.3

Similar Messages

Maybe you are looking for