How To Fix WS565 - No data is updated to LIS but data is transferred to SAP BW

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 565

• Message text: No data is updated to LIS but data is transferred to SAP BW

What causes this issue?

No info structures for event &V1& are active in the Logistics
Information System.
There is also no transfer of data to subsequent settlement (event &V2&,
only supplier billing documents, settlement documents, customer
settlements).
The communication structures are, however, transferred to SAP Business
Information Warehouse.

System Response

No simulation data could be displayed.

How to fix this error?

This transaction can only simulate updates to the Logistics Information
System.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS565 - No data is updated to LIS but data is transferred to SAP BW ?

  Certainly! Here's a detailed explanation regarding the SAP error message WS565: No data is updated to LIS but data is transferred to SAP BW:
  
  Error Message:
  WS565: No data is updated to LIS but data is transferred to SAP BW
  
  Context:
  
  This message typically occurs in the context of Logistics Information System (LIS) and SAP BW (Business Warehouse) data transfer.
  It indicates that while data has been successfully transferred to SAP BW, no data has been updated or written into the LIS tables.
  LIS is an older SAP reporting system that collects and stores logistics data for reporting purposes.
  SAP BW is a more advanced data warehousing and reporting system.
  
  
  Cause:
  
  
  Data Transfer Process:
  
  The data extraction and transfer to SAP BW (via delta or full load) has been successful.
  However, the update to LIS tables (usually in the SAP ERP system) did not happen.
  
  
  
  Possible Reasons:
  
  LIS update is switched off or not active: The LIS update might be deactivated in the system or for the specific data source.
  No relevant data for LIS update: The data transferred to BW might not meet the criteria for LIS update, so no records are written.
  Incorrect or missing LIS update configuration: The LIS update might not be properly configured for the data source or info structure.
  Authorization or system errors: The user or background job performing the update might lack necessary authorizations.
  Technical issues: Issues like missing or inconsistent master data, or errors in the update routines.
  Data already updated: The data might have been already updated in LIS, so no new update is necessary.
  
  
  
  
  Solution / Troubleshooting Steps:
  
  
  Check LIS Update Activation:
  
  Verify if the LIS update is active for the relevant data source.
  Use transaction LBWG (LIS Update Control) to check and activate LIS update for the relevant data source and info structure.
  
  
  
  Check Info Structure and Update Rules:
  
  Ensure that the info structure is correctly defined and active.
  Check the update rules and filters to confirm that data should be updated.
  
  
  
  Check Data Consistency:
  
  Verify that the data being transferred contains records that meet the LIS update criteria.
  Check if the data is already present in LIS tables.
  
  
  
  Review Logs and Dumps:
  
  Check the update logs in transaction LBWG or SM13 (update requests) for errors.
  Look for any short dumps (transaction ST22) related to LIS update.
  
  
  
  Authorization Check:
  
  Ensure the user or background job has the necessary authorizations to update LIS tables.
  
  
  
  Re-run or Schedule Update:
  
  If the LIS update was inactive or failed, activate and re-run the update.
  Use transaction LBWG or relevant batch jobs to trigger LIS update.
  
  
  
  Check SAP Notes:
  
  Search for SAP Notes related to WS565 for any known bugs or patches.
  
  
  
  
  Additional Information:
  
  
  LIS vs BW:
  
  SAP BW is often used as a replacement for LIS, so in many systems, LIS update might be deactivated intentionally.
  If your organization is moving towards BW reporting, LIS update might be obsolete.
  
  
  
  Message Severity:
  
  WS565 is usually a warning/info message, not an error that stops processing.
  It informs that LIS tables were not updated, but BW data transfer succeeded.
  
  
  
  Transaction Codes:
  
  LBWG - LIS Update Control
  SM13 - Update Requests
  ST22 - ABAP Dumps
  RSA3 - Extractor Checker (to check data extraction)
  
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  LIS update not active or no data meets LIS update criteria, though BW transfer succeeded
  
  
  Effect
  No data updated in LIS tables, but data available in BW
  
  
  Solution
  Activate LIS update, check info structures, verify data and authorizations, re-run update
  
  
  Additional
  Often harmless if LIS is not used; check if LIS update is required in your system
  
  
  
  
  If you want, I can help you with specific transaction steps or debugging based on your system setup.