Skip to Content

Basis system access for client copy from production to dev / QA

Hi all,

I've got a request from my Basis team to give them access to SCC7 and SCUA with delete in production to support client copies from there to deveopment / quality. I haven't been able to find any best practices for how to handle this. I'm not sure SCC7 is something we want people to have in production. Deleting CUA doesn't give me a warm fuzzy, but it isn't as big of a deal because I can easily reactivate it from the central system.

What have you guys done in similar situations? The idea is that the access is needed in the source system so that it will be available in the target system when it comes up.

Thanks!

Krysta

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    May 27, 2011 at 07:27 PM

    Hi Krysta,

    Usually during client copies, we generally dont loose user adminiustration capabilities in target systems.. So it should not be a big deal to assign them Client Administration roles in Target systems after the copy...

    However during system copies, we had an issue which was handled by prior assignment of a role in PRD for CUA/Security teams.. We had central CUA in PRD and when it is copied to QAS, the CUA setup also gets transferred and the capability to delete it does not exist since we dont have delete auth in PRD.. So just before system copies to QAS, we had assigned Z role with ALE delete capabilities to remove the central setup from QAS and then readd the system to PRD.

    A better practice would be to assign these users SCC7 for a short period of time when client copies happen (I would asusme remote) in Target systems directly and document that step in Post Client Copy activities task list or something...

    Hope these inputs help..

    ~Sri

    Add comment
    10|10000 characters needed characters exceeded