Use

This function allows you to reconnect a utility installation when an open item that previously contributed to a disconnection has been cleared.

Features

Event 0020 ( Transfer complete document/clearing (without document number) ) is called when open items that were part of a disconnection are cleared. This event allows additional activities to be executed after the open item has been cleared. You can access all payment document information with the exception of the document number.

When the payment document is created, event 0200 checks if the installation can be reconnected. The system checks whether the paid item has a dunning indicator, and whether a dunning history exists for the item.

If the item is allocated to a contract, the system determines all other open items for this contract. If it is not, the system determines all open items for the corresponding contract account. The system decides whether the open item is relevant for a disconnection i.e. whether a disconnection document is allocated to the item.

Event ISU_CECK_RECONNETION_R720 ( trigger reconnection during clearing ) now determines whether the installation should be reconnected. It does this by calculating the difference between the total amount and the total clearing amounts from the disconnection-relevant items.

If the difference is zero the item relevant for disconnection is cleared, and the reconnection can take place.

The system now reads the disconnection processing variant from the disconnection document header. Since the disconnection document was generated from the dunning program, the variant has the abbreviation DUNN .

The Customizing in the processing variant then tells the system whether the reconnection is contract related or contract account related . If the items are to be proposed contract related, you must set the indicator Cntrt-rel. prop (see also Propose contract-related reconnection .).

If the indicator is set, the system triggers the event disconnection reason obsolete ( Disconnection.DisconReasonObsolete ). This starts the reconnection workflow and completes the clearing of open items.

If the indicator is not set, the system determines all other items relevant for disconnection in the contract account. If the system finds other open items relevant for disconnection, the event trigger reconnection via clearing (ISU_CECK_RECONNETION_R720) is called. This checks whether these items have been cleared and whether the clearing amount is sufficient for reconnection.

If these items have not been cleared, reconnection does not take place, and the event disconnection reason obsolete ( Disconnection.DisconReasonObsolete ) is not triggered.

In both cases, open item clearing is completed.