How To Fix LM359 - Generated table &1 already exists for limit type &2 in client &3

SAP Error Message - Details

• Message type: E = Error

• Message class: LM - Treasury: Limit Management

• Message number: 359

• Message text: Generated table &1 already exists for limit type &2 in client &3

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

First delete the table using report <DS:RE.RFTBLT03>RFTBLT03</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LM359 - Generated table &1 already exists for limit type &2 in client &3 ?

  The SAP error message LM359 indicates that there is an attempt to create a table for a limit type that already exists in the specified client. This typically occurs in the context of limit management, where the system is trying to create a new table for a specific limit type but finds that a table with the same name already exists.
  Cause:
  
  Duplicate Table Creation: The most common cause of this error is that the system is trying to create a limit table that has already been created for the specified limit type in the specified client.
  Configuration Issues: There may be issues in the configuration settings that lead to the system attempting to create a table that should not be created again.
  Data Migration or System Copy: If data has been migrated or if a system copy has been performed, it may lead to existing tables that conflict with new creation attempts.
  
  Solution:
  
  Check Existing Tables: Verify if the table for the specified limit type already exists in the client. You can do this by checking the relevant database tables or using transaction codes like SE11 (Data Dictionary) to look for the table.
  Delete or Modify Existing Table: If the existing table is not needed, you may consider deleting it or modifying it as per your requirements. However, be cautious with this approach as it may lead to data loss.
  Adjust Configuration: Review the configuration settings related to limit management to ensure that the system is not set to create duplicate tables. This may involve checking the customizing settings in the relevant IMG (Implementation Guide) sections.
  Consult Documentation: Refer to SAP documentation or notes related to limit management for any specific instructions or known issues that may relate to this error.
  Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SPRO (Customizing) to navigate through the system and check configurations.
  SAP Notes: Search for SAP Notes related to LM359 for any patches or updates that may address this issue.
  Limit Management: Understanding the context of limit management in SAP can help in troubleshooting and resolving issues related to limit types and their associated tables.
  
  By following these steps, you should be able to identify the cause of the LM359 error and implement a suitable solution.