How To Fix /SAPCND/DB_ACCESS069 - Names of scale tables could not be determined for appl &1 and usage &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 069

• Message text: Names of scale tables could not be determined for appl &1 and usage &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 /SAPCND/DB_ACCESS069 - Names of scale tables could not be determined for appl &1 and usage &2 ?

  The SAP error message /SAPCND/DB_ACCESS069 indicates that the system is unable to determine the names of scale tables for a specific application (&1) and usage (&2). This error typically arises in the context of condition management, particularly when dealing with pricing or condition records in SAP.
  Cause:
  
  Missing Configuration: The scale tables may not be properly configured in the system. This could be due to missing entries in the relevant customizing tables.
  Incorrect Application or Usage: The application or usage specified in the error message may not be valid or may not have been set up correctly in the system.
  Transport Issues: If the configuration was recently transported from another system, there may have been issues during the transport that led to incomplete or missing data.
  Authorization Issues: The user may not have the necessary authorizations to access the scale tables or the relevant configuration.
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the transaction code SPRO and navigate to the relevant area for condition management (e.g., pricing, discounts, etc.).
  Ensure that the scale tables are defined correctly for the specified application and usage.
  Verify that the condition types and access sequences are set up properly.
  
  
  
  Validate Application and Usage:
  
  Confirm that the application (&1) and usage (&2) specified in the error message are valid and correctly configured in the system.
  Check if there are any typos or discrepancies in the application or usage names.
  
  
  
  Review Transport Requests:
  
  If the issue arose after a transport, check the transport logs for any errors or warnings.
  Ensure that all necessary objects were included in the transport request.
  
  
  
  Check Authorizations:
  
  Verify that the user encountering the error has the necessary authorizations to access the relevant condition records and scale tables.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the program or function module that is generating the error to identify the exact point of failure.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message number or keywords in the SAP Support Portal.
  Documentation: Review the SAP documentation related to condition management and scale tables for additional insights and best practices.
  Community Forums: Consider searching or posting in SAP community forums for similar issues and solutions shared by other users.
  
  If the problem continues after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation.