jimmymac
Reputable Poster
We are on E1 9.0 and have run into a menu maintenance issue. Currently, whenever we have had menu changes, we've just made them directly to the various environments, but I know they can be promoted via OMW as well. I haven't had the responsibility of managing menus until now.
Our issue was that when we recently refreshed our DEV environment from Production, we restored PRODCTL and PRODDTA and the result was that recent menu changes made in DEV were no longer there. We've had few menu changes so this hasn't been an issue but is now with some current major developer we have going on.
So the basic questions I have are.
1. How are people typically handing menu revisions. Do most use OMW and promote and deploy menu changes as any other changes like for UBEs and Apps? Or is making the changes directly in the environments typical also. Whats the norm or standard in JDE E1 currently.
2. Or does anyone have a recommendation on perhaps how to not have the menu definition overwritten when you do a data refresh. Perhaps certain files to not copy or restore? Any suggestions would be appreciated.
Our issue was that when we recently refreshed our DEV environment from Production, we restored PRODCTL and PRODDTA and the result was that recent menu changes made in DEV were no longer there. We've had few menu changes so this hasn't been an issue but is now with some current major developer we have going on.
So the basic questions I have are.
1. How are people typically handing menu revisions. Do most use OMW and promote and deploy menu changes as any other changes like for UBEs and Apps? Or is making the changes directly in the environments typical also. Whats the norm or standard in JDE E1 currently.
2. Or does anyone have a recommendation on perhaps how to not have the menu definition overwritten when you do a data refresh. Perhaps certain files to not copy or restore? Any suggestions would be appreciated.