Setting up Levels of Approval
To set up levels of approval use the Approval Levels Setup function.
- From the Action menu within Approval Tables (ATS) select Set Details.
-
Specify this information:
- Short Heading
- This field is automatically completed from the current Approval Table.
- Upper Limit Amount
- The amount to be the limit for the approval level.
- When more than one limit is specified, the limit is used as an inclusive figure. For example: A limit amount is specified as 100,000 which sets the limit from 0 to 100,000; the next limit amount is specified as 500,000 which sets the limit from 100,000.01 to 500,000.
- If no approval is required below a certain
threshold, you must set up an Approval Level but do not assign
any Approval
Groups.
Uwaga: When an approval limit is set, you must also set a level for the highest possible amount otherwise transactions over the approval limit will be progressed to the next stage with no approval required. For example, if a limit of 500,000 is set with a Data Access Group specified as the approver, then any purchase order or invoice over that amount does not require approval. If a further approval limit of, say, 9,999,999,999,999 is defined with another Data Access Group, then the order or invoice will be held until they have approved it.
- Analysis Code Basis 1-3 From/To
- These fields specify the range for the Analysis Dimension set up in the Approval Table. If the Analysis Dimension of, for example, Grade is set up in the Approval Table, this range might be specified as 01 to 09. This enables you to specify different ranges for different approvers.
- Actual codes do not need to be entered here. For example, ranges of 0 to 9, A to ZZZZZZ, or 0 to ZZZZZZ can be entered to pick up existing and future codes expected to be entered.
- If the analysis code basis for approval is set to the range of blank to blank, with a Data Access Group specified as the approver, the transaction will be held for approval when no analysis code is entered. Once the transaction is approvaed by the DAG, it can be progressed to the next stage.
- If the analysis code entered is not in any
ranges of analysis code basis for approval, the transaction can be
progressed to the next stage with no approval required. For example,
if the Analysis Code is E, but the analysis code basis ranges A to D
and F to G are set, the transaction does not require approval.
Uwaga: Fields can be made mandatory in Form Designer, or a Business Rule can be used to force the user to enter an analysis code and display a message if they do not.Uwaga: If analysis is optional, create an approval table for the analysis code range that is optional, and ensure no Data Access Group codes are assigned in the Approval Group fields below. The line will not then be held for approval.
- Approver Data Access Group 1-10
- The required Data Access Group for this approval detail line. The order in which the approval groups are defined here is the order in which approvals need to be made.
- Save your changes.