Synchronization Object
Definition
A customizing object in an SAP component, to which a customizing object with the same contents in another component is assigned. The contents of the customizing objects have to be synchronized in different systems in a system landscape.
You create synchronization objects if customizing objects in different systems have the same contents, but different structures, for example different table and field names.
Use
The synchronization objects are the basis for comparisons in the Customizing Scout, and the adjustment of customizing in the Customizing Distribution. You can also select individual synchronization objects for which you want to make a comparison in the Customizing Scout, or an adjustment in the Customizing Distribution, with the Synchronization Group Editor.
Predefined synchronization objects are currently available for the following SAP components:
Components for which synchronization objects are available
Target component |
Software component |
Source component |
Software component |
SAP_HR 6.10 |
SAP R/3 |
SAP_APPL 6.10 |
|
SAP R/3 (stand-alone HR) |
SAP_APPL 6.10 |
SAP HR |
SAP_HR 6.10 |
SAP MDM |
MDM 2.0, 3.0 |
SAP R/3, |
SAP_APPL 3.1 and later |
The Customizing Scout and the Customizing Distribution first get system landscape component information, including the release (e.g. SAP MDM 3.0, SAP R/3 4.0B). This information is important because the mapping of customizing objects in the source component to a customizing object in the target component is release-dependent.
Structure
In the simplest case, a synchronization object comprises one customizing object in a source component, which corresponds to exactly one customizing object with the same name in the target component. If the objects are not identical, the system contains descriptions of how they are mapped onto each other. The description specifies which customizing object in the target component corresponds to a customizing object in a source component, i.e. a customizing object in the target component is mapped onto a customizing object in a source component. The starting point of the assignment is always the object in the target component, i.e. tables and field names of the object in the target component are first determined, and are then assigned to field names of the corresponding object in the source component.
The following forms of mapping are currently supported:
· No Mapping Required (same data): Both the table names and the field names are identical in the target and source components. Not all fields must be in both tables.
· Different Table Names: The field names are identical in the target and source components, but the table names are different. Not all fields must be in both tables.
· Different Table and Field Names: Both the table names and the field names are different in the target and source components. Not all fields must be in both tables.
· Programmed Mapping: The customizing is assigned in the source and target components by a function module.
Integration
The synchronization objects are customizing objects of the following types:
· Table (space)
· View (V)
· Table with text table (S)
· View cluster (C)
· Transactions (T)
· Logical Transport Objects (L)
View clusters are resolved into individual views, and transactions into their tables.