abap post-copy automation configuration guide_v3.2

Configuration Guide CUSTOMER

ABAP Post-Copy AutomationDocument Version: 3.2 - 2014-06-02

ABAP Post-Copy Automation Configuration Guide

Table of Contents1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Basic Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1 System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2 System Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

3.3 Logical System Name Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

4 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6 Predefined Task Lists for ABAP Post-Copy Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96.1 Task List ABAP Basis Copy Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

6.2 Task List ABAP Basis Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

6.3 Task List ABAP Basis Copy Refresh – Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

6.4 Task List ABAP Basis Copy Refresh – Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6.5 Task List ABAP Basis Copy BDLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

7 Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137.1 Standard Roles and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

7.2 Assigning Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7.3 Authorization Objects for Logical System Name Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8 Customizing Post Copy Automation Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178.1 Displaying Task List Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

8.2 Creating Task List Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

8.3 Displaying Event Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8.4 Adding Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8.5 Adding Configuration Tables for System Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.6 Transporting Task List Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

8.7 Importing Task List Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

9 Executing Task Lists with the ABAP Task Manager for Lifecycle Management Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239.1 Executing Task List for Initial System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9.2 Executing Task Lists for System Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

10 Important Disclaimers on Legal Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2C U S T O M E R© 2014 SAP AG or an SAP affiliate company. All rights reserved.

ABAP Post-Copy Automation Configuration GuideTable of Contents

1 Document HistoryBefore you start, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/instlvm

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2013-07-05 Initial version

1.1 2013-07-27 Prerequisites updated

1.2 2013-09-19 Implementing the Latest Note Assistant Updates updated

2.0 2013-12-11 ● Task Lists for ABAP Post-Copy Automation updated

● Using the ABAP Task Manager for Lifecycle Management Automation updated

● Prerequisites updated

3.0 2014-03-17 Installation content moved to ABAP Post-Copy Automation Installation Guide. For more information, see

http://service.sap.com/instlvm .

3.1 2014-03-21 Minor changes

3.2 2014-04-14 Terminology changes

ABAP Post-Copy Automation Configuration GuideDocument History

C U S T O M E R© 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/disclaimer?site=http://service.sap.com/instlvm


2 IntroductionABAP post-copy automation (PCA) provides task lists with a predefined sequence of configuration tasks to configure extensive technical scenarios automatically.

ABAP PCA is part of SAP Landscape Virtualization Management, enterprise edition software. SAP Landscape Virtualization Management is an add-on to SAP NetWeaver 7.3 and SAP NetWeaver 7.4. To use ABAP PCA, you must own an SAP Landscape Virtualization Management, enterprise edition license. To run ABAP PCA task lists, you use the following:

● SAP Landscape Virtualization Management, enterprise editionYou start the execution of a task list in the SAP Landscape Virtualization Management environment directly.

● ABAP task manager for lifecycle management automationFrom a certain release and Support Package level, the ABAP task manager for lifecycle management automation is part of every ABAP system. SAP also offers several non-licensed ABAP automation tasks for an automated initial setup.


ABAP Post-Copy Automation Configuration GuideIntroduction

3 Basic ConceptsThis section describes the principal scenarios for ABAP post-copy automation.

3.1 System Copy

You copy a system to create a duplicate of an existing system with a different host name and a unique system ID.

To adapt the copy to its new identity automatically, you use ABAP post-copy automation (PCA).

Related Information

Task List ABAP Basis Copy Initial Configuration [page 10]After a system copy, you use task list SAP_BASIS_COPY_INITIAL_CONFIG to run required cleanup and configuration steps automatically.

3.2 System Refresh

You refresh a system to overwrite an existing target system with the latest data from a source system while keeping the configuration.

To prevent the target system configuration from being overwritten, you use ABAP post-copy automation (PCA) to export target system tables that contain configuration information before starting the system copy. After the system copy has finished, you use ABAP PCA to import the configuration information into the target system.

Related Information

Task List ABAP Basis Copy Refresh [page 10]You use task list SAP_BASIS_COPY_REFRESH to run a complete system refresh automatically with the enterprise edition of SAP Landscape Virtualization Management.

Task List ABAP Basis Copy Refresh – Export [page 11]Before a system copy, you use task list SAP_BASIS_COPY_REFRESH_EXPORT to export connectivity-related configuration data automatically in the form of table content to the file system using R3trans with the ABAP task manager for lifecycle management automation.

Task List ABAP Basis Copy Refresh – Import [page 11]After a system copy, you use task list SAP_BASIS_COPY_REFRESH_IMPORT to import connectivity-related configuration data in the form of table content automatically from the file system using R3trans with the ABAP task manager for lifecycle management automation.

ABAP Post-Copy Automation Configuration GuideBasic Concepts


3.3 Logical System Name Conversion

After a system copy, you carry out a logical system name conversion in the ABAP target system.

You use ABAP post-copy automation for the following:

● To correct the logical system name● To configure a new logical system name for all partner systems in the target system

Related Information

Task List ABAP Basis Copy BDLS [page 12]After a system copy, you use task list SAP_BASIS_COPY_BDLS to run required BDLS conversion steps concurrently if needed.


ABAP Post-Copy Automation Configuration GuideBasic Concepts

4 PrerequisitesYou have read the ABAP Post-Copy Automation Installation Guide.

For more information, see SAP Service Marketplace at http://service.sap.com/instlvm .

ABAP Post-Copy Automation Configuration GuidePrerequisites



5 Important SAP NotesThe most important SAP Notes that apply to ABAP post-copy automation are shown in the table below.

SAP Note Number Title Description

1614266 System Copy: Post Copy Automation (PCA) / LVM

Installation note for the current release of the ABAP post-copy automation.

1707321 BW System Copy: Note analyzer Post Copy Automation (BW-PCA)

Installation note for the current release of the ABAP post-copy automation for SAP Business Warehouse.

1783702 SAP Landscape Virtualization Management 2.0

Contains the latest information about supported IT infrastructure elements.

1709155 System Provisioning with Landscape Virtualization Management

Contains the latest information about system provisioning with SAP Landscape Virtualization Management.

1928090 Handle PCA SAP Notes for SPDD/SPAU comparison

Contains information about handling modification adjustments for SAP Notes.


ABAP Post-Copy Automation Configuration GuideImportant SAP Notes

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1614266





6 Predefined Task Lists for ABAP Post-Copy AutomationSAP offers predefined tasks lists for ABAP post-copy automation. Each task list consists of a set of configuration tasks.

Predefined task lists for ABAP post-copy automation are only available if you own an SAP Landscape Virtualization Management, enterprise edition license. Contact your SAP representative to obtain a license to make this function available. The task lists are proprietary to SAP and can be overwritten during an upgrade.

NoteThese task lists are not relevant if your system is an SAP Business Warehouse (SAP BW) system or connected to a SAP BW as SAP BW source system. For more information about SAP BW PCA, see the SAP BW PCA

Configuration Guide at http://service.sap.com/instlvm .

RecommendationConsider SAP task lists as templates. Save SAP task lists as a copy.

Related Information


Task List ABAP Basis Copy Refresh [page 10]You use task list SAP_BASIS_COPY_REFRESH to run a complete system refresh automatically with the enterprise edition of SAP Landscape Virtualization Management.



Task List ABAP Basis Copy BDLS [page 12]After a system copy, you use task list SAP_BASIS_COPY_BDLS to run required BDLS conversion steps concurrently if needed.

ABAP Post-Copy Automation Configuration GuidePredefined Task Lists for ABAP Post-Copy Automation



6.1 Task List ABAP Basis Copy Initial Configuration

After a system copy, you use task list SAP_BASIS_COPY_INITIAL_CONFIG to run required cleanup and configuration steps automatically.

NoteThis task list is not relevant if your system is an SAP Business Warehouse (SAP BW) system or connected to a BW as BW source system. For more information about SAP BW PCA, see the SAP BW PCA Configuration Guide

at http://service.sap.com/instlvm .

After the homogeneous or heterogeneous system copy has finished, you have to carry out several cleanup and configuration steps on the ABAP target system. The data cleanup is required to delete the content of tables that contain source system information in the target system. This prevents the target system from interfering with the source system and other connected systems.

6.2 Task List ABAP Basis Copy Refresh

You use task list SAP_BASIS_COPY_REFRESH to run a complete system refresh automatically with the enterprise edition of SAP Landscape Virtualization Management.



The system refresh is done to overwrite an already existing target system with the latest data from a source system while keeping the configuration. To prevent the target system configuration from being overwritten, you need to export the target system tables that contain connectivity-related configuration information before you start the system copy. After the system copy is finished, you need to import the target system tables.

The task list runs in the following order:

1. Export phaseThe system exports connectivity-related configuration data in the form of table content to the file system using R3trans.

2. Stop phaseThe task list run stops so that SAP Landscape Virtualization Management can perform the physical system copy (task CL_STCT_SC_CONFIRM_COPY)

3. Cleanup phaseThe system deletes the content of tables that contain source system information.

4. Import phaseThe system imports connectivity-related configuration data in form of table content from the file system using R3trans.





5. Configuration phaseThe ABAP task manager for lifecycle management automation adapts the configuration to the target system.

6.3 Task List ABAP Basis Copy Refresh – Export

Before a system copy, you use task list SAP_BASIS_COPY_REFRESH_EXPORT to export connectivity-related configuration data automatically in the form of table content to the file system using R3trans with the ABAP task manager for lifecycle management automation.



The system refresh is done to overwrite an already existing target system with the latest data from a source system while keeping the configuration. To prevent the target system configuration from being overwritten, you need to export the target system tables that contain connectivity-related configuration information before you start the system copy. After the system copy, you can import this connectivity-related configuration data into the target system again.

6.4 Task List ABAP Basis Copy Refresh – Import

After a system copy, you use task list SAP_BASIS_COPY_REFRESH_IMPORT to import connectivity-related configuration data in the form of table content automatically from the file system using R3trans with the ABAP task manager for lifecycle management automation.



NoteYou can only use this task list if an export already exists.

The system refresh is done to overwrite an existing target system with the latest data from a source system while keeping the configuration. To prevent the target system configuration from being overwritten, you need to export connectivity-related configuration information before the system copy and import it again into the target system after the system copy has finished.





6.5 Task List ABAP Basis Copy BDLS

After a system copy, you use task list SAP_BASIS_COPY_BDLS to run required BDLS conversion steps concurrently if needed.



After the homogeneous or heterogeneous system copy has finished, you have to carry out logical system name conversion on the ABAP target system. The conversion is required to correct the logical system name or configure a new name in all relevant tables for all partner systems in the target system. The conversion execution takes place in the current client.




7 Security ConsiderationsThe security considerations provide an overview of the security-relevant information that applies to ABAP post-copy automation.

7.1 Standard Roles and Permissions

The table below shows the standard roles and permissions that are used for ABAP post-copy automation activities.

Role Description Permissions

SAP_BC_STC_DISPLAY Role for displaying task lists.

This role allows task lists and corresponding objects (task list runs and task list variants) used for technical configuration to be displayed.

● Display task lists (transaction STC01)

● Display task list variants (transaction STC01)

● Display task list runs (transaction STC02)

SAP_BC_STC_USER Role for a configuration user.

This role reflects the typical usage of the ABAP task manager for lifecycle management automation.


● Execute task lists (transaction STC01)

● Define task list variants (transaction STC01)



SAP_BC_STC_AUTHOR Role for authoring task lists.

This role allows task lists used for technical configuration to be authored.

● Create task lists (transaction STC01)

● Copy task lists (transaction STC01)

● Change existing task lists (transaction STC01)

● Delete task lists (transaction STC01)




ABAP Post-Copy Automation Configuration GuideSecurity Considerations



SAP_BC_STC_REORG Role for cleaning up runtime data.

This role allows task list runs executed during technical configuration to be cleaned up.




● Delete task list runs (transaction STC02)

SAP_BC_STC_REMOTE Role for remote access.

This role contains the authorizations which are necessary to operate on technical configuration task lists remotely.

To perform particular actions, further authorizations are necessary. See other SAP_BC_STC_* roles.

SAP_BC_STC_CUST Role for customizing task lists or task list variants.

This role contains the authorization for transporting task list variants between systems.

NoteIf this role is not yet available in your system, make sure that you implemented all improvements for the ABAP task manager for lifecycle management automation. For more information, see

SAP Note 1681488 Task Manager for Technical Configuration (4. Improvements).



● Create task list variants (transaction STC01


● Transport task list variants (transaction STC01)

SAP_BC_STC_ADMIN Role contains all permissions of the following roles:

● SAP_BC_STC_DISPLAY● SAP_BC_STC_USER● SAP_BC_STC_AUTHOR● SAP_BC_STC_REORG● SAP_BC_STC_REMOTE




● Execute task lists (transaction STC01)


● Create task lists (transaction STC01)





● Create task list variants (transaction STC01

● Copy task lists (transaction STC01)

● Change existing task lists (transaction STC01)

● Delete task lists (transaction STC01)

● Delete task list runs (transaction STC02)

7.2 Assigning Roles

To execute ABAP post-copy automation activities, you must assign the corresponding SAP_BC_STC roles to the administrator (dialog user) responsible for ABAP PCA activities and to the technical users that are used from SAP Landscape Virtualization Management using remote access.

Context

NoteTo execute ABAP post-copy automation tasks and task lists, you need the permissions of the corresponding transaction for each task.

Procedure

1. Log on to your ABAP system.2. Call transaction PFCG.

3. Assign the role SAP_BC_STC_USER to the dialog user and the technical user.

4. Assign the role SAP_BC_STC_REMOTE to the technical user.

5. Assign the role SAP_BC_CTC with authorization object S_CTC and activity 16 to the technical user.



7.3 Authorization Objects for Logical System Name Conversion

To convert logical system names using the BDLS conversion task (remote client conversion function), you need authorizations which are not assigned to a predefined role.

The table below shows the security-relevant authorization objects that are used for the BDLS configuration task:

Authorization Object

Field Value Description SAP NetWeaver Release

S_RFC <RFC_TYPE> FUNC Execute required RFC connection

7.02 and above<RFC_NAME> SCTC_CONV_BDLS

*

<ACTVT> 16

S_CTC <ACTVT> 16 Execute configuration tasks

7.01 and above

S_RFC <RFC_TYPE> FUGR Execute required RFC connection

7.00 – 7.01<RFC_NAME> SCTC_SC_EXEC

<ACTVT> 16

S_RZL_ADM <ACTVT> 01 Define external commands

7.00

B_ALE_LSYS <Logical system>

* Define logical system

Not applicable

S_BTCH_JOB <JOBACTION> RELE Release your own jobs automatically

Not applicable

<JOBGROUP> *



8 Customizing Post Copy Automation ContentYou adapt ABAP post-copy automation content to your needs by using the ABAP task manager for lifecycle management automation.

8.1 Displaying Task List Documentation

Procedure

1. Log on to your ABAP system with logon language English.2. Call transaction STC01.

3. Enter the name of the task list.

4. Choose .

5. Choose Goto Documentation Display with Task Docu .

Results

You get the complete documentation of the task list with a detailed task description.

8.2 Creating Task List Variants

You customize a task list according to your needs.

Procedure


3. Enter the name of the task list you want to customize.

4. Choose .5. Enter the name for the task list variant.

6. Choose .

ABAP Post-Copy Automation Configuration GuideCustomizing Post Copy Automation Content


The ABAP task manager for lifecylce management automation displays a list of the tasks that are defined for the chosen technical configuration scenario in the order of their execution. Mandatory and necessary tasks are preselected for execution.

7. Adapt the task list to your needs.a) If you want some tasks to be skipped, deselect them.

○ You cannot deselect mandatory tasks.○ If tasks depend on each other, the ABAP task manager for lifecylce management automation allows

them to be selected or deselected together only.○ If you deselect tasks, the technical configuration scenario is not configured completely after the

execution of the task list. Make sure that you carry out the skipped configuration steps manually.

b) Some tasks require your input, choose or in the Parameter column of each task, if applicable.Decide for each task if you want to edit the parameters or copy the settings from an existing variant. If you do not edit mandatory parameters, the ABAP task manager for lifecylce management automation uses default settings, if any, or stops and prompts you for your input. After you have made your settings, save them and go back to the task list.

8. Save the task list variant.

9. To run a task list in check mode, choose .The ABAP task manager for lifecylce management automation checks whether the prerequisites for the selected tasks are met. The task list is not executed during this run.

Related Information

Adding Reports [page 19]You add reports to a task list.

8.3 Displaying Event Tasks

Event tasks, such as SAP Business Suite Application specific configuration tasks, which are on a software level above SAP_BASIS, or delivered from or developed under the responsibility of the application, are linked to an event.

Context

The configuration tasks are related to connectivity inside the target system or to systems outside.

The event tasks provide only features and content for refreshing one isolated system. Any related systems are ignored. The task documentation for event tasks contains links to IMG activities. These links can only work correctly if the corresponding SAP Business Suite Application is available.

To display all tasks that are linked to an event without generating a task list run, proceed as follows:



Procedure


3. Enter SAP_BASIS_COPY_REFRESH* in the Task List field.

4. Select the required task list for the system refresh.

5. Choose .

6. In the task list, select the task with task type .7. From the context menu, choose Show Event Tasks.

8.4 Adding Reports

You add reports to a task list.

Prerequisites

The report you want to add to the task list can be executed in background.

Context

NoteDefault values for the reports are not included automatically.

Create a report variant for each report with selection criteria and check the values of the report variant in the task list.

Procedure


3. Enter the name of the task list to which you want to add a report.

4. Choose .The ABAP task manager for lifecycle management automation displays the task list.



5. Choose .6. (Optional) On the Task Reports tab, enter your search criteria.

7. Choose .8. Select the report you want to add.

9. Choose .10. If required, rearrange the task sequence.11. Save the changes.

8.5 Adding Configuration Tables for System Copy Refresh

Enhance the list of configuration tables that are processed by import and export functions.

Prerequisites

The business add-in (BAdI) SCTC_SC_CUSTOMER_TAB is implemented in the enhancement spot SCTC_SC_CUSTOMER.

Procedure


3. Enter SAP_BASIS_COPY_REFRESH in the Task List field.

4. Choose .5. Select the task Export Customer defined Configuration Tables or Import Customer defined

Configuration Tables.

6. Choose in the Parameter column.7. Enter the BAdI string in the Additional Information for Customer Exit field.

Results

The system exports or imports all appended customer configuration tables.



ExampleA BAdI with parameter IV_CUST_INFO is implemented in your ABAP system as follows:

Case IV_CUST_INFO.when 'TAGX'.APPEND 'ZTABLE1' TO et_tables.APPEND 'ZTABLE2' TO et_tables.…when others.APPEND 'ZTABLE3' TO et_tables.APPEND 'ZTABLE4' TO et_tables.endcase.…

● To import or export tables ZTABLE1 and ZTABLE2, enter TAGX in the Additional Information for Customer Exit field.

● To import or export tables ZTABLE3 and ZTABLE4, enter <anything other than TAGX> in the Additional Information for Customer Exit field.

● To import or export no further configuration tables, leave the Additional Information for Customer Exit field empty.

Related Information

SAP Note 1454577 System Copy: Customer Enhancements

8.6 Transporting Task List Variants

You transport task list variants between different systems. In the target system, variants are imported into the specified client only. Transportable task list variants are part of customizing and a customizing request is required if they need to be recorded.

Prerequisites

● You have the authorization to transport task list variants.● The task list variant in the source system starts with the prefix CUS&.● The corresponding task list exists in the source and the target system.



http://help.sap.com/disclaimer?site=http://service.sap.com/sap/support/notes/1454577

Context

NoteDuring a client copy, all variants (local and transportable variants) are copied from the source to the destination client. During installation and upgrade, the delivered SAP variants with the prefix SAP&, are imported into all clients. Existing variants are overwritten.

Procedure


3. Enter the name of the task list that you want to transport.

4. Choose .

5. Choose Task List Variant Transport .6. Enter an existing customizing transport request.

8.7 Importing Task List Runs

Procedure


3. Choose Task List Run Import .4. If required, specify the location where the task list runs are stored.5. Choose the task list run that you want to import.

6. Choose .

Next Steps

After importing a task list run, ensure that you delete the task list run from the file system.



9 Executing Task Lists with the ABAP Task Manager for Lifecycle Management Automation

NoteYou reduce manual effort when you copy or refresh your systems using ABAP post-copy automation with SAP Landscape Virtualization Management. Using SAP Landscape Virtualization Management makes it possible, for example, to:

● Set ABAP system profile parameters automatically● Perform the virtualization or storage-based system copy● Isolate the copied system from the rest of the landscape to avoid conflicts in your system landscape● Resume any task lists run after the system copy during a system refresh procedure

9.1 Executing Task List for Initial System Copy

After the system copy, you execute task list SAP_BASIS_COPY_INITIAL_CONFIG to run the required cleanup and configuration steps automatically.

Prerequisites

● You comply with all prerequisites described in SAP Note 1614266 System Copy: Post Copy Automation (PCA) / LVM.

● Make sure that the following ABAP system profile parameter is set in the copied system (target system) in the default profile:ctc/allow_systemcopy_postconfig = 1Protects your source system. You can execute post-copy automation in the copied system only if this parameter is set.

NoteWhen you execute a system copy/refresh including ABAP post-copy automation (PCA) from SAP Landscape Virtualization Management, SAP Landscape Virtualization Management sets the profile parameters automatically. You must not set the profile parameters manually. You only have to set the profile parameters manually if you execute PCA from the ABAP GUI.

● Make sure that the following is identical on the source system and the target system:

○ Software version○ Post-copy automation SAP Notes

ABAP Post-Copy Automation Configuration GuideExecuting Task Lists with the ABAP Task Manager for Lifecycle Management Automation



○ Task lists

Context

Note● Predefined task lists for ABAP post-copy automation are only available if you own an SAP Landscape

Virtualization Management, enterprise edition license. Contact your SAP representative to obtain a license to make this function available. The task lists are proprietary to SAP and can be overwritten during an upgrade.

● Consider SAP task lists as templates. Save SAP task lists as a copy.

Procedure


3. Enter SAP_BASIS_COPY_INITIAL_CONFIG in the Task List field.

4. Choose .The ABAP task manager for lifecycle management automation assigns a name to the task list run automatically and displays a list of the tasks that are defined for the initial system copy scenario in the order of their execution. Mandatory and necessary tasks are preselected for execution.

5. Some tasks require your input. Choose or in the Parameter column of each task, if applicable. If you do not define mandatory parameters, the ABAP task manager for lifecycle management automation uses default settings, if any, or stops and prompts you for your input. After you have made your settings, save them and go back to the task list.

6. Choose .

7. To get the current status of the task list run, choose .

Related Information


SAP Landscape Virtualization Management, enterprise edition


ABAP Post-Copy Automation Configuration GuideExecuting Task Lists with the ABAP Task Manager for Lifecycle Management

Automation

http://help.sap.com/nwlvm

9.2 Executing Task Lists for System Copy Refresh

Before the system copy, you use task list SAP_BASIS_COPY_REFRESH_EXPORT to export connectivity-related configuration data in the form of table content automatically to the file system using R3trans. After the system copy, you use task list SAP_BASIS_COPY_REFRESH_IMPORT to import connectivity-related configuration data in the form of table content automatically from the file system using R3trans.

Prerequisites

● You comply with all prerequisites described in SAP Note 1614266 System Copy: Post Copy Automation (PCA) / LVM.

● Make sure that the following ABAP system profile parameters are set in the copied system (target system) in the default profile:

○ ctc/allow_systemcopy_postconfig = 1Protects your source system. You can execute post-copy automation in the copied system only if this parameter is set.

NoteWhen you execute a system copy/refresh including ABAP post-copy automation (PCA) from SAP Landscape Virtualization Management, SAP Landscape Virtualization Management sets the profile parameters automatically. You must not set the profile parameters manually. You only have to set the profile parameters manually if you execute PCA from the ABAP GUI.

○ Optional: ctc/export_data = <Directory for export files>Determines the export directory for export files (table content, task list runs, or task list variants) for the system copy refresh scenario. The default value is the path from profile parameter DIR_GLOBAL.

● Make sure that the following are identical in the source system and the target system:

○ Software version○ Post-copy automation SAP Notes○ Task lists

Context

The system refresh is done to overwrite an already existing target system with the latest data from a source system while keeping the configuration. To prevent the target system configuration from being overwritten, you need to export the target system tables that contain connectivity-related configuration information before you start the system copy. After the system copy, you can import this connectivity-related configuration data into the target system again.




Note● Predefined task lists for ABAP post-copy automation are only available if you own an SAP Landscape

Virtualization Management, enterprise edition license. Contact your SAP representative to obtain a license to make this function available. The task lists are proprietary to SAP and can be overwritten during an upgrade.

● Consider SAP task lists as templates. Save SAP task lists as a copy.

Procedure


3. Enter SAP_BASIS_COPY_REFRESH_EXPORT in the Task List field.


5. Some tasks require your input. Choose or in the Parameter column of each task, if applicable. If you do not define mandatory parameters, the ABAP task manager uses default settings, if any, or stops and prompts you for your input. After you have made your settings, save them and go back to the task list.

6. Choose .The ABAP task manager executes all tasks that are in scope.

7. To get the current status of the task list run, choose .8. Perform the system copy.9. Call transaction STC01.

10. Enter SAP_BASIS_COPY_REFRESH_IMPORT in the Task List field.


12. Some tasks require your input. Choose or in the Parameter column of each task, if applicable. If you do not define mandatory parameters, the ABAP task manager uses default settings, if any, or stops and prompts you for your input. After you have made your settings, save them and go back to the task list.

13. Choose .The ABAP task manager for lifecycle management automation executes all tasks that are in scope.

14. To get the current status of the task list run, choose .


ABAP Post-Copy Automation Configuration GuideExecuting Task Lists with the ABAP Task Manager for Lifecycle Management

Automation

Related Information



SAP Landscape Virtualization Management, enterprise edition



http://help.sap.com/nwlvm

10 Important Disclaimers on Legal AspectsThis document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. Regarding link classification, see: http://help.sap.com/disclaimer

Open Source Software and Third Party Components

Please refer to https://scn.sap.com/docs/DOC-42044 for information respecting open source software components made available by SAP as part of SAP NetWeaver and any specific conditions that apply to your use

of such open source software components. Please refer to https://scn.sap.com/docs/DOC-42045 for information relating to SAP’s use of third party software with or within SAP NetWeaver.


ABAP Post-Copy Automation Configuration GuideImportant Disclaimers on Legal Aspects

http://help.sap.com/disclaimer/

http://help.sap.com/disclaimer?site=https://scn.sap.com/docs/DOC-42044

http://help.sap.com/disclaimer?site=https://scn.sap.com/docs/DOC-42045

ABAP Post-Copy Automation Configuration GuideImportant Disclaimers on Legal Aspects


www.sap.com/contactsap

© 2014 SAP AG or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

abap post-copy automation configuration guide_v3.2

Documents

abap task manager

abap pca task lists

task list abap basis

task list variants178

task list runs

task list documentation

copy automation pca

predefined task lists