RAPS Email Log
Log of all emails triggered by RAPS
Written by Jarrad Sonnenberg
Updated at November 29th, 2022
-
Requisition Approval Processing Suite (RAPS)
RAPS Setup RAPS Utilities RAPS Requisition Entry RAPS Requisition Approval RAPS Convert Approved Reqs RAPS Purchase Order Cancel RAPS Delegation Maintenance RAPS Contract Module RAPS Expediting Module RAPS Pre-Revision Quotation Module RAPS - ATC Process (Approval to Commit) RAPS Enquiry by PSA Air Department RAPS Cost Controllers RAPS Unbudgeted/Budgeted RAPS Change Order Mode
- AP - Automated Invoice Workflow
- AP - Payment Approval Management
- Global Upload Program (GUP)
- Document Register (DocReg)
- Rotables / Component Changeout
- PSA Mining Report Suite
- Standard Pronto Modules
- PSA HelpDesk
The RAPS email log is a log file of every email triggered by RAPS.
Modes
Find
The Find mode will search the datagrid based upon the Requisition number and back order flag
Order Enquiry
Order Enquiry will take the user to the PO/Requisition header.
Fields
Order No/BO Flag
This is the Requisition/PO Number
Email Seq
This is the number of the step that has been taken in the requisition that generated an email. Every email generating action, such as acknowledgement, approval, rejection or entry generates a unique sequence for each user.
Reason Code/Desc.
The reason codes are codes specific to the TYPE of email that is being generated by the system. Each Reason code detailed what type of email was sent to the recipients. As an example, a reason code of Y, is the APPROVED email, and this would send to the end users to let them know their requisition has been approved.
Entered
No entry in raps-po-acknowledgement
Purchase-order.po-reason-code is “ “
Email: Please Approve/Acknowledge
Acknowledged Needs Approval
raps-po-acknowledgement – rpa-level-last-ack
Purchase-order.po-reason-code is “A“
Email: Please Approve/Acknowledge
Approved
raps-po-acknowledgement – rpa-level-last-ack – this is not edited.
Purchase-order.po-reason-code is “Y“
po-requisition-approval-user = APPROVING USER
Email: Approved
Requisition Unapproved by Approver
raps-po-acknowledgement – rpa-level-last-ack – this is not edited.
Purchase-order.po-reason-code is “A“
Email: Should not be triggered by unapproved
Rejected
raps-po-acknowledgement – rpa-level-last-ack is the rejecter
Purchase-order.po-reason-code is “R“
Email: Rejected
Resubmitted after Rejection
raps-po-acknowledgement – rpa-level-last-ack is the re-submitter
Purchase-order.po-reason-code is “T“
Email: Please Approve/Acknowledge
Needs PO Revision
raps-po-acknowledgement – does not exist
Purchase-order.po-reason-code is “W“
Email: Please review
Revised
raps-po-acknowledgement – does not exist
Purchase-order.po-reason-code is “V“
Email: Please Approve/Acknowledge
If the major function flag is set to send Reqs to Originator from the PO Officer, it sets;
raps-po-acknowledgement – does not exist
Purchase-order.po-reason-code is “O“
Email: Revised
Resubmitted after Revision
raps-po-acknowledgement – rpa-level-last-ack is resubmitted
Purchase-order.po-reason-code is “T“
Email: Please Approve/Acknowledge
Requisition reverted from a PO being edited
raps-po-acknowledgement – rpa-level-last-ack is set to blank
Purchase-order.po-reason-code is “Y“
Email: Please Approve/Acknowledge
Email to Address
This is the email address that was used for the email notification.
