Home / Services and Requests / Interface – File Feeds / File Feed Policy and Procedures

File Feed Policy and Procedures

Financial Accounting Management Information System (FAMIS) is the accounting system of record for members of The Texas A&M University System that use FAMIS as their primary accounting system. FAMIS was designed primarily for the Fiscal/Business Office, which is accountable and responsible for the accounting records for the member. With many members and thousands of jobs to run, planning and coordinating member interfaces is extremely important.

The focus and mission of FAMIS have always been to provide support to the Fiscal / Business Office in their fiscal responsibilities. Over the years, functionality has been added to accommodate departmental needs, but departmental offices and central offices are increasingly developing or purchasing “side systems” to better meet their departmental or specialized accounting needs. Many of these systems may be programmed to “feed” data to FAMIS. Since the Business Office must be ultimately responsible for the data that enters FAMIS, FAMIS Services needs a Fiscal / Business Office coordinator for these interfaces.

Interface Coordinator

Each interface has tasks that must be addressed before it can be put into Production. The Interface Coordinator is the point of contact for both the Fiscal / Business Office (and member departments) and FAMIS Services. This person assumes the responsibility for the implementation and ongoing support of these interfaces.

Tasks for this person include:

  • Be the point of contact for each interface project.
  • Understand the requirements and monitor the process as the representative of the Fiscal / Business Office of the member.
  • Build knowledge of how interfaces work with FAMIS, including keeping information on the various interfaces that the member has with FAMIS, keeping layouts of the various transactions that are used for each interface and understanding the schedule that each interface follows.
  • Coordinate and attend the initial meeting between the Fiscal / Business Office (any member’s departments) and FAMIS Services to convey the requirements for the interface.
  • Coordinate subsequent meetings, correspondence and phone calls with the Fiscal / Business Office, the department, vendor and FAMIS Services.
  • Assume responsibility for the daily reports and investigate and reconcile any errors that may occur.
  • Assume responsibility for the integrity of the data and give final approval for the data to enter the records of the member.

All submitted batch interfaces that pass the FAMIS program edits are posted into the system. These batch feeds are NOT reviewed by the FAMIS Services staff before they are posted. It is the responsibility of the Business Office to ensure that the data passed to FAMIS has been reviewed and validated as legitimate accounting transactions before being sent by file transfer protocol (FTP) to FAMIS.

Interface Processes

New interface projects require communication between the member’s Fiscal / Business Office and FAMIS. The scope, requirements and potential issues are identified and addressed. When both parties have a clear understanding of the needs, solutions are better formulated.

The following steps are necessary for a smooth, successful process in creating your interface with FAMIS. They are divided into three sections: Preparation, Testing and Production.

Preparation

  1. Submit a Change Enhancement form with the basic information defining the new interface. The form is available on the FAMIS website at http://www.tamus.edu/offices/famis/.
    • Please provide the names and NetIDs for any users that will need access to the output in Laserfiche.
  2. Schedule and hold a Requirements Meeting with FAMISHELP (this can be by phone conference) to discuss the details and process of establishing this new Interface. Topics will include the purpose and type of transactions, the frequency of feeds, the principal persons involved, etc.
  3. FAMISHELP will define and send the following information:
    • Layout for the appropriate transactions
    • Name of the file(s): files are named according to the type of data. Test files are always posted to your Training Campus. The file for testing must have the TEST extension to help prevent accidental posting into Production.
      Sample file names are:
      • K7nnXX.deptname.JE.Dyymmdd
      • K7nnXX.deptname.JE.Dyymmdd.TEST
    • Batch Reference in the form of AAANNN or AAAANN (example:  BUD001)
    • Name of the program that will be used to post the transactions (example:  XFJE1)
  4. Send an email to famishelp@tamus.edu. The output will be reviewed to ensure the success of the testing.
  5. The Interface Coordinator or Authorized Requestor for Change Enhancements (or equivalent Manager) requests RACF security by sending an email to famishelp@tamus.edu that lists the names, UINs and FAMIS userIDs for the individuals performing the FTP process. This security is required for any individual utilizing FTP to send the file to the mainframe.

Testing

  1. FAMIS Services will prepare Training JCL and Laserfiche for the file testing.
  2. Prepare the test files and submit them by FTP to the K7nnXX directory on the mainframe server (TAMMVS1.TAMU.EDU).
  3. Send an email to famishelp@tamus.edu requesting that they post the test file. Include the name of the file to post.

    Sample email:
    K702XX.CORETECH.JE.FMSFEED.P02.TEST
    K720XX.CORETECH.CR.FMSFEED.P20.TEST
    Above files uploaded to your server.
  1. FAMIS Services will post the test files to the Training Campus and notify the A&M System member of the results.
  2. Review the TEST posting for posting and accounting transactions accuracy and any errors that are generated by the posting program. Please send a confirmation email to famishelp@tamus.edu and ensure that users have access to Training to verify the data.
  3. Repeat submitting test files until both FAMIS Services and you are satisfied that the interface is ready to post in the production environment.

At this point, FAMIS Help will close the support ticket created by the Change Enhancement Request.

Transition to Production

Send an email to famisprod@tamus.edu and famishelp@tamus.edu stating you are ready to send files to Production. This email should include:

  • How often you plan to send a file,
  • Who will submit the email to Production stating that a file has been sent by FTP to post,
  • Who needs to be a recipient for the Production output (someone needs to check the output for error messages each time) and
  • Whether you want a print copy as well as a Laserfiche copy.

Production

  1. FAMIS Services prepares Production JCL and Laserfiche.
  2. FAMIS Services completes the scheduling of the Production job(s).
  3. Prepare the Production files and submit them by FTP to the K7nnXX directory on the mainframe server (TAMMVS1.TAMU.EDU). Send an email to famisprod@tamus.edu to post the production file.
    The email should:
    • Be sent by the person who sent the original email,
    • MUST state the proper name of the file and
    • MUST be sent to Production BEFORE 3:00 pm for posting that evening.
  4. FAMIS Services posts the Production file(s) and releases the output to DDRINT.
  5. Review all output errors (something that didn’t post or has gone to suspense) and report any problems or discrepancies immediately to FAMIS Production.
  6. Make any manual corrections for all rejections or suspense items.

Changes to Production Files

ANY changes to an established Production interface must be retested in the training environment before proceeding to Production.

Contact famisprod@tamus.edu and famishelp@tamus.edu whenever any change to the process that generates the file(s) is anticipated or planned.

FAMIS_INTERFACE_Policy-Process