What types of approvers can I include in an approver lookup table?

When you work with approver lookup tables, you specify the types of approvers to include by clicking Approver Type Field check boxes. For each check box that you click, a column is included in the comma-separated values (CSV) file.

• User lets you specify one or more users by user ID. Separate multiple IDs with colons (for example, user1:user2:user3). If you list multiple IDs, the users are added to the approval flow as an ApproverList in one single node. Only one approver in the list needs to approve.
  
  
• Group lets you specify one or more groups by unique name. Separate multiple group names with colons. If you list multiple groups, the groups are added to the approval flow as one single approver. Only one approver group in the list needs to approve.
  
  
• ApproverList lets you specify multiple user IDs, unique group names, or unique field paths. Separate the values with colons (for example, user1:group1:group2 or Approvable.Preparer:Approvable.Requester). The users and groups in a list are added to the approval flow as one single approver/watcher. Only one approver in the list needs to approve. Note that the Approver List function checks to find matching group UniqueName values first, then checks through user UniqueName values if no group match is found. Additionally, if you specify an empty group within ApproverList column, the system will add a blank white space where that group should have been pulled into the approval flow. The Customer Administrator is not pulled into the approval flow for the empty group, as there are other approvers/watchers specified within the same approval node who can take action on the approvable document. Following is an example implementation:
  
  CostCenter,User,ApproverList,Tooltip,Required
  100,,fgifford:Budget Approver,Fred Gifford or Budget Approver must approve,TRUE
  
  

• ApproverFieldPath lets you add an approver based on a field path relative to either the approvable or an object specified in a column of the CSV file.

  • Here are some examples of approver lookup tables that use approver field paths:

    LineItemsDepartment, ApproverFieldPath, Tooltip, Required
    Department-A, LineItemsDepartment.DepartmentManager, Department manager must approve, true

    In the preceding example, the object that the field path is based on is LineItemsDepartment. DepartmentManager is a field in LineItemDepartment objects. In the example, when the value in LineItemsDepartment is Department-A, the value in the DepartmentManager field is added to the approval flow.

    LineItemsAmount, ApproverFieldPath, Tooltip, Required
    10000, Approvable.Auditor, Auditor must approve, true

    In the preceding approver lookup table, Approvable is a hard-coded name used to represent the approvable. For requisitions, the value Approvable.Auditor means the Auditor field on a requisition. If the amount for a line item is greater than 10000, the value in the Auditor field of the requisition is added to the approval flow.

For more information, see the various topics on base and chain approval flows in the Approval Process Management Guide.

Core Procurement > Core Administration > Approver lookups
Invoicing