Performing the ABAP Post-Copy Automation

The figure, ABAP PCA Overview, shows PCA in system copy and system refresh with a focus on post-processing after the system copy in SAP Basis for ABAP-based systems (like SAP ERP) and exporting and importing of configuration data while refreshing an existing system.

State of the art implementation with SAP Note transport-based correction instructions. SAP Note transport-based correction instructions (TCI) is a new way to deliver ABAP correction instructions in a flexible manner and is a composition of objects only related to a specific software package or software component, for example, PCA content.

• Contains specific, single corrections.

• CI can be valid for an SP range and can depend on other CIs.

• Can be implemented automatically for all supported objects.

• Contains corrections of only one specific functional area, which is an encapsulated sub-component.

• Can contain multiple single corrections, which reduces CI dependencies and update artifacts.

• Can be valid for an SP range and can have dependency on other TCIs and CIs.

• Contains an ABAP transport similar to SP deliveries, but is delivered together with SAP Notes as new type of CIs.

• Simplified and accelerated consumption of corrections.

Enable the Note Assistant for TCI as described in the official documentation for SAP TCI.

Implement the TCI for PCA as described in the official documentation for SAP TCI. SAP Notes contain the TCI required for PCA.

Do not implement the following SAP Note, but perform the manual activities (the table shows with which SPS the correction is already included):

Implement SAP Note 1771909 — System Copy: Corrections for Web Service (SOAP).

Use the program A_SAP_NOTE_ANALYZER to ensure that the requirements for using ABAP post-copy automation are met and implement missing SAP Notes.

Activate the usage of PCA and enable the execution of PCA task lists.

Clean-up

Deletion of obsolete information from the original system in the target system.

For example:

• Clean-up of ABAP basis tables.

• Batch jobs.

• DBA cockpit configuration.

• Remote Function Call (RFC) in or outbound queue.

• Spool requests.

• TRUST manager configuration.

Post copy configuration

Adaption of ABAP basis configuration settings.

For example:

• Configuration of standard jobs.

• Licenses.

• Logon groups.

• System profiles.

• Operation modes.

• Secure store.

• Spool and TMS.

• Scheduling in DBA planning calendar.

• Scheduling of job RDDIMPDP.

Pre-checks

Perform checks to ensure consistency and actual use case.

For example, perform initial consistency check (SICK) and check whether copied system is SAP NetWeaver Business Warehouse system or connected to SAP NetWeaver BW.

Retaining existing configuration

Export and import of existing configuration settings to ensure they are retained after system refresh.

For example:

• Application Link Enabling (ALE).

• Archiving.

• Batch jobs or server groups.

• CCMS.

• Customer-defined tables.

• OS commands.

• Licenses.

• Log-on groups.

• Operation modes.

• Printers and spools.

• RFC

• SLD

• SCOT

• STRUST

• TMS

• Users (all, selected clients, exclude).

Clean-up and post-copy configuration

Deletion of obsolete information from original system in target system. If required, additional adaptation of ABAP basis configuration settings.

In addition to the basis task lists presented above, there are more and more application-specific task lists available. For example, task lists for SAP NetWeaver Business Warehouse (SAP NetWeaver BW). In addition to specific tasks for application systems, these task lists also contain required basis tasks. Task lists cover both SAP NetWeaver BW systems and SAP NetWeaver BW source systems (that is, SAP systems connected to SAP NetWeaver BW). If you copy or refresh an SAP NetWeaver BW system and an SAP NetWeaver BW source system, do not use the ABAP PCA task lists, but the SAP NetWeaver BW PCA task lists.

SAP Landscape Management only handles homogenous system copies and refreshes, if you want to automate the post-activities of initial heterogeneous system copies, you can execute ABAP post-copy automation standalone (not integrated into end-to-end process of SAP Landscape Management.

• Framework for automation of ABAP tasks.

• Part of every ABAP system (as of certain release or SP level).

• Easy-to-use for everybody familiar with SAP NetWeaver ABAP systems (similar to SE38).

• Customizing of SAP predelivered task lists.

• Creation of customer-specific task lists.

• Variant maintenance of task lists.

• Check mode for all tasks.

• Resume of task lists in case of error.

• Interrupt of task list execution.

• Local or decentralize execution.

• Parallel execution on multiple systems.

• Execution in dialog or background.

The technical name for ABAP Basis copy initial configuration is SAP_BASIS_COPY_INITIAL_CONFIG. It performs several clean-up and configuration steps on the ABAP target system. Data clean-up is required to delete the content of the tables that contain the source system information in the target system. This prevents the target system from interfering with the source system and other connected systems.

The technical name for ABAP Basis copy BDLS is SAP_BASIS_COPY_BDLS. It corrects the logical system name and configures a new name in all relevant tables for all partner systems in the target system.

The task list is not relevant if your system is an SAP BW system or connected to a BW as SAP BW source system.

The technical name for ABAP Basis copy refresh is SAP_BASIS_COPY_REFRESH. It is intended for integrated use of ABAP post-copy automation (with integration into SAP Landscape Management). It exports the target system tables that contain configuration information before you start the system refresh and imports them afterwards. The task list runs in the following sequence:

Export phase

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

Stop phase

The task list run stops so that SAP Landscape Management can perform the physical system copy (task CL_STCT_SC_CONFIRM_COPY).

Cleanup phase

The system deletes the content of tables that contain source system information.

Import phase

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

Configuration phase

The ABAP task manager for lifecycle management automation adapts the configuration to the target system.

The technical name for ABAP Basis copy refresh export is SAP_BASIS_COPY_REFRESH_EXPORT. It exports 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 technical name for ABAP Basis copy refresh import is SAP_BASIS_COPY_REFRESH_IMPORT. It imports 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.

There are no specfic SAP Business Suite task lists — use SAP_BASIS_COPY_REFRESH*. SAP Business Suite application-specific tasks are handled by event tasks. Within the SAP_BASIS_COPY_REFRESH* task lists, the even task, CL_STCT_SC_EVENT_POST_* exists. This event task is responsible for including the business suite application tasks into the task list. PCA selects only the relevant business suite application tasks for the respective system — all other tasks will not be executed.

Refresh of SAP CRM systems exports and imports configuration tasks for refreshing SAP CRM, related to connectivity inside target system or to systems outside. Only for refreshing one isolated systems — related systems are not changed.

The following is an overview of configuration tasks in SAP CRM:

• Export CRM Middleware Configuration.

• Export CRM Component Configuration.

• Export CRM WebClient Configuration.

• Import CRM Middleware Configuration.

• Import CRM Component Configuration.

Refresh of SAP EWM systems exports and imports configuration tasks for refreshing SA EWM. It is related to connectivity inside target system or to systems outside. This is only for the refreshing of one isolated systems, related systems are not changed.

The following is an overview of configuration tasks in SAP EWM:

• Export EWM Server Configuration.

• Export EWM Interface Configuration.

• Import EWM Server Configuration.

Refresh of SAP GTS systems export and import configuration tasks for refreshing SAP GTS. It is related to connectivity inside the target system or to systems outside. This is only for the refreshing of one isolated systems, related systems are not changed.

The following is an overview of configuration tasks in SAP GTS systems:

• Export GTS Component Configuration.

• Import GTS Component Configuration.

Refresh of SAP SCM systems exports and imports configuration tasks for refreshing SAP SCM. It is related to connectivity inside target system or to systems outside. This is only for the refreshing of one isolated systems, related systems are not changed.

The following is an overview of configuration tasks in SAP SCM:

• Export SCM Basis Integration Configuration.

• Export SCM Server Integration Configuration.

• Import SCM Basis Integration Configuration.

• Import SCM Server Integration Configuration.

Refresh of SAP SRM systems exports and imports configuration tasks for refreshing SAP SRM. It is related to connectivity inside the target system or to systems outside. This is only for the refreshing of one isolated systems, related systems are not changed.

The following is an overview of configuration tasks in SAP SRM:

• Export SRM Component Configuration.

• Import SRM Component Configuration.

You can start the note analyzer implementation in your first system (for example, the development system) and transport the program to all following systems in your landscape. With the note analyzer in all systems, you can check the complete and successful implementation of all required notes. You should regularly check the following notes:

• SAP Note: 1614266 — System Copy: Post-Copy Automation (PCA)/LVM

• SAP Note: 1707321 — BW System Copy: Post Copy Automation (BW-PCA) (if your system is a BW or BW source system) for the latest checks choose Basis_Content_<version>.xml and BW_and_SAPI_Content.xml

You should always start the implementation of SAP Notes in your first system (for example, the development system) and transport the changes to all following systems in your landscape.

Take care that all your systems within your landscape have the same SAP Notes implemented.

You can use the task Export Customer Defined Configuration Tables or Cleanup of Customer Defined Configuration Tables to add customer-specific tables to the list of handled tables, for more information, refer to SAP Note: 1454577.

Start the BADI implementation in your first system (for example, the development system) and transport the enhancement to all following systems (that you want to copy or refresh) in your landscape.

Without the BADI in all systems, you may experience problems during a system refresh.

Create the variants for your task lists in Client 000 in your first system (such as the development system), and transport the variants to all following systems in your landscape. The names of variants that need to be transported must start with cus&. Variants are customizable and therefore are client dependent. If SAP delivered default task lists are suitable for you, create your variants for these task lists. The advantage of this is that with every update of the default lists, your variants can be migrated to the new content.

You should always execute task lists in Client 000 and you should always log on with the language EN. Some basic tasks can only be executed in Client 000. For all the tasks that need to be executed in the productive client, PCA connects via RFC.

Access PCA standalone using the transaction STC01 Task Manager for Technical Configuration. You can prepare your target system for SAP* logon. SAP* is the only user that is able to log on to the system and run the required task list after the database refresh.

If your task list run doesn’t appear in the import dialog in STC02, enter the name in the dialog box as follows:

• Name of the session, for example: STCTM.SAP_BW_BASIS_COPY_REFRESH_CONFIG_<date>.XML

• Name to enter in the Import dialog: SAP_BW_BASIS_COPY_REFRESH_CONFIG_<date>

  Leave out the STCTM at the beginning and the .XML at the end.

While upgrading your system with a Support Package after implementing SAP Notes for PCA, you will find some PCA objects in SPDD/SPAU. For more information, refer to SAP Notes 1928090 — Handle PCA SAP Notes for SPDD/SPAU Comparison.

Use the parameter ctc/allow_systemcopy_postconfig = 1. By setting this parameter you allow ABAP PCA to be executed on that system. The parameter needs to be set in DEFAULT.PFL. You do not set this parameter in productive systems.

ABAP PCA provides task lists with a predefined sequence of configuration tasks to configure extensive technical scenarios automatically. To run ABAP PCA task lists, you need the following:

• A valid license.

• The latest update for ABAP Task Content for PCA. Update via the program Z_SAP_NOTE_ANALYZER or SAP Note Transport-Based Correction Instructions.

• The latest update for content for Task Manager for Technical Configuration. Update via the program Z_SAP_NOTE_ANALYZER or SAP Note Transport-Based Correction Instructions.

• Log on to your ABAP system with the logon language set to English.

• Log on to Client 000 in your ABAP system.

The figure, Calling Task Manager for Technical Configuration, shows how to call the Task Manager for Technical configuration with the transaction code STC01. The Task Manager for Technical Configuration is your central access point to work with the task list.

The ABAP Task Manager for Technical Configuration allows you to do the following:

• Display task lists or your variants.

• Copy default task list.

• Create your own task lists or variants of default task lists, which are delivered by SAP.

• Edit task lists or your variants.

• Delete task lists or your variants.

• Call the online help.

• Execute task lists (using variants).

The figure, Display Task Lists, shows you can get detailed information about certain task lists with the display function, SAP_BASIS_COPY_REFRESH. On the Display Task List SAP_BASIS_COPY_REFRESH, Build 00008 screen, you can change to Edit mode, perform a consistency check (to check if prerequisites are met), and read the documentation of each task.

The figure, Display Online Help, shows how to access the Help function and further information. There is also the option to access Online Help.

Task lists are proprietary to SAP and can be overwritten during an upgrade. It is recommended to think of SAP task lists as templates and to save a copy under a different name. To do this on your keyboard, press F7 Copy Task List to create a copy of the default tasks list and use the customer namespace Z*. You can then copy the documentation.

An event represents a predefined location inside a task list where an extension is possible. You can develop your own ABAP classes (tasks) that are triggered by event. You can use the events provided to extend the task lists with their own code without modification. The actual tasks extending the task list is determined only at runtime. As a result, events introduce an abstraction layer that enables both the reliable extensibility of task lists and the layering of automation scenarios.

You can use the task, Export/Import Customer Defined Configuration Tables or Cleanup of Customer Defined Configuration Tables to add customer-specific tables to the list of handled tables. For more information on how to implement the BADI, refer to SAP Note: 1454577 — System Copy: Customer Enhancements.

You should start the BADI implementation in your first system (for example, the development system) and transport the enhancement to all following systems in your landscape that you want to copy or refresh. Without the BADI in all systems, you may experience problems during a system refresh.

You can move tasks to create the sequence according to your needs. To do this select the task, move the task up or down, and move the task to the start or end.

The following are the options for creating variants:

• Create variants for default task lists delivered by SAP, if these are suitable for you.

  Advantage: If the content of the default task lists are updated via SPs/Notes, you can migrate your variant to new content.

• Create variant for Z* lists (shown in the figure, Variants — Creation)

  Advantage: Adjust the Z* lists to your needs (for example, add or delete tasks).

Some tasks within the task list have parameters that need to be maintained. You decide for each task if you want to edit the parameters. If you do not maintain mandatory parameters, the ABAP Task Manager uses default settings, if any, or stops and prompts you for input.

Variants allow you to save different parameter settings for each task. Each task list can contain several variants and each of these variants can contain different parameter settings. You can use variants to save different parameter settings for different use cases.

After changing the parameter settings for specific parameters, you need to save the settings. After you have finished maintaining the variant, you must save it.

When you no longer need a variant, you can delete it using the transaction, STC01. Enter the name of the task list and select Delete Variants. Select the variant you want to delete and delete it.

To execute a variant, log on to Client 000 with the language EN. Call the transaction STC01, select the task list, and choose Generate Task List Run with Variant.

You can either execute the task list in dialog or in background mode. Always execute task lists in Client 000.

To monitor your current task list execution or view previous runs, call the Task List Run Monitor via the transaction STC02. After starting a task list in background mode, it is possible to monitor the status of the task list as it runs.

For several use cases, you have to assign unique IDs to systems participating in a distributed environment, for example:

• Communication partners in Application Linking and Enabling (ALE) scenarios.

  Interface technology developed by SAP to loosely connect application systems (SAP and external systems) with one another.

• Communication partners in an SAP Business Warehouse scenario.

  Connecting SAP BW systems and SAP BW source systems.

• Communication partners in central user administration.

For systems based on SAP NetWeaver ABAP, logical system names are defined as unique IDs.

You assign a name explicitly to one client in an SAP system, as seen in the figure, BDLS With PCA Introduction.

In case of a system copy or a system refresh, logical system names get duplicated and you have to convert them afterwards to get the unique IDs again.

To convert one or more logical system names to new or existing logical names, you use transaction BDLS. This determines all relevant tables (such as application tables, master data tables, and control data tables) using specific logical system names and converts the corresponding table entries (field values) to a different logical system name.

The BDLS transaction determines all active, transparent database tables where the fields reference the domains, LOGSYS and EDI_PARNUM. It converts corresponding field values to new logical system names and updates the database.

Logical system name conversion usually takes a long time, as the standard conversion program used by BDLS scans all tables in your system and converts the corresponding logical system names — especially in case your system uses many logical system names, or has very large tables (such as in the range of a billion table entries). This most probably results in a long-running conversion task.

ABAP PCA for BDLS allows you to do the following:

• Define more than one conversion name pair.

• Execute concurrent jobs for performance improvements.

• Execute the BDLS conversion in clients other than the executing client and in multiple clients.

• Use built-in checks to verify the parameter consistency.

• Execute the conversion with background jobs.

If the achieved runtime does not meet your requirements, you can further optimize by reducing the amount of tables for conversion — for this, you select the Job Execution, Concurrent Jobs based on Table Entry to process according to the table entry and get several options to run a detailed analysis to isolate tables affected by the logical system name change.

PCA offers tasks based on standard BDLS that already contain several improvements compared to the transaction BDLS. Using BDLS with PCA, it is possible to define more than one conversion name pair. Furthermore, it is possible to execute concurrent jobs for performance improvements and to execute the BDLS conversion in clients other than the executing client. The conversion execution is done with background jobs.

To parallelize, choose the job execution mode, Concurrent Jobs based on Table Name in the BDLS conversion task.

To improve performance, enter a value in the field, Number of Enterprise per Commit. This value should be as large as possible, depending on the limits of the database roll area.

Select one of the following job execution modes:

• Job execution mode 1: Single Job Execution.

  You can select this execution mode only for single pair conversion. This will execute the program RBDLSMAP or RBDLSMAP2 in a single job called SAP_SCTC_RBDLSMAP.

• Job execution mode 1: Concurrent Jobs Based on Table Name.

To enable job execution mode two, Concurrent Jobs Based on Table Name, the local server must have at least four work processes of type batch. This option executes the job RBDLSMAP. Each job converts tables whose names start with a certain prefix and the jobs start with the prefix, SAP_SCTC_BDLS. In addition, the monitoring job SAP_SCTC_BDLS_SYNCH, starts. This job waits until all concurrent jobs are finished. It executes the program RBDLSMAP or RBDLSMAP2 to start the job SAP_SCTC_RBDLSMAP for the special tables defined in exits. All tables defined in tables BDLSEXT and BDLSEXZ are not processed concurrently.

For more information on how to enable job execution mode three, Concurrent Jobs Based on Table Entry, see the following section, PCA — Optimized BDLS Tasks.

To automatically release all scheduled jobs in the configured clients, select the Release Jobs checkbox. If the checkbox is deselected, the jobs will be created in status Planned and you will have to release the jobs manually in the transaction SM37. It is possible to release jobs with the prefix, SAP_SCTC_BDLS<Client> in parallel, but you must ensure to release the job SAP_SCTC_BDLS_SYNCH_<Client> at the end.

To set the local client conversion, no RFC destination is required. To set multiple client conversions, maintain RFC destinations. For the local client, maintain destination NONE. All destinations are checked against the configured client. The remote client execution is only allowed in the local system. The first client with assigned RFC destination is always set for client-dependent and independent table conversion. Additionally maintained clients are then set only for client-dependent table conversion. The conversion takes place in one client after another.

To further reduce the runtime of the PCA BDLS task you can reduce the amount of tables for the conversion. Analyze the system corresponding to logical names and choose Concurrent Jobs based on Table Entry in the BDLS conversion task.

Choose when and how the detailed analysis should run in order to isolate tables affected by the required logical system name change. All options use the report, RBDLS_CHECK, which determines the number of logical systems in relevant tables, but embeds this feature in different ways. The RBDLS_CHECK generates a list of tables and table fields that might contain values that are equal to given list logical system names and it counts the number of occurrences of these logical system names within these table fields.

Results of the analysis get stored in the BDSLCOUTNALL table. Relevant tables and values are automatically passed to the BDLS conversion task CL_STCT_SC_CONV_BDLS as input parameters, which will create separate jobs with specific sets of tables, such that each job converts approximately the same number of table entries.

Option A allows you to run the report, RBDLS_CHECK before the system copy in the source system. Existing analysis from execution of the report, RBDLS_CHECK is used, if the report was executed with corresponding logical system names. The report can be called using the transaction code SE38, either in the source or original system of the copy of in the local system (the copy), because analysis results are stored persistently and are copied together with the system itself. The execution of the analysis in the source or original system can reduce BDLS execution time significantly, as it allows a visual inspection of the table structure before the copy procedure. It enables you to define your optimization strategy early, improves planning of your system copy project, and is especially interesting in SAP BW systems, since certain generated SAP BW tables might be excluded from conversion or change of the data model using SAP Note: 1894679 might be applied.

In any case, potentially time consuming analysis is then prior to time-critical post-copy activities.

Option B allows you to run table analysis within the execution of the BDLS conversion, an analysis of logical system names is executed within the task directly before conversion to determine corresponding relevant tables. The analysis is not done as a separate task, but within BDLS conversion task itself. This is interesting, especially if it is organizationally not possible to execute the report, RBDLS_CHECK prior to task list execution. This means that the result remains valid until execution takes place or the source or original system is not accessible before.

Since analysis and conversion are combined within the BDLS conversion task, only logical system names entered for conversion will be analyzed,

Since analysis itself is time-consuming as well, significant overall performance gain can only be expected (compared to parallelization by table name), if histogram is very distinct from equal distribution, meaning that some tables contain many more entries than most other tables (such as for SAP BW, where most tables start with R).

In your task list run, choose Fill Parameters for the conversion of the Logical System Names task. Specify the mapping of logical system names that you plan to convert (by entering old name or new name pairs).

To determine multiple old logical system names, choose Multiple Selection and enter all name pairs to be converted (lower limit = old name, upper limit = new name).

In Option C, you add a BDLS analysis task manually to the BDLS task list prior to conversion task. Option C is basically the same as Option B, however with the BDLS analysis task (CL_STCT_SC_PREPARE_BDLS) and with the option to run the analysis standalone, before the conversion. The BDLS analysis task CL_STCT_SC_PREPARE_BDLS) executes the report, RBDLS_CHECK and generates a list of relevant tables for optimizing the actual BDLS conversion task.

Similar to Option B, Option C is interesting if it is not organizationally possible to analyze prior to task list execution.

Option C is only enabled in the BDLS conversion task, if the BDLS analysis task is placed in the same task list. The UI is the same as the report, RBDSL_CHECK — customers who have already used this option before can reuse their corresponding task list variants.

It is not recommended to use this option in SAP BW PCA task lists.

An overall performance gain can be expected (compared to parallelization by table name), if the histogram is very distinct from an equal distribution. This means that some tables contain many more entries than most other tables or if the names of the tables cluster for certain letters (such as for SAP BW, where most tables start with R).

In Option C, you add the tasks Analysis of Logical System Names and Configuration: BDLS Prepare Task Successfully finished? to your task list. Both tasks can be found with the task class search pattern, "*BDLS+".

The tasks, Analysis of Logical Systems Names and Confirmation: BDLS Prepare Task Successfully finished? need to be performed in the mentioned order before running the conversion of logical system names.

This setup enables the transfer of parameters from the preparation task to the conversion task when the UI is accessed.

After the successful running of Analysis of Logical System Names, a protocol link will be available displaying the execution results.

Additionally, parameters turned over to the Conversion of Logical System Names task are checked for consistency during the conversion task check phase.

This task is equivalent execute the report, RBDLS_CHECK, in the transaction SE38 manually.

If starting the report manually, or in a separate task list (without the conversion task), make sure that the results are manually copied to the conversion task and take care that the input parameters and result parameters are consistent.

In the configuration task, Analysis of Logical System Names, you specify only the old logical system names that you plan to convert. To determine multiple old logical system names, choose Multiple Selection.

The value in the Number of Entries for Each Package field is only relevant for conversion. To improve performance, enter the largest possible value, depending on the limits of the database roll area.

In the field, Tables, specify or exclude tables for analysis, and therefore target-specific tables in the database. To determine all related tables, leave the Tables field empty. To determine selected tables, choose Multiple Selection.

To determine the relevant tables for all configured clients, select the Cross-Client checkbox.

To use additional system resources and speed up the processing time, select the Parallel Processing Active checkbox.

This task could run for a long time. However, it only performs Read operations and can be started online. SAP recommend the following:

• Execute this task in advance as preparation to the actual conversion task.

• Use this task in the same task list as the conversion task.

You can manually confirm that the BDLS preparation task STCT_SC_PREP_BDLS is finished. Check the values of the BDLS conversion task STCT_SC_CONV_BDLS. Check the conversion pairs of the logical system names. Check the value in the Number of Entries per Commit field. Check the following job execution mode is selected.

The task Concurrent Jobs Based on Table Entry checks that the server has at least four work processes of type and batch. It executes concurrent jobs using the program, RBDSLMAP. The number of created parallel batch jobs is equal to the number of the configured batch work process. The distribution of tables among jobs depends on the sorted order of logical system name entry count, based on the preparation task result. The table with the highest entry count will be processed by the first batch job. Tables with lesser entries are processed by later batch jobs. The job names start with the prefix SAP_SCTC_BDLS.

In addition, the job, SAP_SCTC_BDLS_SYNCH is started. This monitoring job only waits until all concurrent jobs are finished. Then, it executes the program, SAP_SCTC_RBDLSMAP to start the job, SAP_SCTC_RBDLSMAP for the exceptional objects.

You check the RFC destination values and resume the task list.

In case you know your system very well already (for example, because you have executed the BDLS conversions, or system copies, before in your system and do not need to improve conversion speed), SAP recommends that you choose Concurrent Jobs based on Table Name.

However, if you observed high BDLS conversion runtimes or have to idea of the table distribution in your system yet, choose Concurrent Jobs based on Table Entry.

If you have the opportunity to execute the report, RBDLS_CHECK in the original system before system copy, SAP recommends you do so. In case your system is an SAP BW system, we recommend that you use the following advanced procedure and that you check to big generated SAP BW tables, by doing the following:

• Execute table analysis (to reduce table analysis time in the phase of post-copy activities, SAP recommends to perform the analysis already in the source system).

• Analyze results of the analysis run to define optimization strategy — when performed before system copy, you also get a better estimation of improvable BDLS execution runtimes, which improves the planning of your system copy project.

• Execute the BDSL conversion task considering the analysis results — resulting in a significantly reduced BDLS execution time.

You need the latest Note Assistant updates because ABAP PCA notes make use of some corrections of the Note Assistant. You must implement the latest version of the following collective SAP Note:

• SAP NetWeaver 7.00, 7.01, and 7.02: SAP Note: 875986 — Note Assistant: Important notes for SAP_BASIS up to 702.

• SAP Netweaver 7.30, 7.31. 7.40, and 7.50: SAP Note: 1668882 — Note Assistant: Important notes for SAP_BASIS 730, 731, 740, and 750.

You must also implement the SAP Note: 1734555 — SNOTE: Performance fix in Interface Enhancement.

To implement the SAP Notes required for ABAP OCA, you have the following options:

• Implement the notes via the program: Z_SAP_NOTE_ANALYZER.

• Use the SAP Note transport-based correction instructions (TCI).

You must ensure that the requirements for using ABAP PCA are met, to do this you create and use the program Z_SAP_NOTE_ANALYZER. Z_SAP_NOTE_ANALYZER analyzes the following:

To Create Z_SAP_Note_ANALYZER, follow these steps:

1. Open SAP Note: 1614266.

2. Download and unzip the attached file, SAP_NOTE_ANALYZER.zip.

   The ZIP file contains the following files:

   • SAP_NOTE_ANALYZER.txt
   • Basis_Content_<version>.xml

3. Call the transaction SE38.

4. Create the program SAP_NOTE_ANALYZER.

5. Enter the title, SAP Note Analyzer.

6. Choose the attribute key, Executable program.

7. Save the program as a local, temporary object.

8. On the menu bar, choose Utilities → More Utilities → Upload/Download → Upload.

   A dialog box appears.

9. Select the file Z_SAP_NOTE_ANALYZER.txt.

10. Save and activate the program.

1. Execute the program Z_SAP_NOTE_ANALYZER in SE38.

2. Choose Load XML file.

3. Upload the XML content file, Basis_Content_<version>.xml that is attached to SAP Note 1614266.

4. Choose Execute.

   The program schedules a background job with the naming convention, SAP_PCA_NOTES_DOWNLOAD.

   The program downloads the SAP Notes listed in the uploaded XML content files.

   The program exits.

5. Call the transaction SM37.

6. Check the status of the background job.

7. Call transaction SE38, when the background job is finished.

8. Execute the program, Z_SAP_NOTE_ANALYZER.

9. Ensure that the Download needed SAP Notes checkbox is deselected.

10. Choose Execute.

1. Upload the XML content file, Basis_Content_<version>.xml, that is attached to SAP Note: 1614266.

2. For SAP BW systems, or systems connected to an SAP BW as SAP BW source system, read SAP Note: 1707321, and if required, upload the XML content file BW_and_SAPI_Content.xml that is attached to this SAP Note.

3. If you have uploaded the XML content file, BW_SAPI_Content.xml, restrict your check scope according to SAP Note: 1707321 Information publishing on the SAP site:

   • PCA requirements for BW source system that will not be copied.

   • PCA tasks and task lists for BW source system.

   • BW PCA tasks and task lists.

   • BW Housekeeping tasks and task lists.

   • Tasks and task lists for pre and post processing of SAP BW upgrade or migration.

4. Choose Execute and proceed as described in procedure, To Execute Z_SAP_NOTE_ANALYZER.

Traffic lights indicate the status of each checked scope ID and the corresponding objects. In the Action column, the icons indicate possible actions.

The note analyzer program displays the check result listed in different phases. The heading line of each phase displays the overall status in green, yellow, and red.

The result of each phase is shown per scope ID and checked object. A question mark indicates any additional explanations.

You must implement the notes in the displayed order by clicking on the sign in the Action column. Read the notes carefully as some require manual activities. Attached to most of these notes you can find a report (for example, ZNOTE_<note_number>.txt. You must implement and run this report.

You use TCI to implement the required SAP Notes. It is a composition of objects only related to a specific software package or software component, for example, PCA content. You must enable the Note Assistant for SAP Note TCI instructions as follows:

• Ensure the prerequisite SAPM 61+ is installed, update SPAM if necessary.

• Open SAP Note: 1995550 — Enabling SNOTE for transport based correction instruction.

  Choose Correction Instructions → SAP BASIS → [Your Release] and download the .SAR file.

• Log on to your system in Client 000 and upload the .SAR file via SPAM.

• Define a queue in SPAM.

• Import the queue in SPAM.

• Confirm the queue.

• Verify the SAP Note status in SNOTE.

You must always check the latest documentation on how to implement TCI in your system.

Download the .SAR file suitable for your release. It is attached to SAP Note 2191981 — Task Manager for Technical Configuration TCI 1.0 (Including 9. Improvements).

You must not implement the following SAP Notes, but perform the manual activities. The table shows with which SPS the correction is already included:

To upload the .SAR call the transaction SNOTE and choose Goto → Upload TCI. Choose the downloaded .SAR file and choose Goto → Upload SAP Note. You can then start the note implementation in SNOTE.

Implement the following notes:

• SAP Note: 2192206 — System Copy: Task Content TCI 1.0 (including 9. Improvements).

• SAP Note: 1771909 — System Copy: Correction for Web Service (SOAP).

Use the program, Z_SAP_NOTE_ANALYZER to ensure that the requirements for using ABAP PCA automation are met and implement any missing SAP Notes.

The add-on PCAI_ENT 1.0 is dedicated to activating the usage of ABAP PCA and to enable the execution of PCA task lists, please use the appropriate .SAR file for your release.

1. Log on to your ABAP system.

2. Call the transaction SAINT.

3. Choose Installation Package → Load Packages → From Front End.

4. Choose Start.

5. Select PCAI_ENT 1.0.

6. Choose Continue.

   If all necessary conditions for importing the add-on are met, the system displays the relevant queue.

   The queue consists of the add-on package and can also contain support packages and other add-on packages.

7. Start the installation.

If you have one of the following releases, use the SAR archive, SAPK-100AGINPCAIENT:

• SAP NetWeaver 7.0

• SAP NetWeaver 7.0 EHP1

• SAP NetWeaver 7.0 EHP2

• SAP NetWeaver 7.3 EHP1

• SAP NetWeaver 7.4

• SAP NetWeaver 7.5

• SAP S/4HANA (attribute change package (ACP) PCAI_ENT==100 is required)

If you have one of the following releases, use the SAP archive, SAPK_100BGINPCAIENT:

• SAP NetWeaver 7.1

• SAP NetWeaver 7.1 EHP1

• SAP NetWeaver 7.3

• SAP NetWeaver 7.0
• SAP NetWeaver 7.0 EHP1
• SAP NetWeaver 7.0 EHP2
• SAP NetWeaver 7.3 EHP1
• SAP NetWeaver 7.4
• SAP NetWeaver 7.5
• SAP S/4HANA (attribute change package (ACP) PCAI_ENT==100 is required)

• SAP NetWeaver 7.1
• SAP NetWeaver 7.1 EHP1
• SAP NetWeaver 7.3

When you use ABAP PCA from the ABAP GUI, you must set the ABAP system profile parameters manually on the copied system (target system) in the default profile. Set the parameter in the DEFAULT.PFL profile of your target system (for example, TST): CTC/allow_systemcopy_postconfig = 1. Define the export directory for export content (for example, table content) for the system refresh with the parameter ctc/export_data = <Directory for export files>. If the ctc/export_data parameter is not set, the default value of DIR_PUT will be used as the export directory.

If the system copy or system refresh is executed via SAP Landscape Management, SAP Landscape Management sets the profile parameter ctc/allow_systemcopy_postconfig = 1, automatically.

The following table gives an overview of the roles used for system copy.

The user that executes the task lists needs some specific roles and permissions to work with the task lists such as those in the following table:

You must assign the corresponding SAP_BC_STC roles to the administrator (dialog user) responsible for ABAP PCA activities to execute ABAP PCA activities.

1. Log on to your ABAP system.

2. Call the transaction PFCG.

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

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

Additionally, if you are using SAP Landscape Management, you can add the following role to the technical user for remote access, SAP_BC_STC_REMOTE.

To convert logical system names using the BDLS conversion task (remote client conversion function), you need authorizations that are not assigned to a predefined role. The following table displays authorizations: