!--a11y-->
Change Connection Object in
Premise 
Previously, it was not possible to change the connection object in the Change Premise transaction (ES61) once you had created the premise successfully. This function supports the following business cases:
·
Case 1:
Incorrect allocation of a customer and a device to a connection object within
the initial data creation
You have allocated a customer and his/her premise to the wrong connection
object (for example, in the initial data creation). You only notice this error
once the customer has already been billed.
There can be various reasons for the incorrect allocation:
¡ The customer was specified incorrectly.
¡ Street names and house numbers are only issued once the customer has been maintained.
¡ The owner’s plan was incorrect.
¡ The development plan has been changed.
·
Case 2: Division
of connection object due to change to address
One connection object is divided into two.
For example, a second entrance is built for a building with one entrance, or a
corner house has a second entrance from a different street.
·
Premise |
Previous House Number |
Subsequent House Number |
PR1 |
30 |
30 |
PR2 |
30 |
30 |
PR3 |
30 |
31 |
PR4 |
30 |
31 |

· The following functions are required:
· Change Allocation of Premise to Connection Object
· Change Allocation of Device Location to Connection Object
The Change Allocation of Connection Object to Premise/Device Location/Device function is only possible in the following cases:
· The result of checking the address of the connection objects involved against the regional structure is positive.
· When changing the allocation you can only change the House Number, House Number Supplement, and Name fields in the connection object. The Regional Structure Group, Political Regional Structure, and Maintenance Plant fields must not be changed.
· The regional structure data for the connection objects involved are identical (identical street or street section).
· No technical installation is maintained for the premise.
· No allocation exists to a device location remaining in the old connection object, and a premise that is reallocated, and vice versa.
The address of the contract partner to which the address can be passed on during move-in, is not adjusted automatically. It must be maintained manually later.
If the system automatically generates ship-to parties in SD, you must also adjust the addresses manually.
In case 1 the device, whose location allocation is being changed, must comply with the following conditions:
· It does not belong to a device group.
· There are no register relationships to other devices.
· It is not a controlling or controlled device.
· It is the original device that was installed.
In case 2 the devices installed in the device installations, whose allocations to the higher-level connection object are to be changed, must meet the following conditions:
· There are no register relationships to devices from other device locations.
· There is no allocation to a controlling or controlled device from another device location.
· They are the original devices that were installed.
An installation has been inadvertently installed in the wrong connection object. It is possible to correct this error without canceling the entire operation, and must be executed again for the correct connection object.
This is made possible by using the Change Allocation of Premise/Connection Object and Device/Device Location transaction. This allows you to assign authorization to specific agents and process the operation in one step.
The fields that must be processed – Premise, Connection Object, Connection Object (New), Device Location (Old), Device Location (New), and Device – are all found on one screen.
The input help for the respective change transactions are used for the premise, connection object, and device location. The input help for the Device Replacement transaction is used for the device.
Choose the Reassign button to trigger the allocation changes.
If errors occur during the check, the corresponding messages are displayed in the status line.
The connection object is divided into two connection objects. The premises and devices with the installed devices are to be allocated to a new connection object. This is to be executed without it being necessary to cancel the installed devices, create new premises/device locations, and reinstall the devices.
The fields that must be processed – Connection Object (Old), Connection Object (New), Premise, andDevice Location – are all found on one screen.
