Defining a Deal Type

Prerequisites

To define a deal type you should have:

  • Business object defined for the deal type

  • Values defined for the FREQUENCY_​FLG lookup field.

  • Deal approval profiles defined in the application

  • Algorithms defined in the system

  • Algorithms associated with the system events

  • Characteristic types defined in the application (where the characteristic entity is set to Deal Type).

  • Reminder To Do types defined in the application

  • Questionnaire templates defined in the application

Procedure

To define a deal type:

  1. Click the Admin link in the Application toolbar.
    A list appears.
  2. From the Admin menu, select D and then click Deal Type.
    A sub-menu appears.
  3. Click the Add option from the Deal Type sub-menu.

    The Deal Type screen appears. It contains the following sections:

    • Main - Used to specify basic details about the deal type.

    • Deal Approval Profiles - Used to associate deal level, division level, or product level approval profiles with the deal type for approving the deal.

    • Algorithms - Used to associate algorithms with the system events defined for the deal type

    • Characteristics - Used to define the characteristics for the deal type

    The Main section contains the following fields:

    Field Name Field Description Mandatory (Yes or No)
    Deal Type Used to specify the deal type. Yes
    Description Used to specify the description for the deal type. Yes
    Detailed Description Used to specify additional information about the deal type. No
    Deal Commitment Frequency Used to indicate the duration for the periodic analysis of deal usage as per the commitments made by the customer for calculating the deal financial summary. The valid values are:

    • Biannually

    • Monthly

    • Quarterly

    • Yearly

    Note: The list includes only those values which are present in the FREQUENCY_​FLG lookup field.
    		 Yes
    Price Item Approval Required Used to indicate whether the discretion check of an individual price item is required by the approver/user for approving the deal. The valid values are:

    • Yes

    • No

    		 Yes
    Assign Only If In Range Used to indicate whether the deal is assigned to the approver/user as per the limits set in the Approval Hierarchy section of the Deal Approval Profile screen.
    For example, if the deal profitability % range of the approver/user is set as follows:

    • RM (0% - 5%)

    • PM (6% - 15%)

    • SPM (16% - 50%)

    Then,

    • If the calculated deal profitability % is 4 %, then the deal will be assigned to the relationship manager (RM).

    • If the calculated deal profitability % is 11 %, then the deal will be assigned to the pricing manager (PM).

    • If the calculated deal profitability % is 25 %, then the deal will be assigned to the senior pricing manager (SPM).

    The valid values are:

    • Yes

    • No

    Note: This field is valid only for deal level approval profiles.
    		 Yes (Conditional)
    Note: This field is required for assigning the deal when the deal financial summary falls within the specified limits defined for the approver/user.
    Product Level Approval Required Used to indicate whether the discretion check of the price items at the product level is required for approving a deal. The valid values are:

    • Yes

    • No

    		 Yes (Conditional)
    Note: This field is required for approving deal at product level.
    Division Level Approval Required Used to indicate whether the discretion check of the price items at the division level is required for approving a deal. The valid values are:

    • Yes

    • No

    		 Yes (Conditional)
    Note: This field is required for approving deal at division level.
    Highest Level Approval Required Used to indicate whether the hierarchical approval of the deal is required for approving a deal.

    For example, if the approval hierarchy has three levels L0 (RM), L1 (PM), and L2 (SPM), then the deal will pass through all the three levels for approval respectively. L0 (RM) will not be able to finalize the deal without the approval of L2 (SPM).

    The valid values are:

    • Yes

    • No

    		 Yes (Conditional)
    Note: This field is required for approving a deal by each level in the approval hierarchy.
    Status Used to indicate the status of the deal type. The valid values are:

    • Active

    • Inactive

    Note: Only an Active deal type can be used for creating a deal.
    		 Yes
    Pre-Approve Existing Pricing Used to indicate whether the existing price items pricing and commitments should be pre-approved to confirm the financial summary of the deal. The valid values are:

    • Yes

    • No

    		 Yes (Conditional)
    Note: This field is required for approving the existing price item pricing and commitments of the entity.
    To Do Reminder Days Used to specify the number of days using which the system calculates the first To Do reminder date. Yes
    To Do High Priority Days Used to specify the number of days using which the system calculates the date when the To Do reminder of highest priority should be sent.
    Note: You can set a maximum of 9 priority days for the To Do reminder days.
    		 Yes
    Days to Inactivate Used to specify the number of days prior to the last updated date of the deal after which you want to inactivate the deal.
    Note:

    You must specify a numeric value greater than zero in this field. Also, the numeric value should be greater than the values specified in the To Do Reminder Days and To Do High Priority Days fields.

    The deal is automatically inactivated if no action is performed on the deal within the specified number of days in this field.

    The status of the deal is changed to Inactive when the deal inactivation date is equal to the system date.

    		 Yes (Conditional)
    Note: This field is required for inactivating deals which are not updated in the system for a long time.
    Reminder To Do Type Used to indicate the To Do task that you want to send as a notification to the user for the priority days set for reviewing the deal.
    Note:

    The Search (The Search Icon) icon appears corresponding to the Deal Monitor To Do Type field. On clicking the Search icon, the To Do Type Search window appears.

    On specifying the value for a To Do type, the description of the To Do type appears corresponding to the To Do Type field.

    		 Yes
    Questionnaire Template Used to indicate the questionnaire template that you want to associate with the deal type using which the system searches for a list of deals which can be used as references while creating a deal.
    Note:

    The Search (The Search Icon) icon appears corresponding to the Questionnaire Template field. On clicking the Search icon, the Search Questionnaire Template window appears.

    On specifying the value for a questionnaire template, the description of the questionnaire template appears corresponding to the Questionnaire Template field.

    		 Yes (Conditional)
    Note: This field is required for associating a questionnaire template with the deal type.
  4. Enter the required details in the Main section.
  5. Associate deal approval profiles with the deal type in the Deal Approval Profiles section.
  6. Associate algorithms with the deal type in the Algorithms section, if required.
  7. Define characteristics for the deal type in the Characteristics section, if required.
  8. Click Save.
    The deal type is defined.

Related Topics

For more information on... See...
Deal Type screen Deal Type
How to associate a deal approval profile with a deal type Associating a Deal Approval Profile with a Deal Type
How to associate an algorithm with a deal type Associating an Algorithm with a Deal Type
How to define a characteristic for a deal type Defining a Characteristic for a Deal Type