How To Fix J-808 - Cannot generate the portfolio hierarchies; table locked by another user


SAP Error Message - Details

  • Message type: E = Error

  • Message class: J- -

  • Message number: 808

  • Message text: Cannot generate the portfolio hierarchies; table locked by another user

  • Show details Hide details


  • 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 J-808 - Cannot generate the portfolio hierarchies; table locked by another user ?

    The SAP error message J-808, which states "Cannot generate the portfolio hierarchies; table locked by another user," typically occurs in the context of SAP Portfolio and Project Management (PPM) when a user attempts to generate or modify portfolio hierarchies while another user has locked the relevant database table.

    Cause:

    1. Table Locking: The error is primarily caused by a table lock, which occurs when another user or process is currently accessing or modifying the same data. This can happen during operations such as creating, updating, or deleting portfolio hierarchies.
    2. Long-Running Transactions: If a transaction takes a long time to complete, it can hold a lock on the table, preventing other users from accessing it.
    3. Concurrent Users: Multiple users trying to access or modify the same data simultaneously can lead to locking issues.

    Solution:

    1. Wait and Retry: The simplest solution is to wait for a few moments and then try to generate the portfolio hierarchies again. The lock may be released once the other user completes their transaction.
    2. Identify the Lock: If the issue persists, you can identify which user or process is holding the lock:
      • Use transaction code SM12 to view and manage locks. This transaction allows you to see the list of locks and the users holding them.
      • If necessary, you can ask the user holding the lock to complete their transaction or release the lock.
    3. Check for Long-Running Transactions: Use transaction code SM66 (Global Work Process Overview) or SM50 (Process Overview) to check for long-running transactions that might be causing the lock.
    4. Contact SAP Basis Team: If you are unable to resolve the issue, it may be necessary to contact your SAP Basis team. They can help investigate the locking issue further and may be able to release the lock if appropriate.
    5. Review Custom Code: If you have custom code that interacts with portfolio hierarchies, review it to ensure it is not causing unnecessary locks.

    Related Information:

    • Lock Management: Understanding how SAP handles locks can help in troubleshooting. SAP uses different types of locks (exclusive, shared) to manage data integrity.
    • Transaction Codes: Familiarize yourself with relevant transaction codes such as:
      • SM12: To view and manage locks.
      • SM50: To monitor active processes.
      • SM66: To monitor global processes.
    • User Training: Ensure that users are trained on how to properly manage their transactions to minimize locking issues.

    By following these steps, you should be able to resolve the J-808 error and successfully generate the portfolio hierarchies in SAP.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant