Use

This function enables you to reconnect an installation when an installment plan is created. When the installment plan is created, the system calls event 3040 ( installment plan is created ). This event allows further processing steps to be carried out after the installment plan has been created.

Features

When you select due, open items in order to created an installment plan, the system checks whether the items have already been dunned. The system determines all dunned items in the corresponding contract account and checks whether the items have triggered a disconnection. Each of the selected, open items is marked as cleared. The total of the clearing amounts corresponds to the total amount of the disconnection-relevant items once all overdue, disconnection-relevant items have been included in the installment plan. 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 all the disconnection-relevant items included in the installment plan are cleared, the criteria for reconnection has been fulfilled.

If an installation can be reconnected, the system reads the disconnection processing variant from the disconnection document header. 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 .).

Once you have specified that the reconnection should be proposed contract-related, the event disconnection obsolete ( Disconnection.DisconReasonObsolete) is triggered for every contract that fulfils the criteria for a reconnection. The event disconnection obsolete then triggers the reconnection.

If you have specified that the reconnection should not be proposed based on contracts, the system checks all contracts in the contract account. If the criteria have not been fulfilled for at least one contract, the system does not trigger the event. If the installation is to be reconnected, all contracts in the contract account must fulfill the criteria for reconnection.

If all contracts are under the disconnection dunning level, the event disconnection obsolete is triggered and the reconnection started.