Skip to Content

Personas 2.0 and System Copy

Hi Folks - We will soon do a system copy in our ERP landscape (copying production to QA). We use a database restore method for this.

We have a couple of Personas 2.0 SP02 scenarios active in production.

I am concerned about Personas production tables overlaying the QA tables. Has anyone done this type of system copy before with Personas? If so can you recommend a procedure to handle this scenario?

There are currently 46 tables in the /PERSOS/ namespace - should they all be copied from QA and restored after the system copy?

Thanks - Jeff

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    May 07, 2015 at 08:57 AM

    When you do a system copy, everything in the target system is deleted and replaced with the contents of the source system. Personas is no different. After your system copy, you QA system will have all of the Personas flavours from production. Anything that was in QA only will be gone. If you have stuff in QA and not yet in production, you will have to put it back after the copy.

    If the flavours were developed in DEV first, then just replay the transports that copied them to QA. If not, or if they've been changed in QA, then export them before the system copy and import them afterwards.


    Add comment
    10|10000 characters needed characters exceeded

    • I wouldn't advise to do straight table copies, since I'd be worried about tables referencing GUIDs belonging to a different system and similar cases.

      The best way is to do things as Steve suggested: via the transport system.