Creating a New Run ID

After you click Create new run on the initial screen, the following screen appears. The same screen is also shown after clicking the Maintain run ID step in the DTS activity tree.

The following parameters are available on the screen. Note that some of the parameters are available only for certain run ID types:

  • Run ID: Shows the selected or actual DTS run ID. This field cannot be edited on this screen.

  • Description: Describes the purpose of the DTS run ID. This allows you to easily distinguish between multiple run IDs. We recommend maintaining this field.

  • Application: Together with the run ID type, this restricts the list of predefined content packages on the screen below. Once the run ID has been created, the application cannot be changed. The following options are available:

    • ECC: Select this option for any ERP-like systems – ECC or S/4HANA, but also SRM, CRM, EWM systems.

    • BW: Select this option for any BW system, including BW/4HANA.

    • Cross application: Select this option if there is no content package defined for your application.

  • Run ID type: Together with the application, this restricts the list of predefined content packages. Once the run ID has been created, the run ID type cannot be changed. The following options are available:

    • DTS Conversion: For scenarios in which data is changed within the same system. Examples: Chart of accounts harmonization or a fiscal year harmonization.

    • DTS Deletion: For scenarios in which part of the data needs to be deleted. Example: Divestiture scenarios when the sold part of the company occupies 50% or more of the database size.

    • DTS Migration: For scenarios in which data is moved from one to another server. Examples: System upgrades (e.g. to S/4HANA), company code carve-outs (when the sold part of the company occupies less than 20% of the database size) or lift and shift migrations/cloud moves.

    For more information about the scenario differences, see the chapter Transformation Scenarios.

  • Migration system type: Relevant for migration run ID type. Specifies the system type. Possible values: Source system or target system.

  • RFC to source/target system: Relevant for migration run ID type. Specifies the RFC name to the target system if the screen is displayed on the source system or specifies the RFC name to the source system if the screen is displayed on the target system.

  • Secondary RFC: Allows you to add additional RFC connections to a specific application server on the target system. This option makes sense when performance of the beam task is low because of the dialog process capacity on the application server used by the RFC defined in the parameter above. In such cases, the standard SAP process load balancer might cause slower DTS task processing.

  • Delete cluster data after processing: Relevant for the Deletion and Migration scenarios. Allows you to clean up DTS clusters on the source system after the data has been successfully transferred by the beam tasks.

  • Use files: Allows you to store the transformation data in DTS data files instead of in DTS clusters.

    Copy files using RFC: Allows you to copy the data files from the source system to the target system via RFC. This option is only visible in the migration source run ID.

  • Directory: Directory where the data files are stored during the transformation execution. In the case of the Migration scenario, the directory must be accessible from the application servers of the target system. If needed, the path to the directory from the target system can be edited.

    Check directory button: Checks if the directory is accessible from all application servers.

  • Collect runtime statistics: Enables the performance measurement of DTS execution activities by CrystalBridge Monitoring. We recommend keeping this option selected.

  • Run ID for BO replication: Specifies the name of a run ID on a remote system (typically an ERP system) from which the values of its DTS business objects will be replicated. For more information, see the chapter Setting the BO Replication.

  • RFC destination for BO replication: Specifies an RFC name to the system where the run ID for BO replication is created.

  • Content packages grid: Specifies a list of available content packages for the selected application and run ID type. Once the run ID has been created, the content package selection cannot be changed. The DTS activity tree is generated based on the selected content packages.

  • Create: Saves the DTS run ID attributes and creates the DTS activity tree based on the selected content packages.

  • Save changes: Applicable only to the step Maintain run ID. Saves all changes. This is the same as clicking Save (Ctrl+S) in the toolbar.