How To Fix /SRMSMC/ADDRESS012 - Requested address record does not exist: address &1, record &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/ADDRESS -

• Message number: 012

• Message text: Requested address record does not exist: address &1, record &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SRMSMC/ADDRESS012 - Requested address record does not exist: address &1, record &2 ?

  The SAP error message /SRMSMC/ADDRESS012 Requested address record does not exist: address &1, record &2 typically indicates that the system is trying to access an address record that is not available in the database. This can occur in various scenarios, such as when trying to retrieve or manipulate address data in the Supplier Relationship Management (SRM) module or other related areas.
  Cause:
  
  
  Missing Address Record: The address record identified by the specified address ID (&1) and record ID (&2) does not exist in the database. This could be due to:
  
  The record was never created.
  The record was deleted or archived.
  There is a typo or incorrect reference in the code or configuration.
  
  
  
  Data Inconsistency: There may be inconsistencies in the data, such as incorrect links between entities that reference the address.
  
  
  Authorization Issues: The user may not have the necessary permissions to access the address record, leading to the system not being able to retrieve it.
  
  
  Solution:
  
  
  Verify Address Record: Check if the address record exists in the database. You can do this by:
  
  Using transaction codes like BP (Business Partner) or SUI (Supplier User Interface) to search for the address.
  Running relevant reports or queries to see if the address ID and record ID are valid.
  
  
  
  Create or Restore Address Record: If the address record does not exist, you may need to create it or restore it from a backup if it was deleted.
  
  
  Check Configuration: Ensure that the configuration settings related to address management in SRM are correct. This includes checking any custom developments or enhancements that might affect address handling.
  
  
  Review Authorization: Ensure that the user has the necessary authorizations to access the address records. This may involve checking roles and permissions in the user profile.
  
  
  Debugging: If the issue persists, consider debugging the program or transaction that is generating the error to identify where the incorrect reference is being made.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP, SUI, and others that are used for managing business partners and addresses in SAP.
  SAP Notes: Check the SAP Support Portal for any notes or patches related to this error message. There may be known issues or updates that address this specific error.
  Documentation: Review the SAP documentation for SRM and address management to understand the expected behavior and data model.
  
  If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation or to reach out to SAP support for assistance.