Show TOC

  Create and Load Synchronization Objects

Purpose

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

Prerequisites

You have decided which customizing objects you want to 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 Customizing-Synchronization-Compatible .

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

Process Flow

Create synchronization objects

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

  2. Start the Synchronization object specification tool .

  3. Create a synchronization object following the following rules:

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

      Example Example

      You want to create a synchronization object for the table TSAD5. In the transaction SOBJ you find the table as underlying table in the piece list of two objects: in the view V_TSAD5 and in the object TSDAD5 (a table with text table). You create two synchronization objects – one for the view V_TSAD5 and another for the object TSDAD5 .

      End of the example.

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

  4. You can assign tables and field names to each other when you create the synchronization object. Note:

    • The data types of the fields must be assignment-compatible, not necessarily identical.

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

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

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

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

      • One table is flagged as the primary table.

      • The key fields of secondary tables are linked to the fields of the primary table with the same names by an InnerJoin.

      • The secondary table can have other key fields which correspond to fields in the target structure.

      • If you use a table with text table, the text field is also 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 Source Object Filter Conditions : 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 all fields in the source object being mapped to target object fields, you must Specify Source Object Filter Conditions : You create a filter for the unused key fields which have a constant or generic value.

  5. Check all created and existing synchronization objects which you want to use.

Load synchronization objects

  1. Logon to the SAP-Solution Manager system.

  2. Start the transaction Synchronization Group Editor and load the synchronization objects from the system in which you created them, into the SAP Solution Manager system.

Result

The synchronization objects are now available for the Customizing Distribution and the Customizing Scout. You can now use the Customizing Distribution or compare cross-component customizing .