How To Fix KW755 - No statistical key figures exist with LIS connection

SAP Error Message - Details

• Message type: E = Error

• Message class: KW - CO-ABC Activity-Based Costing

• Message number: 755

• Message text: No statistical key figures exist with LIS connection

What causes this issue?

There are no statistical key figures in controlling area &V1& linked to
the Logistics Information System (LIS).

System Response

Processing is terminated.

How to fix this error?

Go to <DS:TRAN.KK02>master data maintenance</> for statistical key
figures.
Here you can set up the link to the LIS the statistical key figure
refers directly to a key figure from logistics. For example, you could
display the number of purchase orders for a particular material as a
statistical key figure for your object.
You must assign the statistical key figures to the objects you require
(cost centers, cost objects, business processes).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KW755 - No statistical key figures exist with LIS connection ?

  The SAP error message KW755 "No statistical key figures exist with LIS connection" typically occurs in the context of using the Logistics Information System (LIS) in SAP. This error indicates that the system is unable to find any statistical key figures that are required for the operation you are trying to perform, such as reporting or analysis.
  Cause:
  
  Missing Statistical Key Figures: The most common cause of this error is that there are no statistical key figures defined in the system for the relevant period or for the specific characteristics you are trying to analyze.
  Incorrect Configuration: The LIS may not be properly configured to pull the necessary statistical key figures.
  Data Not Updated: The data may not have been updated or loaded into the system, leading to the absence of statistical key figures.
  Selection Criteria: The selection criteria used in the report or transaction may not match any existing statistical key figures.
  
  Solution:
  
  
  Check Statistical Key Figures:
  
  Go to the relevant transaction (e.g., transaction code KSU1 or KSU2) to check if the statistical key figures are defined and active.
  Ensure that the key figures you need are created and assigned to the appropriate cost centers or internal orders.
  
  
  
  Update Data:
  
  If the statistical key figures are missing, you may need to run the relevant data update or extraction process to populate the necessary data.
  Check if the data extraction jobs for LIS are scheduled and running correctly.
  
  
  
  Review Configuration:
  
  Verify the configuration settings in the LIS to ensure that it is set up to include the necessary statistical key figures.
  Check if the LIS is connected to the correct data sources and that the data sources are active.
  
  
  
  Adjust Selection Criteria:
  
  Review the selection criteria you are using in your report or transaction. Make sure they align with the available statistical key figures.
  Try broadening the selection criteria to see if any data can be retrieved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on the LIS and statistical key figures.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSU1 (Create Statistical Key Figure), KSU2 (Change Statistical Key Figure), and KSU3 (Display Statistical Key Figure).
  LIS Configuration: Understanding the configuration of the Logistics Information System can help in troubleshooting issues related to data extraction and reporting.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches.
  
  By following these steps, you should be able to identify the cause of the KW755 error and implement a solution to resolve it.