1. ATC Requisition is entered by end user
2. ATC Requisition flows to the buyers for review and updating. Once buyers are happy with the details they will push it into the approval process based on dollar limit.
3. ATC Requisition will flow to each approver to acknowledge until it gets to an approver with the correct dollar limit.
   1. This information is held in the RAPS Office Table.
4. Once the ATC has been acknowledged and approved from an approver with the correct dollar limit, it becomes a purchase order.

This screen is given to the users that are listed as buyers. The primary purpose of this screen is to review and revise the requisitions. This screen is used to correct, remove, revise, or reject ATC Requisition that are going through the approval process. All ATC Requisitions will first go to the buyers before it is sent into the approval workflow.

Buyers will have their authorization code as all ???????

On this screen he primary purpose is for the buyer to review and revise Reqs.

When the buyer is done correcting and updating the information in the ATC Requisition they use the mode Revised.

This mode will send the ATC Requisition into the approval workflow to get approved, acknowledged, or rejected.

When the buyer hits the revised button on an ATC Requisition they will get a warning pop up like below. This is just confirmation that they are done editing this requisition and it is ready to go into the approval process

Once the buyer hits yes, that requisition will flow to the next approver on the authorization tree.

This screen is given to users that have an approval limit and are in the approval workflow in the RAPS Office Table. This screen is used to acknowledge, reject, or approve ATC Requisitions that are coming through the users approval flow.

When the approver accesses this ATC Requisition Approval screen they will only see ATC Requisitions that are sitting with them for action. 

On this screen the approver can do many different things. Details of the modes and functions are listed in below sections.

1. View Header, Lines, and Cashflow information
2. Reject the ATC Requisition back to the originator
3. Add Notes and Documentation (ATC Doc Register)
4. Review information for Budgets and Audits
5. They also have modes called Approve and Acknowledge

At this stage in the process, the approver has three options: Reject, Approve, Acknowledge

Reject - Sends the ATC Requisition back to the originator 

Approve

• Checks the users approval limit. If the requisition is inside of the limit, the requisition will be approved and converted into a purchase order
• If approver does not have the correct limit they will get the error below and they will need to go back and acknowledge the requisition

Acknowledge

• Checks the users approval limit. If the requisition is outside of the limit, the requisition will be acknowledged and moved up the authorization table to the next person in the approval work flow.
• If the approver does have the correct limit to approve the user will get this error. The user will then need to go back to that requisition and approve instead of acknowledge

Once the ATC Requisition has gotten to an approver who has the limit to approve the requisition, that is when the requisition is converted to a purchase order.

This screen gives the end user the ability to correct and resubmit any ATC's that were rejected in the approval process.

On this screen the end user can do multiple things to the ATC that was submitted.

1. Correct the Header and Lines of the ATC
2. View notes, audit, ATC Doc Register, and Cashflow
3. The user can cancel the ATC if it not longer needs to go through the approval process
4. Lastly, once the ATC is correct the user can resubmit the ATC to go back into the approval process.