GRC 5.2 SP upgrade

Hi Guys,
I have GRC 5.2 SP3 available in our Sandbox. If I wish to upgrade it to SP9 (which is the latest) via SDM, can I just download SP9 (from SP3->SP9) and deploy it without going through the SP upgrade sequence...like from SP4->SP5->SP6->SP7->SP8-->SP9?
Thanks.
Raymond

Hi,
yes you can go directly to SP09 for all the Access Control tools on J2EE side. Each SP contains the whole software, it does not add up.
But be aware to undeploy the deployable packages first. This is described in the installation guide / SAP note 1022187.
The RTA on R/3 side must be installed the usual way (import SP01, 02, 03..... up to the current one).
Regards
Daniela

Similar Messages

Validador GRC SP17 não está funcionando corretamente para XML 3.10

Caros,
Recentemente subimos o SP17 no GRC (SAPK-90017INSLLNFE) e também implementamos as notas para nota versão do XML 3.10 no ERP (1933985 - NF-e new layout 3.10 e seus pré-requisitos).
O XML está sendo gerado corretamente, mas nos casos em que alguma informação não é preenchida corretamente e deveria parar no validador do GRC, isto não ocorre. Exemplo tag F_NRO (house number) vazia, não para no validador do GRC.
Antes do upgrade do support package e na versão XML 2.0, o validador funcionava corretamente.
Aparentemente as configurações de NF-e outboud na IMG do GRC estão corretas e as tabelas /XNFE/XMLVALID e /XNFE/NFEVALID estão preenchidas corretamente também.
Alguém está passando pelo mesmo problema?
Obrigada.

Oi Cristiane,
Qual status da NFe no monitor do GRC 3.10
http://<host>:<port>/sap/bc/webdynpro/xnfe/nfe_outb_monitor ?
Dei uma olhada no código da RFC /XNFE/OUTNFE_CREATE chamada pelo ERP para 3.10. Aparentemente somente a visão de CNPJ tem relevância para erro de validação quando o campo validação está preenchido.
(SPRO - Nota Fiscal Eletrônica - Saída - Atualizar resposta do sistema para nºs próprios ID fiscal)
Outro ponto que você pode avaliar e que tem relevância é a função /XNFE/GET_XMLVERSION que reflete as configurações:
SPRO - Nota Fiscal Eletrônica - Saída:
- NF-e: atualizar sistemas das autoridades conectados
- NF-e: atualizar versão dos tipos de mensagem
E que talvez o caminho lógico, seja o que está errado... o que tenho visto muito.
Veja se lhe ajuda na análise...
Obrigado,
Bruno

Install GRC AC 5.3 RTAl in a backend system. (VIRSA) up on VIRSA 400_700

Hi Supports,
I want to install GRC AC 5.3 RTAl in a backend system. (VIRSA)
Where we have below setups already. We have a NW 2004 server with GRC 5.3 Installed and SLD is configured. Now we need to install GRC AC 5.3 RTA in Backend systems, so that we connect the backend system with the GRC server (NW 2004).
The backend system has ECC6.0 + Oralce 10g in AIX 5.3. This system is upgraded from 4.6c to ECC 6.0 recently.
We have already VIRSA 400_700 release in this system. Now we need to install GRC AC 5.3 RTA upon this for configure newer version of VIRSA (GRC).
Now here my quaries ??
1) When we install GRC 5.3 RTA in this system then it over write the existing VIRSA 400_700 release or installed in separate ??
2) We plan to take hole system backup before the installation. Including this we need to take backup of the existing VIRSA 400_700 release. Then what are the things i need to take backup and how ?? (tables of VIRSA backup only how ??)
3)Any one have the RTA installation procedure please forward it ??
4) After installation how can i sure that install is success or not ?? how can i check ??
5) What are configuration settings for NW 2004 server and Backend system after installation require(Procedure) ??
And i request to the guys to post the procedures/process is best way to share knowledge global.
Advance thanks for your replies,
Thanks & Regards,
Jagadish

Hi
> 1) When we install GRC 5.3 RTA in this system then it over write the existing VIRSA 400_700 release or installed in separate ??
> 2) We plan to take hole system backup before the installation. Including this we need to take backup of the existing VIRSA 400_700 release. Then what are the things i need to take backup and how ?? (tables of VIRSA backup only how ??)
> 3)Any one have the RTA installation procedure please forward it ??
> 4) After installation how can i sure that install is success or not ?? how can i check ??
> 5) What are configuration settings for NW 2004 server and Backend system after installation require(Procedure) ??
For GRC 5.3 check below SAP note
1250521 GRC/Virsa Add-On Upgrade Best Practice
SAP Note 1006083 - Virsa Access Control Suite- STMS to SAINT Migration
Also check GRC upgrade guide.
Thanks
Sunny

Preconfigure GRC AC 5.3 Installation

Hello,
The GRC AC 5.3 Upgrade guide says the following:
8.1 Preconfigure the Installation
Preconfigure the installation by applying all the xml files in the Archive (SAR) file VIRACCNT00_0.sar that you downloaded earlier.
Based on the above, what does it mean by preconfigure install by applying xml files into SAR files?
How can we apply xml files into SAR file?
Thanks,
Haleem

You need to upload .xml files in ERM and CUP. Also, there will be a message file which needs to be uploaded to RAR. Go down and read more of the install and config guide. They will help you in understanding of all the .xml files.
Regards,
Alpesh

Compatible Portal Version for GRC 10

Hello GRC Experts,
We are upgrading GRC PC 3.0 to 10.0 and our Client is using Portal to access PC. We are also planning to upgrade Portal version 7.0 to 7.3. Please let us know which version of the Portal is compatible for GRC 10 (PC and AC will be upgraded to 10).
We are informed that Portal 7.3 is not compatible, kindly advise if there is a patch available to make Portal 7.3 compatible for GRC 10 (PC and AC) upgrade.
Thanks and regards
Babu.

Hi Babu,
As of now EP 7.02 is supported for integration with GRC 10. Please check the SAPnotes below for the intgration and compatiability details.
1) Note 1603438 - GRC AC 10.0 EP Plug-In (JAVA), supported NW versions
2) Note 1607279 - GRC 10.0 Enterprise Portal - Integration Scenarios
3) Note 1607232 - GRC 10.0 Enterprise Portal Configuration
BR,
Guru

5.3 upgrade delivered rules vs 5.2 rules

We recently upgraded to 5.3 and noticed there were delivered rules sent with the software. Are these rules different than the ones we used in 5.2 because I have role violations but no user violations and I can't figure this out....any advice?
Regards,
Greg

PROBLEM DESCRIPTION TO SAP: My 5.2 GRC AC system was upgraded to 5.3 in Oct 09. Since the upgrade, no user violations are showing/updating and I know for certain that the users have been assigned roles with conflicts. I would like to obtain a cleanup script to wipe the Business Process, Function, Function Authorization, Rule Set, and Risk rules so that I may reload them.
SAP RESPONSE: Unfortunately, at this time, we are unable to provide you scripts to perform the function you want. Doing direct table updates is not something that GRC is able to support at this time. I'm attaching a word document that provides you the table and field names for the application. Your Database Administrator and developers should be able to use this information to develope scripts to accomplish what you require.
MY RESPONSE: I have asked our DBA to look at the information you sent and he's informed me that he wouldn't know where to begin. Will this script work (script not attached).
SAP RESPONSE: I technically can't confirm that this will work. But the tables
did not change between 5.2 and 5.3.

Change in Access Control components on the Service Marketplace

Hello GRC community:
We would like to inform you that as of yesterday (5/30) the Access Control components for support messages/SAP Notes have been changed (they have actually been replaced so all messages/notes logged under the old component will be moved/replaced to the new).
The main 4 components are now:
New: GRC-SAC-ARA     Access Risk Management
Old: GRC-SAC-SCC          Risk Analysis & Remediation (formerly Compliance Calibrator)
New: GRC-SAC-ARQ     Access Request
Old: GRC-SAC-SAE          Compliant User Provisoning (formerly Virsa Access Enforcer)
New: GRC-SAC-EAM     Emergency Access Management
Old: GRC-SAC-SFF          Superuser Privilege Management (formerly Virsa Firefighter)
New: GRC-SAC-BRM     Business Role Management
Old: GRC-SAC-SRE          Enterprise Role Management (formerly Virsa Role Expert)
There are also NEW components specific to areas of functionality. If you are not sure of what component to log your message under, please use the main components above.
GRC-SAC-ADS          Directory Services
GRC-SAC-BI             Access Control BW
GRC-SAC-CONF       Configuration
GRC-SAC-DAS          Dashboard
GRC-SAC-REP          Repository
GRC-SAC-RPT          Reporting
GRC-SAC-UAR          User Access Review
GRC-SAC-UPG          Installation & Upgrade
GRC-SAC-WF           Workflow
Ramelyn Paredes
AGS Primary Support

Hello COmmunity,
To Summarise in Short: New features introduced to V10.0 : GRC 10.0 is ABAP based, so extraction of data from users is fast & analysis as well.
As usual, the names for the Access control tool has been changed
A. Access Risk Analysis (RAR)
1. USOBT & object information will be automatically updated with GRC rather than manual upload (earlier version)
2. Mass Users can be imported from .CSV file for risk analysis, Role analysis etc.,
3. Variant creation / reuse for any report analysis
4. Option of having multiple rule sets & simulating users across multiple rule sets at same time
5. Risk analysis for CUA, Composite roles
6. Mitigation by system, risk id, mass mitigation for users, audit trail etc.,
7. Risk analysis for HR objects
B. Emergency Access Management (SPM)
1. Mass reporting for all FF users, Ids, Executions
2. Centrally maintained for all systems rather than individual ERPs.
C. User Access Management (CUP)
1. Customizable Access request forms
2. HR based role assignment for position, org unit
3. IDM integration using GRC Web services
D. Business Role Management (ERM)
1. Concept of Business role mapping for Technical roles.
2. Audit Trails & PFCG Change history.
Finally, the look, reporting format has been changed to provide additional information for analysis.
More important - GRC V5.3 support is till 2015 & SAP has planned to push the customers to upgrade to 10.0. Eventually SAP is also planning to release GRC 11.0 by mid next year. So we have to wait & watch the show

SAP GRC NF-e 10.0 - Problema durante Upgrade (mensagem /XNFE/APP 011)

Boa tarde a todos!
Realizamos o "Upgrade" do SAP GRC NF-e da versão 1.0 para a versão 10.0 (SLL-NFE 900, nível 0008) e estamos convivendo com um problema em uma mensagem XML do PI.
Na transação SXMB_MONI, monitor de mensagens processadas, ao filtrar por mensagens com SELSTAT = 017 Application Error - Manual Restart Possible, encontramos problemas em mensagens do seguinte tipo:
Sender: BATCH_BatchProcess_006
Receiver: CLNT100TND (Mandante 100 do Sistema TND)
Receiver Interface Namespace: http://sap.com/xi/NFE/006
Receiver Interface: BATCH_nfeRecepcaoLoteResponse_IB
Para estes, quando vou até o detalhe da mensagem e seleciono "Call Inbound Proxy" (com status vermelho), em "Payloads", vejo o erro "Não existe ID de lote 000000000000000".
Pelo que vi na tabela T100, a mensagem se refere ao código /XNFE/APP, número 011.
Por que será que está acontecendo este erro? Alguém já vivenciou esta situação antes?
P.S.: Já abri chamado na SAP e eles encaminharam o problema para a SAP Alemanha...
Obrigado,
Daniel

Bom dia Fernando (que bom te encontrar aqui também :-)!
Então, o Denny da SAP Alemanha me retornou dizendo que temos que instalar o XI Content SLL-NFE 10.0 e criar novamente os cenários da NF-e.
Eu estou entrando em contato com o nosso Basis que fica em Lima para ver se é possível que ele instale este componente, para que eu crie novamente os cenários da NF-e (extensão _900).
Após a recriação dos cenários, será que eu consigo reenviar as NF-e de teste novamente ou terei que estornar os documentos e fazer os processos novamente?
Obrigado pela ajuda!
Att.
Daniel

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

GRC 10 Upgrade:unable to install the add-on

Hi all,
Here I am facing another problem. I am basically working on SAP NW 7.3 ABAP. I have downloaded the
*51039481 SAP Access Control/SAP Process Control/SAP Risk Mgmt 10.0 * zip file from SMP. My backend system is SAP NW 7.0. For that, I have successfully installed add-on GRCPINW_V1000_700_INST -> K-103AGINGRCPINW.SAR.
Now I have to install the GRCFND_A_V1000_INST component. In the same download, I found this:
GRCFND_A_V1000_INST -> DATA ->K-V10AGINGRCFNDA.SAR. I presume that this component is suitable for SAP NW 7.3
i sucessfully uncarred this and placed in EPS/in folder. When I execute the SAINT in my GRC 10 system (SAP NW 7.3), it does not show me the add-on in the queue, therefore, I am unable to install this add-on.
I have upgraded the BASIS,ABAP,PI_BASIS and BW components to SP05.
Has any one has come across with such problem? Please share/help me on this.
Regards,
Faisal

Hi Faisal,
All of the pre-requisites and documentation points to the requirement for NW7.2 for the GRCFND_A component. I am not aware that it is compatible as yet with 7.3.
Sorry, not particularly helpful in resolving the issue but hopefully it clarifies what I suspect you already worked out.
Simon

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

GRC upgrade to 530_46C taking in account CUA

Hello Guru,
I am actually running GRC 400_46C and we need to upgrade it to 530_46C.
I have been able to find a nice upgrade documentation on service.sap.com; however, I still have a question for you.
I have a CUA installed on my landscape and I was wondering if there is any particular actions/procedures that I will need to follow before doing GRC 530 upgrade.
In addition, if you have any recommendations/comments regarding this upgrade please share them with me.
Thank you and have a great day.
Regards,
Mel

Hi Mel,
As far as I know, there are not additional settings required for CUA when you upgrade from 400_46C to 530_46C.
Alpesh

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 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

GRC Upgrade 4.7 to 5.3 - Rule Set Upload

Questions about upgrade from 4.7 to 5.3
Work in corporate conglomerate that consists of 4 independent business units each with own SOD rule set:
u2022How do we upload each independent set of rule sets so they can coexist within GRC 5.3?
u20224.7 mapping of files to 5.3 naming conventions u2013 see 4.7 rule set download below
CONFIG
CR_PROFS
CR_PROFST
CR_ROLES
CR_ROLEST
CR_TRANS
CR_TRANST
SOD_OBECT01
SOD_OBECT02
SOD_OBECT03
SOD_OBECTT
SOD_TCODE
SOD_TCODET

Alpesh
We are trying to upload our existing SOD 4.7 rules using the 5.3 the configuration tab u2013 rule upload. We are having difficulties associating old 4.7 SOD files names to the 5.3 SOD file names. Is this the correct location within 5.3 to associate a physical system to a specific set of SOD rule sets? If not could you please point us to correct location within 5.3.
Thanks

GRC 5.2 SP upgrade

Similar Messages

Maybe you are looking for