How To Fix FKK_TR_ADDR001 - Error for Province &1 in ADRCITY->T005S for partner &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_TR_ADDR - Migration for TR addresses

• Message number: 001

• Message text: Error for Province &1 in ADRCITY->T005S for partner &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 FKK_TR_ADDR001 - Error for Province &1 in ADRCITY->T005S for partner &2 ?

  The SAP error message FKK_TR_ADDR001 typically indicates an issue related to address data for a business partner in the context of the SAP Convergent Charging or Contract Accounts Receivable and Payable (FI-CA) modules. The error specifically points to a problem with the province (or state) information in the address data for a partner.
  Cause:
  The error message suggests that the province (or state) code specified in the address data does not exist in the relevant table (in this case, T005S, which is the table for geographical data). This can occur due to several reasons:
  
  Missing Province Code: The province code entered for the partner does not exist in the T005S table.
  Incorrect Configuration: The configuration for the address data may not be set up correctly, leading to invalid entries.
  Data Migration Issues: If data was migrated from another system, there may have been issues with the province codes not being correctly mapped.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check the Province Code:
  
  Go to transaction code SE16N or SE11 and check the T005S table to see if the province code exists.
  If the province code does not exist, you will need to add it.
  
  
  
  Add Missing Province Code:
  
  If the province code is missing, you can add it using transaction code SPRO:
  
  Navigate to SAP Customizing Implementation Guide > Enterprise Structure > Definition > Logistics - General > Define Countries.
  Here, you can add the missing province code and ensure it is correctly linked to the country.
  
  
  
  
  
  Validate Partner Data:
  
  Check the address data for the partner in question (using transaction code BP for Business Partner) to ensure that all address fields are correctly filled out, including the province/state.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the business partner data to ensure that all required fields are populated correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the error message for any additional guidance or updates.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  BP: Business Partner Maintenance
  SE16N: Data Browser
  SPRO: Customizing Implementation Guide
  
  
  Tables:
  
  T005S: Table for geographical data (country and province/state codes).
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.