Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micros 2700 SLU and Shell Screen 1

Status
Not open for further replies.

Narvin

Programmer
Jul 27, 2011
18
US
I have a basic understanding of SLU's. I get that there are up to 32 SLU's with hex codes 0x0130 through 0x014F. You can then assign an SLU to a menu item from 1 to 32. Now you can define a button with FNC code 0x0130 which corresponds to SLU 1, for instance, and when you press that button, it will bring up a screen with all menu items that have an SLU of 1. A button with FNC code 0x0131 will bring up all menu items with an SLU of 1, and so on.

But when you press one of these buttons that have an SLU lookup code, in addition to a screen with menu items with the corresponding SLU, there are some other buttons, like Pay, Print Check, etc. These other buttons always appear in a fixed location, no matter the SLU menu items.

There is a touchscreen defined at location 13 that is named Food Shell. It contains these other buttons that always appear in the locations that they appear. So this screen seems to be attached to the SLU buttons.

My question is, how do I assign a different screen as the shell screen? I don't want to modify the original shell screen in case I mess something up. I'd rather create my own shell screen. Or is the shell screen automatically whichever screen is defined as screen 13? That seems random to me.
 
OMG Narvin, now you're asking a lot!

When you go into screens you'll see a style button. The # of styles available are programmed in the memory config so if there's 10 and you need more you'll need to add more style in the memory config but you can have a lot so don't worry re: using up memory (small stuff). You program a TS style, size of the buttons that appear (SLU's), size of font (1,2,3), whether or not they alphabetize, and the last line is what TS # do they use as a default (you call it a shell). Let's say you use a blank line, let's say it's line #10. You want 2x1 buttons, size 1 font, and link this style to screen #20. You then actually program screen #20 to be a "shell", (which is basically what the screen looks like before all your SLU's show up). So on screen #20 you program a print, send, and prev button (just 3 to keep it simple). So now you have a TS#20, and a newly programmed style (that links to TS#20) and the only step left is to link the style to the SLU#. Go into Revenue center, select overhead and page down, there you'll see a chart of 1-32 SLU style links. Each SLU "must" link to a style. If your using SLU #14 (for the menu items) go to line #14 and put in the style # (it's the line #) in this case #10.

Sounds nuts but take your time and as you see the other items programmed I'm confident (based upon your posts) you'll start to grasp the concept. Good Luck.
 
Thanks TobeThor. Your post was invaluable in helping me to design a new shell screen.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top