Copying a Binder Payment Preference

Instead of creating a binder payment preference from scratch, you can create a new binder payment preference using an existing binder payment preference. This is possible through copying a binder payment preference. On copying a binder payment preference, the details including the attributes are copied to the new binder payment preference. You can then edit the details, if required.

Prerequisites

To copy a binder payment preference, you should have:

  • Binder Payment preference (whose copy you want to create) defined in the application

Procedure

To copy a binder payment preference:

  1. Search for the binder payment preference in the Field Mapping screen.
  2. In the Search Results section, click the Duplicate (The Duplicate Icon) icon in the Duplicate column corresponding to the binder payment preference whose copy yo want to create.

    The Field Mapping screen appears. It contains the following sections:

    • Main - Used to specify basic details for the binder payment preference. It contains the following fields:

      Field Name Field Description Mandatory (Yes or No)
      Preference Used to specify the binder payment preference. Yes
      Description Used to specify the description for the binder payment preference. Yes
      Detailed Description Used to specify additional information about the binder payment preference. No
      Status Used to indicate the status of the binder payment preference. The valid values are:

      • Active

      • Inactive

      		 Yes
      Preference Category Indicates the category to which the preference belongs. The valid value is:

      • Binder Payment

      		 Not applicable

    • Preference Settings - Used to set the attributes in the binder payment preference. It contains the following fields:

      Field Name Field Description Mandatory (Yes or No)
      Attribute Used to indicate the attribute which you want to set in the binder payment preference. The valid values are:

      • Binder Contract Type - Used when you want to identify the binder contract in the binder payment preference.

      • Bill Period for Hold Billing - Used when you want to define the bill period when the billing is put on hold for an individual membership until the binder payment is received.

      • Consider Binder Liability Amount - Used when you want to set the consider binder liability amount once the binder payment is received in the binder payment preference.

      • Binder Payment Identification Characteristics Type - Used when you want to identify the membership for whom the payment is received in the binder payment preference.

      • Binder Payment Identification ID Type - Used when you want to identify the membership type in the binder payment preference.

      • Membership Status Code for Active - Used when you want to define the status code when an individual membership is in Active status in the binder payment preference.

      • Membership Status Reason when Binder Payment Canceled - Used when you want to define the status reason code as Binder Payment Canceled when the binder payment is not received for an individual membership within the specified grace days in the binder payment preference.
        Note:
        You must specify the status reason code for the Active status of the C1-IndMembership business object.

      • Membership Status Code for Pending Effectuation - Used when you want to define the status code when an individual membership is in the Pending Effectuation status in the binder payment preference.

      • Membership Status Reason on Activating Membership - Used when you want to define the status reason code once the binder payment is received and the individual membership status is changed to Active for the binder payment preference.

      • Membership Status Reason Binder Business Rule Config Invalid - Used when you want to define the status reason code as Binder Business Rule Config Invalid when the binder payment business rule configuration details are not available for an individual membership in the binder payment preference.
        Note:
        The C1-BusinessRuleService business service contains the configuration details related to the binder payment business rule.

      • Membership Status Reason when Awaiting Binder Payment - Used when you want to define the status reason code as Awaiting Binder Payment when the binder payment is not yet received for an individual membership in the binder payment preference.

      • Membership Status Reason when Binder Payment Not Received - Used when you want to define the status reason code as Binder Payment Not Received when the binder payment is not received for the membership in the binder payment preference.

      • Membership Status Reason when Binder Payment Not Expected - Used when you want to define the status reason code as Binder Payment Not Expected when the system should not perform the binder payment validation for an individual membership in the binder payment preference.

      • Membership Status Reason when Binder Payment Received - Used when you want to define the status reason code as Binder Payment Received when the binder payment is received for the membership in the binder payment preference.

      • To Do Type for Binder configuration not available - Used when you want to specify a To Do type when the binder configuration is not available.

      • To Do Type for Binder Payment not received - Used when you want to specify a To Do type when the binder payment is not received for an individual membership in the binder payment preference.

      • To Do Type for Binder Payment received - Used when you want to specify a To Do type when the binder payment is received for an individual membership in the binder payment preference.

      • To Do Type for Binder Payment Canceled - Used when you want to specify a To Do type when the binder payment is canceled.

      • To Do Type for Binder Payment is not expected - Used when you want to specify a To Do type when the binder payment is not expected.

      Note:
      The attribute list appears only when the preference category is selected from the respective list.
      		 Yes
      Value Used to specify the attribute value. The attribute value list varies depending on the attribute that you want to set in the binder payment preference. The valid values are:

      • Binder Contract Type - The Value field is used to specify the binder payment contract type.

      • Bill Period for Hold Billing - The Value list indicates only those bill periods for hold billing which are already defined in the system.

      • Consider Binder Liability Amount - The Value list contains the following values:

        • Yes

          - The system considers the binder liability amount to calculate the threshold amount.

        • No

          - The system does not calculate the threshold amount.

      • Binder Payment Identification Characteristics Type - The Value field is used to specify the configured characteristic type that identifies the membership for whom the payment is received.

      • Binder Payment Identification ID Type - The Value list includes only those identification ID types which are already defined in the system.

      • Membership Status Code for Active - The Value field is used to specify the status code for an active membership.

      • Membership Status Reason when Binder Payment Canceled - The Value field is used to specify the configured status reason when the binder payment is canceled.

      • Membership Status Code for Pending Effectuation - The Value field is used to specify the configured status code when the membership is in the Pending Effectuation status.

      • Membership Status Reason on Activating Membership - The Value field is used to specify the configured status reason once the binder payment is received and the membership status is changed to Active

      • Membership Status Reason Binder Business Rule Config Invalid - The Value field is used to specify the configured status reason if the binder-payment business-rule configuration is invalid.

      • Membership Status Reason when Awaiting Binder Payment - The Value field is used to specify the configured status reason code when the binder payment is not yet received for the membership.

      • Membership Status Reason when Binder Payment Not Received - The Value field is used to specify the configured status reason code when the binder payment is not received for the membership.

      • Membership Status Reason when Binder Payment Not Expected - The Value field is used to specify the configured status reason code when the binder payment is not expected.

      • Membership Status Reason when Binder Payment Received - The Value field is used to specify the configured status reason code when the binder payment is received for the membership.

      • To Do Type for Binder configuration not available - The Value field is used to specify the configured To Do type when the binder configuration is not available.

      • To Do Type for Binder Payment not received - The Value field is used to specify the configured To Do type when the binder payment is not received.

      • To Do Type for Binder Payment received - The Value field is used to specify the configured To Do type when the binder payment is received.

      • To Do Type for Binder Payment Canceled - The Value field is used to specify the configured To Do type when the binder payment is canceled.

      • To Do Type for Binder Payment is not expected - The Value field is used to specify the configured To Do type when the binder payment is not expected.

      Note:
      The attribute value list appears only when the attribute is selected from the respective list.
      		Yes
      Entity Type Used to indicate the type of entity for which the attribute is applicable. The valid values are:

      • Account

      • Adjustment

      • Billable Charge

      • Membership

      • Payment

      • Policy

      Note:
      At present, this data is stored for informational purposes only and is not considered in the business logic. If required, you can add more entity types to the MAP_​ENTITY_​FLG lookup field.
      		 No
      Note:
      While defining a binder payment preference, you must set at least one attribute in the binder payment preference.
    Tip:
    Alternatively, you can click the Duplicate button in the Field Mapping zone to create a copy of the binder payment preference.
  3. Enter the required details in the Main section.
  4. Define, edit, or remove the attribute from the binder payment preference, if required.
  5. Click Save.
    The new binder payment preference is defined.

Related Topics

For more information on... See...
How to search for a binder payment preference Searching for a Binder Payment Preference
Field Mapping screen Field Mapping