what do I have to do after system copy

[Former Member]

I wander what do I have to do after system copy.

E.g change the logical system in (transaction scc4)scc4,

change entries related to logical system in tables (transaction bdls),

change RFC(delete the PRD one and create the TEST one back),

create CUA for this satellite system,

set the TEST system values in WE20 and WE21 transactions),

set transport system so that the new system is TEST....

I guess I missed some action or... If so please let me know

Thank you in advance

[Former Member · Accepted solution]

Jan

You have missed some post-system copy activities,let us know which SAP system you are referring to and also which database,then only we will be able to help you out in detail

Also you can look to the system copy guides on service marketplace which talk about all activities

Rohit

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Sory for missing information. the system is hp-ux/oracle10.2.0.2 based.

Anyway database group will make homogeneous system copy (in a special way as database is 1T big).

I wander most about idocs, RFC-s ...

So I made screenshots of all RFC destinations in "sm59" , "we20" and "we21" Hope this is enough(as the system is already deleted)

[Former Member]

Jan

Refer to the guide for system copy at

https://websmp210.sap-ag.de/erp-inst,you will get all the steps for post-activities

Here are the steps you can refer though

Actions at Operating System Level

1. Adapt the configuration files at operating system level to meet network and SAP requirements.

2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required.

3. Adapt additional non-SAP software components (for example, archiving systems, monitoring

tools, job schedulers) if required.

4. Adapt backup programs (for example BRBACKUP, BRARCHIVE, BACKINT) if required.

5. Adapt non-SAP directories, file systems, NFS mounts, and so on if required.

6. Check the SAP parameters of the default and instance profiles.

7. Check your UNIX shell files for special entries.

8. Check crontab or AT jobs.

9. Check operating system files (for example, .netrc, .rhosts).

10. Check operating system printers.

11. Oracle: Adapt the database profiles init<SAPSID>.ora, init<SAPSID>.dba and

init<SAPSID>.sap.

03/28/2008 PUBLIC 89/122

5 Follow-Up Activities

5.2 Performing Follow-Up Activities in the Target System

Actions at Database Level

1. Before starting the SAP system, make sure that the logging mechanism of the database is active.

2. Check the parameters in the database profiles.

3. Oracle: Delete all entries from the following tables:

DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA.

4. Oracle: Delete the user OPS$<SOURCE_SAPSID>ADM.

5. Oracle: If you changed the <DBSID> during the system copy, we recommend that you adapt the

global_name parameter with the following SQL command:

alter database rename global_name to <NEW_DBSID>;

If the parameter does not exist on your system, ignore this step.

Actions at SAP System Level

1. Run an installation check: Administration System administration Administration Installation Check

(transaction SM28).

2. Configure the Workbench Organizer (transaction SE06) with the option Database Copy. This releases

all transport, repair, and customizing requests that have not been released in the source system.

3. Adapt the transport parameters and transport routes in the Transport Management System

(TMS): a.

a) Choose transaction STMS Overview Systems .

b) Select the system and select the tab Transporttool.

To adapt the transport routes:

Choose transaction STMS Overview Transport routes .

4. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI,

SDBAD, SDBAH, SDBAP, SDBAR.

5. Delete canceled and finished jobs.

Execute ABAP program RSBTCDEL, marking the field delete with forced mode: Tools ABAP Workbench

ABAP Editor (transaction SE38).

6. Adapt all jobs needed in the target system:

a) Copy the old jobs.

b) Modify the new jobs.

c) Delete the old jobs.

7. Check the consistency of the Temporary Sequential Objects (TemSe) by searching for files of TemSe

objects for which no TemSe objects exist:

Administration CCMS Spool TemSe administration (transaction SP12). For more information,

see SAP Note 16875.

8. Adapt the definition of the printers to meet the new system requirements:

n Device types and character set definitions

n Spool servers

n Output management systems (OMS)

90/122 PUBLIC 03/28/2008

5 Follow-Up Activities

5.2 Performing Follow-Up Activities in the Target System

9. Delete entries in table DDLOG for buffer synchronization.

10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the

logical system.

11. Adapt the RFC destination: Tools Administration Administration Network RFC destinations

(transaction SM59).

12. Clean the transactional RFC: Tools Administration Monitor Transactional RFC (transaction

SM58). For more information, see the relevant description in the SAP Online Documentation.

13. Start transaction SECSTORE using Check Entries. If you find erroneous entries with message text

System-dependent data for entry u2026 changed , see SAP Note 816861.

14. Create new operation modes and remove old ones:

a) Create new operation modes and instance definitions.

b) Maintain the timetable using the new operation modes.

c) Delete the old operation modes and old instance definitions.

15. Adapt the operation mode time tables (CCMS): Administration CCMS Configuration Operation

mode calendar (transaction SM63).

16. Adapt the instances and profiles (CCMS): Administration CCMS Configuration OP modes/instances

(transaction RZ04).

17. Define or remove the SAP system users: Tools Administration User maintenance Users

(transaction SU01). Also revise the authorizations of the system users.

18. Delete all entries from tables TPFET and TPFHT. These contain information about changes made

to the profile of your source system: Administration CCMS Configuration Profile Maintenance

(transaction RZ10).

IBM DB2 UDB for iSeries: Use the commands CLRPFM R3<SID>DATA/TPFET and CLRPFM

R3<SID>DATA/TPFHT.

19. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS

table MONI) if required.

20. Delete all entries from table TLOCK, which holds the repair requests from your source system.

21. Make data archived in the source system (data that does not reside in the database but was moved

to a different storage location using SAP Archive Management) accessible in the target system.

Adapt the file residence information in the target system. For more information, see the SAP

Online Documentation (SAP Web Application Server System Administration Application Data Archiving and

Reorganization) .

22. Redefine database actions (backup, update statistics, and so on) if you have used the DBA calendar

in the source system (transaction DB13).

23. Check logon groups and assignment of application servers to logon groups (transaction SMLG).

24. Check the connection to SAPNet - R/3 Frontend (transaction OSS1).

25. Check self-defined external commands (transaction SM69).

26. Check entries of the following tables in all relevant systems:

n TXCOM (transaction SM54)

n THOST (transaction SM55)

03/28/2008 PUBLIC 91/122

5 Follow-Up Activities

5.2 Performing Follow-Up Activities in the Target System

27. Check the logical system names. For more information, see Preparations [page 17]. If you need to

change logical system names in the system that results from the copy, change the logical system

names at this time as described in SAP Notes 103228 and 544509. Follow your corporate naming

strategy for logical systems when making this change.

BI customers: If you have copied a BI (formerly BW) system, read SAP Note 325525.

28. For every client in your SAP system check the detail settings (client role, changes and transports

for client-dependent objects, changes for client-independent objects, protection level, restrictions)

(transaction SCC4).

29. Check if you can delete clients that will no longer be used in the target system (transaction SCC5).

30. Check the contexts and segments of remote application servers for the SAP Monitoring

Infrastructure if required (transaction RZ21).

31. Configure the domain controller in the Transport Management System (TMS) by using

transaction STMS.

32. Post-processing for customer objects:

If customer objects are not original in the new system, modify the corresponding entries in table

TADIR.

If you encounter problems modifying a customer development class using transaction SMTS or

SM31, try to use the option Validate (ENTER) instead of the option Save to save your changes.

33. ABAP Program Loads

The ABAP loads are platform-dependent programs that are generated during runtime and stored

in database tables. They are not exported when you use the R3load procedure to copy your

SAP system. The ABAP loads are generated in the target system when they are first used. This

might, however, reduce production system performance. To avoid this, you can use transaction

SGEN to generate the missing loads.

Load generation requires a large amount of system resources. Therefore, it makes sense to

schedule the generation job to run overnight.

For a detailed description of the features, see the online documentation in transaction SGEN by

choosing Information on the SAP Load Generator, or in the Job Monitor by choosing Job Monitor.

34. If you did not change the database when copying the system, you have to start program

RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGR. Otherwise, if you

changed the database when copying the system, you have to start program RS_BW_POST_MIGRATION

in the background with variant SAP&POSTMGRDB Program RS_BW_POST_MIGRATION performs

necessary modifications on database-specific objects (mainly BI objects).

Checking the Target System

The following actions are suitable for checking the consistency of the target system:

1. Perform initial consistency check (transaction SM28).

2. Check the system log on all application servers (transaction SM21).

3. Check the consistency of the database (transaction DB02).

4. Perform server check (transaction SM51).

92/122 PUBLIC 03/28/2008

5 Follow-Up Activities

5.2 Performing Follow-Up Activities in the Target System

5. Test transactions frequently used by the customer.

6. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those

gained on the source system before the system copy ( Accounting Financial Accounting General

ledger Periodic Processing Closing Check/count Comparison ).

7. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet),

RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and compare the results to those

gained on the source system before the system copy.

8. CO customers: Run the report group 1SIP and compare the results to those gained on the source

system before the system copy.

Replacing the PSEs in the Target System

Replace all existing PSEs in the target systems with new ones which contain the new systemu2019s

information. Proceed as follows:

1. In your ABAP system, call transaction STRUST.

2. Proceed as described in the documentation Creating or Replacing a PSE in the SAP Library at

http://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Security System Security System Security for SAP Web AS ABAP only Trust Manager .

Note

n Since replacing a PSE will remove all of the previously used certificates, also import all

necessary trusted certificates into the new PSEu2019s certificate list. (Check the old PSEu2019s certificate

list.) Also distribute the new PSEu2019s public-key certificate to the systems where it will be used.

n Make sure the new PSE contains the new system ID.

n Note the naming conventions to use for each PSE. The naming conventions are usually

specified by the Certification Authority (CA) where you obtain the certificate, however, the

type of PSE also has some restrictions, for example, for the SSL server PSE, the CN part of the

Distinguished Name must be the host name used to access the server. For the system PSE, we

recommend using the SID as the CN part.

Rohit

[former_member286504]

Hi Rohit,

Can you please explain the below point...

Adapt the configuration files at operating system level to meet network and SAP requirements.

Thanks

Venkat

[Former Member]

We optimize our system copy by export of tables like information from secstore, SM59, SPAD, archiv-information, table DBCON, SMLG, RZ12, RZ10, BD64.

Our experimant about to export SM37 dosn't work. Aferter im port tables from SM37 standard variants are missing.

JR

[Former Member]

Hi,

Select "Database Copy or Migration" and execute "Post Installation Processing" in SE06 Tcode and Change all of the Source System Objects to Target System Objects as asked.. This should take care of almost all the IMP changes.

Change the print servers in SPAD also. Change the logon groups in SMLG also. Check the operations modes also.

With Regards,

Saurabh

Edited by: Saurabh.Arora on Jun 7, 2009 3:39 PM