Show TOC

Background documentationMigration Parameters

 

You can set the values for certain reusable parameters before a migration process execution. Choosing the parameters enables an automated process execution.

Choosing Parameters: Parameter Levels

You can set migration parameters at different levels of your project.

Project-Level Parameters: Setting parameters at the project level enables the automatic assignment of the parameter values to all migration solutions included in the project.

Note Note

If you set a parameter as final at the project level, you cannot change the setting at a lower level.

End of the note.

Execution Plan-Level Parameters: Setting parameters at the migration solution level enables the automatic assignment of the parameter values to the relevant activities in the migration process tree. Any value you specify at this level overrides the value you set at the project level.

If you do not set parameters at the project level or the execution plan level, you can set them in a migration activity. Parameters you set at the activity level are used for the migration process execution and are automatically assigned to the execution plan- level.

SAP TDMS allows you to set values for the following migration parameters:

  • Specify Data Slice Date

  • Delete SAP Business Workplace Tables

  • Exclude SAP ERP HCM Data

  • Define Data Extract Mode

  • Assign Logical System Names for the Receiver System

  • Transfer Change Log Tables

  • Transfer PSA Tables

  • Transfer New Tables

  • Specify Planning Versions

  • TDMS BPL Parameter

  • Delete BPL Data in the Recv.System

  • Select Objects from SAP Utilities

  • Assign Data Extract ID for File Import

  • Assign Data Extract ID for File Import

  • Lock Users in the Receiver System

Migration Parameters: Detailed Descriptions

  • Migration Parameter: Specify Data Slice Date

    This parameter allows you to specify the date from which you can select data for migration. SAP TDMS transfers all business documents created after the date you specified. The data slice date you specify at the project level is automatically set for all migration solutions in the project.

    Example: You specify the January 1, 2011 as the data slice date for a project containing the following migration solutions: Time-Based Reduction for SAP ERP, Time-Based Reduction for SAP CRM, Time-Based Reduction for SAP SRM. SAP TDMS sets January 1, 2011 as the data slice date for all the migration solutions.

    You can validate this date before executing the solution. You can save the validated date for use by all migration solutions present in the project.

    • If you successfully validate the parameter at the project level, the Specify the Data Slice Date activity is executed in the background.

    • If you do not validate the parameter at the project level or if the validation is not successful, the Specify the Data Slice Date activity is executed in the foreground. You can now set the data slice date for the current migration package.

    • However, the data slice date you specified at the project level is visible at the activity level even if you do not validate the parameter or if the validation is not successful.

    • If you have not entered a value for the data slice date at the project level, the data slice date field is blank at the activity level.

    Note Note

    When you specify the date at the execution plan-level, the date is only valid for the selected migration solution.

    End of the note.

  • Migration Parameter: Delete SAP Business Workplace Tables

    • If you select the Delete Business Workplace Tables check box, the data in the Business Workplace tables is deleted from the receiver system.

    • If you do not select the Delete Business Workplace Tables check box, the data in the Business Workplace tables is retained in the receiver system.

    • If you choose to delete the data, you can continue to access the SAP Business Workplace, but without any historical data.

    Parameter Validation

    • If you successfully validate the parameter at the project level, the activity Delete/Retain Data from Business Workplace in the Receiver System runs in the background.

    • If you do not validate the parameter at the project level or if the validation is not successful, the activity Delete/Retain Data from Business Workplace in the Receiver System runs in the foreground. You can now decide to delete or retain SAP Business Workplace-related data in the current migration package.

  • Migration Parameter: Exclude SAP ERP HCM Data

    This parameter allows you to exclude all SAP ERP HCM data before you transfer data from the sender system to the receiver system.

    Excluding SAP ERP HCM data ensures that sensitive data is not part of your transfer in the following migration solutions:

    • Time-Based Reduction for SAP ERP

    • Time-Based and Company Code Reduction for SAP ERP

    • Transfer of Master Data and Customizing for SAP ERP

    • Full Transfer of Client-Specific Data for SAP ERP

    • Time-Based Reduction for SAP Oil & Gas (Downstream)

    • Object-Based Reduction for SAP Retail

    • Object- Based Reduction for SAP Utilities

    If you choose to exclude the data, you are required to enter the customer-specific tables to be excluded from the transfer.

    If you choose to include the data, you are required to enter the customer-specific tables to be included in the transfer.

    You can validate the names of the customer-specific tables before executing the solution. You can save the validated data for use by all migration solutions present in the project.

    • If you successfully validate the parameter at the project level, the Include/Exclude SAP ERP HCM Objects from Data Transfer activity is executed in the background.

    • If you do not validate the parameter at the project level or if the validation is not successful, the IInclude/Exclude SAP ERP HCM Objects from Data Transfer activity is executed in the foreground. You can now decide to exclude or include the SAP ERP HCM objects in the current migration package.

  • Migration Parameter: Define Data Extract Mode

    This parameter allows you to transfer data through files for the following migration solutions:

    • Time-Based Reduction for SAP ERP

    • Time-Based Reduction for SAP CRM

    • Time-Based Reduction for SAP SRM

    • Time-Based Reduction for SAP SCM

    • Time-Based Reduction for SAP NetWeaver BW

    • Time-Based Reduction for SAP Oil and Gas (Downstream)

    • Company Code and Time-Based Reduction for SAP ERP

    • BPL-Based Transfer

    • Object-Based Reduction for SAP Banking

    • Object-Based Reduction for SAP CRM for Utilities

    • Object-Based Reduction for SAP Retail

    • Object-Based Reduction for SAP Utilities

    • Transfer of PD and PA Data for SAP ERP HCM

    • Transfer of PD and PA Data for SAP ERP HCM (Expert)

    • Transfer of PA Data for SAP ERP HCM

    You can carry out data transfer through files in the following contexts:

    • You do not have a direct connection between the sender system and the receiver system in your test landscape.

    • You want to carry out multiple imports of test data using a single export file.

    To enable file-based transfer, you are required to execute the following packages:

    • Export package: You execute this package in the sender system and the control system. This package extracts data from the sender system and creates an export file. Next, the package saves the file to the export directory in the system landscape.

    • Import package: You execute this package in the control system and the receiver system. This package retrieves data from the file stored in the export directory and stores the data in the relevant tables in the receiver system.

    For more information about the system landscape for file-based transfer, see the Master Guide for SAP TDMS on SAP Service Marketplace at http://service.sap.com/tdmsInformation published on SAP site.

  • Migration Parameter: Assign Logical System Names for the Receiver System

    This parameter allows you to specify the logical system names for the receiver system. The new logical system names specified using this parameter are replicated during the data transfer. The logical system names you specify at the project level is automatically set for the Time-Based Reduction for SAP ERP and Time-Based and Company Code Reduction migration solutions in the project.

    You can validate the logical system names for the receiver system before executing the solution. You can save the validated logical system names for use by Time-Based Reduction for SAP ERP and Time-Based and Company Code Reduction solutions present in the project.

    • If you successfully validate the parameter at the project level, the activity Assign Logical Names for the Receiver System is executed in the background.

    • If you do not validate the parameter at the project level or if the validation is not successful, the activity Assign Logical Names for the Receiver System is executed in the foreground. You can now set the logical system names for the current migration package.

    Note Note

    When you assign the logical system names at the execution plan-level, the logical system names are only valid for the selected migration solution.

    End of the note.

    Example Example

    The logical system name for the sender system is R3PCLNT800 and you want to enter R3TCLNT800 as the logical system name for the receiver system. You enter R3TCLNT800 under Names in the Receiver System corresponding to the logical system name R3PCLNT800 under Names in the Sender System.

    End of the example.

  • Migration Parameter: Transfer Change Log Tables

    This parameter allows you to include change log tables of ODS objects in the TDMS transfer for the migration solution Time-Based Reduction for SAP NetWeaver BW.

    By default, change log tables are excluded from TDMS transfer because they are very large and not essential for reporting purposes.

    The activity Analysis of Table Participating in Data Transfer verifies whether you have selected or deselected the parameter and carries out the required action.

  • Migration Parameter: Transfer PSA Tables

    This parameter allows you to include PSA tables in the TDMS transfer for the migration solution Time-Based Reduction for SAP NetWeaver BW.

    By default, PSA tables are excluded from TDMS transfer because they are very large and not essential for reporting purposes.

    The activity Analysis of Table Participating in Data Transfer verifies whether you have selected or deselected the parameter and carries out the required action.

  • Migration Parameter: Transfer New Tables

    This parameter allows you to include new tables for ODS objects in the TDMS transfer for the migration solution Time-Based Reduction for SAP NetWeaver BW.

    By default, new tables are excluded from TDMS transfer because they are very large and not essential for reporting purposes.

    The activity Analysis of Table Participating in Data Transfer verifies whether you have selected or deselected the parameter and carries out the required action.

  • Migration Parameter: Specify Planning Versions

    This parameter allows you to specify the SCM planning versions for which SAP TDMS transfers relevant data relevant for TDMS data transfer for the migration solution Time-Based Reduction for SAP SCM.

    Example Example

    You specify the planning version as 000 and the data pertaining to this planning version will be included for transfer in the TDMS transfer.

    End of the example.

    • The planning versions you enter should be available in the sender system.

    • The planning version you specify at the project level is automatically set for all the migration packages in the project

    • You can validate the planning versions before you start executing the package.

      If you successfully validate the parameter at the project level, the Specify Planning Versions activity runs in the background.

      If you do not validate the parameter at the project level or if the validation is not successful, the Specify Planning versions activity runs in the foreground. You can now set the planning versions for the current migration package.

  • Migration Parameter: TDMS BPL Parameter

    The TDMS BPL parameter allows you to set data reduction criteria for a project at the execution plan level for the BPL-Based Transfer migration solution.

    While defining parameters, you are required to input values for parameters.

    You can enter the reduction criteria at the execution plan step level.

    You can upload or download data or maintain the data manually at the execution plan step level.

    Setting the criteria enables the automatic assignment of the parameter values to the relevant activities in the migration process tree.

    You can validate the correctness of the parameter values.

    You can choose to change the reduction criteria at the migration package level in activity Specify Migration Parameters for Data Selection. This is usually the case when you want to transfer a new set of data for a BPL object using the same migration package.

  • Migration Parameter: Delete BPL Data in the Recv.System

    You can use this parameter to choose the data deletion behavior at the execution plan level. Selecting or deselecting the checkbox impacts the data deletion and data transfer behavior as described below.

    • Option 1: BLANK

      WRITE Behavior for Data Transfer: MODIFY

      If you do not select the Delete BPL Data in the Recv. System checkbox, SAP TDMS does not delete the BPL data in the receiver system. During data transfer, SAP TDMS overwrites the existing data with the data transferred from the sender system.

      Note Note

      Option 1 is the default behavior. If you do not want to delete the data, choose Option 1.

      End of the note.

    • Option 2: X

      Write Behavior for Data Transfer: INSERT

      If you select the Delete BPL Data in the Recv. System checkbox, SAP TDMS deletes the BPL data in the receiver system. During data transfer, SAP TDMS transfers the BPL data selected in the sender system to the receiver system.

  • Migration Parameter Select Objects from SAP Utilities

    This parameter allows you to enter the selection criteria for at least one of the following selection options:

    • Business Partners

    • Contracts

    • Installations

    • Devices

    • Points of Delivery (External ID)

    Recommendation Recommendation

    To ensure a high-level of consistency in the data transfer, we recommend that you contact your test or functional organization to obtain the required selection criteria.

    End of the recommendation.

    Activities: Enter an individual object or a range of objects.

    Note Note

    Execute the activity Select Objects from SAP Utilities from the migration process tree after you set the parameter and start the execution of the migration package. The activity runs in the background and picks up the parameter values set at the project- or package-level for reduction before transfer.

    End of the note.

    Validating the parameter

    Validate the parameter value before executing the solution. You can save the validated parameter value for use by all migration solutions present in the project. If you successfully validate the parameter at the project level, the Select Objects from SAP Utilities activity is executed in the background with the selected parameter values.

  • Migration Parameter: Assign Data Extract ID for File Import

    You use this parameter to assign the data extract ID to the import package.

    Prerequisites: You have retrieved the data extract ID from the export package.

    Working with the parameter in the Identification of Data for File Import activity: When you execute the Identification of Data for File Import activity in the process tree, the data extract ID assigned to this parameter is displayed by default. You can change this value if you want to enter the data extract ID of a different export package.

    Working with the Process Execution Manager: You can alternatively set the Process Execution Manager to run the Identification of Data for File Import activity in the background. In this context, the Identification of Data for File Import activity picks up the data extract ID specified for this parameter and assigns the ID to the current import package. Next, the Start of File Import activity imports all files assigned to the data extract ID to the import package.

  • Migration Parameter: Assign Data Extract ID for File Import

    You can choose to transfer the following SAP NetWeaver BW tables:

    • Change Log Tables

    • New Tables

    • PSA Tables

    By default, SAP TDMS excludes the above tables from data transfer for the following reasons:

    • The tables usually hold a large amount of data

    • The data in the tables is not required for reporting purposes

    Parameter Names

    • Transfer Change Log Tables

    • Transfer New Tables

    • Transfer PSA Tables

    Interdependency: The activity Analysis of Tables Participating in Data Transfer checks whether you have selected or deselected the parameter and carries out the required action. If you want the tables transferred, select the appropriate checkbox on the Project Parameters tab page or make the appropriate entries in the dialog boxes at the package level before running the activity Analysis of Tables Participating in Data Transfer.

  • Migration Parameter: Lock Users in the Receiver System

    You use this parameter to lock users in the receiver system before you transfer data from sender system to receiver system.

    This parameter allows you to lock users in the receiver system before you transfer data from the sender system to the receiver system.

    If you select the Lock Users in the Receiver System check box, users not directly participating in the current run, (that is, users not registered for the current run) are locked in the receiver system.

    If you do not select the Lock Users in the Receiver System check box, users are not locked in the receiver system.

    Recommendation Recommendation

    The Data Transfer activity overwrites the data in the receiver client during the period of transfer. Hence, we recommend that you define the system downtime by locking users not directly participating in the current run.

    End of the recommendation.

More Information