How To Fix ME835 - Address '&1' in field EKPO-ADRNR does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: ME - Purchasing: General Messages

• Message number: 835

• Message text: Address '&1' in field EKPO-ADRNR does not exist

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 ME835 - Address '&1' in field EKPO-ADRNR does not exist ?

  The SAP error message ME835 indicates that there is an issue with the address number (ADRNR) in the purchasing document item (EKPO). Specifically, it means that the address number specified in the field EKPO-ADRNR does not exist in the address database.
  Cause:
  
  Missing Address Record: The address number referenced in the purchasing document does not exist in the address table (usually ADRC).
  Incorrect Address Assignment: The address number may have been incorrectly assigned or entered in the purchasing document.
  Data Deletion: The address record might have been deleted or not created properly.
  Data Migration Issues: If data was migrated from another system, there may have been issues in transferring address records.
  
  Solution:
  
  
  Check Address Record:
  
  Use transaction code SE16N or SE11 to check the address table (ADRC) for the existence of the address number.
  If the address does not exist, you may need to create it.
  
  
  
  Correct the Purchasing Document:
  
  If the address number is incorrect, you can update the purchasing document with a valid address number.
  Use transaction code ME22N to change the purchasing document and enter a valid address.
  
  
  
  Create Missing Address:
  
  If the address is indeed missing, you can create a new address record using transaction code BP (Business Partner) or SU01 (User Maintenance) depending on your system configuration.
  
  
  
  Check for Data Consistency:
  
  Ensure that the data in the purchasing document is consistent and that all required fields are filled out correctly.
  
  
  
  Consult with Technical Team:
  
  If the issue persists, consult with your SAP technical team to check for any underlying issues in the database or data integrity.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  ME22N: Change Purchase Order
  SE16N: Data Browser
  BP: Business Partner
  SU01: User Maintenance
  
  
  
  Tables:
  
  EKPO: Purchasing Document Item
  ADRC: Address Data
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  
  By following these steps, you should be able to resolve the ME835 error and ensure that the address information in your purchasing documents is accurate and complete.