Acuity Logic Status Update File
Rx-Universe can create a status file to update Acuity Logic with the status of all jobs in the LMS.
This file is in the same format as that used for Acuity Logic Status Updates by VisionStar. One file is created for each customer, based on the ship-to of the account.
Each file will be named “lmsstat.cccc”, where cccc is the ship-to number. Files will be placed into a subfolder called “Acuity”, under the folder specified for the status files in the Remote Parameters configuration:
Each file will contain all in-process orders for the ship-to number of the file, plus all orders completed in the current day for the same ship-to.
This program will normally be run in the Windows task scheduler, on a schedule and interval desired by the lab. (It can also be run from the command prompt for testing purposes).
Layout of each record in each file
Each record (line) contains fixed length fields as follows:
Field | Start Column | Size |
---|---|---|
Acuity Logic order number (PO number field in Rx-Universe) | 1 | 20 |
Rx-Universe order number | 21 | 9 |
Station location code | 30 | 4 |
Station description | 34 | 20 |
Receive date (mm/dd/yy) | 54 | 8 |
Receive time (hh:mm) | 62 | 5 |
Date completed (mm/dd/yy) | 67 | 8 |
Entity (always 0101) | 75 | 5 |
Station description | 80 | 20 |
filler (spaces) | 100 | 32 |
HOW TO RUN THE REPORT
Pre-requisite: One-time setup for this is to set the directory for the report in the REMOTE > REMOTE ORDER PARAMETERS > Directory for status files. The “create status files for jobs” needs to be checked to update the “Directory for status files”. After the directory is entered, you can uncheck the flag if it was not checked. Note that the program will add a subfolder called ““ACUITY” to the path entered (this is needed so the Acutity files do not adversely affect the remote order status logic within the remote processor.
Running the program through Window Task Scheduler
Set up the schedule to run the extract; for example, to run from 9am to 9pm every 1 hour, the Trigger might look like:
Once the trigger has been set up, the “Action” for the scheduled task is:
Program: wrun32.exe (optionally with the complete path if it is not in the system PATH)
Arguments: -c omics.cfg -y omics6 -y xmlif.dll CALLRXOSTAT “PGM=RXORDSTAT”
Start in: [root Rx-Universe folder] - for example, C:\RXUNIVERSE if that is where RxU is installed.