Direct approvers (individual users) for check requests must have either the User Is Invoice Approver or the User is Requisition Approver box checked on their user profiles. (Both can be checked.) Materials Management users: This chapter covers setting up buyers who authorize purchase orders and approve requisitions, invoices, and check requests.
AP Users: For vendor and Check Name approvals, see Vendor Approval Processing.
General Ledger users: This chapter covers mass maintenance for journal vouchers. For the entire approval process, see Journal Voucher Approvals.
System administrators set up identities and permissions for users, including users who approve requisitions, invoices, check requests, and journal vouchers.
Once users are identified to the system, they can be assigned to review and authorize purchase orders from particular organizations, departments, asset locations, and vendors. Buyers and other staff at a site may also research the cost of requested items and approve requisitions. For any user who creates requisitions, the system administrator assigns an individual approver (Direct Approver) or approver group that handles requisition approval.
Similarly, the system administrator can designate users who approve invoices, check requests, and journal vouchers, and assign the users to approver groups. For sites that delegate different dollar limits to approvers, approver groups provide automatic routing of requisitions, invoices, check requests, and journal vouchers. In this way, all approvers who need to approve a document have a chance to do so.
To access organization, department, or asset location data, the organization, department, or asset location must be included in your data profile. Additionally, for any asset location, you must have permission to maintain the asset location record. See "Restricting Users from Editing Asset Location Records."
As described subsequently, approvers must be designated as such on their User Profiles. Approvers are assigned approval limits (dollars). You can also set related approval characteristics, such as how the approver is notified when an element requiring approval is available. Each approver can be assigned an Approver Buddy who handles approvals when the normal approver is out of the office.
Buyers and other users who authorize purchase orders must have the appropriate permissions set in their user profiles. The dollar limits on purchase orders that a person can authorize must also be established for item cost, item extended cost, and PO total cost. Finally, an authorizing user can be designated in the system's records for each organization, department, vendor, and asset location, and for each item type (stock and non-stock/non-file) within an organization.
Depending on the structure of your hospital, you can set up different configurations for requisition approvals. You can assign an approver to each user. You can also create approver groups, made up of several approvers. When you set up an approver group, you specify the order in which requisitions are routed among the group members.
You can assign each department an approver group or a single direct approver (but not both), and an approval profile. Approval profiles contain the dollar limits allowed for different item types (stock, non-stock, non-file) on requisitions.
You can assign one approval profile to a department for bill-only requisitions, and a different approval profile for all other requisition types.
Separate approval paths can be established for commodity items. Bill-only requisitions do not split for commodity approvals. (Typical requisitions that contain lines with commodity codes split those lines into one or more separate requisitions for approval routing. Bill-only requisitions do not do this.)
Requisition reviews proceed through these stages: costing, commodity code, and item type as follows:
If you use approval profiles for your departments, you can assign each department a separate approval profile for bill-only requisitions.
Requisition approvers are typically designated as buyers in their user profiles. User profiles also contain approvers' dollar limits.
Dollar limits and item type requirements are also specified in the user profiles of staff who are allowed to create requisitions. These staff are designated as requisitioners in their user profiles.
Each member of an approver group can approve or reject requisitions up to his/her dollar limit. (Two users in the same group cannot have the same dollar limit, however.) Requisitions are routed within an approver group based on the cost of the requisition, and each group member's approval dollar limit. Users with Administrator privileges create and maintain approver groups.
The Invoice Approvals process enables designated approvers to review and approve or reject invoices created in the system. Any PO invoice, manually-created invoice, or recurring invoice can be put into the approval process, except for invoices created from EDI 810 documents.
The Invoice Approval process, similar to requisition approval, contains an approval workflow that allows invoices to be reviewed by a single “direct” approver, or routed to several approvers in an invoice approver group. Each approver has an approval queue containing invoices awaiting approval.
Invoice approver groups allow invoices to be routed to multiple approvers. Invoices are routed within a group based on the amount of the invoice, and each group member's approval dollar limit. In the routing process, an invoice’s Total is compared to each Approvers Maximum Approval Limit to determine if the approver needs to review the invoice. Each member of an approver group can approve or reject invoices up to his/her dollar limit. (Two users in the same group cannot have the same dollar limit, however.)
Either an approver group or a single approver (Invoice Direct Approval User) is assigned to each person who creates invoices. Users with Administrator privileges create and maintain approver groups.
The invoice approval process and setting up invoice approval groups is described in a separate topic: Invoice Approval Processing.
Once created, check requests are routed for approval. The approvals process contains an approval workflow that allows each check request to be reviewed by a single “direct” approver or routed to several approvers in an approver group. Check requests can be assigned either a requisition approver group or an invoice approver group.
Direct approvers and approver groups for check requests can be identified on a departmental basis. Each department that uses check request processing selects approvers and/or approver groups which are then retained in the department record. If no check request approver or approver group is selected for a department, a user in that department making a check request must specify an approver or approver group on the check request itself.
Direct approvers (individual users) for check requests must have either the User Is Invoice Approver or the User is Requisition Approver box checked on their user profiles. (Both can be checked.)
If a department assigns an approver group to its check requests, the approver group can be either an invoice approver group or a requisition approver group.
Groups of both types are included in the selection list for the AP Check Request Approver Group on the Department Record edit panel. If you set up one or more requisition approver groups or invoice approver groups, that is sufficient for check request processing.
Check request approvers can designate an approver buddy to handle their check requests that need approval when they are out of the office.
Creating and processing check requests -- and setup steps -- are described in a separate topic: Check Request Processing.
Users who authorize purchase orders must be identified as buyers. Buyers authorize purchase orders, but also typically serve as approvers for requisitions and possibly check requests, invoices, and vendors.
To identify a user as a buyer, as with any other user, a system administrator first enters basic information into the application to establish a user profile. User profiles include the user's name, ID, phone number, etc., along with permissions for features and access to a hospital's data records. When you create new user IDs for staff at your site, you assign each user ID a role and a data profile.
A role specifies the application features -- called role objects -- that users assigned to the role may work with. For example, the Buyer role includes the Approval role object. Each role object is set to a security level: None, View, Create, Modify, and All.
A user profile also has a data profile associated with it. A data profile specifies the organizations, departments, and asset locations whose data the user can access. Review your data profiles to determine which one contains the medical center units whose data the buyer will work with, and assign that data profile to the buyer.
The discussion in the following sections assumes that you already have some users set up at your site with basic information, and need to assign them the Buyer role. If the Buyer role -- or a role with a similar name -- does not exist, you can create it. See Set Up and Maintain Users for details.)
You must be a system administrator to view and access the Administration Contents.
).
Several restrictions exist on de-assigning users as approvers/authorizers.
For requisitions and check requests:
For invoices:
You can remove a user's ability to approve requisitions, invoices, and/or check requests by clicking the checked box (Figure 2). The check disappears, and the user is de-assigned.
The steps below assign dollar limits to a buyer for authorizing purchase orders. The buyer can authorize purchase orders for items with an item cost up to the amount entered in the PO Item Cost Limit field. The limit for the line cost that a user can authorize is in the PO Line Extended Cost Limit. The total amount for a PO that the user can authorize is specified in the PO Total Cost Limit.
In Figure 4, the buyer can authorize POs containing items that cost up to $6,999.00. The total dollar amount for a line on a PO that the buyer can authorize is $69,999.00. The buyer can authorize purchase orders whose total is less than $699,999.00. This buyer is allowed to approve price changes on items up to $3.00.
No Dollar Limit Authorization - If you wish to give a buyer no dollar limit, enter a very large value (9,999,999.00) in the fields for PO Item Cost Limit, PO Line Extended Cost Limit, and PO Total Cost Limit.
For each of your approving users, you may wish to identify another user as an "approver buddy." An approver buddy performs the work of a direct approver and an approver group member if the normal approver is out of the office. Your approvers can set their out-of-office status when they leave the office for a vacation or trip, and their approver buddy will be routed their invoices, (or journal vouchers, or requisitions or check requests) for approval.
You can specify dollar limits on approvers so that an approver going out-of-office can select a buddy approver who has the same (or higher) approval limits. This feature requires setting a field in System Values, and assigning Requisition Approval Limits and/or Invoice Approval Limits to users who approve requisitions, invoices, and/or check requests, as appropriate. On the User Profile Approver Limits tab, these limits fields are at the bottom (Figure 5).
This feature applies to approvals for requisitions, check requests, and invoices. (Journal voucher approvals and vendor approvals are not included.)
A System Value "Restrict Approver Buddy by Approval Limits" enables this feature for requisition, check request, and invoice approver buddies. When the system value is enabled, approvals route to assigned approver buddies with the appropriate limits. When the system value is not enabled, approvals route without the restriction of approval limits defined for approver buddies. This system value field is audited.
You can set an out-of-office approver buddy as described below. In the example, the current user "JamesB" has an approval limit of $2000.00 and he is going out-of-office. All potential approver buddies also have approval limits set on their User Profiles.
Imagine that the approver limits in Figure 5 are for user "NancyM." Next we will assign "NancyM" as a buddy approver.
The My Out-of-Office Status panel appears (Figure 7).
Suppose instead of using the prompt to get a select list of approver buddies, you keyed a user into the Invoice, Requisition, or Check Request Approver Buddy field. The system checks that the user you selected is valid; that is, has an approval limit equal to or greater than yours. If not, an error message appears) and you must designate another user, or chose from the select list.
On the User Settings (All Columns) list, the Approval Limits are displayed in the last two columns on the right.
The User Maintenance template (Work in Administration > Administration > User Create Template) also includes the Approval Limits fields for importing when you create new users.
Each organization at your site has a default buyer. If you need separate purchase orders for stock and non-stock items, you can also assign an organization a buyer for stock items and a buyer for non-stock/non-file items. Purchase orders for each type of item are routed to the designated buyer. Each vendor buy-from location may also have several buyers assigned to it, but one buyer must be named as the primary buyer. Additionally, you may assign a buyer to each department, and finally, to any asset location.
Thus, a purchase order can fall under the jurisdiction of several different buyers. When this situation occurs, the system uses the following strategy to locate the appropriate buyer, and to route the PO:
You must assign a Default Buyer to each organization when you create the organization record. You can define and configure an organization from the main Contents by selecting Tables > Organizations. The Default Buyer field is located on the Organization record Main tab, as shown in Figure 8. (Click the prompt to select a buyer from the list.)
In medical centers that keep materials inventories, some organizations may need separate purchase orders for stock and non-stock / non-file items. In this case, you assign a buyer to stock POs and a buyer to non-stock / non-file POs. You can make the buyer assignments on the Organization > MM Information tab (Figure 9). Be sure to also select the field Separate PO By Item Type.
You may assign each department in your organization a buyer, if you wish.
or Menu > Edit next to the department. 
An asset location may be a storage area that maintains a physical inventory of supplies. An asset location may also be a "virtual" organization that contains only inventory records for items, and handles requests and order processing. Asset locations in the virtual sense are used by sites that follow a just-in-time supply strategy, with no physical inventory.
The asset location acquires and issues requested items to medical center departments. You may assign a buyer to each asset location, if you wish. You assign an asset location buyer on the Asset Location record panel, located in the Materials tables.
,
or click New if you wish to create a new asset location. 
You can assign multiple buyers to a vendor buy-from location, but you can only specify one as the primary buyer. (When the system searches for the buyer, it finds the primary buyer.)
Users who approve requisitions, invoices, and check requests must have the appropriate authorization in their user profile.
To set notification options, open user profiles as follows:
to edit the user profile. Users who create requisitions, invoices, and check requests have the option of being notified when a requisition has been approved or rejected by an approver.
Similar fields for invoices and check requests are on the AP Limits panel (Figure 16).
Users who approve requisitions, invoices, and/or check requests have the option to be notified when a transaction needing approval has been added to their approval queue.
When a notification arrives that you have a requisition, invoice, or check request to approve, a link within the email notification takes you directly to the transaction needing approval, and avoids your having to navigate manually through ERP after receiving an email message. Figure 18 is an example of an email for requisition approval, with the link.
If you are not logged in to the application, clicking the link opens the login panel, and you can log in. The system displays the transaction needing approval. The application remains open for other work.
Note: This feature is only available for Microsoft Internet Explorer. Mobile browsers, Firefox, Chrome, and others are not supported.
Requisition approver groups contain users with different approval responsibilities for requisition dollar amounts. Approver groups route a requisition through each member until the requisition is signed off.
Approver groups are organization independent. Thus, users who approve requests do not need to have identical data profiles or departments. For example, if a requisition is created for Department 6200, and the first approver in the group does not have 6200 as a valid department in his/her user profile, the requisition still appears in the person's approval queue, and he/she can still approve or reject it. The system administrator can add any user defined as an approver to an approver group, and to multiple approver groups.
When an approver group is restricted by organization, Yes appears in the Restricted column on the Approver Groups List.
You can copy and delete approver groups. Copying an approver group copies the group and all its members. Deleting an approver group deletes the group and all its members. However, if the approver group is assigned to a requester in User Settings, the group cannot be deleted.
By restricting approver groups by organization, you can limit user access to them based on data profile.
When an approver group has been restricted by organization, it will only appear in lists and prompts where the user has data profile organization access to at least one of the restricted organizations.
),
or select Menu > Edit. The Approver Group Edit panel and the
Approver Group Users list appear. 
Approvals for check requests and requisitions can be automatically escalated up the approver group ladder if the requester is also an approver in the group.
When enabled, this feature prevents users who are members of an approver group from approving their own requests. Approval for requisitions and check requests automatically route to the next approver in the approval group ladder, regardless of the Max Dollar limit for the next approver. This enhancement applies only to members of approver groups, not to direct approvers.
Situation 1: User Abby who normally approves requisitions for a department opens a requisition for $99.50. Abby is part of an approver group configured as follows:
| User Name | Approval Limit |
| Abby | $100 |
| Baker | $1000 |
| Charlie | $10,000 |
Result: The requisition is automatically sent to Baker, even though Baker would not normally get requisitions for under $100.00. Those would be handled by Abby. But, since this requisition was made by Abby, Baker does get it for approval. The notification sent to Baker that a request needs approval includes the information that the approval has been escalated.
Situation 2: An approver -- Frank -- who is the highest level approver in an approval group makes a check request for $3,200.00. The approver group looks like this:
| User Name | Approval Limit |
| Delta | $100 |
| Erin | $1000 |
| Frank | $5000 |
Result: The request routes through approvals normally to Delta and then Erin until it gets to Frank. Frank initiated the request, but no user in the group exists for escalating the request since Frank is the top approver. In this case, the system automatically approves the request.
Situation 3: A requisitioner, Cindy, submits a requisition with a non-file line that requires both an item approval and a commodity code approval.
Commodity Approval Group
| User Name | Approval Limit |
| Joe | $2000 |
| Bill | $3000 |
| Roberta | $5000 |
Item Approval Group
| User Name | Approval Limit |
| Cindy | $1500 |
| Joe | $2000 |
| Steve | $5000 |
Result: Joe approves the requisition as a commodity code approver. Bill also approves. Roberta approves.
For item approval,
Cindy is skipped because she is the requester. Approval is flagged as escalated.
Joe is assigned to approve, but should not because he already reviewed the requisition. Steve is the next assigned approver as an escalated approver.
Enabling the approval escalation feature
This feature can be enabled on the organization MM Info tabbed panel by unselecting the field Allow Requesters To Approve Their Own Requests (Figure 25). (The field is selected by default.)
The path for the panel is: Materials Management (or Accounts Payable) main Contents > Tables > Organizations.
When the field Allow Requesters to Approve Their Own Requests on the organization panel is turned off (unchecked) to prevent approvers from approving their own requisitions/check requests, the following occur:
Invoice approver groups allow invoices to be routed to multiple approvers. In the routing process, an invoice’s Total is compared to each approver's Maximum Approval Limit to determine whether the approver needs to review the invoice. (How to specify the Maximum Approval Limit is explained in subsequent paragraphs. Also, see Figure 26.)
Members of invoice approver groups must have the authorization User is Invoice Approver selected on the User Roles tab of their user profile (Figure 12).
The Invoice Approver Group Edit panel appears (Figure 28). When you add users to the group, they are listed on this panel.
Requisition, invoice, and check request approvers each have their own queue containing documents awaiting approval.
A situation may occur at a medical center where the normal approver for a department's requisitions is out of the office, and the person's approver buddy is also out of the office. In this case, requisitions could sit in an approver's queue for days...or longer. Similarly, check requests or invoices could remain in a queue unattended for a period of time. The All Approver Queues are designed to handle this situation.
For requisitions, the system administrator can assign the role object "AdminApprover" to a user who will be able to view and approve/reject any requisition. This role might be assigned to the Purchasing Manager, for example. In this way, requisitions that need approval will not linger without attention in an approver's individual queue. Once this designation has been set for a user, the user can approve any requisition in the queue: Requisitions > All Approval Queues.
Note: Two differences exist in security settings for the approval queues:
- All Approval Queues
The administrative approval queue (Requisitions > All Approval Queues.) is subject to a user's data profile. The user have permission to access data for the departments and organizations associated with requisitions in the queue. Requisitions for which the user does not have the appropriate data profile will not appear in the queue.
- My Approval Queue
The display of requisitions for approval in My Approval Queue is not governed by users' data profiles. See the previous discussion of Approver Groups.
For check requests, the system administrator can assign the role object "Inv Approval Admin" to a user who will be able to view and approve/reject any invoice. When this role object is set, the use can access invoices in the queue: Invoices > All Invoice Approval Queues.
For check requests, the system administrator can assign the role object "ChkRqstApprovalAdmin" to a user who will be able to view and approve/reject any check request. Once the "ChkRqstApprovalAdmin" role object has been set for a user, the user can approve any check request in the queue: Check Requests > All Check Request Approval Queues. See Check Request Processing for details on setup.
See Set Up and Maintain Users for information on assigning role objects.
This feature generates emailed approval reminders for requisitions (regular, bill-only, standing, and blanket), invoices, and check requests if review/approval/rejection has not occurred within a specified time interval. The scheduled job "Approver Reminder and Redirect," lets you specify the time period, the organization that uses the reminders, and the type of approvals affected: invoices, check requests, requisitions, or all three. For approval groups, you can specify the number of reminders that each group member receives before approval occurs automatically for that group member, and then moves to the next group member.
When a document (invoice, check request, or requisition) appears in an approver's queue, the approver can review it, and then approve or reject it. If the approver does not act within the set time period, the system sends the approver a reminder message. A reminder is sent to both direct approvers and members of approver groups, whichever is applicable.
For approver groups, you can also define the number of reminders to be sent to each approver. After the set number of reminders, the document is marked "auto-approved" (if possible), and appears in the queue of the next approver. For the last approver in the group, reminders persist until the last reviewer reviews, approves, or rejects the document. When a document cannot be marked as auto-approved, it continues to be included in future reminder messages. For example, costing buyer approvals cannot be auto-approved. A costing buyer would receive repeated reminders until he/she acts with review, approval, or rejection.
When the out-of-office flag is set for an approver, the reminder is sent to the approver buddy. The reminder email is generated even for approvers who do not have an email address in their User Profiles.
General instructions for creating scheduled jobs are in the topic "Set Up Schedules for Batch Jobs." Here is a summary for approval reminder scheduled jobs.
1. Open the list of scheduled jobs (Miscellaneous Functions > Scheduled Jobs).
2. Click New to create a new scheduled job.
3. Enter header information (Figure 30) for the new approval reminder job.
- Enter a job description (Job Desc).
-
Select the Job Name Approver Reminder and Redirect.
Organization - You can create an approval reminder job for any organization: select the organization. If you wish to set up the job for all organizations, leave this field blank.
Minimum hours to wait before 1st reminder - The number of hours that can elapse between an approval being required, and the first reminder notice being sent. In other words, when a user creates a requisition (invoice, or check request) and sends it to approval, the document appears in an approver's queue. This field is the time interval (in hours) that must elapse before the approver gets a reminder message. Enter the number of hours.
Reminders to send before moving to next approver - An integer used with reminders in an approver group situation. This value is the number of reminder messages to be sent to a delinquent approver before redirecting to the next approver in the group. Enter an integer.
Approval Types - The types of documents for which the approval reminders are to be used. The options are: invoice, requisition, check request, or all types. Select an approval type.
Note: Be sure to enable the job. (Select the Enabled box.)
When an approver is delinquent in acting on approval queue entries, a formatted reminder message appears in his/her email. The message contains a count of each type of approval awaiting the user in the specified organization. The count includes entries that have been in the user's approval queue longer than the time frame defined in the scheduled job. The counts are broken down by approval type(s), as specified in the job. See Figure 30.
An example of an approval notification emailed to a user is in Figure 32.
Notice that the email message summarizes all available approvals for the approver. If the user is a member of an approver group, and one document -- for example, an invoice -- becomes auto-approved as a result, the count for that type of document is reduced by one.
Several fields on the inquiry panels for invoices, requisitions, and check requests display the status of approvals. Below are several examples.
In the Approval History panel for the invoice in Figure 33,
JuanG is the single direct approver. This assignment is in the column Reason Approval Assigned 
.
is Reviewed. 
were sent to the approver before he reviewed the invoice. The last reminder was sent on October 9. The requisition in Figure 34 is for a non-file item, and requires review by a costing buyer. A costing buyer is the first person to review non-file requisitions, and he/she completes information for the requested item, such as the manufacturer or vendor (if not specified by the requester), the price, etc. Other approvers may follow the costing buyer's review, but the requisition cannot proceed further until the costing buyer approves it.
In the Approval History for the invoice in Figure 34,
is the costing buyer. This assignment is in the column Reason Approval Assigned . is Not Reviewed. have been sent to the costing buyer, and he has not yet reviewed the requisition. The last reminder was sent on October 21.The requisition in Figure 35 is assigned to an approver group with three approvers. The first approver (Mary) approved it. The second approver (Len) was out of the office, so approval bounced to his approval buddy (Nancy). The approver buddy was also out of the office, so after three reminders, the system auto-approved the requisition, and sent it to the third approver. The requisition is now with the third reviewer (Quincy), who needed nine reminders to review it, and who has now done so.
Because the person with nine reminders is the last approver, the system would not have been able to auto-approve the requisition, as it did for the first reviewer. It will stay in Quincy's approval queue until he approves or rejects it.
In Figure 33,
are assigned to an approver group "AMC Group/Area 1 Clinical." was the first approver. We know this from the timestamp at which she reviewed the requisition: October 12 at 3:37 PM (Figure 35, purple box). The other timestamps are later.
also seems to have reviewed and approved the requisition 
on October 12 at 8:00 PM (Figure 35, green box).
, we can see that the system -- not the reviewer -- actually auto-approved the requisition on October 12 at 8:00 PM.
. The last was on October 12 at 7:00 PM.
. Len apparently had out-of-office set. Nancy, however, was also not available. 
.
. A report object "Approval Queue Notify Activity" is available for reports on approval activity, such as the number of elapsed days between a document being placed on an approver's queue and the current day.
This feature allows administrators to create and populate new requisition and invoice approver groups via mass import into ERP. The import avoids the need to go into the ERP application and create approver groups/assign approvers to each approver group manually. This feature lets administrators quickly incorporate approvers from newly acquired units and facilities into medical center operations.
The approver group import tool applies to invoices, requisitions (including bill-only requisitions and invoices), and check requests. You can create requisition and invoice approver groups and assign members on the same upload document. Once you have created and uploaded newly completed approver groups and direct approvers, you can link them to organizations and departments using another import.
Prerequisites
Note: If a check request approval route and limits are the same as the requisition approval route and limits, only one approver group is needed. Otherwise, if the check request approval route and limits need to have differing approver paths, users, or dollar levels, then a second approver group is needed.
This feature is controlled by a new role object: "Approver Group Import." This new role object controls access to the Approver Group Import Template and the import menu options. The initial setting is None. Settings All and Create allow administrators to create and import approver groups.
To populate approver groups, an Excel template is available for entering fields that you then upload and import into ERP.
After you assign users to approver groups on the template, you import them back to ERP.
Important: The file you import must be in .csv (comma-separated values) format.
To display imported Approver Group files and upload a new one,
Valid rows on the spreadsheet will import into the application. If some rows are valid, and other are not, the invalid rows will not be imported. When the Import Status of the uploaded user record file is not Complete, the import encountered errors.
To work with errors, you need to review the import details, make corrections, and reprocess the data.
An import feature also lets you link an existing approver group or direct approver to an organization and department within your ERP application. The link is implemented via a download of a department's current approval setup parameters (approval profiles), followed by upload of approver groups and direct approvers. This capability supports acquisition of new units at a medical center, and quarterly audit compliance. The feature uses the standard import. See Importing Approvers and Approver Group Assignments for Departments.
The mass approver change feature lets you make mass changes to approvers in approver groups.
You can...
Similar to other "mass change" features in the system, for approver changes, you first create a job that specifies the approver changes. When the job runs, the changes take effect.
For vendor approver groups, the Sequence Number on the Insert (Figure 41 tab is required. The Sequence Number determines the order in which the person's approval is solicited.
Figure 42 is an example of a reassignment in which an approver in an approver group is replaced with a different approver.
Figure 43 is an example of a change to an approver's maximum dollar limit.
The Mass Approver Change: Replace Approver User Panel lets you select approver groups in which one approver (Replace Approver User) is removed and another approver (With Approver User) is added (Figure 44).
The Criteria fields (center) let you filter the bottom list (Approver Reference Selections...). The list is governed the by data profile setting of the person making the changes.
Select Action has these options:
The Mass Approver Change: Insert Approver User Panel lets you add an approver to a group that the approver does not currently belong to (Figure 45).
The Criteria panel works the same way as for Replace Approver User.
The Approver Reference Selections for Approver... panel, at the bottom, contains a list of approver groups to which the approver can be added. The approver does not currently belong to any of the groups.
The Mass Approver Change: Remove Approver User Panel removes an approver either from an approver group, or from assignment as the direct approver of another user (Figure 46).
The Mass Approver Change: Remove Approver User Change Max Limits (Figure 47) lets you change the maximum dollar approval limit for an approver. You can select the approver groups where you wish to change the user's dollar limits, or you can change the user's dollar limits for all the groups that include the user.
The Criteria fields (center) let you filter the bottom list (Approver Reference Selections...). The list is governed the by data profile setting of the person making the changes.
Select Action has these options:
For all the mass approver change types:
Copyright © 2023 by Premier Inc. All rights reserved.
