Archiving of GRC 10.0

Hi All,
We are planning to implement GRC 10.0 in our landscape.Our Client needs to know how the archiving startegy of GRC 10.0.Needs your expert help on this.Need to know GRC 10.0 Archiving Strategy & Archiving objects implementation strategy.

Hi Sunny
What do you know about archiving of FF logs in GRC 10? I've searched high and low but unable to find anything.
Thanks in advance
Hussain

Similar Messages

  • Processo Standard de Archiving para GRC NFe Inbound

    Olá pessoal tudo bem?
        Mais uma vez gostaria de apoio para definir a melhor estratégia. Estou em um projeto de implementação do GRC NFe In com o SP16, o ambiente ainda não está pronto para customizações e testes porém algumas preocupações surgiram devido ao volume de XMLs recebidos. Dessa forma, gostaria de entender melhor a abrangência da solução Standard para archiving no GRC NFe in.
        Pelo que percebi, existem monitores específicos para administrar NFe e CTe arquivados (é necessario ativar o service na SICF)
    NF-e Fiscal Workplace for Archived NF-es
    CT-e Inbound Fiscal Workplace for Archived CT-es
        Porém tenho algumas dúvidas quanto ao funcionamento. Alguém já implementou essa funcionalidade, pode me ajudar a esclarecer o funcionamento?
    a) Pelos monitores acima, é possível visualizar e realizar o download dos documentos arquivados? Isso é importante em caso de auditoria...
    b) Hoje utilizamos o monitor "Download XML of NF-es / CT-es" para fazer download em massa de XMLs. Também será possível fazer o download em massa dos registros arquivados?
    c) As rotinas de arquivamento são as mesmas utilizadas no ECC? (SARA. SARI e etc).
    d) Existe alguma limitação para realizar download de documentos arquivados?
        Obrigado pela apoio....
    Abraço
    Edson

    Bom dia Edson,
    b) Sim ele também lê o archiving, inclusive se as estruturas do archiving não estiverem ativas ele fica dando uma mensagem para ativá-las (mesmo que não execute o archiving)
    c) Sim. Entra na SARA e procura pelos objetos de achiving com a mascara /XNFE/*
    d) A limitação é autorização e que o archiving esteja disponível para consulta.
    Atenciosamente, Fernando Da Rós

  • SAP GRC 5.3 CUP Archiving Requests

    All,
    I have a question about archiving and re reviewing requests after they are closed (approved/rejected).
    Let's say I create a request, my manager performs a risk analysis and SOD violations occur, but my manager approves the request. If at some point (say a year down the line) I want to review the request to see what the conflicts were would the request: a. still be in CUP to review and b. would it show the conflicts that were identified at the time.
    How would archiving play into this scenario as well.
    Unfortunately, I cannot test this in CUP as it is time sensitive, but I'm hoping someone has come across this before.
    Thanks,
    Kunal

    Hello Kunal,
    You can test this in a development by re-creating the scenario and archiving the completed request. The length of time archived is not an issue.
    In answer, yes you can pull up the archived request information (provided that you did not delete the archive) and you can see what were the recorded SOD risks at the time. However, the request itself will not tell you the individual transactions that caused the conflicts and may no longer be accurate if the risks and business functions have changed in their content since the time of the request.
    This said, GRC AC seems to be changing in "leaps and bounds" with recent support packs... Who knows if the archiving process will change in the future.
    Best Regards, Dylan

  • Archive and Purge provisions in GRC suite

    Hi,
    I'm trying to understand the Archive and Purge options provided / offered by GRC suite but have very skeletal information. Can somebody help me on that front?
    Balaji K

    In a nutshell,purging is removal of data from a system or storage device with the intent that the data can not be reconstructed by any known technique. In GRC Suite purging has similar concept to purge incident stored after a long period of tie and storage (AACG). You can also purge snapshop or change tracking definitions in CCG. General rule of thumb, ensure you follow your company policies with regards to data archive and purging and access to these functionalities within the GRC Control Suite should be restricted.

  • Problemas para download do XML em massa no GRC NFe 10.0

    Boa tarde
    Fizemos o upgrade de versão do GRC 1.0 para 10.0 e entramos em Produção na segunda-feira, 19/02.
    Estamos tendo dificuldades para efetuar o dwonload em massa dos arquivos. Temos um programa Z que parou de funcionar e quando estamos indo pela opção do Menu
    WDY_APPLICATION - Download Archived XML nem todas as notas estão sendo exportadas
    Ex.: para um determinado CNPJ temos mais de 240 notas de saída aprovadas e só estamos conseguindo exportar 12 arquivos XML
    Alguém tem alguma idéia/dica para a solução?
    Temos que enviar os XMLs em atraso e fazendo o download individual está sendo inviável.
    Grata,
    Denise

    Olá Henrique
    Identificamos o problema através de debug da função /XNFE/OUTNFE_XML_MASS_DATA.
    O parâmetro de seleção está invertido. Se digitarmos o emissor no lugar do recebedor o programa funciona.
    É erro no standard. O curioso é que ninguém reportou esse erro. Não devem estar usando o programa de download em massa.
    De qualquer forma obrigada pela ajuda.
    Denise

  • Installation issue on GRC 7.2.3 on Linux with EBS 12.0.4

    I am following doc http://download.oracle.com/otn_hosted_doc/logicalapps/723Install_GrccSuite.pdf to install GRC. I am doing an installation on Linux and in the section where we are installing Concurrent manager server components.
    As per doc, I have to source the APPL_TOP and run ladbinstall.bin (I am running in GUI mode and not Silient)
    The following is the output.
    -bash-3.1$ ladbinstall.bin
    Preparing to install...
    Extracting the JRE from the installer archive...
    Unpacking the JRE...
    Extracting the installation resources from the installer archive...
    Configuring the installer for this system's environment...
    awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
    dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    /bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
    basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    Launching installer...
    grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    /tmp/install.dir.32554/Linux/resource/jre/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
    I thought that it is not able to find the libraries, so i updated the PATH where libraries are located. I still get the above error. Has anyone come accross this issue and would please share some light on it.
    Thanks.
    Edited by: user495493 on Jul 17, 2009 7:51 PM

    This pulls the value from the APPS Profile
         SQL> select FND_PROFILE.value('APEX_LAUNCHER') from dual ;
         FND_PROFILE.VALUE('APEX_LAUNCHER')
         http://our.group.site:7878
    But
    String l_launcher = ctx.getProfileStore().getProfile("APEX_LAUNCHER"); ------------- doesn't return http://our.group.site:7878
    l_launcher = l_launcher + "/apex/f?p=" + p_application + ":" + p_page;
    l_launcher = l_launcher + "::APPS:::" + p_item_names + ":" + p_item_values;
    if (ctx!=null) ctx.freeWebAppsContext();
    response.sendRedirect(l_launcher);
    Instead I get
    http://our.app.site:8030/OA_HTML/null/pls/apex/f?p=140:2::APPS::::
    Suppose to get
    http://our.group.site:7878/apex/f?p=140:2::APPS::::
    404 Not Found
    Resource /OA_HTML/null/pls/apex/f not found on this server

  • 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

  • Best SAP Security Practices Print,file,job schedule, archiving

    Hello All, i would like to know in your experience which will be the best practices for Security  for this list below:
    - Printer security (especially check printing)
    - File path security for export/import
    - Best Practice for Job Schedule and Spool file
    - Archiving process (I can't think of any specific to security, other than Security Audit Logs)
    Are there any special transactions/system settings/parameters that must be on place in order to hard SAP Systems?
    Do you have any documentation related?
    I mean for example Job, spool i think user must just only run heir own jobs,and se their own works for printing, is there a paremeter to athenticate Prints/user, etc.
    Please let me know your comments about those related issues.
    I appreciate your help.
    Thanks a lot.
    Ahmed

    Hi,
    PFCG_TIME_DEPENDENCY
    This is best to run once a day mostly after 12.01 am as it removes the roles which are invalid for current date. As role assignment is on date basis there is no advantage of running it hourly.
    /VIRSA/ZVFATBAK
    This is for GRC 5.3, and this job is to collect FFID logs from backend to GRC repository, so if you have frequent FFID usage you can schedule it hourly or for every 30 min too, if you have enough bandwidth in your server to get the latest log report. or else you can have it scheduled for twice a day too, so it is purely based on your need.
    Hope this helps.
    BR,
    Mangesh

  • Deleting roles from GRC AC CUP

    Hi
    We had GRC 5.3 installed with SP05. We have archived all our existing requests and are trying to delete some of the roles from CUP. However when trying to delete the role it is giving a message "Cannot delete because this is referenced by request". Is there something else which i need to take care of? Will application of latest support packs help in this situation?
    Appreciate your help regarding the same.
    Thank you.
    Anjan Pandey

    Hi Anajan,
    I feel some requests are still exist in GRC CUP for that particler role. Please follow the below steps and try to delete the Role  again.
    Go to  CUP configuration tab  > click on Request option under the workflow> choose deleting requests > next> then its asks to delete all requests and then choose Submit option.
    once you click on submit button, you will get the message all existing requests are deleted with Job id.
    finally go to the Roles and delete the required roles form the GRC CUP.
    Regards,
    Arjuna.

  • 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

  • Workflow inititator GRC u2013 CUP

    I need to cancel initiator from workflow of GRC CUP. When i try to delete initiator it says" Error deleting initiator. There are workflow paths associated with this initiator".When i try to deactiviate the path and try to cancel that path of workflow it says  "Error deleting workflow path. There are approximately 10 requests associated with this path".Also i cannot cancel the closed request.Is there anyway to delete it.

    Mouhed -
    If you are just trying to delete the initiator, then you can do this by changing the related path to be a 'Detour' and then removing the initiator.  That should take away the dependency that is preventing you from deleting the initiator.
    You cannot delete a workflow path that has requests associated with it.  However, you should be able to deactivate the path as long as there are no actively open requests associated with it.  If you are running into issues there with closed requests, you could use the 'Archive' functionality to take them out of the active queue.  That should take away the dependency on the workflow path and allow you to deactivate it.
    - Rob

  • Archiving data as XML

    Hi,
    I'm trying to write an archive routine (On Oracle 9.0.1)which can extract account data and store it in an XML file. The file may be reloaded later if required. I've looked at the XML-SQL Utility and which seems to do the job but the file limitations with PL/SQL are causing problems (create dir etc). I could use the Java API although would prefer PL/SQL.
    Also if I had 3 tables emp, address and account and was able to build the required sql for selection for each table could I store these 3 XML blocks within the 1 file and use XSU to parse the file and perform the required DBMS_XMLSave.insertXML on each block or is there a better way the achive a solution to this problem,
    Many Thanks,
    Trev.

    i don't think you could reload this back into the grc system therefore you are stuck with raw text file dumps I think.

  • "AUTO ARCHIVE LOCATION" of the configuration of the SPM module

    Hello,
    I want to know the option of the "AUTO ARCHIVE LOCATION" of the configuration of the SPM module of the SAP GRC AC 5.3 SP9.
    This option saves the log directly in a server directory? Where does it save the log? And what does it save?
    Thank you in advance.
    Best Regards.
    Pablo Mortera.

    Hi Pablo,
      Please find my response below:
    But when we use it, does it desactivate the log file os the SPM in the Database? No, it won't. There is a setting where you can configure that while archiving delete the logs from SPM. If you turn this on then you won't see the logs until you upload the archived logs into SPM. If you keep this option off, it will keep all the logs in SPM as well.
    Can I choose a shared domain directory instead of a server directory? Yes, you can as long as it is accessible by the server.
    Cheers,
    Alpesh

  • GRC in Azure

    Hi,
    I need the information regarding Azure GRC and Security.And i need to know the standards of Iaas and Paas with respect to banking domain.
    Thanks
    Asha.

    Hi,
    Please have a look at this article:
    http://blogs.msdn.com/b/grc/archive/2011/04/13/emerging-grc-patterns-around-cloud.aspx, it shows us some information about the GRC patterns around Cloud.
    Regards

  • DEVOLUÇÃO DE EXPORTAÇÃO - CFOP 3201 - GRC VALIDA DADOS DI.

    Boa tarde a todos!
    Estamos em um projeto de NFE XML 2.00 e nos deparamos com o seguinte erro:
    Ao emitirmos um NF-e de devolução da mercadoria que se encontrava no Porto (devolução de exportação - CFOP 3201), a validação do monitor GRC informa que é necessário constar os dados de importação, apesar deste processo não se tratar de importação. Os seguintes logs de validação são gerados:
    Erro de validação: campo Código do fabricante estrangeiro no sistema. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-CFABRICANTE, ID campo I028)
    Erro de validação: campo Nº da adição. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-NADICAO, ID campo I026)
    Erro de validação: campo Nº sequencial do artigo na adição. Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_ADI-NSEQADIC, ID campo I027)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-CEXPORTADOR, ID campo I024)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-DDESEMB, ID campo I023)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-DDI, ID campo I020)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-NDI, ID campo I019)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-UFDESEMB, ID campo I022)
    Erro de validação: campo . Campo é obrigatório e não pode ficar em branco. (campo IT_NFE_IMP-XLOCDESEMB, ID campo I021)
    Estamos no SAPK-10015INSLLNFE e as seguintes notas relacionadas a validação estão aplicadas:
    1493980     Validation for field xJust in cancel and skipping messages
    1499921     Problem with validation after implementing SP15
    1500046     Upgrade validation rule for field ID for version 2.00
    1500742     Adjust validation for field NADICAO and NSEQADIC layout 2.00
    1502217     Extend validation rules for , layout 2
    1504379     Adjust validation for field X_CLISTSERV
    1511291     Update allowed values for field E1_CPAIS for validation
    1511577     Update validation rules for field VUNCOM_V20
    1520861     Update validation rules for OIL_CPRODANP and OIL_UFCONS
    Não encontrei nenhuma nota SAP recente para o componente SLL-NFE que seja relacionada a este problema.
    Desde já agradeço pela ajuda.
    Sds / Renato Penido.

    Boa tarde, Fernando,
    Obrigado pela pronta resposta.
    Debugamos a BADI e descobrimos que os dados de importação estão sendo gravado "em branco", gerando o erro de validação no GRC, tal qual dito por você.
    Aprimoramos a lógica da BADI para que a tag de importação não seja preenchida indevidamente para as notas de devolução do porto e as notas foram aprovadas.
    Muito obrigado,
    Renato Penido.

Maybe you are looking for