cancel
Showing results for 
Search instead for 
Did you mean: 

Data of Outbound Queue never arrives the client

christoph_kurtz2
Participant
0 Kudos

Hi all,<br>

<br>

I am developing a mobile application for handhelds for MI7.1. I have created several data objects by importing the related BAPI wrapper, the distribution models are also generated and active. I have set up a mobile device with the application and registered the device on NWA. Data are transfered from backend to DOE by the related instance push functions.On DOE, I have maintained that the outbound will be refreshed synchronously.<br>

<br>

Now the phenomena: the pending extracts are filled as soon as data are pushed from the backend. When synchronizing the client, data are transfered to the outbound queue as required. On the client, one data object doesn't arrive in the database, all others are transfered completely. The one missing data object has an active bulk rule which is also assigned to my device on DOE. Because I have no other idea, I have regenerated the data object on DOE again, also the related distribution model and the bulk rule. Moreover, I have refreshed the data objects in NWDS, redeployed the application and installed it on the mobile client. But the phenomena can still be observed.<br>

<br>

My question is: has anybody an idea hot I can solve this problem? I am looking into this subject for more than a day now, but I couldn't find a solution for this.<br>

<br>

Best regards,<br>

<br>

Christoph

Accepted Solutions (1)

Accepted Solutions (1)

former_member185875
Contributor
0 Kudos

Hi Christoph,

I need some clarification's

1. Missing Data object having the data in CDS?

no, enter data in the back end and call your instance push.

yes,-->2.

2. Are you getting the missing data object up to pending extract?

no. deactivate and active the rule once.

yes.--->3

3. Check whether Refresh Queue for the missing Data object is configured.

4. If your done the all above steps already. I think it's problem with the client.

5. Reset the client. and do from scratch.

6. still your facing the problem. uninstall the client s/w and install it.

i think it's help to you.

Regards,

lakshman balanagu.

christoph_kurtz2
Participant
0 Kudos

Hi Lakshman!<br>

<br>

1. Data are in CDS.<br>

2. The data are in pending extracts. After synchronization, I can also see them in the "View session details" that they should be sent.<br>

3. Refreshing the data queue is set to "Synchronously" and "All Data Objects".<br>

4. - 6. Perhaps there is a problem with the client. But resetting it or reinstalling it from scratch didn't solve the problem. The phenomena can still be observed.<br>

<br>

Do you perhaps have an other idea?<br>

<br>

Best regards,<br>

<br>

Christoph

Former Member
0 Kudos

Here's how you'd usually develop your app:

1. Create Data Objects (DOs)

2. Import the DOs into NWDS and write your application logic.

Now, every change done to your DO in the DOE calls for a re-import and rebuild of the application.

=> If you do local deployment, the DOE will not know which version of the DO you are using in the client. So if you have changed any of the DOs since the last time you imported your DOs into NWDS (any change that causes their version to be bumped up), you need to re-import them and build the application against the new version.

Basically: If the version that the client expects is different from the version the DOE sends, the DOs tables in the client will not be filled.

This is one of the possibilities I can think of.

Former Member
0 Kudos

Ah! You say you 'refreshed' the DOs in NWDS. Then this is probably not the reason for the problem.

Former Member
0 Kudos

Hi Christoph,

still facing this issue?

Like mentioned a few times before, most likely you have an issue with the process.

Every time you generate/change the Data object in the SDOE, you need to reimport the model into your Eclipse development framework. Then I prefer to presss F5 on the prioject to have a complete refresh, but that is just because I am a little paranoied if it comes to MI software.

Once this is done, build your app again and upload it to the server by SDOE_UPLOAD_ARCHIVE. Necessary, so the middleware knows the actual version of your used DataModel.

Then delete your client on the device completely and install it from scratch. As well delete the device in the middleware and create it from scratch. Install device locally again, setup,sync,app assignment,.....

If you do it like that the issue should be solved. If not - perhaps we should get in close contact and we can check.

As I said: this is only necessary if you change the data model and it is not the fastest solution, but it is the save way of solving that issue.

Reason: if you receive any DO from the middleware, it send a version number with it. If you deploy any sort of app, it stores the version number of the relevant DO at deployment time into the lokal table and it will not change that number again. So if you generate the DO in Middleware again, this number gets different on both sides and does not match any longer. If you now send data from middleware to client with new version number, it compares the numbers, they do not match, data is not booked into the persistence and now the funny thing: NO ERROR MESSAGE ANYWHERE

Well, so be paranoid and do the described procedure, hopefully it helps.

Regards,

Oliver

christoph_kurtz2
Participant
0 Kudos

Hi Oliver!<br>

<br>

I have resolved the problem. When regenerating the DO on middleware system, I made a mistake in naming it (forgot an 'i'). When trying to reimport the model in NWDS, there was no error message that the original DO isn't existing anymore so I thought that everything is OK. After importing the new DO and following the steps you described, data are coming to the client.<br>

<br>

Thanks to all for your suggestions!<br>

<br>

Best regards,<br>

<br>

Christoph

Answers (1)

Answers (1)

former_member185875
Contributor
0 Kudos

Hi Christoph,

I need some clarification's

1. Missing Data object having the data in CDS?

no, enter data in the back end and call your instance push.

yes,-->2.

2. Are you getting the missing data object up to pending extract?

no. deactivate and active the rule once.

yes.--->3

3. Check whether Refresh Queue for the missing Data object is configured.

4. If your done the all above steps already. I think it's problem with the client.

5. Reset the client. and do from scratch.

6. still your facing the problem. uninstall the client s/w and install it.

and do from scratch(redeploy,register,initial sycn etc..)

i think it's help to you.

Regards,

lakshman balanagu.