Exporting micros 3700 menu

[LethargicCoder]

We would like to export the menu from the 3700 to utilize it to display on a web server.

I can't find anything that clearly idicates what tables would be required to clearly show menu items, condiments, combo meals, etc.

we will duplicate the required tables and just select from the pos to update our copy.

Can anyone help out with a list of the tables that would be required for such functionality? And if posible any documentation that might clarify this and how the items are used?

Thanks

 

[pmegan]

It may be a bit tough to get this together, the menu items, condiments and combos use a lot of many-to-one and one-to-many relationships to keep things open ended and flexible. This might give you a start though:

Menu item tables
micros.mi_def - menu item file
micros.mi_price_def - menu item prices
micros.mi_type_class_def - menu item classes

Condiment (modifier) tables
micros.cond_grp_def - cond groups
micros.cond_grp_mem_def - cond group memberships, (what they belong to & which can be used)
micros.cond_grp_sel_def - cond group selection, (forced modifiers)

Combo Meal Tables
micros.combo_def - combo meal definitions
micros.combo_grp_def - combo meal groups (behaviors)
micros.combo_menu_item_def - combo menu items, (which menu items are allowed main items)
micros.combo_side_def - combo meal sides, (which menu items are allowed sides)

There are also db schema and domain reports in the micros/res/pos/reports folder, but if you're on a new version or service pack they may not be up to date. Sybase Central is pretty handy finding out how the tables all link together.

Hope this helps...
Pat

 

[LethargicCoder]

Thanks for your reply, it does help. I originally was thinking it was just the mi_ tables until I spotted the cond_ and combo_.

This definately reaffirms what I was thinking.

Eric

 

[LethargicCoder]

Does anyone know of any default user/passwords for the sample DB install on for 3700.

I am using custom/custom and with that I am restricted from some tables.

Something with more access like micros/? or DBA/?

Thanks

 

[pmegan]

Micros is, understandably, pretty protective of the admin passwords for the 3700. The current version has 1543 tables, 685 views, 1781 stored procedures and 1367 views. It also has user defined data types with default and check constraints for most fields. Supporting the product would be impossible if end users and third party vendors were allowed to make changes. I've been writing custom stuff for the 3700 for 7 years, up to additional total and tracking sets, and haven't needed more access than the custom user has. You just have to re-think the approach sometimes.

A good way to know what you can access is by the table name. Anything that ends in "def", (micros.mi_def, micros.fam_grp_def, etc...), will allow you to insert, update and delete data. Anything that ends in "dtl" will not. You can't make changes to the structure of any standard micros tables, procedures, etc...

It seems like you're developing some kind of web based system to place orders into a 3700. You're going to need to learn their proprietary scripting language, SIM, in order to get the orders placed. This will emulate keystrokes that the users would make and push the order through POS Operations. Inserting data for an order directly into the database probably won't work. POS Ops writes all kinds of info to temp tabels behind the scenes to keep track of itself. The only place to find info for this is in the Micros directories:
\Micros\res\pos\bin\Simhelp.hpl and
\Micros\documentation\res\pos\sim\3700SIM_CompMan.pdf.

Two last points in case you manage to get one of the admin access.
1) The dba & micros user passwords change with every release, so if your planning on installing on multiple versions you'll need multiple installation programs.
2) If you do makeany changes using one of the admin accounts it will void you're customers warranty and/or service agreement. If an internal database error occurs, especially if there's 3rd party software installed, one of the first things Micros support does is translate the db log and look for suspicious admin logins.

 

[LethargicCoder]

Thanks for your help. We aren't looking to make changes to anything in the schema or write to the DB at all.

We are doing an external order entry.

For this aspect, we just want to read tables to be able to represent the menu both visually and for order creation. We should only be doing selects to copy the information from the tables discussed above. The only reason I was looking for more access is that I was having difficulty generating DDL for the tables and it appeared to be an access isssue.

For entering orders. Micros just released a WebService component (POS Transaction Services) that should allow most of the functionaliaty we were looking for. SIM programming would definately be another route and maybe would have been the better one (Micros didn't really mention SIM to me when I first talked with them).

 

[pmegan]

You should be able at least see all the tables, except for some of the system tables. Are you using sybase central to look at the db? If not then it's definately the way to go.

I forgot about that new component. Unfortunatly my company won't be using it so I haven't looked into it at all. It sounds pretty cool though.