30 Jul 12 14:48
It sounds like you may have a problem with your menu levels, but it's hard to tell without knowing what kind of foundation you have set up. There's a lot of base work that has to be done before you can start running transactions. At a minimum you'll need to set up at least one each of these:
revenue center - where the sale get posted
period - defines periods throughout the day
auto-level - assigns a menu level for each period in each revenue center
menu level class - uses the active auto-level to determine menu item availability
menu item class - defines how a menu item behaves
major group - for reporting
family group - for reporting
You can add a menu item with just a name and link a button to it in the touchscreen designer, but that doesn't mean it's configured correctly. Without a menu item class, major group or family group you won't be able to order it. If you don't have your RVC, periods and levels set up correctly the menu item may never be available. Either case will give you a Menu Item Not Found error.
Honestly, if you're going to be writing a 3rd party application to access Micros you should probably hire somebody who knows the system, at least on short term contract basis. It's a pretty complicated database with thousands of options that don't all play nice together. Restaurant owners and managers can get by knowing very little about the system because they can always call their micros dealer for help, but as a developer you need an in depth understanding to make sure your product will work under different scenarios. I don't meant to be harsh, but I've stumped probably 80% of the salesmen and "technical leads" demoing 3rd party Micros applications with simple "what if" questions.