xMAM30 order downloaded to the client even if cascade search fails in MI

Hello,

I have a strange behaviour on one of our systems. I created an order for which the partner is not replicated to the middleware. To my surprise the order is downloaded to the mobile client....

When I look into the log in merep_mon for MAM30_001 I see:

2007-09-06 10:53:05 MEREP_PROCESS_HANDLER_WL has started for run number 0000135260 and runtime counter 2

2007-09-06 10:53:05 Z_MEREP_GEN_S01_____MAM30_001 has started for run number 0000135260 and runtime counter 3

2007-09-06 10:53:05 MAM30_001_GETLIST has started for run number 0000135260 and runtime counter 4

2007-09-06 10:53:07 MAM30_001_GETLIST has finished for run number 0000135260 and runtime counter 4

2007-09-06 10:53:07 MAM30_001_GETDETAIL has started for run number 0000135260 and runtime counter 5

2007-09-06 10:53:08 MAM30_001_GETDETAIL has finished for run number 0000135260 and runtime counter 5

2007-09-06 10:53:08 Line items: R/3 key=000005105625, synchronization key=0001144137

, action=A, item number=62

2007-09-06 10:53:08 Line items: add=62, changed=0, deleted=0, not changed=0

2007-09-06 10:53:08 Objects found in R/3=1, passed filter=0, loaded filter=1

2007-09-06 10:53:08 Objects: Add=1, changed=0, deleted=0, not changed=0

2007-09-06 10:53:08 Mobile ID=0000000471: Total records=0, total worklists=0, conflicts detected=0

2007-09-06 10:53:08 Mobile ID=0000000471: Added=0, changed=0, deleted=0

2007-09-06 10:53:08 Cascade search failed; from (SyncBO=MAM30_001, SKey=0001144197

) to (SyncBO=MAM30_050, R3Key=KU0010000022)

2007-09-06 10:53:08 Downloader completed successfully (mobile ID: 0000000471, SyncBO: MAM30_001)

2007-09-06 10:53:08 Z_MEREP_GEN_S01_____MAM30_001 has finished for run number 0000135260 and runtime counter 3

2007-09-06 10:53:08 3 worklists found to be processed for mobile ID 0000000471

2007-09-06 10:53:08 MEREP_PROCESS_SENDER_WL has started for run number 0000135260 and runtime counter 6

2007-09-06 10:53:08 MEREP_PROCESS_SENDER_WL has finished for run number 0000135260 and runtime counter 6

2007-09-06 10:53:08 MEREP_PROCESS_HANDLER_WL has finished for run number 0000135260 and runtime counter 2

Now the strange thing is:

Cascade search failed and refers to synckey 0001144197, when I look to the synckey of the order this is different: R/3 key=000005105625, synchronization key=0001144137

In the other systems when a cascade search failed happens I find the same synckey for the order....

Any ideas what's going wrong?

Kind regards,

jeroen