Diagnosis
The extended table maintenance (sm30) uses the (new) Business AddressServices for maintaining customizing object addresses from Release4.0A.
The associated entry in the Business Address Services control tableTSADRV does not exist.
A domain of the old address tables is also used for the address in thistable.

System Response
The extended table maintenance calls the function module of the oldaddress maintenance. This can cause problems.

Procedure

• If the table is part of a customer development which existed before the
upgrade to 4.0, it has not yet been modified for the changes in Release4.0. You can proceed, but you are strongly recommended to perform thesteps described in the address management 4.0A Release notes, so thatthe Business Address Services functions are available to customerdevelopments in the same way as to SAP functions.
The address management Release notes are under Cross-applicationcomponents -> General application functions.

• If the table is part of a new customer development for Release 4.0:

use the Business Address Services domain AD_ADDRNUM for the addressreference.
maintain the table TSADRV with the transaction SM30.
create an entry for Dictionary table &V1&, Dictionary field &V2&.
enter the address group:
A consistent address group in the customer namespace should be used foraddresses of customizing objects not delivered by SAP: use the addressgroup 'ZA01'.
As this address group is in the customer namespace of table TSAD7, theentry 'ZA01' must also be made in table TSAD7 in the customer system:
Key: ZA01
Description: Customizing: Customer object addresses
Direct maint.: not marked
Also create the address group 'ZADE' in the table TSAD7 for addressesof deleted customer objects (if the address of the address group 'ZA01'is still referred to elsewhere when you try to delete a customerobject, the address is not deleted, the address group is changed to'ZADE'):
Key: ZADE
Description: Customizing: Adresses of deleted customer objects
Direct maint: not marked

• If the table is an SAP table this case should not arise in a customer
system. If it does, send a problem message to SAP quoting the number AM291 of this message.
Continuing can lead to inconsistencies.