abap post-copy automation configuration guide

Configuration Guide | PUBLICABAP Post-Copy AutomationDocument Version: 8.0 – 2021-10-11

ABAP Post-Copy Automation Configuration Guide

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Basic Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1 System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.2 System Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.3 Logical System Name Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

6 Predefined Task Lists for ABAP Post-Copy Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106.1 Task List ABAP Basis Copy Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116.2 Task List ABAP Basis Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116.3 Task List ABAP Basis Copy Refresh – Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126.4 Task List ABAP Basis Copy Refresh – Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.5 Task List ABAP Basis Copy BDLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

7 Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147.1 Standard Roles and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147.2 Assigning Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167.3 Authorization Objects for Logical System Name Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

8 How To Assign ABAP Post-Copy Automation Roles for Executing Task Lists. . . . . . . . . . . . . . . 188.1 Recording Authorization Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198.2 Creating ABAP PCA Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228.3 Generating Authorization Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238.4 Adjusting Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268.5 Transporting ABAP PCA Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9 Customizing Post-Copy Automation Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319.1 Displaying Task List Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319.2 Creating Task List Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329.3 Displaying Event Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339.4 Adding Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349.5 Adding Configuration Tables for System Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359.6 Transporting Task List Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369.7 Importing Task List Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2 PUBLICABAP Post-Copy Automation Configuration Guide

Content

9.8 Maintaining Task Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

10 Executing Task Lists with the ABAP Task Manager for Lifecycle Management Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

10.1 Client-Specific Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3910.2 Executing Task List for Initial System Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4010.3 Executing Task Lists for System Copy Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

ABAP Post-Copy Automation Configuration GuideContent PUBLIC 3

1 Introduction

ABAP 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 Management, enterprise edition software and SAP Landscape Management Cloud software. To use ABAP PCA, you must either own an SAP Landscape Management, enterprise edition license or an SAP Landscape Management Cloud subscription.

To run ABAP PCA task lists, you use the following:

● SAP Landscape Management, enterprise editionYou start the execution of a task list in the SAP Landscape 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 nonlicensed ABAP automation tasks for an automated initial setup.

Disclaimer: Nonlicensed usage and storage of ABAP post-copy automation tasks and task list is strictly forbidden. Before you unsubscribe from SAP Landscape Management Cloud or return your SAP Landscape Management, enterprise edition license, you must uninstall all ABAP post-copy automation tasks and task list.


Introduction

2 Document History

Before you start, make sure you have the latest version of this document.

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

Version Date Description

8.0 2021-10-11 ABAP post-copy automation (PCA) is now bundled with the SAP Landscape Management Cloud subscription.

7.0 2021-03-16 New section Client-Specific Configura-tion Tasks [page 39]

6.0 2018-03-15 New section How To Assign ABAP Post-Copy Automation Roles for Executing Task Lists [page 18]

5.0 2016-11-07 Minor changes

4.0 2015-03-10 You now have an overview on which system you must maintain task lists. For more information, see Maintaining Task Lists [page 37].

3.2 2014-04-14 Terminology changes

3.1 2014-03-21 Minor changes

3.0 2014-03-17 Installation content moved to ABAP Post-Copy Automation Installation Guide.

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

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

1.1 2013-07-27 Prerequisites updated

1.0 2013-07-05 Initial version

ABAP Post-Copy Automation Configuration GuideDocument History PUBLIC 5

3 Basic Concepts

This 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 11]

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 11]Task List ABAP Basis Copy Refresh – Export [page 12]Task List ABAP Basis Copy Refresh – Import [page 13]


Basic 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 13]

ABAP Post-Copy Automation Configuration GuideBasic Concepts PUBLIC 7

4 Prerequisites

You have read the ABAP Post-Copy Automation Installation Guide.

For more information, see ABAP Post-Copy Automation Installation Guide.


Prerequisites

https://help.sap.com/viewer/38b28084beaa4247959c1d36c3a68b6b/latest/en-US

5 Important SAP Notes

The 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) / SAP Landscape Management (LaMa)

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.

2350235 SAP Landscape Management 3.0 - Enterprise Edition

Contains the latest information about supported IT infrastructure elements.

1709155 System Provisioning with SAP Landscape Management

Contains the latest information about system provisioning with SAP Landscape 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 PUBLIC 9

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





6 Predefined Task Lists for ABAP Post-Copy Automation

SAP 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 Management, enterprise edition license or an SAP Landscape Management Cloud subscription. 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.

Disclaimer: Nonlicensed usage and storage of ABAP post-copy automation tasks and task list is strictly forbidden. Before you unsubscribe from SAP Landscape Management Cloud or return your SAP Landscape Management, enterprise edition license, you must uninstall all ABAP post-copy automation tasks and task list.

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 ABAP Post-Copy Automation for SAP BW Configuration Guide.

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

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

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

Task List ABAP Basis Copy Refresh – Export [page 12]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 13]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.

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


Predefined Task Lists for ABAP Post-Copy Automation

https://help.sap.com/viewer/89fdefbec1094207a50273f7d477b9ac/latest/en-US

Related Information

Client-Specific Configuration Tasks [page 39]

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 ABAP Post-Copy Automation for SAP BW Configuration Guide.

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.

Related Information


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 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.

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





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 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.

Related Information


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.

Related Information



Predefined Task Lists for ABAP Post-Copy Automation



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.

Related Information


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.

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





7 Security Considerations

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

Standard Roles and Permissions [page 14]This section shows the standard roles and permissions that are used for ABAP post-copy automation activities.

Assigning Roles [page 16]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 Management using remote access.

Authorization Objects for Logical System Name Conversion [page 17]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.

7.1 Standard Roles and Permissions

This section 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)




Security Considerations


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)




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.



● Create task list variants (transaction STC01


● Transport task list variants (transaction STC01)

ABAP Post-Copy Automation Configuration GuideSecurity Considerations PUBLIC 15


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● SAP_BC_STC_CUST




● 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 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.


Security Considerations

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> *

ABAP Post-Copy Automation Configuration GuideSecurity Considerations PUBLIC 17

8 How To Assign ABAP Post-Copy Automation Roles for Executing Task Lists

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

You have the following options:

Use SAP standard user

● DDICWith profile SAP_ALL

● <PCAUser>With profile SAP_ALL

● SAP_ALLThis is the most convenient way.

If you do not want to assign any of your users the profile SAP_ALL, proceed as follows:

1. Recording Authorization Checks [page 19]You use the system trace to record authorization checks for ABAP post-copy automation. In this example, you record authorization checks for task list SAP_BASIS_COPY_REFRESH_EXPORT.

2. Creating ABAP PCA Role [page 22]You use transaction PFCG to create a role in your customer namespace for executing ABAP post-copy automation tasks and task lists. In this example, you create the role A_PCA_REFRESH.

3. Generating Authorization Profile [page 23]You assign all authorization objects recorded during the authorization check to the ABAP PCA role created.

4. Adjusting Authorization Objects [page 26]You add authorization values to the authorization objects assigned to the ABAP PCA role.

5. Transporting ABAP PCA Role [page 29]You transport the ABAP PCA role created to the systems required for running ABAP post-copy automation tasks and task lists.


How To Assign ABAP Post-Copy Automation Roles for Executing Task Lists

8.1 Recording Authorization Checks

You use the system trace to record authorization checks for ABAP post-copy automation. In this example, you record authorization checks for task list SAP_BASIS_COPY_REFRESH_EXPORT.

Procedure

1. Call transaction STAUTHTRACE.

The trace in transaction STAUTHTRACE evaluates authorization checks.

2. Specify the trace options for the special user such as DDIC or <PCAUser> with profile SAP_ALL.

3. To start the trace, choose Activate Trace ( F6 ).

Authorization trace is switched on. The system writes the trace data in the current trace file.

ABAP Post-Copy Automation Configuration GuideHow To Assign ABAP Post-Copy Automation Roles for Executing Task Lists PUBLIC 19

4. Call transaction STC01 with the same user you activated the authorization trace.

5. Enter SAP_BASIS_COPY_REFRESH_EXPORT in the Task List field.

6. Choose .

7. To set all tasks in scope, choose .

8. Choose .

9. Wait until the task list SAP_BASIS_COPY_REFRESH_EXPORT is finished.

10. Call transaction STAUTHTRACE.

11. To deactivate the authorization trace, choose Deactivate Trace ( F7 ).

Authorization trace is switched off.12. In the Restrictions for the Evaluation section, adapt the evaluation time frame. Ensure that the From date

and time is in the past.



13. To display the collected trace data, choose Evaluate.

Ensure that you evaluate the trace with the correct user.

14. To receive a plain overview of the authorization objects, mark column Object until column Value 5.

15. To sort the trace data ascending, choose .


Task overview: How To Assign ABAP Post-Copy Automation Roles for Executing Task Lists [page 18]

Next task: Creating ABAP PCA Role [page 22]

8.2 Creating ABAP PCA Role

You use transaction PFCG to create a role in your customer namespace for executing ABAP post-copy automation tasks and task lists. In this example, you create the role A_PCA_REFRESH.

Procedure

1. In alternate mode call transaction Role Maintenance (PFCG). Enter command /oPFCG.

2. To create a role in your customer namespace, enter the role name. For example A_PCA_REFRESH.

3. Choose Single Role.

4. Enter a description. For example PCA refresh role.

5. Save your entries.




Previous task: Recording Authorization Checks [page 19]

Next task: Generating Authorization Profile [page 23]

8.3 Generating Authorization Profile

You assign all authorization objects recorded during the authorization check to the ABAP PCA role created.

Procedure

1. On the start screen of transaction PFCG, choose tab Authorizations.

2. Choose Change Authorization Data.

3. Confirm the dialog box.


4. Choose Do not select templates.

5. Choose Manually.

6. Add all authorization objects displayed in column Object of the System Trace for Authorization Checks to the dialog box Manual selection of authorizations.



7. Repeat step 5 and 6 until you reached the end of authorization trace.8. Save your entries.

9. Confirm the dialog box.

10. To generate the profile, choose .


Previous task: Creating ABAP PCA Role [page 22]

Next task: Adjusting Authorization Objects [page 26]


8.4 Adjusting Authorization Objects

You add authorization values to the authorization objects assigned to the ABAP PCA role.

Procedure

1. Go to back to start screen of transaction PFCG.

2. Choose tab Authorizations.3. Choose Change Authorization Data.

4. Choose Trace.



5. Choose Evaluate Trace System Trace (ST01) Local .

6. Choose Evaluate.

Ensure that you have selected the trace by the appropriate user and time frame.

7. To add authorization values to the authorization objects, start with the first authorization object from the dropdown. In this example start with authorization object B_ALE_MODL.

8. Mark all values.


9. To receive all values, choose Transfer.

10. To receive all additional values, choose Full Authorization.

11. All authorization values are added to the authorization object.12. Repeat the steps 9 – 12 for each authorization object listed in the dropdown.

13. Confirm with Enter .

14. Save your entries.

15. To generate the role, choose .



The status of the role is now green.16. Add the role to the regarding <PCAUser>.


Previous task: Generating Authorization Profile [page 23]

Next task: Transporting ABAP PCA Role [page 29]

8.5 Transporting ABAP PCA RoleYou transport the ABAP PCA role created to the systems required for running ABAP post-copy automation tasks and task lists.

Procedure

1. Call transaction PFCG.

2. On the entry screen of transaction PFCG, choose .

3. Choose .


The request contains all green roles.

4. Transport this role to the systems required for running a system refresh.


Previous task: Adjusting Authorization Objects [page 26]



9 Customizing Post-Copy Automation Content

You adapt ABAP post-copy automation content to your needs by using the ABAP task manager for lifecycle management automation.

Displaying Task List Documentation [page 31]Get the complete documentation of the task list with a detailed task description.

Creating Task List Variants [page 32]You customize a task list according to your needs.

Displaying Event Tasks [page 33]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.

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

Adding Configuration Tables for System Copy Refresh [page 35]Enhance the list of configuration tables that are processed by import and export functions.

Transporting Task List Variants [page 36]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.

Importing Task List Runs [page 37]

Maintaining Task Lists [page 37]This section gives an overview on which system you must maintain task lists before system copy.

9.1 Displaying Task List Documentation

Get the complete documentation of the task list with a detailed task description.

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 Display Task List.

ABAP Post-Copy Automation Configuration GuideCustomizing Post-Copy Automation Content PUBLIC 31

5. Choose Goto Documentation Display with Task Docu .

Results

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

9.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 Create New Variant.5. Enter the name for the task list variant.

6. Choose Continue.The ABAP task manager for lifecycle 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 lifecycle 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 Change Parameter or Fill Parameter 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 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.

8. Save the task list variant.

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


Customizing Post-Copy Automation Content

Related Information

Adding Reports [page 34]

9.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 Display Task List.6. In the task list, select the task with task type Event.7. From the context menu, choose Show Event Tasks.


9.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 Edit.The ABAP task manager for lifecycle management automation displays the task list.

5. Choose Add Task.6. Optional: On the Task Reports tab, enter your search criteria.

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

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



9.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 Generate Task List Run.5. Select the task Export Customer defined Configuration Tables or Import Customer

defined Configuration Tables.

6. Choose Change Parameter 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.

Example

A 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

9.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.

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




http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fnotes%2F1454577

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

4. Choose Display Variants.

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

9.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 Continue.

Next Steps

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

9.8 Maintaining Task Lists

This section gives an overview on which system you must maintain task lists before system copy.

Task List TST System PRD System

Task List ABAP Basis Copy Initial Configuration [page 11]

not applicable x

Task List ABAP Basis Copy Refresh [page 11]

x not applicable

Task List ABAP Basis Copy Refresh – Export [page 12]

x not applicable

Task List ABAP Basis Copy Refresh – Import [page 13]

not applicable x

Task List ABAP Basis Copy BDLS [page 13]

not applicable x


Related Information

Transporting Task List Variants [page 36]Creating Task List Variants [page 32]



10 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 the enterprise edition of SAP Landscape Management. Using SAP Landscape 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

Client-Specific Configuration Tasks [page 39]This section provides an overview of client-specific configuration tasks.

Executing Task List for Initial System Copy [page 40]After the system copy, you execute task list SAP_BASIS_COPY_INITIAL_CONFIG to run the required cleanup and configuration steps automatically.

Executing Task Lists for System Copy Refresh [page 42]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.

10.1 Client-Specific Configuration Tasks

This section provides an overview of client-specific configuration tasks.

The following configuration tasks must run in client 000:

Task Task List

CL_STCT_SC_CONFIG_TMS_SINGLE SAP_BASIS_COPY_INITIAL_CONFIGSAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_PREPARE_TMS SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

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

If you run a task list in client 000, check and, if necessary, run the following configuration tasks also in a business client:

Task Task List

CL_STCT_SC_CLEANUP_TC_TASKRUN SAP_BASIS_COPY_INITIAL_CONFIGSAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_CLEANUP_TC_TASKVARI SAP_BASIS_COPY_INITIAL_CONFIGSAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_CLEANUP_SCOT SAP_BASIS_COPY_INITIAL_CONFIGSAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_PREPARE_BCSDUSER SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_EXPORT

CL_STCT_SC_IMPORT_SCOT SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_IMPORT_SAPOFFICE SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_POSTPROC_SAPOFFICE SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_POSTPROC_SAPOFFICE1 SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_IMPORT_TC_TASKRUN SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

CL_STCT_SC_POSTPROC_RHOMATTR SAP_BASIS_COPY_REFRESHSAP_BASIS_COPY_REFRESH_IMPORT

10.2 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) / SAP Landscape Management (LaMa).

40 PUBLIC

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

Automation


● 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 Management, SAP Landscape 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○ Task lists

Context

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

Management, enterprise edition license, or an SAP Landscape Management Cloud subscription. 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 Generate Task List Run.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 Change Parameter or Fill Parameter 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 Start/Resume Task List Run in Background.


7. To get the current status of the task list run, choose Refresh Task List Run.

Related Information

Task List ABAP Basis Copy Initial Configuration [page 11]SAP Landscape Management 3.0, enterprise edition

10.3 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) / SAP Landscape Management (LaMa).

● 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 = 1

Protects 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 Management, SAP Landscape 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

42 PUBLIC


Automation

https://help.sap.com/viewer/p/SAP_LANDSCAPE_MANAGEMENT_ENTERPRISE


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

Management, enterprise edition license, or an SAP Landscape Management Cloud subscription. 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 Change Parameter or Fill Parameter 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 Start/Resume Task List Run in Background.The ABAP task manager executes all tasks that are in scope.

7. To get the current status of the task list run, choose Refresh Task List Run.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 Change Parameter or Fill Parameter 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 Start/Resume Task List Run in Background.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 Refresh Task List Run.

Related Information

Task List ABAP Basis Copy Refresh – Export [page 12]Task List ABAP Basis Copy Refresh – Import [page 13]SAP Landscape Management 3.0, enterprise edition

44 PUBLIC


Automation

https://help.sap.com/viewer/p/SAP_LANDSCAPE_MANAGEMENT_ENTERPRISE

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

ABAP Post-Copy Automation Configuration GuideImportant Disclaimers and Legal Information PUBLIC 45

www.sap.com/contactsap

© 2021 SAP SE 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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 SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

abap post-copy automation configuration guide

Documents