Skip to Content
avatar image
Former Member

Synchronization object

Hi all,

Whenver we create a syn obj(used for scout and distribution)

we have to provide source and target component......................depending upon them we are getting the list of source and target sytem names or RFC.

1.What is the importance of source and target components and how are they linked to the individual objects.

2.Later we have to provide the syn oject or include the same but can we provide custom obj like ztables because it gives option for fetching data from source and target IMG only.

I will reward points.Please help me out.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 22, 2007 at 12:19 PM

    Hi Prakhar,

    Could you please provide more details - like which systems are to be synchronised / what scenario is being implemented .

    Regards,

    Anita

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi ,

      Sorry but this is not something I am familiar with, although this question has increased my awareness.

      What I understood was that you want to identify the object to be used to synchronise data- by searching in OSS for a single object came across several patches related ot specific errors, from this I undestand that probably there maybe more than one synchronisation object/ one master synchronisation object containing several objects related to a specific CRM scenario eg: pricing.

      Pls refer OSS note 552494 this contians several sub notes related to setting up the customizing distribution. Also by searching with the keyword SCDT_GROUPS a lot of information is available in OSS notes, this could be a pointer.

      Meanwhile, will continue to search for relevant information on this issue.

      Regards,

      Anita

  • Aug 23, 2007 at 12:18 PM

    Hi Prakhar,

    I am able to found some important piece of information, which may help you to solve.

    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.

    For more details please refer the following URL

    http://help.sap.com/saphelp_nw04/helpdata/en/46/46c7d6195842eab5190d04859c2a33/content.htm

    Regards,

    Harish

    Add comment
    10|10000 characters needed characters exceeded