Skip to Content

Change JCo Destination

Hi,

GRC 5.1 is connected to QAS system and PRD system (R/3 4.6). There's only phisical systems.

Into ECC upgrade projetc we would switch Jco destination from R/3 4.6 (QAS) to ECC 6.0 QAS.

Any experience? I think that for GRC should be transparent. The Risk analysis data? After the switch need to do a new full analysis?

Thanks.

Massimo

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 07, 2010 at 06:42 PM

    Massimo,

    This would be transparent to RAR (CC). You won't loose any data. It would be better to do a full sync or simulation to make sure that the connection is working fine.

    Alpesh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 07, 2010 at 07:17 PM

    Massimo,

    From my experience on impact of system upgrade/JCo destination switch, would recommend you to take care of following -

    1) Ensure to bounce system (on system with multiple App servers I observed that sometimes changes are not reflected on all servers).

    2) Verify/adjust your RAR connector settings(adaptive RFC).

    3) Reimport the static text, permission files.

    4) Rerun the full risk analysis.

    I observed one issue after backend upgrade on our system - Alert generation job was failing while generating conflicting transaction alerts. We even logged a SAP message but, were not able to find any clue. The error mysteriously went away for few days and issue cropped in again. We were not using that feature so finally decided to turn it off.

    Make sure you test thoroughly with QAS system before proceeding with production upgrade.

    Regards,

    Amol

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 08, 2010 at 11:04 AM

    Many thanks, I will let you know.

    Massimo

    Add comment
    10|10000 characters needed characters exceeded