‎2009 May 15 12:30 PM
Hi abapers,
I have created a ztable and it is working fine on dev and quality server,
but when i am transporting it to prd server, and trying to create some entry ,
it is giving runtime error....
but i am able to make entries in dev and quality server...
Error message:
Error analysis
Program "SAPLZHARY" tried to use screen 0012.
The screen does not exist.
However this screen is already there in table maintainence
‎2009 May 15 3:36 PM
Hi,
Just check in production whether the screen 0012 corresponding to the table maintenance exists.
If exists, then it is better to delete the table maintenance created and then create it again in development and then transport it.
‎2009 May 15 12:37 PM
Hi,
Check whether the request relaetd to table maintanence has moved to production or not?
Regards,
Swarna M
‎2009 May 15 12:39 PM
yes its is already done....
This is basic step and i have already take care of this ...
‎2009 May 15 1:29 PM
in the production system try to check whether the Function Group for the table maintenance is Activated or not.
Try to reactivate the Function group.
Regards,
gurpreet
‎2009 May 15 2:01 PM
Transport the Entire Function Group to Prod and it will work, I can sense that the screen is missing in production version. Do the version comparison to understand whats missing.
Regards
Shital
‎2009 May 16 4:52 AM
Thanks for the reply ....
I have done all the steps before posting this question..
except the version comparison...
so can u pls tell me how to do this...
Edited by: Aarif Baig on May 16, 2009 5:53 AM
‎2009 May 16 11:26 AM
Hi Aarif,
Follow below steps to do the version compare for screen:
1) Go to se11 and then table Maintainance
2) Click on Overviewscreen specified in maintainance
3) Now from Menu Utilities -> Versions -> Version Management. Now specify the production systems name in the pop up.
4) Again click Remote Comparison.
Hope this help!
Regards
Shital
‎2009 May 15 3:33 PM
‎2009 May 15 3:36 PM
Hi,
Just check in production whether the screen 0012 corresponding to the table maintenance exists.
If exists, then it is better to delete the table maintenance created and then create it again in development and then transport it.