The customer themes not working after installing support package.

Question

Hi,
  In a Web dynpro ABAP aplication that i made in a project, we have a customer theme. We transported the development of a new host that had a higher level of support package, and it has stopped working properly the customer theme. We´ve gone from 7.0 sp 9 to sp 20. Well, when you run the programa WD_THEMES, in the ALV appeared to me not the customer theme. So I exported the standar themes and with Eclipse, I´ve copied and re-created the customer theme by modifying the latter.
Once changed, I try exporting to the test environment and it is here that the level of support package was sp18. I could not import it because the version was not the same.In the development environment was 7.0.19.1 and in the test environment was 7.0.15.1.
The question that comes to me is when we have a customer theme in a environment and upgrade the level of support package, is the version of all themes listed in the program updated or only the standar themes?. If this is so, if we upgrade the level of support package we will have to re-export the standar themes, copy one of theme and go back to redo our theme, right?.
Thanks and hope your answer.

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