How To Fix HRPAYDESVA1073 - Address key &1 &2 is not available in the address management (T536C).

HRPAYDESVA1073 - Overview

• Message type: E = Error

• Message class: HRPAYDESVA1 - Message Class for A1 Procedure

• Message number: 073

• Message text: Address key &1 &2 is not available in the address management (T536C).

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.

HRPAYDESVA1073 - Details

• The SAP error message HRPAYDESVA1073 indicates that the address key specified in the error message is not available in the address management table (T536C). This typically occurs in the context of HR (Human Resources) processes, particularly when dealing with employee addresses or related data.
  
  Cause:
  
  Missing Address Data: The address key (which usually consists of a combination of fields like country, postal code, etc.) does not exist in the T536C table. This could be due to data not being maintained or incorrectly entered.
  Data Inconsistency: There may be inconsistencies in the data, such as incorrect entries or missing records that should have been created during data migration or updates.
  
  Configuration Issues: The system may not be properly configured to recognize the address key, possibly due to missing customizing settings.
  
  
  Solution:
  
  Check Address Data: Verify that the address key exists in the T536C table. You can do this by using transaction SE16 or SE16N to view the