Approval Levels
The people a rule asks to sign, one level at a time, in order. A level whose approver has left or is on leave is skipped and the next one fills it; a level that must be filled by somebody holds the document instead. Works the same way for a purchase order and for a requisition, because it is one policy.
Where to find it
- Module: Supply Chain
- Group: Purchasing
- Section: Procurement Control
- Screen: Approval Levels
Address in the console: /scm/approval-levels
List · 27 columns · 14 fields on its form · 2 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Rule | Code | rule_code |
| Applies to | Status | applies_to |
| Rule order | Number | rule_priority |
| Level | Number | level_no |
| Signs in turn | Number | effective_sequence |
| Called | Text | name |
| Who | Status | approver_kind |
| Approver | Text | approver_name |
| Employee | Code | employee_no |
| HRMS position | Text | approver_position |
| Signs in with role | Text | approver_sign_in_roles |
| What this level does | Text | routing_note |
| Role | Text | approver_role |
| Held by | Text | approver_role_holders |
| Status | Status | employee_status |
| Reachable | Yes or no | is_reachable |
| Why not | Text | unreachable_because |
| Covered by | Text | delegated_to |
| Cover ends | Date | delegation_ends |
| At or above | Amount | amount_threshold |
| May be skipped | Yes or no | may_skip_if_absent |
| Due in (h) | Number | due_in_hours |
| Active | Yes or no | is_active |
| Added by | Text | created_by_name |
| Added | Date and time | created_at |
| Last changed by | Text | updated_by_name |
| Last changed | Date and time | updated_at |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Requisition rule | Choice | Looked up from existing records | A level belongs to one rule — a requisition rule or a purchase order rule, not both. |
| Purchase order rule | Choice | Looked up from existing records | |
| Level required | Number | Signatures are collected in this order. Level 2 cannot decide before level 1 has. | |
| What this level is called | Text | e.g. "Manager 1". It is what the approver sees on the document. | |
| Who signs required | Choice | A named person (their sign-in) — no HRMS needed, An employee (HRMS), Whoever holds a position (HRMS), Anyone holding a role, The cost center’s manager, The reporting line of whoever raised it (HRMS) | Choose one; only the field for that choice is needed. "The cost center’s manager": The manager recorded on the cost center (Accounting › Controlling › Cost Centers): its HRMS manager, or else its responsible person. |
| Person | Choice | Looked up from existing records | Anyone who signs in to this company. They decide it from My approvals, whatever modules they have. |
| Position | Choice | Looked up from existing records | Whoever holds this position in HRMS when the document is sent. When somebody else takes the post, new documents go to them with nothing to change here. |
| Employee | Choice | Looked up from existing records | |
| Anyone holding this role | Text | A sign-in role from Administration › Roles, by its name or code — not a position in HRMS. If nobody holds it the level is skipped where it may be, and otherwise the document is refused with the reason. | |
| Only at or above | Number | Lets one rule say "a manager over 5,000, an executive over 50,000". | |
| May be skipped when the approver is away | Yes or no | On: the next level fills it. Off: the document waits until somebody is in the post — which is usually right for a final authority. | |
| Due within (hours) | Number | ||
| Notes | Long text | ||
| Active | Yes or no |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.