A new batch control named C1-ADMON is introducedin this release. It considers all the parent customers where the advancedeposit level is set to PG or POLI. For a parent customer where advance deposit level is set to PG, the batch checks whether any customer contact iscreated using the given customer contact type for the given customercontact class where the respective person ID is stored as a characteristicon the customer contact. The system considers the characteristic typewhich is specified in the Person ID Characteristic forInbound Log option type of the C1-ASOBLLNG feature configuration. If a customer contact exists for the parentcustomer, the batch does not consider the parent customer for furtherprocessing.
However, if a customer contact does not exist for the parent customer,the batch derives the advance deposit amount and advance deposit gracedays from the parent customer level. It then calculates the graceend date and checks whether the grace end date is earlier than orequal to batch business date. If so, the system derives the advancedeposit account relationship type and advance deposit contract typefrom the delinquency process preference. The system then derives theparent customer's advance deposit account and advance deposit contractusing the advance deposit account relationship type and advance depositcontract type, respectively. The batch then checks whether the paymentsreceived against the advance deposit contract exceeds the advancedeposit amount. If the sum of payments does not exceed the advancedeposit amount, the system creates a customer contact using the givencustomer contact type for the given customer contact class. In addition,the system considers the characteristic type that is specified inthe Person ID Characteristic for Inbound Log option type of the C1-ASOBLLNG feature configurationand then stamps the person ID using the respective characteristictype on the customer contact.
However, if the grace end date is later than the batch businessdate or if the sum of payments exceeds the advance deposit amount,the system does not consider the parent customer for further processing.
Similarly, for a parent customer where advance deposit level isset to POLI, this batch fetches all the policieswhere the parent customer is the policy holder and where the advancedeposit applicability is set to Y. The systemconsiders those polices where the parent customer is associated usingthe policy person role that is specified in the ParentCustomer Policy Person Role option type of the C1-ASOBLLNG feature configuration.
For each such policy, this batch checks whether any customer contactis created using the given customer contact type for the given customercontact class where the respective policy ID is stored as a characteristicon the customer contact. The system considers the characteristic typewhich is specified in the Policy Characteristic Type forCustomer Contact attribute of the delinquency processpreference. If a customer contact exists for the policy, the batchdoes not consider the policy for further processing.
However, if a customer contact does not exist for the policy, thebatch derives the advance deposit amount and advance deposit gracedays from the policy. It then calculates the grace end date and checkswhether the grace end date is earlier than or equal to batch businessdate. If so, the system derives the advance deposit account linkedto the policy and the advance deposit contract using the advance depositcontract type specified in the delinquency process preference. Thebatch then checks whether the payments received against the advancedeposit contract exceeds the advance deposit amount. If the sum ofpayments does not exceed the advance deposit amount, the system createsa customer contact using the given customer contact type for the givencustomer contact class. In addition, the system considers the characteristictype that is specified in the Policy Characteristic Typefor Customer Contact attribute of the delinquency processpreference and then stamps the policy ID using the respective characteristictype on the customer contact.
However, if the grace end date is later than the batch businessdate or if the sum of payments exceeds the advance deposit amount,the system does not consider the policy for further processing.
Note: The system considers the delinquency process preference whichis specified in the Delinquency Process Field Mapping option type of the DELINPROC feature configuration.For more information about the feature configuration, see Setting the DELINPROC Feature Configuration.
This batch also derives the preferred contact method for the customercontact. While deriving the preferred contact method, the batch firstfetches the main customer's bill route type on the advance depositaccount and then fetches the bill routing method of the bill routetype. Once the bill routing method is derived, this batch considersthe preference which is specified in the Routing Method- Contact Method Mapping option type of the DELINPROC feature configuration. For more informationabout the feature configuration, see Setting the DELINPROC Feature Configuration.
It then checks whether any preferred contact method is mapped tothe bill routing method in the preference. If the preferred contactmethod is mapped to the bill routing method in the preference, thesystem stamps it on the customer contact. However, if the preferredcontact method is not mapped to the bill routing method in the preference,the system considers the default contact method as the preferred contactmethod and stamps it on the customer contact.
This batch is a multi-threaded batch. The multi-threading is basedon person ID and chunks for multi-threading are created based on numericaldistribution of person ID. You can specify the following parameterswhile executing this batch:
| Parameter Name | Mandatory (Yesor No) | Description |
|---|---|---|
| Customer ContactType | Yes | Used to indicatethe customer contact type using which you want to create the customercontact. Note: You must specify a customer contact type with the appropriateletter template depending on the type of letter you want to send tothe customer. |
| Customer ContactClass | Yes | Used to indicatethe customer contact class to which the customer contact type belongs. |
| Default ContactMethod | Yes | Used to indicatethe contact method that you want to use when the preferred contactmethod cannot be derived for the routing method from the preference. |
| Chunk Size | Yes | Used to specifythe number of persons you want to process in each work unit. |
| Thread PoolName | No | Used to specifythe thread pool on which you want to execute the batch. |
