How To Fix SCPR339 - Data records of table/view &1 only read in logon language

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 339

• Message text: Data records of table/view &1 only read in logon language

What causes this issue?

When you read data records from a transport request, language-dependent
data records are only read in the current system logon language.

System Response

The data records of table/view &V1& are only read in the logon
language.

How to fix this error?

Save the BC Set.
When you save the BC Set, the missing languages are read from the
tables and put in the BC Set.
Only the languages which you specified in your user settings are
recorded in the BC Set. You can change the language selection in the
"Utilities -> User Settings" menu in one of the BC Set transactions.

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 SCPR339 - Data records of table/view &1 only read in logon language ?

  The SAP error message SCPR339 indicates that data records of a specific table or view (denoted by &1) are only being read in the logon language of the user. This typically occurs when the system is trying to access data that is language-dependent, and the data is not available in the language that the user is currently logged in with.
  Cause:
  
  Language Dependency: The data in the specified table or view is stored in a specific language, and the system is unable to find the corresponding entries in the user's logon language.
  Missing Translations: The translations for the data in the required language may not have been maintained in the system.
  Configuration Issues: There may be configuration settings that restrict the visibility of data based on language.
  
  Solution:
  
  Check Data Availability: Verify if the data exists in the required language. You can do this by checking the relevant table or view directly in the database.
  Maintain Translations: If the data is missing in the user's logon language, you may need to maintain the translations for that data. This can typically be done through transaction codes like SE63 (for translation) or directly in the relevant customizing settings.
  Change Logon Language: If possible, log in with a different language that has the required data available. This is a temporary workaround and may not be feasible for all users.
  Review Configuration: Check the configuration settings related to language handling in your SAP system. Ensure that the necessary settings are in place to allow for multilingual data access.
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SE63 (Translation), SE78 (SAPScript Forms), and SE80 (Object Navigator) can be useful for checking and maintaining data.
  Language Settings: Review the language settings in your user profile and the system settings to ensure they are correctly configured.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling language-dependent data.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation and resolution.