Micros 3700/4.9

[jason5641]

Ok, here goes nothing...

I am the technical guru for a payroll processing company (PEO). I am trying to assist our sales department in bringing in an account, and currently they use ADP - which has its own Micros interface. Their current Micros support provider is refusing to assist, stating that it would require a complete interface overhaul, even when I ask them if they have a very basic interface/SQL module that could simply be tweaked for the potential client.

So, I've been asked (without a Micros POS to play on, of course) to try to put something together as a starting point for the support company in an effort to cut our expense (we have informed the potential client that we will pay up to a certain point for the necessary interface/module) of trying to on-board this client.

What we need is a dated CSV file - SSN, last name, first name, job code, date worked, hours for that person/job code, and cash/charge/declared tips for that person/job code. The issue is, as mentioned previously, I don't have a system for my own experimentation.

Could/would anybody be willing to assist? What we need is the mentioned data above, a simplistic interface that the client can use to specify the necessary date range, and a 'Save As' dialog to pop so the client can specify where to and what to name the CSV file... Again, my issue is that I don't have one of these systems to play on for myself.

Thanks in advance!
-Jason

 

[Wildbar]

Use the Micros Export utility. They will need to get it licensed but that license is pretty inexpensive. They should be able to put it there micros system in demo mode for that module and you can do a export ( think it limits to 10 items in demo mode) and you can see if that gives you the info you need You will need to build the sql request for the payroll info.

 

[pmegan]

The Export utility will take care of the user interface portion of it. I've never used it in production so don't know if it can be scheduled to run with an autosequence. If it's like other 3700 modules it will spit out a file with a hardcoded name which would have to be renamed with some kind of program or script, but that's just a guess.

You're really going to need a test system to write the export. Most of what you want is pretty easy to get by linking the time card, employee def and job def tables. It gets sticky if the database is set up to post a percentage of charge tips to tips paid. The most common reason for this is taking a credit card percentage out of the charge tips. I don't like the practice, but it's relatively common. So if there's a $100 tips and the "post a percentage" is set to 98, the charge tip is still $100 but tips paid, which isn't in the time card detail, will be $98, which is what the server collected and should be taxed on. This total is held in the employee shift totals, but that table of course doesn't have any links back to the time card table, that would make things too easy.

As a payroll processing company it may be worth the money to have a 3rd party take care of the SQL side of this.