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 Type using which the To Do task 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 propose a change in the proposed pricing of the price item. The valid values are: -
Yes
-
No
Yes (Conditional) Note: This field is required while defining approval levels for 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 manager 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 approving a deal.Approve Deal Used to indicate whether the deal creator (at Level 0) and the subsequent users with the respective To Do role in the approval hierarchy are entitled to approve the deal after all the discretion check is validated. 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 for the deal creator (at Level 0), then, all the users with the respective To Do role can approve the deal including the deal creator (at Level 0). This changes 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 approving a deal.Enable Self-Approval Used to indicate whether the deal creator (at Level 0) is entitled to approve the deal after all the discretion check is validated. The valid values are: -
Yes
-
No
Note:If you set the Enable Self-Approval option to No at Level 0, the system will allow all users with the respective To Do role except the deal creator to approve the deal. However, if you set the Enable Self-Approval option to Yes at Level 0, the system will allow all users with the respective To Do role including the deal creator to approve the deal.
This option is not applicable for others levels in the deal approval profile.
Yes (Conditional) Note: This field is required while defining approval levels for approving a deal.View Only Eligible Price Items Used to indicate whether the approver/user at the specified hierarchy level can view only those price items for approval which meet the pricing limits as set in the approval level criteria for the respective approver/user. The valid values are: -
Yes
-
No
Yes (Conditional) Note: This field is required while defining approval levels for approving a deal.Approval Level Criteria On clicking the Add (
) icon, you can define multiple approval criteria
for the approval level in the approval hierarchy.Yes (Conditional) Note: This field is required while defining approval levels for 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.
- Define multiple approval criteria for the approval level, if required.
-
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 define an approval criteria for the approval level | Defining an Approval Criteria for an Approval Level |
