What/How it runs
WIM, daily 7:10PM, W_FastCommand
fastcommand.kni
 fastcommand.knx
 fastcommand.bat


Parent process
none


Child process
FastHealth picks up the file at 12:00Midnight and processes it into their dbase tables
 and send Joann a huge "results" email
THEY MUST RENAME FILE ONCE PROCESSED TO FastCommandSent.txt


Input system/files
Lawson dbase tables


Output system/files
common\lawson\FastCommand.txt


Automation
SFTP to the FastHealth, They cannot do key authentication, will have to use sftp/pword.


ARCHIVE
only archives one day of files
common\lawson\FastCommandSent.txt


Hard Coding
EMPLOYEE.emp_status not in ('00','T1','T2','T3','T4','T5','T6','T7','T8','T9');


Contacts
Lawson Team - Joann Powell, Ruth

Fast Command contact
Dennis Carwyr (programmer type)
205.752.5050 ext 122
dcarwyr@fasthealth.com

Thomas Jones (Sys Admin technical type)
205.752.5050 ext 113
tjones@fasthealth.com


DOWNTIME
none - it is a refresh of employee data, they can do without for a day or two.
can run early, can run late, can run multiple times.


Notes I found
FastCommand KNI generates an output file, FastCommand.txt, from Lawson.  It is then sent via SFTP to the FastHealth folks to keep our data in their system updated on a regular basis.

They cannot do key authentication, will have to use sftp/pword.

Sent to:
clients.fastcommand.com
username - fgeneral

DOWNTIME:  No downtime action required.  Can rerun as often or whenever necessary.  It only puts a file of active emps on the Fast Command server.  Fast Command will have to run their import process to ingest the file if required outside of normal automation times which is midnight CST every night.  If there is not a file, it will not care.

Fast Command contact
Dennis Carwyr (programmer type)
205.752.5050 ext 122
dcarwyr@fasthealth.com

Thomas Jones (Sys Admin technical type)
205.752.5050 ext 113
tjones@fasthealth.com

http://forrest.fastcommand.com/
admin username - forrest