Show TOC

Procedure documentationTransporting Data Sources or Attribute Lists

 

Use this procedure if you want to transport data sources or attribute lists from the test system or consolidation system to the production system. Note that this function is only intended for a one-time transport of data sources and attribute lists. Once you use the data in the target system, it can no longer be overwritten.

Prerequisites

You have assigned the authorization object CRM Marketing: Authorization Object for Transporting Data Sources (CRM_MKDSTP) to the user who wants to transport the data sources, with the following characteristics:

  • In the source system for the export, the value 61 in component ACTVT

  • In the target system for the import, the value 60 in component ACTVT

Procedure

  1. In the source system, in Customizing activity Maintain Data Sources and Attribute Lists, select the data sources and attribute lists that you want to transport, and choose Export.

    The Prompt for Workbench Request dialog box appears.

  2. Enter the number of the transport request, and choose Continue.

    The system transports the selected data sources to the Customizing tables of the target system.

  3. In the target system, call up the Customizing activity Maintain Data Sources and Attribute Lists, and select Import.

    The dialog box Import Data Sources appears.

    • Test Run Only

      Select this option if you only want to perform a test import and then use the log to check whether you need to clean up anything in the target system, before you import the data source or attribute list.

    • Trigger TREX Upload

      Select this option if the system should trigger a TREX upload immediately after the import of the data source or attribute list. This means that you neither have to select Refresh Fast Find in the attribute list, nor immediately schedule a job for report CRM_MKTTG_TREX_UPDATE.

    Choose Start Import.

    Note Note

    Ensure that the following IDs are identical in the source system and target system:

    • Usage ID for attribute lists

    • IDs of InfoSets and attribute sets

    End of the note.

  4. If the data source or attribute list calls an RFC destination for TREX systems or BWA systems, a dialog box appears in which you must enter the corresponding RFC destination for the target system.

When importing a data source, the system checks whether the data source already exists in the target system:

  • If the data source does not yet exist, the system creates it in the target system with the same transport ID that was allocated during the export from the source system. If the system cannot create the data source for technical reasons, it outputs an error message in the application log.

  • If a data source with the same transport ID already exists, the system overwrites the existing data source, as long as it is not yet being used in the target system. If the existing data source is already being used in the target system, the system does not overwrite it, and outputs an error message in the application log.

When importing an attribute list, the system checks whether the attribute list already exists in the target system:

  • If the attribute list does not yet exist, the system checks whether the data sources of the attribute list exist, and whether the attributes of the attribute list from the source system can be used:

    • If the data sources exist, and the attributes can be used, the system creates the attribute list in the target system with the same transport ID that was allocated during the export from the source system.

    • If no data sources exist, the system outputs an error message in the application log. The attribute list is not created.

      Note Note

      This case can only occur if you transport an attribute list from the source system, without the assigned data sources.

      End of the note.

    • If the data sources only partially exist, for example if out of six data sources, only five already exist in the target system, the system creates the attribute list with the existing data sources; in this example this would be five data sources.

    • If an attribute from the data source of the target system does not exist in the data source of the source system, the attribute is created with an inactive status, without a filter.

    • If an attribute from the data source of the source system does not exist in the data source of the target system, the attribute is not created in the target system.

  • If an attribute list with the same transport ID already exists, the system overwrites the existing attribute list, as long as it is not yet being used in the target system. If the existing attribute list is already being used in the target system, the system does not overwrite it, but checks the assignments to data sources instead. If the attribute list of the source system has assignments to data sources that do not yet exist in the attribute list of the target system, the attribute list of the target system receives these additional assignments to data sources.

Result

The data sources or attribute lists have been transported, and are available in the target system for segmentation.

If there are problems during the import, you receive an application log. Entries with errors are not imported by the system. As the system deletes all data in the import tables after the import, a subsequent transport is necessary once you have solved the problems.