I have created a Timed 2 way syncbo for contacts. Also uploaded the application(generated app by SAP) to MI client . I am able to see Contact header and item(address,email) details.When i add an item(say address), am unable to see the change in MI client even after replication. If i add any header data,it is getting reflected in MI client. Could anyone help me on this?.
As you said, i added data in <i>MEREP_E_MAIL</i> table, did replication and synchronization in MI client. I went and saw the Sender data in <i>MEREP_MON</i>. I dont find data which i have added in <i>MEREP_E_MAIL</i> table so it means data is not there in replica db. What could be the problem??. As i said before i am able to see the changes made in header data but not on item data. Also checked the bapi wrapper <i>MEREP_CONTACT_GETDETAIL</i>output,its giving correct data for the particular persn number.
<b>In this case , u r using the SyncBo of synchronization type T01. In the case of T01 syncbos , the actual replication of data to the replica database from the Back end system is to be executed manually by running the replicator(by means of a scheduled program . job).</b>
If the applications use SyncBOs of type Timed 2-Way, the program MEREP_DISTRIBUTOR must be scheduled for execution after the expected end of the replication database update. This ensures the data is as accurate as
possible.
In the case of T01 syncbos , the replica data base and the behaviour of replication during sync is different.
The Client Data Distributor (program MEREP_DISTRIBUTOR) determines the delta data, independent of the download request from the client. The system creates and processes the worklists and stores the relevant delta data in the outbox(es) for the defined devices, independent of the SyncBO type.
The administrator can create variants for the program and define the mobile components,mobile groups, users, devices, mobile IDs, or SyncBOs that the delta data is to be determined and processed for. The administrator can execute the variants manually or create a background job to execute them on a regular basis.
Just refer the installation guide for configuring this.
The Client Data Distributor (program MEREP_DISTRIBUTOR) determines the delta data, independent of the download request from the client. The system creates and processes the worklists and stores the relevant delta data in the outbox(es) for the defined devices, independent of the SyncBO type.
Just run this and sync again ...
one more doubt ,
Could u create new entries from the Client device itsels. ? Is it showing any inconsistencies there ?.
Are you using the Standards BAPI Wrappers (CREATE also ) for Contact SyncBO creation ..
If not ... just check the Export param of your Create BAPI Wrapper . just check whether you are filling the export param with values corresponding to your personal ID created or not ...
I have done the steps you mentioned many times. I am able to see the new header data in the MI client if i have added the header data(merep_person table) but am able to see only one record in all the items. I am using standard bapi wrapped for contact creation and am using all the 4 bapi wrappers in syncBO. I have not done custom coding in the application which has been generated by SAP. The application uses only getlist and getdetail only.
Since you are able to see the header data, there seems to be no problem with replication. The problem is that the call made to your getdetail fails.
Could you check whether your getdetail bapi wrapper is RFC - enabled? If the function is not RFC enabled then data cannot be fetched by the middleware.
Also plese check the logs and report if you find any thing unusual.
I tried to find out the probelm and i could find out the exact reason.
Just check the key fields u have mapped in the GETDETAIL Wrapper for your two TABLE parameters (MEREP_ADDRESS and MEREP_E_MAIL).
I think u might have checked the PERSON Number only as the key field in the GETDETAIL Wrapper against your two tables.. At this time , when u try to create more than one Address and Email entries in your tables , this will violate the key concept. Since the replication is the first step in the case of T01 syncBos , the problem will start from this point. It will not insert data into the merep_207(common table for T01).. So u will not get the data in the client during sync. During sync , data from the merep_207 table is fetched and copied to the merep_10700 table with respect your particular mobile id...
So u can resolve this problem in this way...
In the MEREP_CONTACT_GETDETAIL Wrapper ,
Against your Table parameters
-
ADDRESS (table)--- PERSNUMBER and SEQNO_ADR as key
E_MAIL (table)--- PERSNUMBER and SEQNO_E_MAIL as key
One more thing,,
If u want to insert multiple Address details for same person number
then for example ..
PERSNUMBER 1 <other details>
SEQNO_ADR 1 <other details>
PERSNUMBER 1 <other details>
SEQNO_ADR 2 <other details>
You have to insert appropriate values in place of SEQNO_ADR ..
The same thing u have to follow in the case of EMAIL also...
One more thing...
If you have Crete and Modify wrappers , then this must be mapped as keys in those parts also ....
I did the steps you mentioned. Now i am able to see multiple item records i entered for email and address but seeing the same record multiple times. I checked the merep_mon, i am able to see the new data in outbound worklist. I feel something to do in the client side.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.