FAMIS Sequence of Events

The schedule for the interfaces file transfers follows, starting with the KFS source export and ending with the FAMIS destination import jobs.

1a. KFS Account Export – S, M, T, W, T, KFS Batch start at 9:30 pm EDT (start date), Complete after midnight (start date+1), file names will reflect (start date+1)

1b. KFS Account Export – F, KFS Batch start at 7:30 pm EDT (start date), Complete after midnight (start date+1), file names will reflect (start date+1)

2a. KFS Vendor Export – S, M, T, W, T, KFS Batch start at 9:30 pm EDT (start date), complete after midnight (start date+1), file names will reflect (start date+1)

2b. KFS Vendor Export – F, KFS Batch start at 7:30 pm EDT (start date), complete after midnight (start date+1), file names will reflect (start date+1)  

3. KFS Account Export filename with start date+1 will exist on the Uconn batch server

4. KFS Vendor Export filename with start date+1 will exist on the Uconn batch server

5. PRD-KFS-Famiskfs_101account_xfer runs following genrateFamisCOAFile job, usually after midnight, to transfer 101account file, to Santa Clara, CA FAMIS

6. PRD-KFS-Famiskfs_101vendor_xfer runs following genrateFamisVNDFile job, usually after midnight, to transfer 101vendor file to Santa Clara, CA FAMIS 

7. Oracle job scheduled, FAMIS Stored Procedure, “ACCOUNTINTERFACE”, every morning at 03:15 am EDT, looks for filename with current date as of 03:15 am EDT

8. Oracle job scheduled, FAMIS Stored Procedure, “VENDORINTERFACE”, every morning at 03:15 am EDT, looks for filename with current date as of 03:15 am EDT