210564 - Copying a Complete APO System

7/21/2019 210564 - Copying a Complete APO System

http://slidepdf.com/reader/full/210564-copying-a-complete-apo-system 1/4

SAP Note

210564 - Copying a complete APO system

Version 15 Validity:17.08.2006 - active

Language English

Header Data

Released On 17.08.2006 11:55:58

Release Status Released for Customer

Component BC-DB-LCA liveCache Applications

Other Components BC-DB-LVC liveCache

Priority Recommendations / Additional Info

Category Consulting

Symptom

For Release SCM 4.0 and higher, refer to Note 886103.

You want to copy a complete APO system with all its master data and transaction data from oneinstallation (source system) to another installation (target system).If the source system is connected to one or more R/3 systems, the source system (not the targetsystem) is still connected to these R/3 systems after the copy procedure. Therefore, after thecopy procedure, the target system is not populated with data from the R/3 systems connected tothe source system. As a result, an APO system copy only makes sense for a data backup, forexample, but not if you want move the production system to different hardware.

Carefully read the points described in this note. Pay particular attention to the points markedCaution. An incorrect system copy may result in some inconsistencies in the source system.

Additional information is also available on SAP Service Marketplace at:http://service.sap.com/scm >> mySAP SCM Technology >> Installation, Upgrade, Migration, System Copy .... >> SAP APO Homogeneous System Copy

See also the following Best Practice document on this subject:"mySAP SCM System Landscape Copy"This document is available at: http://service.sap.com/solutionmanager >> SAP Solution Manager >> Functions in Detail

>> Operations & Services >> Best Practices for Solution Management >> Availability >> By Topic Area

Other Terms



Reason and Prerequisites

Solution

As a prerequisite, the APO database and liveCache configurations must be identical in both the

source and target systems.You can only copy an APO system offline, which means that no users must be working in the APOsystem during the copy process. Furthermore, after the copy process, you should stop and restartthe CIF queues in the R/3 systems connected to the source system.

Procedure:

1. Make sure that no users are active in the APO system.

2. Stop the database and the liveCache. You stop the liveCache in transaction LC10. (InLC10, enter the database connection LCA and then choose "liveCache Administration" or"liveCache: Monitoring". In the newer version of LC10, go to the "Administration" ->"Operating" subtree. Then choose "Stop liveCache". Do NOT choose the "InitializeliveCache" button. If you choose this button, you will lose all of the transaction data inthe liveCache).

While the liveCache is stopping, it writes the data to the data devspaces, thatis, all data stored in the liveCache is written to the hard disk of the liveCache instance.

After you have successfully stopped the liveCache, the traffic light intransaction LC10 turns red.

3. Make a database copy. The database must be copied from the source system to the targetsystem. (Follow the normal procedures of the relevant database manufacturers.)

4. Copy the liveCache:

For more information about copying a liveCache, see Note 457425.

5. You can now start the database in the source system. Use transaction LC10 to start theliveCache. To do this, choose "Start liveCache". (Do NOT choose "Initialize liveCache"here.)

6. Caution:

The liveCache of the source system is configured in the target system. You mustprevent transactions (for example, background jobs) from accessing the liveCache of the sourcesystem. If this happens, some inconsistencies may arise between the APO database and theliveCache in the source system.

Configure the central instance of the target system (by setting up a relevantprofile) in such a way that no background processes are started.

7. Start the APO database and the central instance of the target system. Make sure that noAPO users are working in the system yet.

8. Call transaction LC10 in the target system and establish the database connection asfollows:

After you call transaction LC10, enter LCA as the database connection and thenchoose "Integration" (Ctrl + F4). Here, enter the name of the liveCache server of the targetsystem and then choose "Save". Repeat the process for the LDA database connection.

Note that, if you forget to execute this step, data may be lost or someinconsistencies may arise in the source system.

9. Now restart the central instance of the target system. To do this, use the defaultprofile, which means that background processes can be started again. You do not have torestart the APO database. You can now also start other application servers if you wish.

10. In the target system, start the liveCache in transaction LC10. The liveCache thenstarts on the basis of the backup created by the source system.



Both the database and the liveCache in the target system then contain the same data as in thesource system.

Other Attributes

Transaction codes COPY

HIER

LC10

TRANSAKTIONEN

Validity

Software Component From Rel. To Rel. And SubsequentSAP_APPL 46A 46B

SAP_APO 20A 20A

30A 30A

310 310

References

This document refers to:

SAP Notes

886103 System Landscape Copy for SAP SCM

877203 Post steps after the Homogenous liveCache copy using backup/

631009 Duplicate orders with same external number

558563 How does a client copy work with Demand Planning?

500843 Composite SAP note for COM and SAP liveCache 7.2 or higher

457425 Homogeneous liveCache copy using backup/restore

This document is referenced by:

SAP Notes (7)

500843 Composite SAP note for COM and SAP liveCache 7.2 or higher

457425 Homogeneous liveCache copy using backup/restore

886103 System Landscape Copy for SAP SCM

1014782 FAQ: SAP MaxDB system copy

https://websmp130.sap-ag.de/sap/support/notes/631009













877203 Post steps after the Homogenous liveCache copy using backup/

631009 Duplicate orders with same external number

558563 How does a client copy work with Demand Planning?




Documents

210564 - Copying a Complete APO System