How To Fix SCPR743 - Data records for table/view &1 are only read in the logon language

SCPR743 - Overview

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 743

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

What causes this issue?

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

System Response

When you save the BC Set, the missing languages are read from the
tables, according to the user settings (see Utilities -> User Settings
in the BC Set maintenance transaction SCPR3), and put in the BC Set.
Only the languages specified in your user settings are put in the BC
Set. You can change the language selection a BC Set transaction under
"Utilities -> User Settings".

How to fix this error?

Create the BC Set and check the languages in it, in the BC Set overall
view, under "BC Set" -> "Print...", in the BC Set maintenance
transaction SCPR3.

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 SCPR743 - Data records for table/view &1 are only read in the logon language ?

  The SAP error message SCPR743 indicates that data records for a specific table or view (denoted by &1) are only available in the logon language of the user. This typically occurs when the data in the specified table or view has not been translated into the user's logon language, leading to the inability to display or process the data correctly.
  
  Cause:
  
  Language-Specific Data: The data in the specified table or view is maintained only in the logon language and not in other languages. This is common in scenarios where translations for certain fields or records have not been provided.
  Missing Translations: The relevant entries in the database may not have been translated into the user's logon language, which can happen if the data was entered in a different language or if the translation process was not completed.
  
  
  Solution:
  
  Check Data Availability: Verify if the data exists in the logon language. You can do this by