The ATC process is part of RAPS and allows an organization to have a separate and segregated workflow for ATC type Requisitions that will not be accessible by normal RAPS functions and vice versa.

The process is similar to RAPS, in that a user enters a request, it goes for approval and becomes a purchase order. The primary difference is that every raised ATC requisition has an ATC number which is a unique contract reference which will tie all spending on that requisition to the ATC.

Every requisition raised will have its own unique ATC number. Any receipts or backorders will still remain tied to the original ATC number.

If a change order is raised to an original ATC, it will create a new revision number under the same ATC.

ATC set up is required in the RAPS Major Function Flags;

It is recommended for this process that the requisition is set to go to the buyer first;

and that the contract module is turned on;

The ATC menu has its own unique menu structure;

The ATC process conforms to the standard RAPS officer table. There is no need to specify a seperate tree for this process.