***Aloha Schedule Files for FOH enforcement (non-native)***

[RokStar]

We've created 20170524.sch files that appear identical to the old, native sch files. However, it's not working and I'm not sure why. It seems pretty straight forward.

I see that in Aloha QS 12.3, at some point, I assume EOD, the native (created by MenuLink) are ingested and a 20170524.ok file is created. The file then appears in DATA and the FOH can read it without issues. I have limited knowledge about the AlohaSchedule.dbf being some sort of "working area" for the ingest, but I understand, at least for MenuLink, it just simply needs to exist, which it does.

This homegrown file never sees a matching 20170524.ok file, and never makes it to DATA after EOD.

Is there anything I'm missing about creating a sch file for the FOH????

Thanks all!

 

[strangemadness]

The file needs to go into New Data, not data. I'm not sure why it is handled that way, but our system putsit into New Data and it shows in New Data on POS terminals as well, never being moved to data. It works properly with our mock .sch files.