MFF DOA
Delegation of Authority Controls
Written by Jarrad Sonnenberg
Updated at September 9th, 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
- AP - Automated Invoice Workflow
- AP - Payment Approval Management
- Global Upload Program (GUP)
- Document Register (DocReg)
- Rotables / Component Changeout
- Standard Pronto Modules
- PSA HelpDesk
Table of Contents
The DOA MFFs refers to a subset of functionality in PSA Air for Delegation of Authority approval. Documentation on how the DOA functionality works can be found in the DOA Overview section.
The standard process in Air, is that once an invoice is marked by the department as READY FOR PROCESSING, the AP team can post the invoice to the GL. When the DOA is activated, an additional approval is required prior to the invoice being visible to AP for posting. Its a second approval level that can be tailored to a customers DOA matrix.
DOA vs Payment Approval
It is important to note that the DOA functionality will be ignored if there is an entry in the MFF table for PMNT_APPR. PMNT_APPR is an approval that would occur AFTER the invoice has been posted to the GL to enable the invoice to show up on a payment run. DOA uses the same principles but is PRIOR to the invoice being posted.
Summary;
- DOA is second approval of an invoice PRIOR to AP posting
- Payment approval is second approval of an invoice AFTER AP Posting
Each flag impacts the DOA matrix in the following ways;
DOA_REQD
This flag will turn on the DOA approval process. The warning above notes that if PMNT_APPR exists the DOA will be ignored, and even if this flag is turned on, the DOA will not activate.
The flag is a Y/N flag. If it is set to N, the DOA process is ignored. If the flag is set to a Y, then the DOA will be activated.
DOA_THRESH
This flag refers to a thresh hold for the value of invoices that should go through secondary approval.
IE, if this flag is set to 5,000, only invoices with a value of over 5,000 LOCAL currency will go through for secondary approval in the DOA. If the Invoice value is lower than this threshold, it will proceed directly to the Ready for Processing screen.
DOA_MINAPP
This refers to the minimum number of people that must approve a DOA invoice. If it is set to 3, then the invoice must have been approved by people on level 1, 2 and 3 for it to be released into ready for processing.
DOA_DEPT
This will activate the departmental DOA approval process. There are two process flows in the DOA.
The first being the DOA acts as a financial approval tree above the approval of invoices, with no specific link to a department. If this flag is set to N, then anybody in the DOA can approval any invoice from any department. This is commonly used when treasury of finance people are using the DOA from a compliance perspective.
The second being the DOA is actually departmental. So if an invoice comes through from the Safety department, and is approved by somebody within that department for DOA approval, only DOA approvers with access to the Safety department can see or approve those invoices.
This then allows the user to set up users by department in ZUIT.M018 PSA Air - DOA Users.
DOA_CONF
This flag will control if a pop up shows when pressing approve in the DOA screen.
If this flag is set to a Y, it will suppress the warning message below. If it is set to N, it will show the messages.
DOA_1APP
This flag allows for a user who is both an approver at the department level and the DOA level to perform all their actions in one passing.
Example: Mining manager can approve departmental invoices. Mining manager is also a DOA approver. Instead of the user having to approve the invoice two in two places, this flag being turned on will automatically perform the DOA approval when their departmental approval is executed.
This is used to streamline the approval process for the users.
DOA_LMTU
In initial versions of the DOA hierarchy, each level of the DOA had a dollar amount. When DOA evolved to be by department, clients needed greater control over who had what limit within the DOA. This flag, if turned on will use the limits from the DOA Departments screen that can be specified at a user level in ZUIT.M018 PSA Air - DOA Users.
