You want to copy a complete APO system with all its master data and transaction data from one installation (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 target system) is still connected to these R/3 systems after the copy procedure. Therefore, after the copy procedure, the target system is not populated with data from the R/3 systems connected to the source system. As a result, an APO system copy only makes sense for a data backup, for example, but not if you want move the production system to different hardware. 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 APO system during the copy process. Furthermore, after the copy process, you should stop and restart the CIF queues in the R/3 systems connected to the source system.
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. (In LC10, 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 "Initialize liveCache" button. If you choose this button, you will lose all of the transaction data in the liveCache).
While the liveCache is stopping, it writes the data to the data devspaces, that is, 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 in transaction LC10 turns red.
3. Make a database copy. The database must be copied from the source system to the target system. (Follow the normal procedures of the relevant database manufacturers.)
4. Copy the liveCache:
5. You can now start the database in the source system. Use transaction LC10 to start the liveCache. To do this, choose "Start liveCache". (Do NOT choose "Initialize liveCache" here.)
The liveCache of the source system is configured in the target system. You must prevent transactions (for example, background jobs) from accessing the liveCache of the source system. If this happens, some inconsistencies may arise between the APO database and the liveCache in the source system.
Configure the central instance of the target system (by setting up a relevant profile) 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 no APO users are working in the system yet.
8. Call transaction LC10 in the target system and establish the database connection as follows:
After you call transaction LC10, enter LCA as the database connection and then choose "Integration" (Ctrl + F4). Here, enter the name of the liveCache server of the target system 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 some inconsistencies may arise in the source system.
9. Now restart the central instance of the target system. To do this, use the default profile, which means that background processes can be started again. You do not have to restart 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 then starts 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 the source system.