2. ⢠This is the third in a series of presentations dedicated to SAP
Landscape Virtualization Management (LVM)
⢠This document provides a quick overview of how to integrate
SAP LVM Post Copy Automation (PCA) in SAP LVM
⢠The document is aimed at system administrators responsible
for configuring SAP LVM and performing SAP system copies
⢠The document assumes the reader has a high level of
experience with system copies and associated terminology
Introduction
3. Overview
⢠SAP LVM Enterprise Edition can be used for various system
provisioning activities such as cloning, copying, refreshing and
renaming of SAP systems
⢠With Enterprise Edition, customers have the option to use PCA
for ABAP and Java systems
⢠SAP LVM Enterprise Edition allows integration of PCA for SAP
systems without activating them for provisioning activities i.e. it
can be invoked in standalone mode
⢠This document focuses on the integration of standalone PCA
with an example showing steps following a database refresh
4. Pre-ÂâRequisites
 in
 ABAP
⢠Before integrating PCA with LVM you must configure PCA in the back-Ââ
end systemthat is the target of the systemcopy
⢠An overview of this configuration is available in SlideShare document
entitled âSAP Post Copy Automationâ
⢠In addition to this configuration, a system user (e.g. LVMADM) with
high authorizations (e.g. SAP_ALL) is required in all clients excluding
client 000
⢠This system user is used during the PCA BDLS task in the back-Ââend
systemvia RFC calls from client 000 to all other relevant clients
⢠Ensure you know the password for SAP* in client 000 of the source
system as this will be needed by PCA before the user masters are
imported into the new target system
5. Configuration
 in
 LVM
⢠Before being able to perform any system copy or refresh
related activities, the system must be enabled for provisioning
in LVM
⢠The system is enabled for provisioning in the âSystemsâ tab
under the âConfigurationâ section
6. Configuration
 in
 LVM
⢠Edit the system for which provisioning should be enabled and
select the âStandalone PCAâ radio button in the âSystem and AS
Provisioningâ section
7. Configuration
 in
 LVM
⢠Now, in the âProvisioningâ section, with the system selected,
you will see the new button âStandalone PCAâ
⢠Standalone PCA can now be executed for this system
8. Task
 Lists
⢠Depending on your scenario (i.e. copy or refresh) you will need
to decide which PCA tasks to execute in the system
⢠For a system copy, youâll probably want to include PCA standard
task lists SAP_BASIS_COPY_INITIAL_CONFIG and
SAP_BASIS_COPY_BDLS
⢠For a system refresh (export), youâll probably want to include
PCA standard task lists SAP_BASIS_COPY_REFRESH_EXPORT
⢠For a system refresh (import), youâll probably want to include
PCA standard task lists SAP_BASIS_COPY_REFRESH_IMPORT
and SAP_BASIS_COPY_BDLS
9. Execution
 for
 System
 Refresh
⢠Start the standalone PCA with type âTask List Executionâ
10. Execution
 for
 System
 Refresh
⢠Using the âAddâ button and drop-Ââdown, add tasks
â SAP_BASIS_COPY_REFRESH_IMPORT
â SAP_BASIS_COPY_BDLS
⢠Modify the parameters for the BDLS task
11. Execution
 for
 System
 Refresh
⢠Add logical systems pairs to be converted during the BDLS
execution
12. Execution
 for
 System
 Refresh
⢠When all tasks have been added and parameterized, move on
to the summary screen
14. Monitoring
 the
 Execution
⢠Basic monitoring of the standalone PCA execution can be done
via the âMonitoringâ section in LVM
15. Monitoring
 the
 Execution
⢠Detailed monitoring on the progress of individual tasks within
the PCA task lists can be done in the ABAP back-Ââend system
using transaction âSTC02â in client 000
16. Reference
 Material
⢠The
 following
 pages
 on
 SAP
 Help
 are
 useful:
â Provisioning
 Systems
â System
 Copy
â System
 Refresh
â Refreshing
 a
 Database
 Only
⢠Further
 details
 are
 available
 on
 request
Â
â mailto:info@aliterconsulting.co.uk