Steps involve in real time synchronization

[Former Member]

Hi All,

Please let me know what are the difficulties we face in the real time data synchronization in smart sync and what is the solution to overcome.

Thanks

Regards

Santosh

[Former Member · Accepted solution]

Hi,

this link will help you troubleshooting problems in Data synchronization in smart sync.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/909d75c3-0801-0010-5f92-920...

hope this helps.

Regards

Divya

[Former Member]

Hi Santosh,

There are quite a problems in SS.

Errors can occur when uploading or downloading during the synchronization process. The system detects these errors, and there are mechanisms for processing these errors on both the mobile device and the server. You can configure the behavior thru MCD.

Possible errors are:

· Application errors that are normally returned by the BAPI wrapper functions

This also includes authorization errors, which are classified as application errors by the SAP MI Server Component, since there is no application-specific authorization check.

· Framework errors

· System errors

This includes, for example, RFC connection errors.

Monitoring is one of the best techniques used for solving errors while Sync

refer this

http://help.sap.com/saphelp_nw04s/helpdata/en/43/174d79176b576ee10000000a1553f6/content.htm

While there are still more troubleshooting scenarios:

Missing Data After Synchronization like in cases1. Application Data Download Error where No data was downloaded to the application during the synchronization process. The relevant

data does exist, however, in the table MEREP_207.

2. Missing Sales Order on Mobile Client where You created a sales order on the backend system but you could not download the sales order

to the mobile client using MSR. The data was found in the message using MEREP_MON.

3. Empty Inbound Container:The synchronization log on the Mobile Infrastructure client returns the message Received

empty inbound container and no data has been downloaded to your mobile device.

4. Missing Synchronization Key

5. Incomplete Application on Device:You have not received the complete MAM application on your mobile device.

Replication Errors:

1. Replicated Database Update Error: When you tried to replicate the MAM_095 SyncBO the system generated the error message

Error updating replica DB for download (SyncBO=MAM_095, Mobile ID=).

Tracing and Logging

1. Missing Data: You can see from the MI client’s trace file that data has been successfully downloaded but

this data is not in the middleware.

2. Log Monitor Runtime Error:

When you use the log monitor (transaction MEREP_LOG) and specify a name of a SyncBO,

a runtime error occurs.

3. Data Conflicts

and hey you can add yours too if you find a serious one

Regards

Divya

[Former Member]

Hi ,

Thank you so much for your quick reply.

Thanks

Regards

Santosh

[Former Member]

Hi Santosh,

General problems might be data inconsistencies between Client and middleware.

For that..reset the client and sync again to get fewsh data download.Reasons can be many..this is one of the option.

Records going into waiting state/partial state I-Waiting,I-Partial...So from here on wat ever u create from client will not be reflected in the backend...So we need to clear these waiting/partial rdcords in MEREP_MON...

https://wiki.sdn.sap.com/wiki/display/profile/2007/04/04/MIUNVEILED1

Check the above wiki.

There can be N number of issues while using real time data...each thing has its own solution depending upon the problem.

Cheers,

Karthick

[Former Member]

Hi Karthick,

Thanks for the link.

Regards

Santosh