MAM Not Working After Applying Support Package

Question

We have been lived with MAM 2.5 with SP16 for almost a year now.  We recently applied support package 19 for ABAP and J2EE stacks but MAM stopped working right after that.  To fix the problem we had to do the following steps:
1.  Disable all SyncBO
2.  Regenate all SyncBO
3.  Run Replicate Database
4.  Enable all SyncBO
5.  Delete MAM 2.5 client by WebConsole for all PDA (over 100 devices)
6.  Re-Assign MAM 2.5 client back to PDA from WebConsole
My question is do we have to perform those steps above every time we are applying new support package?  If it is a case, it's very time consuming because we have to manually perform step 5-6 for every users.
Does anyone have seen or experience this scenario before?  Your comment is highly appreciated.
Regards,
Dai Ly

Answer 1

Hi Karthik,
Let me clarify on "Not working"
It showned synchrozation successuffly but no data transfer between client and middleware and vs.  For instance, the user never receive any new work orders, or their times never got transfered back to R/3.  Even though, there is no error on the client.
It appear that step 1-4 are required otherwise, you get ABAP Runtime error (using ST22):
Runtime Error          CALL_FUNCTION_NOT_FOUND    
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          02/07/2007 08:12:27        
After we performed step 1-4 but there were data transfer between client and R/3.  The only way to get it working, we had to delete client and re-assign MAM 2.5 back to each users.
No, we didn't apply client patch SP19.  We are still using SP16.
As we speak, everything is working because we had to re-assign MAM 2.5 for every users. but I hope we don't have to do this next time we apply another Support Package.
Thanks.
Dai Ly