Copy PCR /Schema

[SAPSF6]

Hi All,

can we import and export Schema /PCR from one system to another

If yes, What will be th Procedure

SK

[former_member193210 · Accepted solution]

As mentioned by Janga, Schemas and PCRs are usually transfered from DEV to QAT and then PRD using Transports, but that implies that the environments are on the same transport path.

On the other hand, if you want to transfer a Schema or PCR from environments that are not linked, then you could do it "manually".

Using the "Table View", you can transfer a Schema or a PCR to an Excel file.

Then, you could use the "Copy" and "Paste" commands to transfer the data from your Excel file into the Development or Sandbox environment of a different Client.

[SAPSF6 · Accepted solution]

Hi Remi,

How is that table view for PCR & Schema

SK

[sikindar_a · Accepted solution]

you can use the following

SE16 T52C5 , T52C2

Tcode PE01N

[former_member193210 · Accepted solution]

When you activate t-code pe02 to modify a pcr, use the icon to switch from Tree Structure View to Table View.

Then, once you have the pcr on screen, you can use the key combinations Ctrl+Y to switch your cursor to a marker, mark the section you want to copy, and use Ctrl+C to copy that section. Note that this only enables you to see one PAYTP at a time.

If you want to copy a large section of the pcr, you can also use the "Print" icon to get a different view of the pcr, where more than one PAYTP can be visible.  Here, you can also use the key combinations Ctrl+Y, Ctrl+C and Ctrl+V to mark the section to copy, to copy it, and then to paste it elsewhere.

[jagan_gunja]

1. All config including PCR's and schemas is done in dev.system config client.  This applies when your installation has a separate client as (a)config,client, (b)a common client for non-client specific objects like ABAP programs/includes, and (c)one as Dev test,   In this case after config, is saved in a transport request, the transp request needs to be copied to the Dev test client using SCC1 txn. 

If you have only one client for the purpose a, b, c above, then copying does not apply.

2. After testing in Dev test client, you may want to further make config corrections and repeat the copy/test process..  Or release the transport task/s; then the transport request.

3. Then the transport request is moved to QA system.  Here you would further do system test.  After you are satisfied with the reukts, get the user or HR/Payroll dept client to complete UAT and sign off.  You may assist the UAT process with any test scenarios in addition to user's scenarios.

4. After UAT sign off, mve the transport request to production system.  This move may include to other systems/clients used for purposes like Disaster recovery.  User training, etc.

Normally the transports are copied from one client to another within the same system by the config consultant;  moved from one system to another (as in steps 3 & 4) by Basis staff.

Hope this clarifies/helps.