Show TOC

Create and Load Synchronization ObjectsLocate this document in the navigation structure

Use

This process creates Synchronization Objects, which you want to use later for comparison with the Customizing Scout or for Customizing Distribution, in the system. You create synchronization objects if customizing objects in different system have the same contents, but different structures, for example different table and field names.

Prerequisites

You have decided which customizing objects you want assign to each other in a source and target component. You have checked that the objects are in the transaction SOBJ. You have checked whether the objects are appropriate for Customizing Synchronization.

You have set up RFC connections for the synchronization object specification tool.

Process

Create synchronization objects

  1. You log on to the Customizing Distribution target system. If you want to create synchronization objects for the software component BBPCRM 4.0, for example, log on to a system which contains this component.

  2. You start the Synchronization Object Specification Tool.

  3. You create a synchronization object according to the following rules:

    • If a table is used in several customizing objects, create a synchronization object for each customizing object.

      You want to create a synchronization object for the table TSAD5. The transaction SOBJ shows two objects in the piece list based on the table: the view V_TSAD5 and the object TSDAD5 (a table with text table). You create two synchronization objects - one for the view V_TSAD5, and one for the object TSDAD5.

    • You put tables or views in one synchronization object which must be transported together. For example, you combine all tables in the target system which correspond to subobjects of a view or view cluster in the source system.

  4. You assign table and field names to each other as appropriate, when you create the synchronization object. Note the following:

    • The field data types must be assignment-compatible, not necessarily identical.

    • Fields are truncated if they are longer in one component than the other.

    • Data fields which are not in one component are ignored.

    • All key fields of the tables and views in a customizing object must be defined for the target system. You can use any fields in the tables or views for the source system.

    • If several tables or views are used for the source system, the system links their records according to the following algorithm:

      • One table is flagged as the primary table.

      • Secondary tables are linked to the key fields of the primary table with the same name by InnerJoin.

      • The secondary table can have other key fields which are mapped onto target structure fields.

      • If you use a table with text table, the text field is automatically flagged as such by the system.

    • If you assign a table with text table in a source system to a view in the target system, you must specify filter conditions for the source object: you create a filter for the language field with the value $SPRAS or $SLANGU.

    • If you assign a table/view to another table/view, without mapping all fields in the source object to fields in the target object, specify filter conditions for the source object: you create a filter for the ignored key fields which have either a fixed or a generic value.

  5. You check all newly-created and already existing synchronization objects which you want to use.

Load synchronization objects

  1. Log on to the SAP Solution Manager system.

  2. Load the synchronization objects from the system in which sie created them, into the SAP Solution Manager system.

Result

The synchronization objects are now available to the Customizing Distribution and Customizing Scout.