cancel
Showing results for 
Search instead for 
Did you mean: 

MI 7.1 data objects push data to backend in some sequence

pvannest
Participant
0 Kudos

Hi all,

Let's say we have 2 data objects with no dependency between these. If we add instances of these data objects on the client in some sequence, can we be sure that these instances will arrive on DOE in the same order and will be processed in that order? Or do we actually have to define this order with report 'DOE_MAINTAIN_DO_SYNC_ORDER' ? But i've read on this forum that this is only for backward compatibility reasons... I find it rather strange that this sequence was easily be set in MI7.O with MI_MCD, but in MI7.1 it seams not.

In thread , someone says that this will be encorporated in the DOE workbench (SDOE_WB) itself. We are on MI 7.1 SP9. Is this the case then? Were can we do these settings?

Additional question:

Let's say there is a dependency between these 2 data objects, then i know that download request for leading data object triggers download request of following DO. Does this also define the update order from client to DOE?

thanks in advance,

regards

Peter

Accepted Solutions (0)

Answers (2)

Answers (2)

VikasLamba
Advisor
Advisor
0 Kudos

Hi,

I will answer your questions in the same sequence as posted by you.

1. If the objects have no association between them: In this case whenever on the client any change is made to an object the state of the transaction is commited to the device outbound queue. It does not matter whether Obj1 was modified or object 2. The order in which the changes are done will be the order in which the transactions will be commited to DB and the same order will be used by MI to process these messages when client syncs.

2. In case the objects have dependency: Here also the same principle works as in 1. Having a dependency between two objects technically drills down to having referential integrity between these objects. Lets say DO1 refers to DO2 instances. Then when you are saving DO1 your application would obviously ensure that it maintains the business referential integrity to DO2 else it will not even be a valid DO1 instance in your SAP Backend.

Thus the order in which changes are done on the client is what determines the order of processing of these instances on the server.

Regards,

Vikas

pvannest
Participant
0 Kudos

Thanks for feedback

rohith_deraje
Advisor
Advisor
0 Kudos

Hi,

The sequence of the instance will be same as you create on the client. Once you create an instance and Save, the instace will be pushed to queue. During sync it will be fetched in the same order.

Regards

Rohith