Creating Customer Contacts for Each Membership Billed to Delinquent Customer or Account

If you send a debt collection letter to a delinquent customer or account through a delinquency process, you can configure the system to create a customer contact for the main subscriber of each membership which is billed to the delinquent customer or account. The system creates a customer contact for the main subscriber of each membership whenever an event is triggered in the delinquency process to send a debt collection letter.

Two fields named Send Membership Level Notification Source and Send Membership Level Notification field are available when you add a delinquency event type in a delinquency process type. You can set the Send Membership Level Notification Source field to either Delinquency Process Type or Algorithm. If you set the Send Membership Level Notification Source field to Delinquency Process Type, the system derives the value for the Send Membership Level Notification field corresponding to the respective event type from the delinquency process type. However, if you set the Send Membership Level Notification Source field to Algorithm, the system derives the value for the Send Membership Level Notification field from a business rule. To derive the value from the business rule, the system uses the C1-DERMLNBR algorithm attached to the Send Member Level Notification Option Derivation system event in the respective delinquency process type. For more information, see C1-DERMLNBR. Note that these fields are applicable only when the delinquency event is triggered in the delinquency process to send a debt collection letter (such as, warning, dunning, or harsh letters) to the delinquent customer or account.

If the value of the Send Membership Level Notification field is set to Send Membership Level Notification Required either in the delinquency process type or in the business rule depending on the send membership level notification source, the system derives the memberships billed to the delinquent customer or account. It then checks whether the number of memberships derived is less than or equal to the value specified in the Member Level Notification Deferred Processing Threshold parameter of the C1-DLQSENDCC algorithm. If the number of memberships derived is less than or equal to the specified value, the system creates a customer contact for the main subscriber of each derived membership in the real time (i.e. immediately). In addition, the status of the delinquency event is changed to Complete.

However, if no value is defined for the Member Level Notification Deferred Processing Threshold parameter or if the number of memberships derived is greater than the specified value, the system changes the status of the delinquency event to Pending Contact Creation.

The C1-MBRNT batch considers the delinquency processes which have at least one delinquency event in the Pending Contact Creation status. It then derives the memberships billed to the delinquent customer or account and creates a customer contact for the main subscriber of each derived membership.

In addition, this algorithm does the following:

  • Creates a log entry for each customer contact in the delinquency process.

  • Stamps the delinquency process ID as a characteristic using the given characteristic type on the customer contact.

  • Stamps the membership ID as a characteristic using the given characteristic type on the customer contact.

Note: Once a customer contact is created, a record is added in the C1_​DELIN_​PROC_​EVT_​NOTIF table where the DP_​EVT_​NOTIF_​TYPE_​FLG column is set to CC and the DP_​EVT_​NOTIF_​ID column is set to the customer contact ID.

This batch derives the preferred contact method for the customer contact. While deriving the preferred contact method, the batch first fetches the main customer’s bill route type on the account and then fetches the bill routing method of the bill route type. Once the bill routing method is derived, the system considers the preference which is specified in the Routing Method – Contact Method Mapping option type of the DELINPROC feature configuration. For more information about the feature configuration, see Setting the DELINPROC Feature Configuration. It then checks whether any preferred contact method is mapped to the bill routing method in the preference. If the preferred contact method is mapped to the bill routing method in the preference, the system stamps it on the customer contact. However, if the preferred contact method is not mapped to the bill routing method in the preference, the system considers the default contact method as the preferred contact method and stamps it on the customer contact.

This batch is a multi-threaded batch. The multi-threading is based on membership ID and chunks for multi-threading are created based on numerical distribution of membership ID. For more information about the batch, see Oracle Revenue Management and Billing Batch Guide.