Copying an Overpayment Handling through a Match Type Preference

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

Prerequisites

To copy an overpayment handling through a match type preference, you should have:

  • Overpayment handling through a match type preference (whose copy you want to create) defined in the application

  • Value defined for the Field Mapping for Match Type option type in the C1-PAYFLUPLD feature configuration.

  • Values defined in the FIELD_​CAT_​FLG, FIELD_​STATUS_​FLG, and FIELD_​NAME_​FLG lookup field.

  • Values defined in the PAY_​TND_​STG_​ST_​FLG lookup field.

Procedure

To copy an overpayment handling through a match type preference:

  1. Search for an overpayment handling through a match type 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 overpayment handling through a match type preference whose copy yo want to create.
  3. Click OK.

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

    • Main - Used to specify basic details of the overpayment handling through a match type preference. It contains the following fields:

      Field Name Field Description Mandatory (Yes or No)
      Preference Used to specify the overpayment handling through a match type preference. Yes
      Description Used to specify the description for the overpayment handling through a match type preference. Yes
      Detailed Description Used to specify additional information about the overpayment handling through a match type preference. No
      Status Used to indicate the status of the overpayment handling through a match type preference. The valid values are:

      • Active

      • Inactive

      		 Yes
      Preference Category Indicates the feature for which the preference is designed. The valid values is:

      • Handling overpayment through Match Type

      		 Not applicable

    • Preference Settings - Used to set the attributes in the overpayment handling through a match type preference.

      Field Name Field Description Mandatory (Yes or No)
      Attribute Used to indicate the attribute which you want to set in the overpayment handling through a match type preference. The valid values are:

      • Match Type for On Account Payment (C) - At present, there is no functionality built using this attribute. It would be used in the future release of ORMB.

      • Match Type for Default Payment Distribution (D) - Used to indicate the match types for which the system should behave in the following manner:
        PUPL Batch Run Then...
        First
        The system does the following:

        • Processes the first payment record of each payee account and changes the status of the corresponding payment tender staging records to Pending.

        • Does not process the subsequent payment records of each payee account and changes the payment tender staging record status of the subsequent payment records to Ignored.

        Note: Once the three-step PUPL batch cycle is completed, the status of the payment record is changed to Processed or Error in Staging depending on whether it is successfully processed or not. In addition, the status of the corresponding payment tender staging records is changed from Pending to Complete.
      		Yes (Conditional)
      Note: This field is required while defining the settings for an overpayment handling through a match type preference.
      PUPL Batch Run Then...
      Second
      The system does the following:

      • Processes the second payment record of each payee account and changes the status of the corresponding payment tender staging records from Ignored to Pending.

      • Does not process the subsequent payment records of each payee account and the payment tender staging record status of the subsequent payment records remains as Ignored.

      Note: Once the three-step PUPL batch cycle is completed, the status of the payment record is changed to Processed or Error in Staging depending on whether it is successfully processed or not. In addition, the status of the corresponding payment tender staging records is changed from Pending to Complete.
      Note: In each three-step PUPL batch cycle, the system considers and processes one payment record of a payee account at a time and therefore you need to repeat the three-step PUPL batch cycle until all payment records of the payee account are processed.
      • Match Type for Overpayment Distribution (O) - Used to indicate the match types for which the system should behave in the following manner:
        PUPL Batch Run Then...
        First
        The system does the following:

        • Processes the first payment record of each payee account and match value combination and changes the status of the corresponding payment tender staging records to Pending.

        • Does not process the subsequent payment records of each payee account and match value combination and changes the payment tender staging record status of the subsequent payment records to Ignored.

        Note: Once the three-step PUPL batch cycle is completed, the status of the payment record is changed to Processed or Error in Staging depending on whether it is successfully processed or not. In addition, the status of the corresponding payment tender staging records is changed from Pending to Complete.
      PUPL Batch Run Then...
      Second
      The system does the following:

      • Processes the second payment record of each payee account and match value combination and changes the status of the corresponding payment tender staging records from Ignored to Pending.

      • Does not process the subsequent payment records of each payee account and match value combination and the payment tender staging record status of the subsequent payment records remains as Ignored.

      Note: Once the three-step PUPL batch cycle is completed, the status of the payment record is changed to Processed or Error in Staging depending on whether it is successfully processed or not. In addition, the status of the corresponding payment tender staging records is changed from Pending to Complete.
      Note: In each three-step PUPL batch cycle, the system considers and processes one payment record of each payee account and match value combination at a time and therefore you need to repeat the three-step PUPL batch cycle until all payment records of each payee account and match value combination are processed.
      • Match Type for Segment Level Overpayment Distribution (R) - Used to indicate the match types for which the system should behave in the following manner:
        PUPL Batch Run Then...
        First
        The system does the following:

        • Processes all payment records of the same or different payee account with the same or different match value and changes the status of the corresponding payment tender staging records to Pending.

        Note: Once the three-step PUPL batch cycle is completed, the status of the payment record is changed to Processed or Error in Staging depending on whether it is successfully processed or not. In addition, the status of the corresponding payment tender staging records is changed from Pending to Complete.
      Note:

      You can specify maximum of 20 match types separated by a comma (,) symbol for the above attributes in the field mapping.

      Now, while executing the step-three PUPL batch, the system considers the field mapping which is specified in the Field Mapping for Match Type option type of the C1-PAYFLUPLD feature configuration whenever there are multiple payment records of the payee account in the CSV file. In the following scenarios, the system behaves in the manner as if the match type is set to the Match Type Default Payment Distribution (D) attribute:

      • The value for the Field Mapping for Match Type option type is not defined in the C1-PAYFLUPLD feature configuration

      • The value specified for the Field Mapping for Match Type option type in the C1-PAYFLUPLD feature configuration is invalid

      • The match type received in the payment record is not specified against any of the attribute in the referred field mapping

      To implement this change, a new status named Ignored is added in the PAY_​TND_​STG_​ST_​FLG lookup field.
      Value Used to specify the attribute value. Yes (Conditional)
      Note: This field is required while defining the settings for an overpayment handling through a match type preference.
      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 an overpayment handling through a match type preference, you must set at least one attribute in the overpayment handling through a match type preference.
    Tip: Alternatively, you can copy an overpayment handling through a match type preference by clicking the Duplicate button in the Field Mapping zone.
  4. Enter the required details in the Main section.
  5. Define, edit, or remove the attribute from the overpayment handling through a match type preference, if required.
  6. Click Save.
    The new overpayment handling through a match type preference is created.

Related Topics

For more information on... See...
How to search for an overpayment handling through a match type preference Searching for an Overpayment Handling through a Match Type Preference
Field Mapping screen Field Mapping