How To Fix OK036 - Internal error in LDB PSJ (&1)

SAP Error Message - Details

• Message type: E = Error

• Message class: OK - Logical database PS

• Message number: 036

• Message text: Internal error in LDB PSJ (&1)

What causes this issue?

During the selection of objects in a project an error occured in the
data retrieval program SAPDBPSJ while it was editing the internal table
&v1&, which lead to a endless loop.

How to fix this error?

Contact SAP

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OK036 - Internal error in LDB PSJ (&1) ?

  The SAP error message OK036, which states "Internal error in LDB PSJ (&1)," typically occurs in the context of using the SAP system for project management or related functionalities. This error is associated with the Logical Database (LDB) PSJ (Project System) and indicates that there is an internal issue that the system encountered while processing a query or report.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies or corruption in the underlying data that the LDB is trying to access.
  Configuration Issues: Incorrect configuration settings in the project system or logical database settings can lead to this error.
  Program Errors: There may be bugs or issues in the ABAP program that is utilizing the LDB.
  Authorization Issues: Lack of proper authorizations for accessing certain data can also trigger this error.
  System Bugs: Sometimes, this error can be due to bugs in the SAP system itself, especially if you are using an older version.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like SE11 to check the database tables related to the project system for inconsistencies. You may also want to run consistency checks.
  Review Configuration: Ensure that the configuration settings for the project system and logical databases are correct. This may involve checking settings in SPRO (SAP Project Reference Object).
  Debugging: If you have access to the ABAP code, you can debug the program that is causing the error to identify the exact point of failure.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the data being queried.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  System Update: If the error is due to a known bug, consider updating your SAP system to the latest version or applying relevant support packages.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE38 (to run reports), SE11 (to view database tables), and SE80 (to access the Object Navigator).
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Documentation: Review SAP documentation related to the Project System and Logical Databases for any specific guidelines or troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.