Defining an Approval Level in the Approval Hierarchy
Prerequisites
To define an approval level in the approval hierarchy, you should have:
-
Approval hierarchy levels defined in the application.
-
To Do roles and To Do types defined in the application.
Procedure
To define an approval level in the approval hierarchy:
-
Ensure that the Approval Hierarchy section is expanded in the Deal Approval Profile screen when you are defining, editing, or copying a deal approval profile.
The Approval Hierarchy section contains the following fields in a grid:
Field Name Field Description Mandatory (Yes or No) Level Used to indicate the approval level. Note:The user who creates the deal i.e. the relationship manager (RM) should always belong to the first level (Level 0) in the deal approval hierarchy.
There cannot be a parallel level for the first level (Level 0) in the approval hierarchy. In other words, there can be only one relationship manager (RM) in the entire deal approval hierarchy.
Yes To Do Type Used to specify the To Do task which is assigned to the approver/user group for approving the deal at the specified hierarchy level. Note:The Search (
) icon appears corresponding to the To Do Type field. On clicking the Search icon, the To Do Type Search window appears.
On specifying the value for a predefined To Do type , the description of the To Do type appears corresponding to the To Do Type field.
Yes To Do Role Used to indicate the approver/user group to whom the To Do task is assigned for approving the deal at the specified hierarchy level. Yes Propose Pricing Used to indicate whether the approver/user (other than the relationship manager) at the specified hierarchy level is entitled to recommend a change in the proposed pricing of the price item. The valid values are: -
Yes
-
No
Note: By default, this field is read only and the value is set to No for the first level (Level 0) approver/user i.e. the relationship manager (RM) in the approval hierarchy.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Submit Price Item for Approval Used to indicate whether the approver/user at the specified hierarchy level is entitled to submit one or more price items to the respective product managers for approval. The valid values are: -
Yes
-
No
Note: The approver/user can submit the price items to the respective product managers for approval when the values for the Price Item Manager To Do Type and Price Item Manager To Do Role fields are defined in the respective Price Item screen.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Approve Deal Used to indicate whether the approver/user at the specified hierarchy level is entitled to approve the deal after all the discretion check is confirmed. The valid values are: -
Yes
-
No
Note:At least one approval hierarchy level must have the value of the Approve Deal field set to Yes.
If the value of the Approve Deal field is set to Yes, then, the approver/user can change the status of the deal from Draft to Ready for Approval or Approved.
Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.View Only Eligible Price Items Used to indicate whether the approver/user at the specified hierarchy level can approve only those price items which meet the pricing limits as set in the approval hierarchy. The valid values are: -
Yes
-
No
Note: By default, this field is read only and the value is set to No for the first level (Level 0) approver/user i.e. the relationship manager (RM) in the approval hierarchy.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Minimum Profitability (%) Used to specify the minimum deal profitability percentage for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Maximum Profitability (%) Used to specify the maximum deal profitability percentage for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Minimum Profitability Amount Used to specify the minimum deal profitability amount for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Maximum Profitability Amount Used to specify the maximum deal profitability amount for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Minimum Deviation (%) Used to specify the minimum deal variation percentage for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Maximum Deviation (%) Used to specify the maximum deal variation percentage for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Minimum Deviation Amount Used to specify the minimum deal variation amount for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Maximum Deviation Amount Used to specify the maximum deal variation amount for the approver/user at the specified hierarchy level for approving the deal. Note: You can either specify the percentage or amount values for minimum and maximum limit.Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Minimum Revenue Amount Used to specify the minimum deal revenue which can be approved by the approver/user at a specified hierarchy level. Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal.Maximum Revenue Amount Used to specify the maximum deal revenue which can be approved by the approver/user at a specified hierarchy level. Yes (Conditional) Note: This field is required while defining approval levels for the approving a deal. -
- Enter the required details in the Approval Hierarchy section.
-
If you want to define more than one approval level in the
approval hierarchy, click the Add (
) icon and then repeat step 2.
Note:However, if you want to remove an approval level from the approval hierarchy, click the Delete (
) icon corresponding to the approval hierarchy.
At present, you can add an approval level from 0 to 10. If required, you can add more approval levels in the system through the C1_DEALHIERARCHYLEVEL lookup field.
-
Click Save.
The approval level is defined in the approval hierarchy.
Related Topics
For more information on... | See... |
---|---|
Deal Approval Profile screen | Deal Approval Profile |
How to define a deal approval profile | Defining a Deal Approval Profile |
How to edit a deal approval profile | Editing a Deal Approval Profile |
How to copy a deal approval profile | Copying a Deal Approval Profile |
How to delete a deal approval profile | Deleting a Deal Approval Profile |