How To Fix /PMG/GE_ENH117 - No change log determined; input Base Journal ID does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /PMG/GE_ENH -

• Message number: 117

• Message text: No change log determined; input Base Journal ID does not exist

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 /PMG/GE_ENH117 - No change log determined; input Base Journal ID does not exist ?

  The SAP error message /PMG/GE_ENH117 No change log determined; input Base Journal ID does not exist typically occurs in the context of the SAP system when dealing with change logs or journal entries, particularly in the context of the SAP Project Management (PM) or similar modules.
  Cause:
  
  
  Non-Existent Journal ID: The error indicates that the system is unable to find a change log for the specified Base Journal ID. This could be due to:
  
  The Base Journal ID provided does not exist in the database.
  The journal entry has been deleted or is not yet created.
  There may be a typo or incorrect ID being used in the input.
  
  
  
  Data Consistency Issues: There might be inconsistencies in the database or issues with the data migration process that led to the journal ID not being properly recorded.
  
  
  Authorization Issues: The user may not have the necessary permissions to access the change log for the specified journal ID.
  
  
  Solution:
  
  
  Verify Journal ID: Check the Base Journal ID you are using. Ensure that it is correct and exists in the system. You can do this by querying the relevant tables or using transaction codes that allow you to view journal entries.
  
  
  Check Change Logs: If you have access, check the change log tables to see if there are any entries related to the Base Journal ID. This can help determine if the ID is valid and if there are any logs associated with it.
  
  
  Data Integrity Check: If you suspect data integrity issues, you may need to run consistency checks or consult with your SAP Basis team to ensure that the database is in a healthy state.
  
  
  User Authorization: Ensure that the user has the necessary authorizations to access the change logs. You may need to consult with your SAP security team to verify and adjust user roles if necessary.
  
  
  Consult Documentation: Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for further assistance. Provide them with detailed information about the error, including the context in which it occurs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help you view journal entries and change logs, such as FB03 (Display Document) or S_ALR_87012357 (Change Log Report).
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal, as there may be specific fixes or recommendations provided by SAP.
  Change Log Tables: Understand the structure of the change log tables in your SAP system, as this can help in troubleshooting and verifying the existence of the journal ID.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.