Synchronisation after Backend(R/3) system Refresh

[Former Member]

Hi Experts,

We have Refreshed our back end(R/3) QA system, say QAS, with the latest Production(R/3) Data, say PRD.

After a successful system copy when we try to synchronise our mobile client with the Mobile WEB AS, say MQA, we get time out errors.

We see that the client is making a rfc connection into the MQA and the MQA is receiving notifications from back end QAS.

But for some reason the data seems to queue up in the outbound queue of the Web AS.

Our Mobile consultant has suggested that we delete all the synch BO's from the MQA and replicate them back from the Back end QAS.

The issue is that we are planning to do System Refresh every 6 months as per the business requirement, so do we have to follow the procedure mentioned by our consultant everytime we do the Refresh or is there a better way.

Thank you

Note: Points will be awarded.

[Former Member · Accepted solution]

Hi,

this seems to be more a technical issue - like RFC connections not working or so.

Anyway it is a good idea to replicate all the data again once you have done a system refresh - yes - but this a usual step, cause you have changed the data, so you want to have the new data on the device - so it makes sence to replicate this data again.

Check if the replication works as expected - if this works, the sync should work fine as well....

Hope it helps!

Regards,

Oliver

[Former Member · Accepted solution]

Hi Oliver,

Thank you for your response.....

The RFC Connections seem to be working fine.....becoz....when i start the Merep_replicator for the Synch BO's on the Web AS MQA...it finishes off successfully bringing back notifications from the QAS or any new users created or any work center associations.

But when i try to synchronise with the client...i can see the client logging in into the MQA Web AS with the client User ID.

But i see that when the synchronization is in progress i do not see it logging back into the backend QAS(r/3)....i dont think this is a necessity for a successfull synch...please correct me if i am wrong.

As the replications are running successfully i dont think there is a problem with the RFC.

Please suggest on how we move forward on this.

Thank you

[Former Member · Accepted solution]

Hi,

ok, the replication was successfull and you are as well right: at sync the user does not need to logon to the backend. He only needs to login to the middleware successfull.

Are all SyncBOs enabled in MEREP_PD?

What is the state in MEREP_PD?

Does MEREP_LOG tell you something more?

Regards,

Oliver