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

/PMG/GE_ENH117 - Overview

• 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.

/PMG/GE_ENH117 - Details

• 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