Mobile sales for R/3 set up

[Former Member]

Hi All

Iam doing a set up for Mobile sales for R3 solutions for laptop Iam facing some issues with respect to synchronization. The sync BO's used for the set up is a standard setup provided from SAP . I am able to configure and get data for the R3 .

But when i sync the data from the MW .I am not able to get the data properly in the mobile device .

Currently i am not using DB2e Mi client Addon , I am Using File IO ...

As the sync BO are time 2 ways smart sync BO's ,Was wondering are there any additional set up to be done in the Mi client side .

without using IBM db2e I am still able to get data but not a proper one . Not sure where the problem is ?

Would be great if any body has done the set up for mobile sales for R3 ( without using IBM db2e ).

regards

rajesh

[Former Member]

hello rakesh,

could you please provide more info?

> But when i sync the data from the MW .I am not able

> to get the data properly in the mobile device .

> without using IBM db2e I am still able to get data

> but not a proper one

could you elaborate? what do you mean by "not a proper

one"?

regards

jo

[Former Member]

Hi Jo ,

As per the configuration docs I am supposed to use IBM DB2e Only . But when i tried with the Default DB ( File I/O)I was able to get data for one of the Synch BO but for other BO it was able to download to the device ,while for some no dat files were created . Since these sync BO are T01 2 way smart sync BO's...I checked data in the MW DB ( merep_207 table ) . The MW had data for all the Sync BO's , but i was not able to see it in the device when i check my application ....

Any pointers on this is appreciated

regards

rajesh kr

[Former Member]

hi rakesh,

first, check on the outbound messages sent to your

client thru the worklist monitor. tcode: merep_mon

- are all the records for the SyncBos sent to the client?

- what are the messages' state?

if all the messages are received in the client, check

your trace file for the container dumps and errors.

- do you find the xml smartsync messages of your raw data?

- any errors/exceptions logged?

regards

jo

[Former Member]

Hi jo

I synched twice from the mobile device and the status of all are o-waiting and O-sent ,the moment i again synchronize from the device again both the counters increase for the o-waiting and O-sent list

Also can you please let me know what do u mean by

reqDirectSync="true" in the syncBo defn in the

meRepMeta.xml

<SyncBO id="MSR20_01" version="10" type="timedTwoWay" allowCreate="false" allowModify="true" allowDelete="false" reqDirectSync="true">

regards

rajesh

[Former Member]

Continuation to the previous post :

Using the TX merep_log i get the following Log for the one of the Synch BO

-

---

5 S 31.01.2006 04:00:59 No download data from R/3 found in downloader

11 5 S 31.01.2006 04:00:59 Downloader ended successfully (Mobile ID: 0000000119, SyncBO: MSR20_01) -

---

Also in the Mobile Device trace files the same is shown .

As this synch bo are TO1 Smart Sync BO , Iam able to get data when i try replication the data from the backend to the MW . But unfortunately on synchinh from the device its not able to create a File named MSR_01 in th data folder for the correspondimg Synch BO.

regards

rajeshkr

[Former Member]

hello rakesh,

the SyncBo attribute reqDirectSync defines the message

exchange behavior during the synchronization. if it is

specified to true, your SyncBo delta data from the client

and MW wil be exchanged SYNCHRONOUSLY, i.e. in one

synchronization process. if false, the it will be

ASYNCHRONOUS.

regarding your problem, do you have any exceptions in the

client trace file?

regards

jo

[Former Member]

hi jo

Are there any help docs provided for looking in the usage of attributes and elements in the meRepMeta.xml document as i was not able to get any help from help.sap.com.

regards

rajeshkr

[Former Member]

hello rakesh,

generally, you won't be entering the element and attribute

values directly into the xml file. the meRepMeta.xml is

generated by the SyncBo Builder when you download the

metadata. the values will be according to the settings

of the attributes (SyncBo attributes e.g.).

manually editing the metadata xml file is not recommended.

as this might lead to unknown elements/value problem during

the application deployment.

im not sure if the schema is available to public.

comparing the generated xml file with that of your

settings in the SyncBo builder will help you understand

which element is for which UI.

regards

jg

[Former Member]

Hi jo

thats right , but I am helpless if i dont know what attribuyte corresponds to what usage in the metarep xml even though i will not be editing it ?

Also wanted to knw one more thng since iam doing a standard sap solution set up , while importing the synch bo the version number of the synch bos are different for the meRepMeta.xml generated when compared to the standard one which SAP provided for this solution .

Can this cause any proble while data creation on the client ,since Some of the Table strtuctures are not getting generated .

regards

rajesh kr

[Former Member]

hello rajesh,

by experience, MI doesn't check for the meta version

at the moment. neither it uses some of the Property

elements in the metadata.

when there's an inconsistency with the metadata

definition on the middleware and client, (e.g. old

application using a different metadata sync with

a MW having a SyncBo definition), an error in the

client and/or in the middleware will occur.

in the MW, your BAPI might throw an error. in the

client, a runtime exception might be caught when the

data is received from the MW.

regards

jo

[former_member207329]

Hi Santiago, i have create a syncbO S01 tyepe: the attribute <type="upload"> is not present in the meRepmeta.xml: this attribute is necessary to download the delta?

[Former Member]

hi rocco,

following my experience

only the syncbo type = 'upload' (<i>U01</i>) call bapi create.

the syncbo for download (type = 'download') can be:

<i>S01</i>: sync type

<i>T51</i>: replicator is called from backend 'whenever data is changed there'

<i>T01</i>: async type, call replicator job

<i>D01</i>:(deprecated)

-for download:

the TOP structure of a syncbo is from getList function,

ITEM structure going from getDetail function.

- doc: def. sync bo structure:

<i>http://help.sap.com/saphelp_erp2005/helpdata/en/a6/c32a89005ab2449cf95e5b0731ee40/content.htm</i>