How To Fix LR351 - Data records have not been imported completely, reduce the selection

SAP Error Message - Details

• Message type: E = Error

• Message class: LR - CATS: Cross-Application Time Sheet

• Message number: 351

• Message text: Data records have not been imported completely, reduce the selection

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 LR351 - Data records have not been imported completely, reduce the selection ?

  The SAP error message LR351, which states "Data records have not been imported completely, reduce the selection," typically occurs during the import of data records in the SAP system, particularly when dealing with large datasets. This error indicates that the system is unable to process the entire selection of data records due to various reasons, such as performance limitations or system constraints.
  Causes:
  
  Data Volume: The selection of data records is too large for the system to handle in a single import operation.
  Memory Limitations: The system may be running out of memory or resources to process the data.
  Timeout Settings: The operation may be timing out due to the length of time it takes to process the data.
  Configuration Issues: There may be configuration settings in the system that limit the number of records that can be processed at once.
  
  Solutions:
  
  
  Reduce Data Selection: 
  
  Break down the data import into smaller batches. Instead of importing all records at once, try to limit the selection to a smaller subset of records.
  Use filters to narrow down the data set based on specific criteria (e.g., date ranges, specific categories).
  
  
  
  Increase System Resources:
  
  If possible, increase the memory allocation for the SAP application server or the database server to handle larger data sets.
  Check for any performance bottlenecks in the system and address them.
  
  
  
  Adjust Timeout Settings:
  
  Review and adjust the timeout settings in the SAP system to allow for longer processing times if necessary.
  
  
  
  Check Configuration Settings:
  
  Review the configuration settings related to data imports and ensure they are set appropriately to handle the expected data volume.
  
  
  
  Use Background Processing:
  
  If the import process allows, consider running the import in the background rather than in the foreground to avoid timeouts and resource limitations.
  
  
  
  Consult SAP Documentation:
  
  Refer to SAP documentation or support for specific guidelines related to the transaction or process you are using, as there may be additional recommendations or best practices.
  
  
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may be using specific transaction codes (e.g., LSMW, BAPIs, etc.) for data import.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates that could resolve the issue.
  Performance Monitoring: Utilize SAP performance monitoring tools to identify any underlying issues that may be affecting data processing.
  
  If the problem persists after trying these solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.