How To Fix AM290 - Entry missing in TSADRV; new address maintenance cannot be called

SAP Error Message - Details

• Message type: E = Error

• Message class: AM - Business Address Services

• Message number: 290

• Message text: Entry missing in TSADRV; new address maintenance cannot be called

What causes this issue?

The extended table maintenance (sm30) uses the (new) Business Address
Services for maintaining customizing object addresses as of Release
4.0A.
The associated entry in the Business Address Services control table
TSADRV does not exist.
A domain of the old address table is also used for the address in this
table.

System Response

The extended table maintenance calls the old address maintenance
function module. This causes errors in SAP developments.

How to fix this error?

Maintain the table TSADRV with the transaction SM30.
Make an entry for Dictionary table &V1&, Dictionary field &V2&.
Enter the address group:
All SAP customizing objects use the address group'CA01'. Make the
appropriate entry.
If it is a new development, the address number field should also refer
to the Business Address Services (AD_ADDRNUM) domains.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AM290 - Entry missing in TSADRV; new address maintenance cannot be called ?

  The SAP error message AM290 ("Entry missing in TSADRV; new address maintenance cannot be called") typically occurs when there is an attempt to access address maintenance functionality in SAP, but the system cannot find the necessary entries in the table TSADRV. This table is used to store address-related data for various applications in SAP.
  Cause:
  
  Missing Entries: The most common cause of this error is that the required entries for the address maintenance are missing from the TSADRV table. This can happen due to data inconsistencies, incomplete configuration, or if the relevant address data has not been set up properly in the system.
  Custom Development: If there are custom developments or modifications in the system that interact with address maintenance, they might not be correctly configured or might be referencing non-existent entries.
  Transport Issues: If the system has recently undergone a transport of changes, it is possible that the transport did not include the necessary entries for address maintenance.
  
  Solution:
  
  Check TSADRV Table: Use transaction code SE11 (Data Dictionary) to check the contents of the TSADRV table. Ensure that the necessary entries for the address maintenance you are trying to access are present.
  Maintain Entries: If the entries are missing, you may need to create them manually or ensure that the relevant configuration is completed. This might involve setting up address types or other related configurations in the system.
  Review Custom Code: If there are custom developments, review the code to ensure that it is correctly referencing the TSADRV table and that it is not causing the error due to incorrect logic.
  Transport Check: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport. You may need to re-transport the missing entries.
  Consult Documentation: Review SAP documentation or notes related to address maintenance for any specific requirements or configurations that may be necessary.
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SE16 (Data Browser), SE37 (Function Module), and SE80 (Object Navigator) can be useful for troubleshooting.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional guidance.
  Community Forums: SAP Community and other forums can be helpful for finding similar issues faced by other users and their solutions.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to your SAP Basis or technical team for further investigation, as they may have access to additional tools and logs that can help diagnose the issue.